Post by: GOTitCUZiMODDED on August 20, 2011, 06:59:00 PM
I used to painfully read the nand with an LPT port, which was like waiting in purgatory. Now that I'm trying to do this 256MB nand with USB, it still seems painfully as long but not as bad. Mainly my question is whether I really do need to read out the whole 256MB of the nand or is it possible to read out a smaller increment since I doubt it's important to backup the storage partition of said nand?
I've read out the whole 256MB about 10 times and when I try to compare each read against another, I seem to get between 8 to about 57 mismatches. I should point out that there are a couple of them that are error 250, which I know is a valid bad block. One other read gave me error 204, 300, and a few sparatic error 0's so I know those reads can be disregarded and I'll just reread again. I understand that it's normal that there are all sorts of bad blocks in the [memory card] storage partition of the nand which i'm sure is contributing to the large amount of non-mismatching blocks i'm getting between comparing these multiple nand reads.
Those mismatches alone are the reason why I choose not to try to continue further at this moment and am looking for some help as to know the true size of the 256MB Jasper's nand and if I will be better off reading the actual nand size (which I believe is 64MB?) or should I try to read the whole 256MB nand till I find 2 reads with the minimal amount of mismatches (which hopefully are just in the storage partition, with the exception of any valid Error 250 at the same spots within different reads).
The best read that I've gotten so far is one that gave me the first Error 250 @ 0x001929 and then some Error 0's @ 0x001CE6, 0x001CE7, 0x001CE8 (which I hope is the unimportant storage partition). Is the block @ 0x001929 past the actual nand size and therefore, inside the the extra memory partition or not?
I've tried to be as detailed as possible and if anyone who's stayed with me reading this far, I truly do appreciate you taking the time to hear me out and would appreciate even more, any help or insight into helping me set up this Jasper correctly. Thanks!
Post by: boflc on August 21, 2011, 02:05:00 PM
CODE
nandpro usb: -r64 nand1.bin
nandpro usb: -r64 nand2.bin
fc /b nand1.bin nand2.bin
nandpro usb: -r64 nand2.bin
fc /b nand1.bin nand2.bin
Post by: GOTitCUZiMODDED on August 21, 2011, 09:39:00 PM
QUOTE(boflc @ Aug 21 2011, 03:05 PM) 
either:
-r64 output.bin
or
-r256 output.bin 0 0fff
will grab just the system file area as well as the reserved area. bad blocks up in the "memunit" area are just skipped, so there's really no value in dumping anything about 64mb+reserved.
that said:
you've got a messload of mismatches. 250's should be marked as 0's and as a result you shouldn't have an issue with mismatches with those blocks. if you don't have consistent reads across multiple system file area reads, don't move forward. check your soldering.
tldr, just:
CODE
nandpro usb: -r64 nand1.bin
nandpro usb: -r64 nand2.bin
fc /b nand1.bin nand2.bin
nandpro usb: -r64 nand2.bin
fc /b nand1.bin nand2.bin
Hell yeah buddy! Thank you so much for your feedback bro, it is greatly appreciated! I'll use your pointers and look forward to reporting a good outcome. I have 3 more Jaspers to pick up this week and look forward to using the knowledge I gain from this BB jTag process on those (2 of which I believe are 512MB BB's!). Although my current USB nand reader has been reliable this past 1.5 years with Xenons, Falcons and Zephyrs, I do recall doing more reads than necessary. I will replace the wiring with a thicker guage and shorten it up to hopefully eliminate the need to do more reads than necessary. Will post back results!
Post by: GOTitCUZiMODDED on August 24, 2011, 01:48:00 AM
Post by: boflc on August 24, 2011, 10:59:00 AM
glad you got it sorted, but i would guess that you had a bridge/loose solder strand/loose wire strand/solder splash somewhere that was interfering.
literally.
using a maximus 360nandflasher, a team-x nand-x, and a diygadget usb spi flasher, i have never had mismatched reads. (ftr, that doesn't mean i don't read multiple times to make sure of this)
yes, i just knocked on wood, but i don't think i'm doing anything special beyond being careful and visually inspecting every nand r/w point before reading or writing. given, everyone makes mistakes and arrogance can lead to regret; but this careful inspection has caught a loose wire strand a few times before it caused any problems.