Print

[Strigy]

QUOTE(MadBoxer @ Nov 26 2010, 03:13 AM)

No, once you update your dash, the old nand dump is pretty much trash unless you have the CPU key. I know it doesn't help you now, but this is why it is important to backup the nand every time you update the dash.

thanks,  I'm going to keep playing with it over the weekend and see if i can get something to work, but it sounds like i might be out of luck.

[rzax2]

QUOTE(userix @ Nov 24 2010, 11:44 PM)

When and where are you getting the E79 error?  Did you actually attempt to zero fill and flash some of the secdata back and boot the console?  The absence of leading values you are referring to is the repeating "1F FB" that is suppose to show up at the beginning of the individually dumped secdata sector?

Yeah i attempedt zero-fills on some of the secdatas, and tried booting the console. E79 right away.  And yes, those are the leading values I am talking about missing.  I have given up for the time being but if i find anything out or get something working, Ill definitely let you know.

This post has been edited by rzax2: Nov 27 2010, 12:23 AM

[danthaman673]

QUOTE(userix @ Nov 24 2010, 10:33 AM)

Is it only flagged offline? Mine is flagged and it is not crippled, I can still use my save games and play other games that are non-AP2.5.  I was thinking of trying to restore an old secdata.bin using the guides posted in this forum, but thought about the same problem you have encountered with all the timestamps being the same due to the system being offline and not able to obtain the real time.  

Is the secdata.bin dashboard specific?  I thought it was only the encrypted x-value, which is independent of dashboard versions.  But even then, wouldn't there be at least one secdata.bin instance that was created from installing the new dash update?

In theory, couldn't you back up your NAND, and then try zero-filling all instances of secdata.bin except one to see if that can restore the xval back to the clean state?  And then repeat all possible combinations to see if one will restore secdata to clean state?  Since zero-filling all instances of secdata.bin except one, would force the xbox to restore the only secdata.bin instance that wasn't zero-filled.  Someone please correct me if my logic is incorrect.

rzax2, can you post your findsecdata output?  I want to see what exactly it looks like in your case.

 A couple of things occurred to me whilst reading ur posts:

1st of all: (I think this may have been tried before but..) You could try searching for the Xval (In it's hex value) of the banned and then zeroing (If it worx, it may only work for UserIX type situation)

2nd How do you have all the exact same dates?? (Internal battery fized perhaps? seems odd for an xbox but I have seen this in many older PC's etc..) But if that is indeed the case you could perhaps Try doctoring the dates and seeing what happens, you would have to make a variation for each unique secdata (10 at the most???)

3rd Are you guys absolutely syre ur using the latest version of  findsecdata I have a feeling earlier versions had a bugs like the above, I think some may have even written a newer (better) version (I can't recall) Also have you tried Nand Healer?? I know it's all a bit daunting but keep at it (I promise to do some research in this area when I get the time to do it properly)

And remember: You can uncripple most dashes just by updating (at least for the most part - I'm still not 100% on there being 126111 offline crippling as now that I think of it I haven't actually heard from some1 who has had it happen to memory)
 

Also (Just to be clear) When you are testing, go by the dash Xval, not corruption as all ur profiles etc.. will need to be unflagged on a PC with Le Fluffie once you have uncrippled


I am starting to get worried that M$ have maybe included something to prevent us uncrippling in this manner (Hope not, but it would make sense)

Like I said I'll get back to you guys, Hopefully this coming week (We're not done yet!)


 

[userix]

As for the time issue, the xbox actually doesn't keep time when the system is turned off, guess they don't have battery backup inside.  Since our systems are strictly offline, there is no way for it to get the right time from xbox live, so it keeps restarting to a preset time/date, as shown in rzax2's post.  Normally, the system gets the time everytime it is turned on and connected to xbox live.

[Strigy]

here is what i get when i try findsecdata.  i also tried to zero 21b, but when i check the xval it shows as secdata invalid.  i then tried zeroing all secdata except for 345 but then the xbox boots with 1 red light and E79.  i really don't know what else can be done, nothing i try is working for me.  The only thing i can think of at this point is, i have a non modified xbox that i can dump the nand on and maybe try taking a valid secdata from that. does anyone know if that will work? or is it tied to the console?

findsecdata v0.61 2009-12-01 by boby2pc
Controller version 1
Last filetable change: 0x42
ECC change: 0x42 Filetbl: 0x021B Secdata: 0x021A Timestamp: 3376602F 2005-11-22
ECC change: 0x40 Filetbl: 0x0218 Secdata: 0x0348 Timestamp: 33766001 2005-11-22
ECC change: 0x3D Filetbl: 0x0054 Secdata: 0x0348 Timestamp: 33766001 2005-11-22
ECC change: 0x36 Filetbl: 0x0345 Secdata: 0x03A0 Timestamp: 3B5CA60D 2009-10-28

Checking secdata:
0348 containts not 0 values above offset 1024
0348 containts not 0 values above offset 1024
03A0 containts not 0 values above offset 1024

Searching for recommended

Extracting secdata:
secdata021A.bin

Extracting filetables:
filetable021B.bin

Creating patched secdata:
Patchedsecdata021A.bin

Creating patched filetables:
Patchedfiletable021BBy021B.bin

Use:

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

Press ENTER

[illegaloperation]

I stumbled across this thread because I have the same issue. Accidentally tried to run NFS before the firmware was updated on one of my boxes here and got the AP 2.5 flag.

I dumped my nand several times, and in Hex Workshop I have exactly 12 instances of secdata.bin. 11 of them have the same exact date code of 3D 75 0A 9C but the 3rd to last one is different, it has a date code of 33 76 60 13.

I was going to try zeroing them but before I did I searched first and found this topic. I most defiantly don't want no error code 79 because I had to dump my nand via LPT and I got a lot of errors. BUT the same errors on each dump.

Im afraid if my experiment goes array I will have issues restoring my nand.

Looks like Microsoft got us this go around with the nand   .

Im gonna keep this 360 off because it's just a spare and hope that someone smarter than me can figure a way. It can just stay an offline spare box but I can't stand having something borked  



Edit: I used FindSecData after seeing this thread and wrote back the dumps it told me and all is fine. My X Val is no longer flagged. It wrote 2 files.

Yippee

[userix]

QUOTE(illegaloperation @ Nov 29 2010, 02:46 PM)

I stumbled across this thread because I have the same issue. Accidentally tried to run NFS before the firmware was updated on one of my boxes here and got the AP 2.5 flag.

I dumped my nand several times, and in Hex Workshop I have exactly 12 instances of secdata.bin. 11 of them have the same exact date code of 3D 75 0A 9C but the 3rd to last one is different, it has a date code of 33 76 60 13.

I was going to try zeroing them but before I did I searched first and found this topic. I most defiantly don't want no error code 79 because I had to dump my nand via LPT and I got a lot of errors. BUT the same errors on each dump.

Im afraid if my experiment goes array I will have issues restoring my nand.

Looks like Microsoft got us this go around with the nand  (IMG:style_emoticons/default/ohmy.gif) .

Im gonna keep this 360 off because it's just a spare and hope that someone smarter than me can figure a way. It can just stay an offline spare box but I can't stand having something borked  (IMG:style_emoticons/default/grr.gif)
Edit: I used FindSecData after seeing this thread and wrote back the dumps it told me and all is fine. My X Val is no longer flagged. It wrote 2 files.

Yippee

In your case, was your console ever connected online?  Was it only flagged offline?  Also, which Findsecdata version did you use?  can you post the output of the findsecdata results that worked for you?  Did secdata give you this message:

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

This post has been edited by userix: Dec 2 2010, 03:34 AM

[onlyXMan]

rzax2: you have good secadata.bin at block 0138 and You are rescued
Strigy: your all secdata.bins are overwritten, sorry

[userix]

QUOTE(onlyXMan @ Dec 2 2010, 12:37 PM)

rzax2: you have good secadata.bin at block 0138 and You are rescued
Strigy: your all secdata.bins are overwritten, sorry

How do you know rzax2 secdata at 0138 is good?  His FindSecdata results came back negative.  Did you manually scan his  nand dump?  He said he couldn't find any good secdata himself.

[onlyXMan]

findsecdata log will tell you

[Strigy]

QUOTE(onlyXMan @ Dec 2 2010, 04:37 PM)

rzax2: you have good secadata.bin at block 0138 and You are rescued
Strigy: your all secdata.bins are overwritten, sorry

thanks guys for all your input and help.  this is kinda what i figured anyway. a little annoying but nothing i can do about it.  thanks.

[userix]

QUOTE(onlyXMan @ Dec 3 2010, 03:07 AM)

findsecdata log will tell you

 

Check rzax2's post:  his findsecdata finds nothing, but you said 0138 is good?

[userix]

Finally got around dumping my nand.  Here is my result from findsecdata:

C:\nandpro_20d_drivers\test>FindSecData.exe orig2.bin -vts -vft

findsecdata v0.62 2009-12-09 by boby2pc
Controller version 1
Last filetable change: 0x4E
ECC change: 0x4E Filetbl: 0x01C3 Secdata: 0x01C2 Timestamp: 33766049 2005-11-22 12:02:18 PM
ECC change: 0x4C Filetbl: 0x01C0 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x4B Filetbl: 0x03B6 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x49 Filetbl: 0x03B3 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x48 Filetbl: 0x0226 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x47 Filetbl: 0x0225 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x46 Filetbl: 0x0224 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x42 Filetbl: 0x021A Secdata: 0x0378 Timestamp: 33766001 2005-11-22 12:00:02 PM

Checking secdata:
021D containts not 0 values above offset 1024 or zeros below 1024 (overwritten)
021D containts not 0 values above offset 1024 or zeros below 1024 (overwritten)
0378 containts not 0 values above offset 1024 or zeros below 1024 (overwritten)

Searching for recommended

Extracting secdata:
secdata01C2.bin

Extracting filetables:
filetable01C3.bin

Creating patched secdata:
Patchedsecdata01C2.bin

Creating patched filetables:
Patchedfiletable01C3By01C3.bin

Use:

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

Press ENTER



Guess I am SOL, like Strigy.


Another side question:  

I don't have a second console and was wondering if there is anyway to check if my save games/profile are corrupted? I tried opening my profile using Hash block calculator, but its giving me an error saying it can't open it. When I open it using con flag remover just to check, the flagged area is all 0's. I know transferring the saves and profile to another console is the fastest way to check for profile corruption. Also, I notice some of my savegames won't open in hash block calculator either.  Since system is always kept offline, it has never been banned.

[danthaman673]

QUOTE(userix @ Dec 6 2010, 11:03 AM)

Finally got around dumping my nand.  Here is my result from findsecdata:

C:\nandpro_20d_drivers\test>FindSecData.exe orig2.bin -vts -vft

findsecdata v0.62 2009-12-09 by boby2pc
Controller version 1
Last filetable change: 0x4E
ECC change: 0x4E Filetbl: 0x01C3 Secdata: 0x01C2 Timestamp: 33766049 2005-11-22 12:02:18 PM
ECC change: 0x4C Filetbl: 0x01C0 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x4B Filetbl: 0x03B6 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x49 Filetbl: 0x03B3 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x48 Filetbl: 0x0226 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x47 Filetbl: 0x0225 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x46 Filetbl: 0x0224 Secdata: 0x021D Timestamp: 33766001 2005-11-22 12:00:02 PM
ECC change: 0x42 Filetbl: 0x021A Secdata: 0x0378 Timestamp: 33766001 2005-11-22 12:00:02 PM

Checking secdata:
021D containts not 0 values above offset 1024 or zeros below 1024 (overwritten)
021D containts not 0 values above offset 1024 or zeros below 1024 (overwritten)
0378 containts not 0 values above offset 1024 or zeros below 1024 (overwritten)

Searching for recommended

Extracting secdata:
secdata01C2.bin

Extracting filetables:
filetable01C3.bin

Creating patched secdata:
Patchedsecdata01C2.bin

Creating patched filetables:
Patchedfiletable01C3By01C3.bin

Use:

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

Press ENTER
Guess I am SOL, like Strigy.
Another side question:  

I don't have a second console and was wondering if there is anyway to check if my save games/profile are corrupted? I tried opening my profile using Hash block calculator, but its giving me an error saying it can't open it. When I open it using con flag remover just to check, the flagged area is all 0's. I know transferring the saves and profile to another console is the fastest way to check for profile corruption. Also, I notice some of my savegames won't open in hash block calculator either.  Since system is always kept offline, it has never been banned.

[userix]

QUOTE(danthaman673 @ Dec 6 2010, 09:04 AM)

Upload me a link and I'll check 4u

You want a copy of my nand dump bin file?  I can get it to you at the end of the week, I don't have the bin files with me right now.  But findsecdata results looks like I'm SOL.