Jump to content


Photo

xeBuild GUI v2.0 FINAL


  • Please log in to reply
23 replies to this topic

#1 Xbox-Scene

Xbox-Scene

    Memba Numero Uno

  • Admin
  • 5,201 posts
  • Location:Yurop
  • Xbox Version:unk
  • 360 version:unknown

Posted 22 February 2012 - 04:55 AM

xeBuild GUI v2.0 FINAL
Posted by XanTium | February 21 22:55 EST | News Category: Xbox360
 
Swizzy released a new version of his GUI for xeBuild.

What's new/fixed:
- Fixed: There was a minor error with my new Fuse parsing, in some cases it would skip some 0's not anymore ;)
- Changed: You can now select seperate names for bin/ecc, previous configurations can still be loaded (and will be checked if it's .bin or .ecc and write the names into the appropiate place)
- Added: Failsafe for motherboard choices, if you select a motherboard that doesn't match the suggestion from the app it'll warn you about it, and ask if you want to correct it (use suggestion) or if you want to continue...
** NOTE: If it cannot determine what motherboard to suggest it'll just ignore it as it can't really check anything ;) **
- Added: Failsafe for image type, it'll check if ecc/glitch/freeboot is the appropiate image type for your motherboard (based on CB) if it can't check it'll ignore it (same as motherboard)
- Fixed: The app no longer tells you that the input is to short whiles you are writing the cpukey...
- Fixed: The app can now build retail images even if you don't have a SMC.bin file in the root directory of the app :)
- Fixed: The app no longer includes Dashlaunch when NOT building Glitch/JTAG images...
- Added: You now have a option to use Current SMC (meaning the app will not replace it, useful if you don't know what you should use or just don't want to replace it)
** NOTE: You'll need to select Current/Retail SMC if your SMC is patched, otherwise it won't work... **
- Changed: Building Retail/Devkit images now also requires you to choose Current/Retail SMC in order to be valid
- Fixed: The app no longer crashes when trying to download an invalid link (it'll tell you there was an error whiles trying to initalize the download)
- Fixed: If your download fails when downloading dashfiles the app will no longer try to install after download (as it has failed!)
- Changed: The app now uses Dashlaunch 2.30
- Added: New options available since Dashlaunch 2.30 :)
- Changed: The app now includes files for creating 2.0.14717.0
- Changed: The app now uses xeBuild 1.01 along with all of the new patches...
- Fixed: Minor bugs a little bit here and there, none really fatal/worth mentioning (most are basicly things i missed adding in for certain parts of the automation stuff)
- Added: Xell Failsafe, it'll automatically change Xell to Xell-reloaded if you've selected custom and it cannot find the file, it'll also do the same if you've previously selected JTAG type (unlocking Xell and Xellous) and having it fixed to Glitch type
- Added: SMC Failsafe when selecting JTAG (Freeboot), this will ask you what SMC you want to use, if you select JTAG (Freeboot) first then change it during earlier failsafes it'll set it to current automatically... (this feature also allows you to change the settings by spamming you with questions untill you answer yes to any question...)
- Changed: The app now uses Xell-Reloaded built 2012-02-19 (v0.991)

Official Site: n/a, by Swizzy
Download: n/a (might be illegal under DMCA/EUCD)
News-Source: xbins.org | xbox-360.logic-sunrise.com






#2 kero

kero

    X-S Member

  • Members
  • Pip
  • 103 posts
  • Xbox Version:v1.6b
  • 360 version:v1 (xenon)

Posted 22 February 2012 - 06:18 AM

Ive never used the Xell-Reloaded option before. Ive always just stuck with Xell when updating my nand.

When updating; if i use the 'Xell-Reloaded' option when creating my image can i just use flash360 to flash the new updflash file to my box like i normally do?

Or is there a different procedure when updating and changing to a Xell-Reloaded based nand?

#3 DMAddict

DMAddict

    X-S Expert

  • Members
  • PipPipPip
  • 678 posts
  • Location:Tetraspace
  • Xbox Version:v1.0
  • 360 version:v4.0 (jasper)

Posted 22 February 2012 - 07:47 AM

QUOTE(kero @ Feb 21 2012, 09:18 PM)  


When updating; if i use the 'Xell-Reloaded' option when creating my image can i just use flash360 to flash the new updflash file to my box like i normally do?


Flash360 works fine when using Xell-Reloaded. Same process.

#4 Joshff

Joshff

    X-S Enthusiast

  • Members
  • 17 posts

Posted 22 February 2012 - 06:53 PM

Has anyone succesfully created a devkit image for a jtag console?

#5 Swizzy

Swizzy

    X-S Young Member

  • Members
  • Pip
  • 46 posts
  • Location:Sweden
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 22 February 2012 - 09:16 PM

QUOTE(Joshff @ Feb 22 2012, 06:53 PM)  

Has anyone succesfully created a devkit image for a jtag console?


Doing this requires specific files and patches that aren't included, so no wink.gif

#6 Joshff

Joshff

    X-S Enthusiast

  • Members
  • 17 posts

Posted 22 February 2012 - 11:02 PM

QUOTE(Swizzy @ Feb 22 2012, 10:16 PM)  

Doing this requires specific files and patches that aren't included, so no wink.gif


I meant people that have them smile.gif

I want so badly to convert my jtag to a devkit so I can start porting some stuff that the waiting is killing me sad.gif

#7 warbeast

warbeast

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,170 posts

Posted 22 February 2012 - 11:22 PM

just to point out for anyone like me that has messed up there 14717 trinity retail nand and is trying to build another this gui is using the wrong retail.ini witch will result in a non working retail image it shows as
cba_9188.bin,5a76752d
cbb_9188.bin,febb1074
cd_9452.bin,455fa02c
ce_1888.bin,ff9b60df
cf_14717.bin,2d73039a
cg_14717.bin,cf74e2b4

and should be
cba_9230.bin,0483216e
cbb_9230.bin,c2c95118
cd_9230.bin,1d800cf0
ce_1888.bin,ff9b60df
cf_14717.bin,2d73039a
cg_14717.bin,cf74e2b4

once you correct it xebuild will complain that its missing the cbx_9230.bin files so you will need to find them to add ive just read there up in the usual place now under kernal/rebooter_fsdata/14717_bls.zip



#8 xerogravity21

xerogravity21

    X-S Enthusiast

  • Members
  • 7 posts

Posted 23 February 2012 - 03:31 AM

I also messed up my 14717 falcon retail nand and tried generating a new retail image using this gui however it is not working when flashed. Do you know if the retail.ini is correct for the falcon??

#9 warbeast

warbeast

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,170 posts

Posted 23 February 2012 - 04:38 AM

QUOTE(xerogravity21 @ Feb 23 2012, 03:31 AM)  

I also messed up my 14717 falcon retail nand and tried generating a new retail image using this gui however it is not working when flashed. Do you know if the retail.ini is correct for the falcon??


looks like it is to me are you sure the ldv didnt change and have u put a switch on the glitch chip 3.3v so that it can boot stock?

#10 DEDDOA

DEDDOA

    X-S Enthusiast

  • Members
  • 8 posts

Posted 23 February 2012 - 01:44 PM

I don't know if it was this or the new update, but after many tries on previous firmware, my Falcon that was was stuck on XBR3 that would E79 and christmas lights on Freeboot, has now updated and is fully working.

All I did was made a clean falcon nand with JTAG Tool, Used xeBuild to make the Freeboot nand (no to use current SMC, no to use old SMC hack, the yes to using the aud clamp hack as thats the wiring I have) , then used JTAG tool to remap the damaged blocks and USB flash my 360.

Works like a dream now, so maybe an added bonus for those like myself who had a JTAG falcon that was playing silly buggers (after searching the forums I know there are a fair few who do).

Edited by DEDDOA, 23 February 2012 - 01:48 PM.


#11 xerogravity21

xerogravity21

    X-S Enthusiast

  • Members
  • 7 posts

Posted 23 February 2012 - 01:59 PM

QUOTE(warbeast @ Feb 23 2012, 03:38 AM)  

looks like it is to me are you sure the ldv didnt change and have u put a switch on the glitch chip 3.3v so that it can boot stock?


well i wanted to go on live so i put retail 14699 nand back on and when i went on live it asked me to update which i did to 14717 not knowing that it blocked glitched consoles. Once the update completed the console rebooted however would not turn back on as glitch chip was connected. I then tried reverting back to 14699 however this would not boot either (as cant go back to previous kernel). So now i am trying to rebuild a retail 14717 image using this gui however when i did this it would not boot (I disconnected the 3.3 from glitch chip prior to trying this).

#12 warbeast

warbeast

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,170 posts

Posted 23 February 2012 - 02:08 PM

QUOTE(xerogravity21 @ Feb 23 2012, 01:59 PM)  

well i wanted to go on live so i put retail 14699 nand back on and when i went on live it asked me to update which i did to 14717 not knowing that it blocked glitched consoles. Once the update completed the console rebooted however would not turn back on as glitch chip was connected. I then tried reverting back to 14699 however this would not boot either (as cant go back to previous kernel). So now i am trying to rebuild a retail 14717 image using this gui however when i did this it would not boot (I disconnected the 3.3 from glitch chip prior to trying this).


what you said above is the same that happend to my trinity i also erased my nand after flashing back 13699 when 14717 wouldnt boot

but my ldv never increased its still on ldv6 the same as when it was on retail 13699 however the update did still block the glitch as my 13699 freeboot no longer works but 14717 using ldv6 does

this is odd to me as i thought the updates dont change the cb untill it completes a good update showing a higher ldv this is why jtag uses remove efuse resistor so that a update will fail and keep the exploit but in this case if i was using a jtag with efuse resistor removed it still would have blocked the exploit....


#13 xerogravity21

xerogravity21

    X-S Enthusiast

  • Members
  • 7 posts

Posted 23 February 2012 - 04:02 PM

QUOTE(warbeast @ Feb 23 2012, 01:08 PM)  

what you said above is the same that happend to my trinity i also erased my nand after flashing back 13699 when 14717 wouldnt boot

but my ldv never increased its still on ldv6 the same as when it was on retail 13699 however the update did still block the glitch as my 13699 freeboot no longer works but 14717 using ldv6 does

this is odd to me as i thought the updates dont change the cb untill it completes a good update showing a higher ldv this is why jtag uses remove efuse resistor so that a update will fail and keep the exploit but in this case if i was using a jtag with efuse resistor removed it still would have blocked the exploit....


If thats the case then my ldv should not have changed.i will try creating a new 14717 retail again other than that i dont know why it isnt working.

#14 warbeast

warbeast

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,170 posts

Posted 23 February 2012 - 04:49 PM

QUOTE(xerogravity21 @ Feb 23 2012, 04:02 PM)  

If thats the case then my ldv should not have changed.i will try creating a new 14717 retail again other than that i dont know why it isnt working.


hopefully that should fix it! the ldv doesnt increase untill the update has been comfirmed this is why i never took a backup of the failed 14717 as to me the ldv hadnt changed so no reason why i couldnt go back and start again from 13699 but i was wrong if this is correct then removing the efuse resistor now on a jtag will do nothing other then brick ur 360 aswell and stop the exploit if you update by mistake

#15 xerogravity21

xerogravity21

    X-S Enthusiast

  • Members
  • 7 posts

Posted 23 February 2012 - 09:05 PM

QUOTE(warbeast @ Feb 23 2012, 03:49 PM)  

hopefully that should fix it! the ldv doesnt increase untill the update has been comfirmed this is why i never took a backup of the failed 14717 as to me the ldv hadnt changed so no reason why i couldnt go back and start again from 13699 but i was wrong if this is correct then removing the efuse resistor now on a jtag will do nothing other then brick ur 360 aswell and stop the exploit if you update by mistake


Well I tried again and eventually got it working. Like with the trinity the _retail.ini file is also incorrect for the falcon. You were right about about the ldv not changing.

This is what it is

[falconbl]
cb_5771.bin,859140f0
none,00000000
cd_8453.bin,25e0acd0
ce_1888.bin,ff9b60df
cf_14717.bin,2d73039a
cg_14717.bin,cf74e2b4

while it should be

[falconbl]
cba_5773.bin,b8849c79
cbb_5773.bin,4ee83ea3
cd_5773.bin,4fccf593
ce_1888.bin,ff9b60df
cf_14717.bin,2d73039a
cg_14717.bin,cf74e2b4

Got the xxx_5773.bin files from 14717_bls.zip. The new version of 360 Multi Builder v0.8 by Rogero has the correct _retail.ini however is still missing the xxx_5773.bin files.

Thanks for the help




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users