Topic: 360 Not Booting After Xellous/free60 Flash (Read 25 times)

brandogg · « **on:** May 07, 2010, 10:53:00 PM »

Try building/flashing an XBR image first, if that works, then you know you didn't eff up your console somehow. After that, I would (and have) use freeBOOT toolbox maker to turn my XBR image into a freeBOOT image, and use Flash360 to install it, saying "yes" to keep current KV and Config when it asks.

phiquach · « **Reply #1 on:** May 08, 2010, 12:15:00 AM »

i pmed you but,

did you install the jtag wires?

Maximize · « **Reply #2 on:** May 08, 2010, 12:24:00 AM »

I can still read from the jtag I havent tried to write again yet

yes after uninstalling the jtag and still being in the same boat I reinstalled the jtag spi flasher

from what I can tell from re reading exactly what I wrote is there, there doesnt seem to be a discrepancy

phiquach · « **Reply #3 on:** May 08, 2010, 01:06:00 AM »

I pmed you but i'll post here.

You need to install the Jtag wires.

The USB SPI is only to read the nand. there are additional wires needed.

http://i12.photobuck...r-falcon--1.jpg

The red/yellow/blue part.

Maximize · « **Reply #4 on:** May 08, 2010, 03:36:00 PM »

ok thanks for that, now I have MORE PROBLEMS

i cannot seem to copy anything larger than fuses.txt, but I already have complete dumps, kv's, and config's

so the next problem would be that freeboot doesn't seem to give me a output file, does it just alter the input file, i guess when I get back from lunch with the moms I will run a compare on the original dump to see if it has been altered

Maximize · « **Reply #5 on:** May 08, 2010, 07:15:00 PM »

ok so I went ahead and installed xbr since I wasnt having any luck compiling freeboot, or with easy freeboot

maybe I will try again after my hair grows back

brandogg · « **Reply #6 on:** May 08, 2010, 10:01:00 PM »

Use freeBOOT toolbox maker .22 - then use flash360 to update the NAND, keeping the current kv and config when it asks. FreeBOOT toolbox maker will create a file called "freeBOOT.bin" just rename it to updflash.bin and put it in the root of your USB drive. Don't flash this image with Xellous because, from what I've read, the image it creates doesn't patch in your kv/config, which is why you use flash360 since it can leave what's already on your NAND in tact.

Maximize · « **Reply #7 on:** May 09, 2010, 10:15:00 AM »

cool thats the method I will try, I dont know if I will do it today I think I have had enough for the moment

Author Topic: 360 Not Booting After Xellous/free60 Flash (Read 25 times)