Print

[ste030]

yehh u can still dump the nand but you cant jtag

[warbeast]

or you could do this i guess to save alot of winhex

open nand in flashtool on the right look for secdata.bin write down the location for me 0x0296
add one to it in nandpro so
nandpro lpt: -r16 bad.bin 0x297 1
then open this file and zero it out save as good.bin
nandpro lpt: -w16 good.bin 0x297 1

worked for me

[thwack]

QUOTE(warbeast @ Nov 21 2009, 11:10 PM)

or you could do this i guess to save alot of winhex

open nand in flashtool on the right look for secdata.bin write down the location for me 0x0296
add one to it in nandpro so
nandpro lpt: -r16 bad.bin 0x297 1
then open this file and zero it out save as good.bin
nandpro lpt: -w16 good.bin 0x297 1

worked for me

Yep - worked on the one I just tested, did the hex heavy one for less 'shartability' so if it works for you, dandy

[AnimeCommander]

Thanks for all the work in translating and laying it out for us. Now I just need to dig up the instructions for dumping the NAND (cable creation and everything). Then my third box will be a little more sellable.

[wyldstallions]

if you can dump the nand and restore it to a previous version would that not revert it to an earlier version that you could jtag....


looks like I'm gonna get busy with me soldering iron

[thwack]

QUOTE(AnimeCommander @ Nov 22 2009, 12:26 AM)

Thanks for all the work in translating and laying it out for us. Now I just need to dig up the instructions for dumping the NAND (cable creation and everything). Then my third box will be a little more sellable.

Cable and dumping:

http://forums.xbox-s...howtopic=690493

Checking:

http://www.free60.org/Reading_out_NAND

Getting Degraded to work (you'll have to google for the 1BL number, and this is just for checking that the NAND dump is OK - when you save it in the Hex editor, don't overwrite your NAND, call it summit like Degnand.bin):

Degraded v1.1 won't open NAND files without the string "2004-2005 Micros... ect" at the begining of the hex.
Open the NAND file with Hex Workshop, look at the writing on the left - where it reads '2004-200X' if the X is a 5 you're fine and can open it in Degraded; if not highlight the X number, and type 5 then save the .bin. It'll open in Degraded (REMEMBER this is just to validate your dump, not part of the hex editing to get the Hard Drive functions back!)

QUOTE(wyldstallions @ Nov 22 2009, 12:27 AM)

if you can dump the nand and restore it to a previous version would that not revert it to an earlier version that you could jtag....
looks like I'm gonna get busy with me soldering iron

You can't downgrade the dash from the 8XXX version as of yet - you still require the CPU keys, which are unobtainable since that update. This just makes (as far as I'm aware) the pointer in the fubar'd NAND point to a blank table, and then default to the working non-fubar'd table

[DemisesAngel]

QUOTE(bannzzay @ Nov 21 2009, 07:09 AM)

From russian xbox forum (translated)

The HDD ban label is written in the NAND in the file secdata.bin.

NAND has a copy secdata.bin without ban label.

The goal is to force the xbox to use the old secdata.bin
 

Am I understanding this correctly? The old secdata.bin is still located somewhere in the nand? So having a pre-ban nand wouldn't matter as long as you can still dump the nand you have now?

[AnimeCommander]

QUOTE(thwack @ Nov 21 2009, 04:42 PM)

Cable and dumping:

http://forums.xbox-scene.com/index.php?showtopic=690493

Checking:

http://www.free60.org/Reading_out_NAND

Getting Degraded to work (you'll have to google for the 1BL number, and this is just for checking that the NAND dump is OK - when you save it in the Hex editor, don't overwrite your NAND, call it summit like Degnand.bin):

Degraded v1.1 won't open NAND files without the string "2004-2005 Micros... ect" at the begining of the hex.
Open the NAND file with Hex Workshop, look at the writing on the left - where it reads '2004-200X' if the X is a 5 you're fine and can open it in Degraded; if not highlight the X number, and type 5 then save the .bin. It'll open in Degraded (REMEMBER this is just to validate your dump, not part of the hex editing to get the Hard Drive functions back!)
You can't downgrade the dash from the 8XXX version as of yet - you still require the CPU keys, which are unobtainable since that update. This just makes (as far as I'm aware) the pointer in the fubar'd NAND point to a blank table, and then default to the working non-fubar'd table (IMG:style_emoticons/default/smile.gif)

Thanks boss. I found it anyway, but this gives me one thread to look up again when I get back from getting me the cable parts. I found this guide: http://forums.xbox-scene.com/index.php?showtopic=691873 I planned on using it for the proper solder points and pins. I'll also test a few saves and profiles to see if this takes care of those too. I'll report back if no one beats me to it.

[thwack]

QUOTE(AnimeCommander @ Nov 22 2009, 12:58 AM)

Thanks boss. I found it anyway, but this gives me one thread to look up again when I get back from getting me the cable parts. I found this guide: http://forums.xbox-s...howtopic=691873 I planned on using it for the proper solder points and pins. I'll also test a few saves and profiles to see if this takes care of those too. I'll report back if no one beats me to it.

Nice - cheers for the link Nice and neat! If you have trouble dumping the NAND (NANDPRO errors), use the switching diode in this piccy:

http://forums.xbox-s...p;#entry4523337

works a treat, pop it on the DB25 25-way male plug (with the black band 360 side), Maplin's part no: QL80B :

http://www.maplin.co...?moduleno=46386

24p - bargain

QUOTE(DemisesAngel @ Nov 22 2009, 12:51 AM)

Am I understanding this correctly? The old secdata.bin is still located somewhere in the nand? So having a pre-ban nand wouldn't matter as long as you can still dump the nand you have now?

Thats pretty much it - MS left in pre ban secdata tables (in case of update errors?)

[nemiers]

So can someone please write in clear noob language?

If I have 8955 update and got banned and dont have no nand backup,
this tut is still useless???

This post has been edited by nemiers: Nov 22 2009, 03:09 AM

[garyopa]

QUOTE(thwack @ Nov 21 2009, 08:24 PM)

Thats pretty much it - MS left in pre ban secdata tables (in case of update errors?)

M$ does not leavve the "pre-ban" in on purpose, it is just a side-effect of the nand software controller, all nand's use a function called wear-leveling, since flash have a limited life-span, you can only write to the same spots so many times before you get errors.

Because of that, when a new version of a often updated file is writted to the nand, it goes into another spot on the nand, and then the index table pointing to the files gets updated to point to the new location, and the old spot at some point will be overwritten once it enters the loop for usage by the wear-leveling index.

I am sure at some point M$ will update their nand software controller to next wipe out old versions left behind or force it to overwrite and not use the default wear-leveling, or decided to encrypt the file index pointing table values also with the cpukey.

As this "uncrippling" all tho most places charging for it are calling it "unbanning" is fast becoming the latest thing to charge money for.

Also note if you decide to test your network connection after doing this hexediting, you will end up needing to do this again or restore your nand backup, as M$ will see your 360 is using an outdated "secdata" and right away write the new one again with the "untrust'ed" content flag, which causes the hdd crippling feature.

[akirhol]

QUOTE(nemiers @ Nov 22 2009, 03:09 AM)

So can someone please write in clear noob language?

If I have 8955 update and got banned and dont have no nand backup,
this tut is still useless???

Yes you can still do this with the 8955 update. No you don't need a previous NAND backup.

Zeroing out the banned secdata.bin is something I hadn't thought of... force the 360 to revert back to a previous copy of secdata.bin ... makes sense, I mean that's what the previous ones are there for, backups in case an update fails. I was going to find the second most recent secdata.bin and inject it over the banned secdata.bin but now I see I won't have to.

Has anyone had a chance to test moving game saves and profiles to/from a 360 with the secdata reverted like this? I had considered buying two new xbox arcades because of the profile issue but if this fixes that as well, I'd be good with just a single new xbox for online play.

[dekochin]

ok ok ok I like what i read, but... what can I do with this? Would I be able to save and install games? and would there be any problems while changing the HDD to a non banned console?

This post has been edited by dekochin: Nov 22 2009, 04:32 AM

[akirhol]

QUOTE(dekochin @ Nov 22 2009, 04:32 AM)

ok ok ok I like what i read, but... what can I do with this? Would I be able to save and install games? and would there be any problems while changing the HDD to a non banned console?

You'll be able to install and play games on HDD like you could before the ban... don't know if anyone yet has tested moving saves/profiles between consoles yet after making this change. I'm hoping for a positive answer on that myself as well.

[majinsoftware]

Congrats, Thats pretty much the same method as mine.

Just one problem tho. Now that its public knowledge MS will be able to change it.
So you should have waited intill the ban wave had been over for a few weeks.

This post has been edited by majinsoftware: Nov 22 2009, 06:39 AM