Topic: Personal Help: Getting Freeboot Installed (Read 342 times)

antisniperspy · « **on:** July 26, 2010, 02:03:00 PM »

I can help you out, but if you dont have a way to recover I don't recommend updating because you could brick you jtag.

AIM - AntiSniperSpy

sm32 · « **Reply #1 on:** July 26, 2010, 09:09:00 PM »

i think something along the lines of if you have your keyvault you can use a "donor NAND" from someone with the same revision, change the keyvault, and use it with your box. but it would help to have your cpu key for that...

antisniperspy · « **Reply #2 on:** July 27, 2010, 08:17:00 AM »

QUOTE(sm32 @ Jul 26 2010, 11:09 PM)

i think something along the lines of if you have your keyvault you can use a "donor NAND" from someone with the same revision, change the keyvault, and use it with your box. but it would help to have your cpu key for that...

He has his cpu key, and his original nand but the original nand is corrupt. I tried to extract it with ibuild with no luck. He also has three dumps of xbr.

thwack · « **Reply #3 on:** July 27, 2010, 12:39:00 PM »

This is how I used to do it (although haven't needed to for some time):
You need:

Bincrypt
360 Flash Tool.
KeyVault Modder
The corrupt NAND dump
The donor NAND dump (Should be same model mobo as corrupt one - preferably the same kernel but not necessarily)
Both nands CPU keys

Open bincrypt and place your CPU Key (from the bad NAND) in the 'CPU Key' box. Click 'Raw Flash Bin' and make sure the 'Extract' has a dot in it. Then click 'Decrypt' under 'Operation'. Then click 'Process', open the bad NAND, and then name the kv whatever you like.

Bincrypt again: Now place the donor CPU key in the CPU key box, and follow the same steps as above.

Now open KeyVault Modder and open your KeyVault from the bad NAND, you should be able to view the information, although some bits may be missing. Don't worry, but note the stuff that's there down.

BinCrypt again: Place your original (bad) CPU key in the CPU Key box. Click 'Raw Flash Bin' and 'Replace'. Under 'Operation' click 'Encrypt', then click 'Process'. Select your donor NAND dump, then select the donor keyvault when asked.

This has injected the donor keyvault signed with your 'bad' CPU key

Open 360 Flash Tool, click 'Keys' and pop your 'bad nand' CPU key in there. Open the 'bad nand' dump, and note down all the LDV values in the order they appear.

Now open 360 Flash Tool, Click Keys, place your 'bad nand' CPU Key on the line intended, open up the now 'good nand' dump you've injected your CPU key into. Click Ok, it will probably say 'bad kv' (not always though). Then click 'Patch', tick the 'Patch Headers', and enter the LDV values you noted down above, in the order you wrote them in. Also tick the 'Patch Keyvault' box (if you can - if not, click 'ok' which will patch the info, then open the 'patch' window again and it should allow you). Under the 'Patch Keyvault' you need to enter your bad nand dumps region, drive type, and drive key. Click ok, and you're done

Probably massively out of date, but dragged it up from an email I sent someone a while back........

matt186 · « **Reply #4 on:** July 27, 2010, 03:22:00 PM »

QUOTE(matt186 @ Jul 27 2010, 09:44 PM)

you didnt click the link in my post did you

ok going to attempt this: does anyone have a Jasper 16mb donor nand and CPU?

Twis7eD · « **Reply #5 on:** July 27, 2010, 04:24:00 PM »

QUOTE(matt186 @ Jul 27 2010, 04:22 PM)

ok going to attempt this: does anyone have a Jasper 16mb donor nand and CPU?

http://www.mediafire.com/?tzgnnzoyrmy

That is a RAR that contains donor files for Xenon, Jasper, and Falcon motherboards. It also contains a lot of other useful files that you probably don't need.

matt186 · « **Reply #6 on:** July 29, 2010, 07:37:00 AM »

QUOTE(matt186 @ Jul 27 2010, 11:50 PM)

Thanks for the reply but I think the file above lacks the CPU/NAND I need to perform the above method

quick bump

blbassi · « **Reply #7 on:** July 29, 2010, 12:53:00 PM »

i had a currupt nand, but got a donor nand to work on my xbox, post a link with your xbr and original nand and ill give it a whirl..also your cpu key.

matt186 · « **Reply #8 on:** July 29, 2010, 01:58:00 PM »

QUOTE(blbassi @ Jul 29 2010, 07:53 PM)

i had a currupt nand, but got a donor nand to work on my xbox, post a link with your xbr and original nand and ill give it a whirl..also your cpu key.

Thanks for the offer mate - could i ask that you sent the donor nand and CPU instead? I would prefer doing it myself

THanks

blbassi · « **Reply #9 on:** July 29, 2010, 02:12:00 PM »

what rev of jasper do you have, the donors above prob have what you need...i think they are what i used

blbassi · « **Reply #10 on:** July 29, 2010, 05:49:00 PM »

http://forums.xbox-s...o...712076&st=0

has files and info that you can use!

matt186 · « **Reply #11 on:** July 30, 2010, 12:16:00 AM »

QUOTE(blbassi @ Jul 30 2010, 12:49 AM)

http://forums.xbox-s...o...712076&st=0

has files and info that you can use!

nope - as mentioned before : my nand is corrupt on xbr so that wont work

EDIT: could be wrong, will check it out later

blbassi · « **Reply #12 on:** July 30, 2010, 07:08:00 AM »

your entire nand cannot be corrupt or your xbox would be bricked...you can still extract parts around the bad blocks. worse case you may need to build with a donor nad, your cpu key, and freeboot .30

antisniperspy · « **Reply #13 on:** July 30, 2010, 11:13:00 AM »

QUOTE(matt186 @ Jul 30 2010, 02:16 AM)

nope - as mentioned before : my nand is corrupt on xbr so that wont work

EDIT: could be wrong, will check it out later

Your nand1.bin was corrupt. This was your original nand. The only one you had that was original.
nand2 , nand3 and xbr.bin were not corrupt but they were xbr copies.

blbassi · « **Reply #14 on:** July 30, 2010, 02:16:00 PM »

e52 can be due to changing a kv in freeboot .32 ...try the same build using freeboot .30 and it might work

Author Topic: Personal Help: Getting Freeboot Installed (Read 342 times)