Print

[golteef]

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?

[golteef]

QUOTE(golteef @ Nov 29 2009, 12:20 AM)

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.

[Redsquirrel]

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 .

[sas83]

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

[drakul71]

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?

[visionzwp21]

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

[Setesh]

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

[Setesh]

QUOTE(Setesh @ Dec 1 2009, 04:10 PM)

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!

[rubaff]

CODE

Open up NANDPRO again, and this time, enter:

NandPro lpt:-w16 nandzero.bin 0x0119 1

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

Thanks!

[Odb718]

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??

[insanity4all]

QUOTE(rubaff @ Dec 4 2009, 08:44 AM)

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.

[Martinchris23]

QUOTE(Odb718 @ Dec 4 2009, 12:02 PM)

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??

If you have a Jasper, HDFR is going to freeze when you try and open it. Use FindSecData instead. It even gives you the command lines to enter back into nandpro.

[Stripey_Horse]

QUOTE(whopacha @ Dec 14 2009, 11:59 AM)

understanding:
After much Reading and confusion about the whole NAND reading/writing process and what it actually means to be crippled (funtionalities / profile and game save corruption)... im trying to piece things together from several sites and forum topics...initially i was under the impression that uncrippling would also uncorrupt my profile and gamesaves. (appear to be wrong in this aspect?)

steps i took:
built the lpt cable (LPT Cable Tut) (thx btw)
dumped nand with nandpro2.0b twice (no errors) then compared them (matched) = success.
used findsecdata
used nandpro to write the commands findsecdata told me to write.

questions:
NOW....
what is the easiest way to test if iam actually successful or not?
the NAND read took about 35 mins and when the write so fast in comparison, i assumed it hadnt worked.... but i guess its not re-writing the whole nand... just patching it right?

my HDD does not have enough room to copy a game to... but it does try to start copying(not enough room left error) (whilst my bro's crippled/banned xbox comes up with unable to copy error) Is this a sign that Iam successful?

moving the HDD to another xbox (currently not crippled or banned -but is modded and im not willing to risk plugging back into live yet, at least until ixtreme LT is released)[may be flagged for a ban already?] however shows that my profile is corrupt - along with just about all of my game saves. (also it asks me to update.. assuming it means update the dash... from the hdd?) should i let it? 8507->8955
imguessing nothing bad will come of that?

I found this tut: http://www.se7ensins...xbox-360-a.html

i am planning to attempt to un-corrupt my profile... but this does not appear to include game saves also?
I have a LOT of corrupt gamesaves...

Is there a one-stop program or method to uncorrupt my profile AND gamesavs all at once without having to manually do each save? (even though i dont even know how to do the saves yet... as the tut only really shows the profile)

also it mentions "This must be done each time hard drive is connected to a banned console. Its a bit of a pain but does make it so you can continue to get achievements on a banned console."
does this exclude a banned but uncrippled console?

I want to be able to switch my HDD between my banned(uncrippled) console and legit consoles(currently not LIVE- but will be in the near future) without corrupting profile/saves.... is this easily done?

sorry for the super long post...

this has all been covered in the UnCripple Thread... RTFM

[whopacha]

there were a few noob-ish questions in there i know... but i thought most were relevant....
anyways,...
everything seems to be working now.... uncorrupted the profile..... and all the saves seem to be alright now also.
although im not connecting this modded/notbanned console to live yet.... it doesnt read discs properly (even after swapping dvd drives?) so it will become my ixtreme LT LIVE test xbox... see if it gets banned... when ixtreme lt is released.

[marianxdq]

Worked for me with HDFR 1.03.