strange prob with freeboot i have bad block at 6 and 2f5 i can install xbr and return to orig but if i flash freeboot then copy out 6 and 2f5 from freeboot image then send to 3ff and 3fe as with xbr just boots to black screen then rrod? tried making freeboot with bad block orig image and block corrected image and no luck this is n ot my first jtag have done others with bad blocks with no prob at all just man sent blocks after flash with nand pro but no go with this 1. the console is xenon with nand x fitted on 7173 cb 1903 any help???
xenon help
- Thread starter craigj172
- Start date
big_ted
VIP Member
you need to make fix original dump with the bad blocks moved from the reserved area back to the image in your case 3ff and 3fe need to go back to 6 and 2f5, then you can make your freeboot image using the "fixed original dump"
once you have made the freeboot image you need to remap the bad blocks back to the reserved area.
hope that made sense.
Ted
once you have made the freeboot image you need to remap the bad blocks back to the reserved area.
hope that made sense.
Ted
just tried that and same result. just to make sure i flashed back to xbr and booted xellous to check cpukey and its correct its very strange think it is because the bad block 6 is in the first 50 blocks but i dont see why if i copy out the 6 and 2f5 and upload to 3ff and 3fe it should work?
big_ted
VIP Member
The image needed to make the freeboot needs to be complete with no bad blocks (ideally)
you to make the (original) dump you are using to make freeboot have no bad blocks,
copy the bad blocks from reserved area to the image, (3ff & 3fe to 6 & 2f5)
then make freeboot then copy the bad blocks back to the reserved area in the freeboot image.
no reason for it not to work then.
Ted
you to make the (original) dump you are using to make freeboot have no bad blocks,
copy the bad blocks from reserved area to the image, (3ff & 3fe to 6 & 2f5)
then make freeboot then copy the bad blocks back to the reserved area in the freeboot image.
no reason for it not to work then.
Ted
Well remapped orig dump to have no bad blocks made freeboot image flashed to xbox rrod, remapped freeboot to match have bad blocks at 6 and 2f5 moved to 3ff and 3fe flashed back and still no go? flashed to orig and works, flashed to xbr and works??????
- Jun 4, 2010
- 3,080
- 0
tried both 1st as is then with the 6 and 2f5 extracted using nandpro (nandpro freeboot: -r16 fix6.bin 6 1 then nandpro usb: -w16 fix6.bin 3ff 1) same with 2f5 but nothing but rrod flashed back to xbr works fine i think that freeboot just cant handle bad blocks below 50 it must not jump to 3ff as xbr or orig nand would it wont boot xell with freeboot image but boots in to xellous with eject every time with xbr shame cos i really wanted freeboot as xbr will no longer be updated?
its really bugging me cos i have done other jtag with bad blocks and just resent the blocks after flash with nandpro working back from 3ff and all worked fine but trust me to have a bad block in 1st 50 on my own xbox lol.
- Jun 4, 2010
- 3,080
- 0
Did you try the 2nd freeboot image I emailed you? Don't remap the 2nd one cause it's already remapped!!!
its looking like freeboot cant work with a bad block at 6 even if it is remaped. is there any way to use the 1st 50 blocks from the xbr image?
- Jun 4, 2010
- 3,080
- 0
I will construct a final Freeboot image from scratch manually as a last resort and see what that does.
worth a try when i flash xell to the box i have to remap block 6 but it works fine so thats why i think the problem is with freeboot not looking in 3ff for the missing block at 6
- Jun 4, 2010
- 3,080
- 0
The xell part in your first freeboot works fine even when not remapped. If you try the first freeboot I sent you and power the console with the eject button and leave the disc tray open you should get xell screen. And as stated that one isn't remapped.
no luck still just boots to black screen then 20 sec later rrod but if i flash orig or xbr works fine again?
- Jun 4, 2010
- 3,080
- 0
Out of interest Carig, when you dumped your NAND the first time. Did you get 3 dumps and checked if all 3 had no mismatching blocks?
i have 4 dum ps all same bad block at 6 and 2f5 also when writing back fails to write to 6 and 2f5? i still think the problem is with freeboot not looking in the right place 3ff for block 6 but dont know how to correct it as xbr and xellous work with no problem. i have even made an orig file from xbr that works but wont convert to freeboot. would love to sort this cos i just dont see how xbr and xellous work but freeboot wont? i have read that you can extract the smc from xbr and inject it in to freeboot but cant find any info on doing it or if it would help in my case?
- Jun 4, 2010
- 3,080
- 0
XBR doesn't depend on the original NAND and as well it doesn't require the CPU key like freeboot does. This is probably why Freeboot has more capabilities than XBR and is preferred by many.
SMC here is not related as the SMC file will be the same for booth so it won't make a difference. Even though if you wanted to do that, just use the updatemysmc tool to extract the SMC file from XBR, place it into the smc folder within JTAG tool and compile a copy of Freeboot (ensure that you rename the smc file to xenon.bin and it should be 12kb in size).
My assumption is that Freeboot halts when it comes the CPU key interptation as it displays the same behavior if you would to use the incorrect CPU key.
I'm trying to create another freeboot image using iHc tool but it keeps crashing on me so might take a while as well might try Easy Freeboot.
thats the tool i use. i can recheck the cpu key but it shows the sams when i boot to xellous is there anything that would make it desplay wrong cpu key but still boot xellous?