3 Tools to Help UnCripple Your Xbox360 HDD Posted by XanTium | November 26 19:52 EST | News Category: Xbox360

A few tools have been released to help you uncripple your HDD after ban, so you don't have to do it all manually. * FindSecData v0.4 (by boby2pc) I wrote little program to extract secdata.bin and filetable of NAND dump. It uses patch latest secdata.bin method (not delete method). Changelog: * v0.11 Fixed regional settings problem. * v0.2 support for 256 MB and 512 MB NANDs implemented. * v0.3 Different NAND controller support * v0.4 - "ommit timestamp" parameter removed - this is now default - added parameter to show more recomendations - "recommandation" algoritm changed - support for gaps in filesystem table version Official Site: n/a, by boby2pc on xboxhacker.net Download: here * Secdata Scan v0.2 (by zouzzz) Secdata Scan is a small utility that will save you manually open your NAND dump to find the address to hex edit to restore the functionality of the hdd after a ban. Once you load your nand image in Secdata, it will show you the last secdata updated on your console and the real address of this bloc to use with with nandpro. Official Site: by zouzzz at gx-mod.com Download: here * 360 HDFR v1.03 (by SoulHeaven) (French) 360 Hard Disk Functinalities Restorer v1.03 will allow you to patch your nand automatically in order to restore the functionality to install games on your harddrive on a banned Xbox 360. Does the same as Secdata Scan but with more functionality: - Show you the real date of secdata update - Can generate a zero filled file from your nand image for nanpro - Can patch your nand for Cygnos v2 Note: does not work on 256/512MB NANDs yet. Official Site: by SoulHeaven at gx-mod.com Download: here

Neat. Steps are now the following?

1. Extract with NandPro
2. Run secdata.bin through 360 HDFR v1.03
3. Flash fixed secdata.bin with NandPro
4. *Dance*

I honestly just logged onto xbox scene to ask for an automated utility for HDD uncrippling. looks like you read my mind, Cannot wait to give this a shot. Excellent work

Yay! Now if only it didn't take ages ...

The alternative is a 360 that can run trusted content without borking it.

the scene just spitted a giant stinking loogie into Microsoft's face, then shit on their face with a big kick in their asses.

I wonder how difficult it would be to remove the cygnos360 v2 from a 360, put it on a banned one to do this, and put it back to the orig one.

I havent installed my chip on my older, disconnected 360, to do XeLL, but im wondering if/when i get banned sometime after iXtreme LT comes out if i'd be able to swap the chip back and forth between my units.

Nice tread.

Now the next topic shall be......

FindSecData vs Secdata Scan vs 360 HDFR

Who will win?

exactly how many wires need to be soldered for this to work?

Nm, found out myself.

Good to see the modders one-upping M$ again. Gotta love arms races^_^

Can someone update the news page - this application is in French AND English! One only has to click on the appropriate flag at the bottom of the screen.

Used this tool last night and can personally vouch for it

Nice one, MS pushed it to far trying to disable fetures on a persons private property.

Hello!

can someonehelp me please ? i've a dump of mu XBOX360 NAND, so, which tool of these 3 have i to use to uncriplig automatically my hdd, please ?

If i correctly understood, i can launch 360 HDFR v1.03 and automatically modify my dump, so next i can flash my NAND with the patched dump, is it correct ?

thanks & sorry from my english

Does any of the utilities also show the last timestamp for secdata.bin as if this was modified after the ban date, changing it will not help anymore (will not regain the hdd functionality)?
Thanks for the proggies;)

Hi - I wrote a fairly simple guide here:
http://forums.xbox-scene.com/index.php?sho...231&st=165#




360HDFR will list all revisions and dates for versions of secdata.bin on your NAND. you can just take the offset value from the date earlier than the ban. What I don't understand is why your secdata.bin was modified after the ban? If you modified it, surely you still have a backup of the NAND?

Secdata.bin pointer gets modified after the ban if you install a new update (e.g. from a Game DVD). In this situation you can't restore your HDD functionality as your NAND only keeps copy of two pointers from sectdata.bin (the actual pointer and one previous pointer). As the previous pointer will still contain the sectdata.bin with an unusable hdd service you will not be able to restore your hdd functionality.

thanks Martinchris23 , I LOVE YOU!! really really thanks!

Have you tried to delete all of them?

I guess that deleting all of them will not work either way, didn't tried tho.

Can you do this if you have the 84xx or 89xx update already?

can this help transfer a 20gig drive to a 120gig drive using a PC?? thanks and sorry for idiocy.

thanks to all involved in making these cool tools.

love all of u

Could this possibly help to stop console corrupting gamer profiles?

I'm frequently playing in a friend's house, and have a memory with a complete profile, but when he wants to go to my console (for live) is impossible...

Have you tried? If you have a dump of your NAND you don't really have much to lose since you can always write them back.



Yes - it has nothing to do with dashboard version, doesn't require you to have an exploitable kernel and you don't need the CPU key.



No - do a search for HDDHackr




Depends - if both consoles are on XBL then it's probably too late to do anything about it. The corruption COULD be revokation but I would guess it was more of an accidental corruption.

If the suspect 360 hasn't been on XBL for a good while then it might be possible to downgrade the console and re-update to correct the 'corruption'. I've had to do it on two unbanned consoles so far and have successfully corrected this.

Are there any physical tools available for uncrippling the hdd? I'm not really into making my own wire etc... thx!

The console has been banned a year ago, but that guy has updated to lates firmware, so I don't think is gonna be possible, unless timing atack still works (xenon board 84XX)

My console doesn't have any reason to be flagged, no mod no that console (but in another one).

Any idea why 360HDFR freezes when I open my nand.bin?

I'm having the same issue. tried it with 2 different nand dumps.
Got all the wiring done no problem dump my nand now if only I understood all this hex stuff I'd be in business!
I saw these tools and was excited only to be kicked in the arse.

Any chance you've got Jasper consoles?

It's an older Elite without the onboard memory, from may 08' from what I read only the arcades have the onboard 256/512mb but I don't know for sure. When I dumped it I selected the 16 and it took so I just assumed it was correct, but we all know what assuming gets ya

I've played MW2 and AC2 since the ban wave, on my 360...Would these games have overwritten my previous secdata.bin??

I dont want to go through the effort of soldering wires to my 360 and risk messing it up only to find out the secdata.bin has been overwritten (im still a bit of an amateur at sodering)

Any ideas?

Unless you had a prompt to update your console after the ban wave, you should be ok. If you're that unsure about soldering I would advise you re-think doing it yourself !



Jaspers weren't shipping until 2009 so it's gonna be a 16MB NAND.

What does Degraded say about your dump?

I have a xenon mobo.



I couldn't get HDFR to work, so I did it manually. I copied all instances that the secdata.bin occured in my Nand and found the latest offset. Divided it by 4200 and got 0x21a, which is also what SecDataScan got as well.
Opened the file through HW, selected all and replaced with Zero's. Renamed to NandZero.bin and flashed it to the offset 0x21A. Checked to see if it restored, nothing.

Edit: FindSecData App:



Is that right? It's telling me to use 274 which would still contain the ban-secdata.bin?

Edit 2: My nand dump

Degraded 1.1 crashes when I load the nand.bin, I changed the date from 2004-2007 to 2004-2005 and it still crashes. I don't have a clue whats going on here. my nand.bin is 16.5mb

I'm also not getting any errors during the reading process and the status reads as follows,

Testing LPT device address:0378
Using LPT device at address:0378
FlashConfig:01198010
Starting Block:0x000000
Ending Block:0x0003FF
Press any key to begin reading nand

Thanks, is there any instructions to copy data from an official 20GB to an official 120GB via PC?

Just tried to dump it using the 256 option and error happened around 400 block, since the 16mb ends at 3FF block then must def be a 16mb nand. still won't open in degraded or the 360HDFRv1.03, also ran it thru the FindSecDatav0.4 and it said it found something and patched it. wrote it back to the nand and still no worky. I'm bout ready to toss at into the sewer

Well after hours of this and that I finally was able to restore HDD install function however, when I put the HDD on the unbanned console the profile shows corrupted even with a new one. so I have no friggin clue why that shows corrupt shouldn't it be fine if I can install to HDD?

n/m had to format hdd and all was good swap back n forth between banned and unbanned no corruption.

My mate played left 4 dead 2 on his banned console ? He had all updates up to the point of his ban . It was wave 5 game I think .

hi to all...i did dump of my nand using programmer(desolder Nadn) what i do after that:

1. Using 360HDFR try to open it...but that programm freeze.
2. Using SecDataScan open nand dump,do scaning...got something : "Max" Adress :3à3610 ,Max Value :3B6592EB , "Max" Adress / 0x4200 : 0xf5 .... now can someone explain what i need to do with that full dump of nand in HEXredactor? what blocks i need to full with "0"?? coz i need to change and that full damp and flash it using programmer back

All my Secdata.bin time stamps are the same!!! After manually check all 60 instances in WinHex, I confirmed what appears to be the same time stamps. Here's the log:

F:\DownloadFiles\xbox360\FindSecDatav0.4>FindSecData.exe banned.bin -rc 15

findsecdata v0.4 2009-11-26 by boby2pc
Controller version 1
Last filetable change: 0xFB
ECC change: 0xFB Filetbl: 0x013B Secdata: 0x013A Timestamp: 33766001 2004-04-13
ECC change: 0xFA Filetbl: 0x0139 Secdata: 0x0138 Timestamp: 33766001 2004-04-13
ECC change: 0xF9 Filetbl: 0x0137 Secdata: 0x0136 Timestamp: 33766001 2004-04-13
ECC change: 0xF8 Filetbl: 0x0135 Secdata: 0x0133 Timestamp: 33766001 2004-04-13
ECC change: 0xF7 Filetbl: 0x0132 Secdata: 0x0131 Timestamp: 33766001 2004-04-13
ECC change: 0xF6 Filetbl: 0x0130 Secdata: 0x012F Timestamp: 33766001 2004-04-13
ECC change: 0xF5 Filetbl: 0x012E Secdata: 0x012D Timestamp: 33766001 2004-04-13
ECC change: 0xF4 Filetbl: 0x012C Secdata: 0x012B Timestamp: 33766001 2004-04-13
ECC change: 0xF3 Filetbl: 0x012A Secdata: 0x0129 Timestamp: 33766001 2004-04-13
ECC change: 0xF2 Filetbl: 0x0128 Secdata: 0x0127 Timestamp: 33766001 2004-04-13
ECC change: 0xF1 Filetbl: 0x0126 Secdata: 0x0121 Timestamp: 33766001 2004-04-13
ECC change: 0xF0 Filetbl: 0x0114 Secdata: 0x0113 Timestamp: 33766001 2004-04-13
ECC change: 0xEF Filetbl: 0x0112 Secdata: 0x0111 Timestamp: 33766001 2004-04-13
ECC change: 0xEE Filetbl: 0x0110 Secdata: 0x010F Timestamp: 33766001 2004-04-13
ECC change: 0xED Filetbl: 0x010E Secdata: 0x010D Timestamp: 33766001 2004-04-13
ECC change: 0xEC Filetbl: 0x010C Secdata: 0x010B Timestamp: 33766001 2004-04-13
ECC change: 0xEB Filetbl: 0x010A Secdata: 0x0109 Timestamp: 33766001 2004-04-13
ECC change: 0xEA Filetbl: 0x0108 Secdata: 0x0107 Timestamp: 33766001 2004-04-13
ECC change: 0xE9 Filetbl: 0x0106 Secdata: 0x0105 Timestamp: 33766001 2004-04-13
ECC change: 0xE8 Filetbl: 0x0104 Secdata: 0x0103 Timestamp: 33766001 2004-04-13
ECC change: 0xE7 Filetbl: 0x0101 Secdata: 0x0100 Timestamp: 33766001 2004-04-13
ECC change: 0xE6 Filetbl: 0x00FF Secdata: 0x00FE Timestamp: 33766001 2004-04-13
ECC change: 0xE5 Filetbl: 0x00FD Secdata: 0x00FC Timestamp: 33766001 2004-04-13
ECC change: 0xE4 Filetbl: 0x00FB Secdata: 0x00FA Timestamp: 33766001 2004-04-13
ECC change: 0xE3 Filetbl: 0x00F9 Secdata: 0x00E6 Timestamp: 33766001 2004-04-13
ECC change: 0xE2 Filetbl: 0x00E5 Secdata: 0x00E4 Timestamp: 33766001 2004-04-13
ECC change: 0xE1 Filetbl: 0x00E3 Secdata: 0x00E2 Timestamp: 33766001 2004-04-13
ECC change: 0xE0 Filetbl: 0x00E1 Secdata: 0x00E0 Timestamp: 33766001 2004-04-13
ECC change: 0xDF Filetbl: 0x00DF Secdata: 0x00DE Timestamp: 33766001 2004-04-13
ECC change: 0xDE Filetbl: 0x00DD Secdata: 0x00DC Timestamp: 33766001 2004-04-13
ECC change: 0xDD Filetbl: 0x00DB Secdata: 0x00DA Timestamp: 33766001 2004-04-13
ECC change: 0xDC Filetbl: 0x00D9 Secdata: 0x00D8 Timestamp: 33766001 2004-04-13
ECC change: 0xDB Filetbl: 0x00D7 Secdata: 0x00D6 Timestamp: 33766001 2004-04-13
ECC change: 0xDA Filetbl: 0x00D5 Secdata: 0x00D4 Timestamp: 33766001 2004-04-13
ECC change: 0xD9 Filetbl: 0x00D3 Secdata: 0x00D2 Timestamp: 33766001 2004-04-13
ECC change: 0xD8 Filetbl: 0x00D1 Secdata: 0x00D0 Timestamp: 33766001 2004-04-13
ECC change: 0xD7 Filetbl: 0x00CF Secdata: 0x008D Timestamp: 33766001 2004-04-13
ECC change: 0xD6 Filetbl: 0x008C Secdata: 0x008B Timestamp: 33766001 2004-04-13
ECC change: 0xD5 Filetbl: 0x008A Secdata: 0x0089 Timestamp: 33766001 2004-04-13
ECC change: 0xD4 Filetbl: 0x0088 Secdata: 0x0087 Timestamp: 33766001 2004-04-13
ECC change: 0xD3 Filetbl: 0x0086 Secdata: 0x0085 Timestamp: 33766001 2004-04-13
ECC change: 0xD2 Filetbl: 0x0084 Secdata: 0x0083 Timestamp: 33766001 2004-04-13
ECC change: 0xD1 Filetbl: 0x0082 Secdata: 0x0182 Timestamp: 33766001 2004-04-13
ECC change: 0xD0 Filetbl: 0x0181 Secdata: 0x0180 Timestamp: 33766001 2004-04-13
ECC change: 0xCF Filetbl: 0x017F Secdata: 0x017E Timestamp: 33766001 2004-04-13
ECC change: 0xCE Filetbl: 0x017D Secdata: 0x017C Timestamp: 33766001 2004-04-13
ECC change: 0xCD Filetbl: 0x017A Secdata: 0x0179 Timestamp: 33766001 2004-04-13
ECC change: 0xCC Filetbl: 0x0178 Secdata: 0x0176 Timestamp: 33766001 2004-04-13
ECC change: 0xCB Filetbl: 0x0175 Secdata: 0x0174 Timestamp: 33766001 2004-04-13
ECC change: 0xCA Filetbl: 0x0167 Secdata: 0x015E Timestamp: 33766001 2004-04-13
ECC change: 0xC9 Filetbl: 0x015D Secdata: 0x015C Timestamp: 33766001 2004-04-13
ECC change: 0xC8 Filetbl: 0x015B Secdata: 0x015A Timestamp: 33766001 2004-04-13
ECC change: 0xC7 Filetbl: 0x0159 Secdata: 0x0157 Timestamp: 33766001 2004-04-13
ECC change: 0xC6 Filetbl: 0x0156 Secdata: 0x0155 Timestamp: 33766001 2004-04-13
ECC change: 0xC4 Filetbl: 0x0151 Secdata: 0x0150 Timestamp: 33766001 2004-04-13
ECC change: 0xC3 Filetbl: 0x014F Secdata: 0x014E Timestamp: 33766001 2004-04-13
ECC change: 0xC2 Filetbl: 0x014D Secdata: 0x014C Timestamp: 33766001 2004-04-13
ECC change: 0xC1 Filetbl: 0x014B Secdata: 0x014A Timestamp: 33766001 2004-04-13
ECC change: 0xC0 Filetbl: 0x0147 Secdata: 0x0146 Timestamp: 33766001 2004-04-13
ECC change: 0xBF Filetbl: 0x0145 Secdata: 0x0144 Timestamp: 33766001 2004-04-13
ECC change: 0xBE Filetbl: 0x0143 Secdata: 0x0142 Timestamp: 33766001 2004-04-13

..and so forth

Looks like they're all dated 33766001

And finally:

Use:

Old secdata.bin not found. Console might be not banned, already patched or secda
ta.bin overwritten.

I know I'm screwed. I was fiddling with the unit while trying to flash a dvd drive last week after the ban and I'm guessing it kept writing the bad data each time I powered up the Xbox without a DVD sata attached. Does this make sense? Is their any possible recourse around this?

Is their anyone out their willing to offer this as a service? I would rather have someone or some group attempt to uncripple the drive then for me to short something.

PM me

Hey guys i dumped my nand 3 times with a 16mb jasper, both had a 250 error but seemed fine, i opened the nand with 360HDFR and did the zero fill and saved the Secdata patch file, and then wrote the patch file with the correct offset back to the 360.

Fired up the 360 and put my 120gb hdd on from my unmodded console, put it back in the unmodded console and its corrupted. any idea whats gone wrong/ how to fix?

cheers

Nevermind i fixed it, had to use FindSecData 0.5 and that worked wonders. excellent! niiice!

I hope somebody help me!

I dumped three times my NAND without any error.

So, I used findsectordate, and typed all commands

But my HDD still not installing games.....

I'm Using a x360 xenon board

I really got the right flash code.

Can somebody help me change patch my nand??

Please take a look on this pic

[IMG=http://img705.imageshack.us/img705/7272/nand.jpg][/IMG] [IMG=http://img705.imageshack.us/img705/nand.jpg/1/w648.png][/IMG]

Thank you very much

Best Regards

Resistol

Hi!

just to be sure, before modding my banned box with HDFR:

How do I write the NAND back to the console, since I don't have the Hex from this tutorial?



Or does HDFR tell me, which command-prompt to use, to write the NAND back to the console?

Thanks!

Is there a working version of 360 HDFR v1.03??
Every time I put the 16MB nand in it my pc bogs down and the program stops responding.
What's up with devs making tools and putting little in the readme or not even having one to start with??

Can't somebody tell, who already used the tool?

Use Nandpro to dump the nand
use Secdata Scan v0.2 to locate the secdata.bin (s) in the dump, it will display the address blocks where the bins are for you to use with nandpro to write to 0's

The "Max" address / 0x4200 display is the address you use with nandpro

Then you use nandpro and actually do it.

Then redump the nand, name it something like nandcheck.bin and run that through Secdata. You should notice that the block address you wrote to is different in the nandceck.bin than it was in your nand.bin

Then you know you're good to go and power it up with the HD to check.
(Yes you can leave the wires attatched to the motherboard while you check, but make sure you disconnect the circuit from your PC, or things may go ::poof:: )

EDIT: Don't forget about Degraded! to verify your dumps are good, and you may need to use winhex to change the date in the dump to be compatible with degraded.