freeBOOT 0.32 and e71

[cheezy102]

Having a bit of trouble with a freeBOOT install (Xenon).

I have flashed freeBOOT 0.32 but the system starts to boot (gets about 2 seconds in) then goes to e71 screen. Heres what I have done:

1) Read Nand 2 times. Matching reads with bad block 72 remapped to 3ff
2) I extracted block 3ff with nandpro and injected it back to block 72
3) I then built the freeBOOT image with jtag tool
4) I remapped block 72 of the freeBOOT image to 3ff
5) Flashed freeBOOT

Have done the remaps a couple of times to make sure I didn't make a mistake. Also the console boots fine with the original nand flashed back to it. Xell also boots fine.

Any help would be greatly appreciated!

 

[jhgerm7300]

Whick jtag tool are u using if its 2.0 uninstall it and get 1.74 i hope this helps

 

[cheezy102]

Whick jtag tool are u using if its 2.0 uninstall it and get 1.74 i hope this helps

It's 2.01. Is there a bug in this version?

 

[manwithoutname]

There is a possibility that v2.00 or above might have a mix up with xell files as few people who used it experienced non powering consoles after flashing xell. However this is probably not related to your case as you seem to already have obtained your CPU key and attempted to compile a freeboot image.

My recommendation is to use a non remapped image of your original NAND dump to compile freeboot and then remap freeboot once it has been created. I personally do it that way, add to this those who remapped their original NAND before creating freeboot usually have either experienced problems.

PS. I'd suggest writing freeboot to your console before remapping at all, if that doesn't work then remap and reflash again and try.

 

[cheezy102]

There is a possibility that v2.00 or above might have a mix up with xell files as few people who used it experienced non powering consoles after flashing xell. However this is probably not related to your case as you seem to already have obtained your CPU key and attempted to compile a freeboot image.

My recommendation is to use a non remapped image of your original NAND dump to compile freeboot and then remap freeboot once it has been created. I personally do it that way, add to this those who remapped their original NAND before creating freeboot usually have either experienced problems.

PS. I'd suggest writing freeboot to your console before remapping at all, if that doesn't work then remap and reflash again and try.

Thanks for the help. Tried it with no remaps at all and with only remapping the freeBOOT image. Same problem

 

[jhgerm7300]

Did you ever try with jtag tool 1.74 we shared smiliar problems and that is how i resolved mines... or it could be ur jtag solder connection them requiring resistors.. do you have anything else plugged in your xbox while booting

 

[cheezy102]

Did you ever try with jtag tool 1.74 we shared smiliar problems and that is how i resolved mines... or it could be ur jtag solder connection them requiring resistors.. do you have anything else plugged in your xbox while booting

Ye tried with 1.74. Nothing plugged in while booting. Really stuck on this one.

 

[manwithoutname]

The version of Jtag tool in this case is irrelevant as the issue is not related to xell but to freeboot it self.

You might want to try and construct freeboot using a different tool instead of jtag tool this time. Maybe you'd like to try iHc NANDTool, freeBOOT ToolBox & other similar tools to construct freeboot and see what's the outcome with that?

 

[cheezy102]

The version of Jtag tool in this case is irrelevant as the issue is not related to xell but to freeboot it self.

You might want to try and construct freeboot using a different tool instead of jtag tool this time. Maybe you'd like to try iHc NANDTool, freeBOOT ToolBox & other similar tools to construct freeboot and see what's the outcome with that?

Tried freeBOOT Toolbox and got the same error so I thought I would try XBR and see what happens with that. XBR doesn't boot at all!

 

[cheezy102]

Also Xell does now seem to be booting (no error) from the eject button when freeBOOT is flashed

 

[cheezy102]

Any ideas?

 

[tonyintn]

manwithoutname is correct... Take your original Nand with the bad blocks Do Not Remap. Next Use Freeboot to make the 9199 image. When finished go back to your original nand take note of the bad blocks use this information to remap the 9199 new freeboot built image. Write that to your box (the remapped freeboot image).

It should work.

 

[cheezy102]

manwithoutname is correct... Take your original Nand with the bad blocks Do Not Remap. Next Use Freeboot to make the 9199 image. When finished go back to your original nand take note of the bad blocks use this information to remap the 9199 new freeboot built image. Write that to your box (the remapped freeboot image).

It should work.

Already tried it mate. It gives the same error

 

[big_ted]

You new image need the info from the bad blocks, I normally do it like this,

1) dump the image
2) map the bad blocks back to the correct position, so the image is now complete
3) make the new 9199 image as per norm
4) map the "original bad blocks" from the new 9199 image to the bad blocks in spare.
5) flash back to console

works for me

Ted

 

[cheezy102]

You new image need the info from the bad blocks, I normally do it like this,

1) dump the image
2) map the bad blocks back to the correct position, so the image is now complete
3) make the new 9199 image as per norm
4) map the "original bad blocks" from the new 9199 image to the bad blocks in spare.
5) flash back to console

works for me

Ted

That's exactly what I did. Read the original post lol

 

[manwithoutname]

Guys, he tried both ways. Remapping the original NAND dump followed by creating freeboot and also creating freeboot from the non remapped nand dump and then remapping it.

Considering that he tried everything possibly I might do, I wouldn't mind having a go at it my self over a Team viewer session!!!

 

[cheezy102]

Guys, he tried both ways. Remapping the original NAND dump followed by creating freeboot and also creating freeboot from the non remapped nand dump and then remapping it.

Considering that he tried everything possibly I might do, I wouldn't mind having a go at it my self over a Team viewer session!!!

Team viewer session?

 

[big_ted]

this has been fixed, on pm.
dumped original flash
moved bad blocks from spare to image to make good image
made new dash image
flashed back using xell, Auto sorted the bad blocks and now boots.

Sorted


Ted

 

[jolyrojr]

Dang, I wish that worked for me. This box is driving me crazy :[

I know for sure my wiring is good, so I have been focusing on the bad blocks. So far nothing I have found works

nm, i finally got it! I had to use all 6 nand reads I did, in different combinations to get a good one, then I moved the bad sectors to the original spots, covered up the 3ff and 3fe blocks with zeros, built freeboot, manually put the bad block bad to 3ff and 3fe, covered the bad blocks with zeros, then flashed with lpt.