Print

[Faluke]

I followed this guide.

I already performed the JTAG before starting up the guide using this diagram (I had to use the bottom point for DB1F1 because the joker that had this before me lifted the solder point).

I noticed after flashing in step 6n. that the xbox booted to solid green light with no video. Then I saw at the top of the guide where it says that he is using a different JTAG than I was so the SMC's are wrong???

Anyway, can anyone tell me how to recover and finish the JTAG? I'm trying to get to freeboot 0.32. Thx.

[Inuyasha152]

Yep, you're using the old diagram where the SMC doesn't get patched. Unless you want to re-solder your JTAG points to match the new method (resolves boot issues with some consoles) then just reflash Xellous (inject config + kv) and dont use the SMC IO utility or the donor SMC.

[thwack]

As Inuyasha said - Just reflash Xellous (although you don't need your config.bin):

Get your KV from the console:

nandpro usb: -r256 kv.bin 1 1

Do this twice and compare the files in a hex editor - if there's no differences, then you're good to go (or just use the one you got when you created your XBR).

Now  to flash Xell (get it from the usual places 360/development/Free60 - you want - 'jasper_6723_hack_for_256mb_512mb.bin' put file in your NandPro folder. Rename it Xell.bin.

nandpro usb: -w256 xell.bin 0

Now flash the KV back:

nandpro usb: -w256 kv.bin 1 1

Now to update Xell to Xellous - again from the usual places and you want the Xell-1f.bin. Put it in the NandPro folder:

nandpro usb: +W16 xell-1f.bin 40

(note the uppercase 'W', the '+' and the '16')

Now leave the 360 unplugged for 30 seconds, and boot via the eject button - Xellous will boot and you should get your CPU key.

Now take your original NAND dumps, and using Best Pigs FreeBoot Toolbox, make a FreeBoot image for your 360. Rename the image to 'updflash.bin', pop on the root of a FAT32 formatted USB stick. Put USB stick in the 360, boot using the eject button, and watch in awe as it updates (IMG:style_emoticons/default/wink.gif)

Worth a note though - Looouky's tut (the Aud_Clamp + bugfix) will stop the odd random RLOD errors HDMI consoles sometimes suffer from. As you have a Jasper you don't necessarily need the transistors, just swap the wire that runs to the ROL point, and resolder to the Aud_Clamp point. It's Zephyrs that really need the transistors.

This post has been edited by thwack: Aug 16 2010, 10:38 AM

[Faluke]

QUOTE(thwack @ Aug 16 2010, 01:36 AM)

As Inuyasha said - Just reflash Xellous (although you don't need your config.bin):

Get your KV from the console:

nandpro usb: -r256 kv.bin 1 1

Do this twice and compare the files in a hex editor - if there's no differences, then you're good to go (or just use the one you got when you created your XBR).

Now  to flash Xell (get it from the usual places 360/development/Free60 - you want - 'jasper_6723_hack_for_256mb_512mb.bin' put file in your NandPro folder. Rename it Xell.bin.

nandpro usb: -w256 xell.bin 0

Now flash the KV back:

nandpro usb: -w256 kv.bin 1 1

Now to update Xell to Xellous - again from the usual places and you want the Xell-1f.bin. Put it in the NandPro folder:

nandpro usb: +W16 xell-1f.bin 40

(note the uppercase 'W', the '+' and the '16')

Now leave the 360 unplugged for 30 seconds, and boot via the eject button - Xellous will boot and you should get your CPU key.

Now take your original NAND dumps, and using Best Pigs FreeBoot Toolbox, make a FreeBoot image for your 360. Rename the image to 'updflash.bin', pop on the root of a FAT32 formatted USB stick. Put USB stick in the 360, boot using the eject button, and watch in awe as it updates (IMG:style_emoticons/default/wink.gif)

Worth a note though - Looouky's tut (the Aud_Clamp + bugfix) will stop the odd random RLOD errors HDMI consoles sometimes suffer from. As you have a Jasper you don't necessarily need the transistors, just swap the wire that runs to the ROL point, and resolder to the Aud_Clamp point. It's Zephyrs that really need the transistors.

Ok, so now I have RROD with 0022 error code. That guide had me make some kv1.bin and kv2.bin files and they both checked out when I compared them with nandpro. I just used kv1.bin in your steps above.

quick update:

I reflashed xell and then injected kv1.bin into my nand. It booted so I took a picture of my keys and then updated using usb and updxell.bin instead of flashing over my lpt.

xellous is working now so I'll continue from there and report back

This post has been edited by Faluke: Aug 16 2010, 04:24 PM

[Faluke]

okay so I'm on the step where it says to use the freeboot maker and when I select my 66mb file it says that it doesn't recognize my mobo type and to select it myself. How do I do that? Also in that guide he says to locate the smc file that I used in step yadda yadda, but you told me not to use those smc files.

Current setup:

Xellous working on Jasper 256

Where do I go from now?

*update*

I just unchecked the autodectect for mobo's and selected Jasper 256. I ran the freeboot maker and then flashed using xellous. All is working perfectly! Thanks for all your help!

This post has been edited by Faluke: Aug 16 2010, 05:15 PM