so you want me to find a leak and dump using the tool? i hear its copyright and i shouldnt touch it due to risk of brick. if it can do the fwtool i can wait for release which shouldnt be too long. imma try dumping again and retrying the extraction.Hm. I've tried deliberately sabotaging my footer, and whether it's the console ID or CID that's screwed up, I only get error 1-2435-8325 from NO$GBA. I'm guessing that your NAND dump might be bad?
Have you tried taking several dumps and checking to make sure they match? If not, HxD has a great comparison feature (Analysis > File-compare > Compare...).
If you get multiple matching dumps, I'd double-check your wiring, or try dumping it through software means. Not that I advocate using leaked tools, but shutterbug2000's exploit ugopwn (Flipnote Studio) was leaked by the ever-so-subtle ryanrocks462, and does function with fwTool. (Even if you don't trust it to flash a NAND dump, you could use it to verify dumps taken via hardmod.)
I'm still unable to find what the error code means. I did, however, find someone complaining about the same error on actual hardware (scroll to the bottom).
Based on the DSiBrew page for the bootloader, I'd guess that it's an error related to parsing the filesystem?
According to the DSiBrew page, this is the boot process for Stage2 (the part of the boot process that is failing in NO$GBA):
Error 1-2435-8325 apparently means the MBR signature or type of the first partition are invalid (step 3).
Error 3-2435-8325 apparently means the DSi Menu's signature is invalid (step 5?).
So, I guess it stands to reason that 2-2435-8325 means there's a failure in step 4 or early step 5? If your CID or ConsoleID were bad, the MBR would be decrypted to garbage -- causing 1-2435-8325, and not 2-2435-8325...
(This is all conjecture; I could be horribly off-mark. )
--------------------- MERGED ---------------------------
also the weird thing is i got a properly decrypted file after getting a dsiware game moved and everything. so its not a cid + consoleid problem. also im not in that much a rush. as far as i can see theres not much in the dsi scene yet. afaik hbmenu cant even load above 2gb sdcard and only mounts read onlyHm. I've tried deliberately sabotaging my footer, and whether it's the console ID or CID that's screwed up, I only get error 1-2435-8325 from NO$GBA. I'm guessing that your NAND dump might be bad?
Have you tried taking several dumps and checking to make sure they match? If not, HxD has a great comparison feature (Analysis > File-compare > Compare...).
If you get multiple matching dumps, I'd double-check your wiring, or try dumping it through software means. Not that I advocate using leaked tools, but shutterbug2000's exploit ugopwn (Flipnote Studio) was leaked by the ever-so-subtle ryanrocks462, and does function with fwTool. (Even if you don't trust it to flash a NAND dump, you could use it to verify dumps taken via hardmod.)
I'm still unable to find what the error code means. I did, however, find someone complaining about the same error on actual hardware (scroll to the bottom).
Based on the DSiBrew page for the bootloader, I'd guess that it's an error related to parsing the filesystem?
According to the DSiBrew page, this is the boot process for Stage2 (the part of the boot process that is failing in NO$GBA):
Error 1-2435-8325 apparently means the MBR signature or type of the first partition are invalid (step 3).
Error 3-2435-8325 apparently means the DSi Menu's signature is invalid (step 5?).
So, I guess it stands to reason that 2-2435-8325 means there's a failure in step 4 or early step 5? If your CID or ConsoleID were bad, the MBR would be decrypted to garbage -- causing 1-2435-8325, and not 2-2435-8325...
(This is all conjecture; I could be horribly off-mark. )
--------------------- MERGED ---------------------------
it does have alot of 0's but im pretty sure thats normal. aint it?
--------------------- MERGED ---------------------------
plus i dont feel like pressing a button 122 times just to dump my nand :<
--------------------- MERGED ---------------------------
well. gonna try again.
dumping nand...