Print

[kero]

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?

[DMAddict]

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.

[Swizzy]

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

[Joshff]

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

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

I meant people that have them

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

[warbeast]

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

[xerogravity21]

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??

[warbeast]

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?

[DEDDOA]

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).

[xerogravity21]

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).

[warbeast]

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....

[xerogravity21]

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.

[warbeast]

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

[xerogravity21]

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

[xerogravity21]

QUOTE(krizalid @ Feb 24 2012, 01:06 AM)

so... the solution is to copy the _retail.ini from original xeBuild 1.01 Release, replace with the one in this app and also add the 14717_bls so that they properly build?

Thanks in advance.

yep worked for me.

[krizalid]

Thanks and I found a bug....

launch.ini is not being included in the nand.bin output. I have not tested with all posibilities, only on the following:

- Trinity, Glitch Image
- Yes I have checked the options to include dashlaunch and custom settings.

Note: launch.xex and lhelper.xex do get added, except the launch.ini