Elberethz
Newbie

Posts: 1
|
 |
« Reply #240 on: November 29, 2009, 10:25:07 AM » |
|
Thanks boby2pc for your tool. I successfully uncrippled the HDD of my Xbox 360 thanks to NandPro & your tool.  Just for info: - Used LPT connection on my Gigabyte GA-G31-S2L (setting SPP). I first tried with the 100 Ohm resistors but it wouldn't work, removing them did the job. Parallel cable was 5m. - Console had 16MB flash (I think it is the model just before the Jasper, as I bought it just before the Jasper came out) - I use a modified Western Digital HDD 250GB. Installing games on the hard disk is the thing I missed most on my banned console. Back to business! Thanks again to all who made this possible!
|
|
|
|
« Last Edit: November 29, 2009, 10:30:03 AM by Elberethz »
|
Logged
|
|
|
|
|
jz_5_3
|
 |
« Reply #241 on: November 29, 2009, 10:54:05 AM » |
|
well, the chance for you to recover it is close to 0. you only have one valid copy of secdata.bin which is the banned one. You have several versions of filesystem, from B7 to C1 and C5. however, versions from C2 to C4 are missing (overwritten?). You probably need the one in C4 to replace the one in C5. Does anyone mind taking a look at mine? Whenever I replace the latest secdata (00c545d0, 3b 66 bd f9 , 02fd) it boots up to a "update failed" page with pv 0.0.0.0 and cv 2.0.8955.0....... http://www.mediafire.com/?mzmj2yohznjThanks! As Application displayed both old secdata sectors are overwritten. I checked it manually and there is something which is not secdata.bin. Yesterday someone have similar in that place. It looks like clock time settings, but I'm not sure. Check it at $9b*$4200 = $27f600 Sorry, What does that mean for my chances of uncrippling then? Is there anything I can try replacing? [/quote
|
|
|
|
|
Logged
|
|
|
|
|
boby2pc
|
 |
« Reply #242 on: November 29, 2009, 11:21:40 AM » |
|
Sorry, What does that mean for my chances of uncrippling then? Is there anything I can try replacing?
No (in my opinion), but You could try if You wish.
|
|
|
|
|
Logged
|
|
|
|
|
boby2pc
|
 |
« Reply #243 on: November 29, 2009, 11:32:04 AM » |
|
nazster, I sent You PM, please try it and send feedback
|
|
|
|
|
Logged
|
|
|
|
pumauk
Newbie

Posts: 3
|
 |
« Reply #244 on: November 29, 2009, 11:37:49 AM » |
|
well, the chance for you to recover it is close to 0. you only have one valid copy of secdata.bin which is the banned one. You have several versions of filesystem, from B7 to C1 and C5. however, versions from C2 to C4 are missing (overwritten?). You probably need the one in C4 to replace the one in C5. Does anyone mind taking a look at mine? Whenever I replace the latest secdata (00c545d0, 3b 66 bd f9 , 02fd) it boots up to a "update failed" page with pv 0.0.0.0 and cv 2.0.8955.0....... http://www.mediafire.com/?mzmj2yohznjThanks! As Application displayed both old secdata sectors are overwritten. I checked it manually and there is something which is not secdata.bin. Yesterday someone have similar in that place. It looks like clock time settings, but I'm not sure. Check it at $9b*$4200 = $27f600 Sorry, What does that mean for my chances of uncrippling then? Is there anything I can try replacing? [/quote Sorry, could you explain a bit simpler for me? Why would I not have C2 / C4? If M$ release a new version of the dashboard could I not remove my current secdata and then use an update disc to create a new one?
|
|
|
|
|
Logged
|
|
|
|
|
dak
|
 |
« Reply #245 on: November 29, 2009, 12:00:45 PM » |
|
ECC change: 0x82 Filetbl: 0x039B Secdata: 0x039A Timestamp: 3B6D4DEB 2009-11-12 ECC change: 0x79 Filetbl: 0x00E7 Secdata: 0x0100 Timestamp: 3B3ABBCA 2009-09-23
Checking secdata: 0100 containts not 0 values above offset 1024
...
Ran findsecdata with -ocs and tried it (replacing 39b with 0e7) I extracted all secdata.bins (0e5, 0e7, 3ab, 3ac, 3ad, 3ae) and put some on 39b, with -w16. Didnt write down which  before i went for some beer. Ill just put this aside now for some time, restored my original nand like 5 times today (E71). boby2pc if you are lucky with nazster's problem (which is similar to mine), it would be great if u can look in mine too. Edit: answer to post under this: ah ok guess i didnt read all of nazster's posts, guess ill wait if some1 finds out how to change the banned secdata
|
|
|
|
« Last Edit: November 29, 2009, 12:07:45 PM by dak »
|
Logged
|
|
|
|
|
boby2pc
|
 |
« Reply #246 on: November 29, 2009, 12:04:47 PM » |
|
ECC change: 0x82 Filetbl: 0x039B Secdata: 0x039A Timestamp: 3B6D4DEB 2009-11-12 ECC change: 0x79 Filetbl: 0x00E7 Secdata: 0x0100 Timestamp: 3B3ABBCA 2009-09-23
Checking secdata: 0100 containts not 0 values above offset 1024
...
Ill just put this aside now for some time, restored my original nand like 5 times today (E71). boby2pc if you are lucky with nazster's problem (which is similar to mine), it would be great if u can look in mine too. Your problem is different. You have old secdata overwritten and it's not possible to restore HDD functionality. Nazster has a couple of secdata.bin copies in his NAND, but problem with large block NAND controller.
|
|
|
|
|
Logged
|
|
|
|
rafaelbf
Newbie

Posts: 4
|
 |
« Reply #247 on: November 29, 2009, 06:36:44 PM » |
|
Hi boby2pc I have the same problem here, like nazster (large block size?) I have a 512MB flash. D:\nandpro>NandPro.exe lpt: -r512 nand.bin NandPro v2.0 by Tiros
Testing LPT device address:0378 Using LPT device at address:0378 FlashConfig:00AA3020 512MB Nand Detected Starting Block:0x000000 Ending Block:0x007FFF Press any key to begin reading nand Error: 250 reading block 5D8 Error: 250 reading block E08 Error: 250 reading block 2420 7FFF
------------------------
findsecdata v0.4 2009-11-26 by boby2pc Controller version 2 Last filetable change: 0xFF ECC change: 0xFF Filetbl: 0x01C1 Secdata: 0x0328 Timestamp: 3B71BCCB 2009-11-17
Checking secdata: 0328 containts not 0 values above offset 1024
Searching for recommended
Extracting secdata:
Extracting filetables:
Creating patched filetables:
Use:
Old secdata.bin not found. Console might be not banned, already patched or secda ta.bin overwritten.
findsectdata 0.42 hangs: Exception EInvalidOp in module FindSecData.exe at 00007830. Invalid floating point operation. Here is my dump: (passwd=nand99) (removed) Thanks For some reason I am getting this message and I just can't install any game on harddrive 
|
|
|
|
« Last Edit: December 05, 2009, 09:05:33 AM by rafaelbf »
|
Logged
|
|
|
|
|
boby2pc
|
 |
« Reply #248 on: November 29, 2009, 07:39:50 PM » |
|
I have the same problem here, like nazster (large block size?)
yes, this is the problem for now. I sent You PM, please check it and give feedback.
|
|
|
|
|
Logged
|
|
|
|
Scarpa
Newbie

Posts: 8
|
 |
« Reply #249 on: November 29, 2009, 11:25:34 PM » |
|
I have the same problem where FindSecData says "Old secdata.bin not found. Console might be not banned, already patched or secdata.bin overwritten." All the time stamps have the same date, 08/22/05. Any chance of recovery or am I SOL?
|
|
|
|
|
Logged
|
|
|
|
|
dgx
|
 |
« Reply #250 on: November 30, 2009, 12:22:36 AM » |
|
i aint sure if this is ok but i am getting these errors on my first dump of my nand
Testing LPT device address:0378 Using LPT device at address:0378 FlashConfig:008A3020 256MB Nand Detected Starting Block:0x000000 Ending Block:0x003FFF Press any key to begin reading nand Error: 250 reading block f78 Error: 210 reading block f79 Error: 210 reading block f7a Error: 210 reading block f7b Error: 210 reading block f7c Error: 210 reading block f7d Error: 210 reading block f7e Error: 210 reading block f7f Error: 250 reading block 2498 Error: 210 reading block 2499 Error: 210 reading block 249a Error: 210 reading block 249b Error: 210 reading block 249c Error: 210 reading block 249d Error: 210 reading block 249e Error: 210 reading block 249f Error: 250 reading block 3360 Error: 210 reading block 3361 Error: 210 reading block 3362 Error: 210 reading block 3363 Error: 210 reading block 3364 Error: 210 reading block 3365 Error: 210 reading block 3366 Error: 210 reading block 3367 3FFF didnt get any errors when i dump my sons 16mb nand so i bit stump as to let it carry on doing the 2nd dump of it
second dump so far
Testing LPT device address:0378 Using LPT device at address:0378 FlashConfig:008A3020 256MB Nand Detected Starting Block:0x000000 Ending Block:0x003FFF Press any key to begin reading nand
Error: 250 reading block f78 Error: 210 reading block f79 Error: 210 reading block f7a Error: 210 reading block f7b Error: 210 reading block f7c Error: 210 reading block f7d Error: 210 reading block f7e Error: 210 reading block f7f
then it carrys on as norm no errors
thanks
|
|
|
|
« Last Edit: November 30, 2009, 01:03:45 AM by dgx »
|
Logged
|
|
|
|
|
cory1492
|
 |
« Reply #251 on: November 30, 2009, 01:19:45 AM » |
|
Error: 250 reading block f78 Error: 210 reading block f79 Error: 210 reading block f7a Error: 210 reading block f7b Error: 210 reading block f7c Error: 210 reading block f7d Error: 210 reading block f7e Error: 210 reading block f7f
then it carrys on as norm no errors
thanks
You would get 8 errors on a single bad block with 256/512 NAND as the blocks are technically 8 small blocks being read by nandPro. Something to try when you see this, unplug everything from the console (lpt from pc, video, power - basically resets everything) and plug it all back in and then, for example: nandpro lpt: -r256 f78dump.bin f78 8 If redump of the same block after hard reset produces same error it's a very good bet it is a (which is entirely normal) bad block. If you check that single block dump with a hex editor, a manufacturers bad block (not the only kind) should be filled with 0x00's; I'm not sure how the spare data looks on such a NAND dump with nandpro but in a 16M dump the first 512bytes are user data, the next 16 are spare data - the bad block mark on 16M dumps is the 6th byte of spare data of either of the first two spares of the block being anything but 0xFF (this is when the bad block is found long after manufacture, the user data area is unreliable and can still contain anything, but the block gets marked as such, bad.)
|
|
|
|
« Last Edit: November 30, 2009, 03:34:56 AM by cory1492 »
|
Logged
|
|
|
|
|
dgx
|
 |
« Reply #252 on: November 30, 2009, 02:02:40 AM » |
|
redump of the same block after reset gives me the same error and checked with hex editor with and is all 00's
|
|
|
|
|
Logged
|
|
|
|
|
boby2pc
|
 |
« Reply #253 on: November 30, 2009, 03:17:20 AM » |
|
redump of the same block after reset gives me the same error and checked with hex editor with and is all 00's
Hi, corry1492 is absolutly right about that bad blocks. In jaspers there are large blocks which constists of 8 small blocks, so it's only one bad block. Byte on which You could recognise bad block is $201 byte of large block (all good are $ff). Continue the second dump and compare both images when finished.
|
|
|
|
|
Logged
|
|
|
|
|
dgx
|
 |
« Reply #254 on: November 30, 2009, 03:22:18 AM » |
|
ok i start the second dump of again another 15 hour lmao thahks guys
|
|
|
|
|
Logged
|
|
|
|
|
boby2pc
|
 |
« Reply #255 on: November 30, 2009, 03:31:46 AM » |
|
I have the same problem where FindSecData says "Old secdata.bin not found. Console might be not banned, already patched or secdata.bin overwritten." All the time stamps have the same date, 08/22/05. Any chance of recovery or am I SOL?
So far there are many reasons why old secdata is overwritten. Usually there is large DASH update and some games like fifa10 or assassin creed 2 (for example) writes many changes to NAND filesystem. Only on two images there was something really strange like temporary regional settings, but it's really strange that was written to the filesystem.
|
|
|
|
« Last Edit: November 30, 2009, 05:27:12 AM by boby2pc »
|
Logged
|
|
|
|
|
boby2pc
|
 |
« Reply #256 on: November 30, 2009, 12:50:05 PM » |
|
|
|
|
|
|
Logged
|
|
|
|
|
dgx
|
 |
« Reply #257 on: November 30, 2009, 01:39:34 PM » |
|
i give the new 1 a try once my second dump is done 
|
|
|
|
|
Logged
|
|
|
|
|
dgx
|
 |
« Reply #258 on: November 30, 2009, 02:47:30 PM » |
|
i get use : old secdata.bin not pound.console might not be banned,already patch or secdata.bin overwritten
i know i am banned it woz the 7th,i aint patch it yet,hope mine aint able to get hdd back i ave got my sons sorted,and even my step sons but mine is going to be the sob that i cant coz it the jasper 256 lol mind as long as i got 2 sorted thats wot matters to me..
time out 4 me i want a dime bar lmao
|
|
|
|
|
Logged
|
|
|
|
|
|
|