Gaming dsi version data

[MarioMasta64]

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. )

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.

--------------------- MERGED ---------------------------

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. )

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 only

--------------------- 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...

 

[Friendsxix]

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.

In terms of brick risk, Robz8 mentioned that it can't brick consoles. EDIT: Actually, I'm not sure that's referring to ugopwn. Disregard that (though if you're only reading the NAND, I doubt it could do any harm anyways...)
In terms of copyright, that is a valid concern. Under US copyright law (as far as I know), all creative works are considered copyrighted without any formal filing from the creator. So technically, yes -- the exploit is copyrighted.

I would suggest against it from a moral perspective, but it would be an easy way to verify your hardmod's wiring. If taking several dumps via hardmod yield identical dumps that still don't boot, and your wiring looks good, it could be worth a shot.

And yes, the over-abundance of 00s is normal.

(And 122 times is a lot. e_e)

If your NAND is only corrupted enough to prevent it from booting, it is possible that you could be able to still extract some information from the dump. PC extraction tools might be less picky than the DSi itself.

 

[MarioMasta64]

In terms of brick risk, Robz8 mentioned that it can't brick consoles. EDIT: Actually, I'm not sure that's referring to ugopwn. Disregard that (though if you're only reading the NAND, I doubt it could do any harm anyways...)
In terms of copyright, that is a valid concern. Under US copyright law (as far as I know), all creative works are considered copyrighted without any formal filing from the creator. So technically, yes -- the exploit is copyrighted.

I would suggest against it from a moral perspective, but it would be an easy way to verify your hardmod's wiring. If taking several dumps via hardmod yield identical dumps that still don't boot, and your wiring looks good, it could be worth a shot.

And yes, the over-abundance of 00s is normal.

(And 122 times is a lot. e_e)

If your NAND is only corrupted enough to prevent it from booting, it is possible that you could be able to still extract some information from the dump. PC extraction tools might be less picky than the DSi itself.

hmm...

--------------------- MERGED ---------------------------

dump complete. moving files to pc. also using flipnote studio as basegame for --basename=FlipnoteStudio TitleID.bin cause dsi shop is dead and i cant find any other titles to dump

--------------------- MERGED ---------------------------

getting consoleid: dsi_srl_extract.exe --basename=FlipnoteStudio 4B475545.bin

 

[Friendsxix]

hmm...

Any way you slice it, the error you're getting is very bizarre to not be documented on DSiBrew.

dump complete. moving files to pc. also using flipnote studio as basegame for --basename=FlipnoteStudio TitleID.bin cause dsi shop is dead and i cant find any other titles to dump

That should be fine. Any title should provide you a valid ConsoleID, though I'm almost positive that your CID and ConsoleID are correct, based on your Bootloader error.

 

[MarioMasta64]

unexcpected bannersave elength but i still got my valid footer

--------------------- MERGED ---------------------------

i know for sure my cid is right so ill skip that.

--------------------- MERGED ---------------------------

alright nand is decrypted succesfully. time to open it in ofsmount or whatever its called. partition 0 the ~200mb drive

--------------------- MERGED ---------------------------

now to mount and copy the folders as per downgrade instructions (with the addition of version data)

--------------------- MERGED ---------------------------

as to show im using the right part

--------------------- MERGED ---------------------------

also i made up a backup using that leaked exploit as per your advice and the nand dumps are the same. so perhaps its how i did something with mounting and changing files.

 

[Friendsxix]

also i made up a backup using that leaked exploit as per your advice and the nand dumps are the same. so perhaps its how i did something with mounting and changing files.

Well, at least that 100% rules out the wiring of your hardmod. Still doesn't explain why a clean NAND doesn't boot in NO$GBA, though...

 

[MarioMasta64]

Well, at least that 100% rules out the wiring of your hardmod. Still doesn't explain why a clean NAND doesn't boot in NO$GBA, though...

unmounting drive now. i should rencrypt it and add the footer now correct?

 

[Friendsxix]

unmounting drive now. i should rencrypt it and add the footer now correct?

Yep.

 

[MarioMasta64]

Yep.

reencrypted:

 

[Friendsxix]

reencrypted: View attachment 94561

Oops, that might be your mistake -- you didn't add the --encrypt flag to the end!

 

[MarioMasta64]

now with the footer. its AAAAAAAA forward and BBBBBBB backward. correct? so 12 34 56 would be 56 34 12

--------------------- MERGED ---------------------------

Oops, that might be your mistake -- you didn't add the --encrypt flag to the end!

lmao wut

--------------------- MERGED ---------------------------

is this better?

 

[Friendsxix]

now with the footer. its AAAAAAAA forward and BBBBBBB backward. correct? so 12 34 56 would be 56 34 12

--------------------- MERGED ---------------------------


lmao wut

Yep. Your command should have been:

twltool nandcrypt --cid XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --consoleid XXXXXXXXXXXXXXXX --in NAND_DEC_MOD.bin --out dsi_nand_mod.bin --encrypt

Try that, and see if it fixes anything.

 

[MarioMasta64]

also guide never specified --encrypt:

--------------------- MERGED ---------------------------

also:

 

[Friendsxix]

also guide never specified --encrypt:View attachment 94564

--------------------- MERGED ---------------------------

also: View attachment 94565

Oops, you're right -- I'm thinking of syscrypt. *Facepalm*
You did paste the command twice, though. Try fixing that?

 

[MarioMasta64]

it keeps saying "decrypt done"

 

[Friendsxix]

it keeps saying "decrypt done"

Yeah, that sounds wrong. I noticed that you're using a particularly old version of TWLTool. Try updating from 1.1 to 1.6?

 

[MarioMasta64]

Yeah, that sounds wrong. I noticed that you're using a particularly old version of TWLTool. Try updating from 1.1 to 1.6?

also:

--------------------- MERGED ---------------------------

especially since dec_nand is full of data:

--------------------- MERGED ---------------------------

 

[Friendsxix]

also: View attachment 94566

The bytes turning into question marks typically means that HxD lost access to a file that was open -- perhaps it was moved, or a program took control of it?

 

[MarioMasta64]

The bytes turning into question marks typically means that HxD lost access to a file that was open -- perhaps it was moved, or a program took control of it?

ah. ill try again.

--------------------- MERGED ---------------------------

AYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY:

--------------------- MERGED ---------------------------

time to append footer and test in no$gba

 

[Friendsxix]

ah. ill try again.

--------------------- MERGED ---------------------------

AYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY: View attachment 94569

--------------------- MERGED ---------------------------

time to append footer and test in no$gba

Even if it works in NO$GBA, you might wish to redo everything from the original NAND dump with TWLTool 1.6, as apparently old versions destroyed some data:

v1.6 - 5/25/2016
-CID and consoleID can now be loaded from files (just pass a filename instead of a hex ID)
-TWL decryption now decrypts MBR and partitions (copying the rest) instead of annhilating unencrypted parts
-3DS consoleID bruteforce is slightly faster and supports exporing ID to file on completion
-System file crypto should support 3DS now

(Italics added for emphasis)