Falcon XBR 8955_3 to Freeboot no orig.bin help

[ReverseAffect]

that unit alone, re-check for your bad block relocation and make sure it's placed within the 64mb's (system).
or major corruption......

[barnhilltrckn]

that unit alone, re-check for your bad block relocation and make sure it's placed within the 64mb's (system).
or major corruption......

Maybe its the pain pills the dr has got me on right now but i dont understand what you mean lol.

[Tiros]

update
fixed my LPT cable and used donor nands (thanks guys!) to build a donor nand by decrypting and extracting all parts of my orig.bin in bincrypt 2.5.

bidomo's nand was closest to mine although different region NTSC
........

An obvious problem is that your bootloaders are not encrpyted with your cpu key.
Youd need to build a correct set, possibly with build.py, modified to encr the CD+ with cpu key.
Ill bet you cant extract kernels in flashtool with the image you have created

[Gazcoigne]

tiros i really appreciate your input

do you know why freeboot toolbox does not create a working freeboot image for me?

all other guides/posts indicate that it works pretty much every time for others

am i wrong about my LDV value theory?

i dont need this done for me just a pointer in the right direction so i can figure this out myself.

cheers

[phonsey]

i have solved this problem b4 guys its the LDV and smc thats the problem! use smc from xbr which should give you LDV 16 when creating a freeboot image! use ibulid.py to create the freeboot image and it doesnt matter if you have blown that many fuses are not it will still work! if you want send me your nand dump and ill make you the freeboot image! 

[Gazcoigne]

cheers phonsey check ur pm

[justmeee]

I think i have the same problem. XBR and freeboot 0.03 are running well, but when i update to freeboot 0.032 the Box gives me an E52. My orig is gone coz i my hd crashes. It's a 256 mb jasper. Any ideas how i can fix it? when the next freeboot will come (kinect update) i think i cant update coz of the lvd problem.

[Gazcoigne]

@Gazcoigne

Did you ever give my suggestion a try?

just tried your suggestion used XBR.bin to build freeboot image through bestpigs app then used that to compile a freeboot

same problem

now going to try phonesey's suggestion of using XBR SMC and setting LDV to 16 for a laugh

[Gazcoigne]

SUCCESS!!!

firstly many many thanks to phonsey who took the time to help me out and create a working freeboot for me.

phonsey=360 legend!!

Seems i was using the incorrect odd.bin according to phonsey anyways.

i used ibuild to extract the odd.bin from my working XBR, which according to phonsey was incorrect, as the XBR image is a zero paired image ibuild does not extract the odd.bin correctly.

should have used the odd.bin_dec generated from 360flashtool renamed to odd.bin

for those guys that were in the same situation, there is light at the end of the tunnel!!

phonsey please make your tutorial about this issue, save some poor people like me a few sleepless nights!!

[bidomo]

phonsey please make your tutorial about this issue, save some poor people like me a few sleepless nights!!

I think it was like a month, but is good to hear it's been worked out, cheers.

[Gazcoigne]

phonsey please make your tutorial about this issue, save some poor people like me a few sleepless nights!!

I think it was like a month, but is good to hear it's been worked out, cheers.

nah it was far longer tried for ages on my own before i came on here for help

hopefully the images can be put on xbins for everyone to use

[shyam_2666]

i have solved this problem b4 guys its the LDV and smc thats the problem! use smc from xbr which should give you LDV 16 when creating a freeboot image! use ibulid.py to create the freeboot image and it doesnt matter if you have blown that many fuses are not it will still work! if you want send me your nand dump and ill make you the freeboot image! 

Could not understand , having the same problem got ctistmas light every time
please help

[Gazcoigne]

sorry to raise an old thread, but this problem has reared its ugly head again when trying to update this JTAG to latest freeboot with fbbuild 0.32

ive tried every combination to make the updflash for this, and all boot with solid centre light and no error code, XELLOUS also boots so the SMC is correct.

used working 12611 FB image as nanddump.bin in fbbuild (completed with no errors)

used fbbuild with files extracted from working 12611 image using 360flashtool 0.97 (completes saying crl.bin is corrupted)

used easyfreeboot with working 12611 FB image

phonsey made me the working 9199 and 12611 FB images that have worked, everything else errors out.

bad blocks are no onger the issue as last time, i have ditched flash360 and am using xellous or LPT manually remapping blocks when flash is bad.

pulling my hair out on this JTAG

even tried a donor image working on another falcon i have here with bad blocks remapped and still no boot.

relfashing the 9199 or 12611 FB images returns it to booting correctly.

WTF??

[phonsey]

sorry to raise an old thread, but this problem has reared its ugly head again when trying to update this JTAG to latest freeboot with fbbuild 0.32

ive tried every combination to make the updflash for this, and all boot with solid centre light and no error code, XELLOUS also boots so the SMC is correct.

used working 12611 FB image as nanddump.bin in fbbuild (completed with no errors)

used fbbuild with files extracted from working 12611 image using 360flashtool 0.97 (completes saying crl.bin is corrupted)

used easyfreeboot with working 12611 FB image

phonsey made me the working 9199 and 12611 FB images that have worked, everything else errors out.

bad blocks are no onger the issue as last time, i have ditched flash360 and am using xellous or LPT manually remapping blocks when flash is bad.

pulling my hair out on this JTAG

even tried a donor image working on another falcon i have here with bad blocks remapped and still no boot.

relfashing the 9199 or 12611 FB images returns it to booting correctly.

WTF??

http://www.megaupload.com/?d=XFQIFWC5

[Gazcoigne]

still no joy, i have tried everything i can think of, and i am completely stumped.

all images i create using working 12611 image for 13599 fail, but XELLOUS still boots (SMC ok)

no RROD, just solid green light on centre of ROL board, and no picture sound.

its like the dash is stalling when loading.

flashing back to the 12611 image, the console boots and operates normally.

downloaded latest coolshrimps jtag tool, and used it to create a repaired original NAND, and used it to make the fb image, it thows an error that the crl is corrupted and the extended.bin is not there, and the image also fails.

even a donor image that i know is working great on friends JTAG (also a falcon) doesnt boot on the console, with blocks remapped.

WTF is up with this JTAG? will i be stuck on 12611 forever?

[ddxcb]

still no joy, i have tried everything i can think of, and i am completely stumped.

all images i create using working 12611 image for 13599 fail, but XELLOUS still boots (SMC ok)

no RROD, just solid green light on centre of ROL board, and no picture sound.

its like the dash is stalling when loading.

flashing back to the 12611 image, the console boots and operates normally.

downloaded latest coolshrimps jtag tool, and used it to create a repaired original NAND, and used it to make the fb image, it thows an error that the crl is corrupted and the extended.bin is not there, and the image also fails.

even a donor image that i know is working great on friends JTAG (also a falcon) doesnt boot on the console, with blocks remapped.

WTF is up with this JTAG? will i be stuck on 12611 forever?

I fix an xbox like that, erase the nand and use a fresh image.

[Gazcoigne]

i erase the nand before every write, and remove power cable etc before fresh write that does not solve the issue.