Hey so the new firmware update just came out, and you might or might not be able to hack your system when you get it back... You might want to reconsider sending it off to Nintendo, because they'll almost definitely update it.
Hacking [Q] Error on boot followed by strange brick
- Thread starter Deleted member 310901
- Start date
- Views 10,824
- Replies 120
Have you even restored the 9.2 NAND? If so, and it still errors out, then I'm out of ideas. You might want to hold back on sending it off to Nintendo due to 11.0, unless you
Ouch, the timing for this couldn't be any worse... It's already unusable at this point anyway. Better to be able to use it rather than not being able to use it at all.
Unless there's something else I can do?
Last edited by Deleted member 310901,
At this point, you might as well. smealum's confirmed he's gonna update the OoThax payload, but I'm not sure if anyone's confirmed that 11.0 can still be downgraded yet.
how about you try to restore that old 9.2 backup you have with the (keep a9lh) restore option in, uh, which one of them, was it decrypt9 that had it? so many of these apps have nand backup/restore I get confused.
decrypt9 or emunand9 or otphelper. anyway it's like nand->sysnand->restore (keep a9lh) or something.
Damn...just hope they forget to update it or give me a non-updated refurbished model...
I ran out of space for the SD padgen...
I ran out of space for the SD padgen...
Last edited by Deleted member 310901,
Unfortunately I doubt they won't update it. If you wish to hack that particular system with all your games in-tact, you'll have to hardmod it so you can tweak and flash a downgradable NATIVE_FIRM onto your system. Here's a list of people you can commission: https://gbatemp.net/threads/list-of-hardmod-installers-by-region.414224/
Didn't know how the SD padgen actually worked, try out the following:
1. Backup everything on your SD Card (IMPORTANT)
2. Get into SD/Nintendo 3DS/SysNand1/SysNand2(these are random letters, just choose the folder with the biggest filesize if there are multiple)/title
3. Search for "content" in Windows Search and let it load up everything
4. Select everything by pressing CTRL+A and delete it
5. Also make sure to delete the existing padgens on the SD Root / inside the Decrypt9 directory, if you have one
6. Enter decrypt9 and let it generate the padgens, choose the folder "title"
7. When it's done, copy the padgens to your computer
8. Restore the SD Backup you made in step 1
You are basically temporally deleting every game / title except for it's save, which is stored seperatly in a "data" folder next to the "content" folder, to generate the pads only for your save data and after that, you restore everything again. I have not tested this, but it should be absolutly safe if you make a backup beforehand!
If they send you a new unit, you will be able to use the xorpads to decrypt your saves and then encrypt them using the xorpads of your new unit. (Which will probably be hard to do, so just pray that they wont send you a new unit)
I apologise in advance for (probably) some grammar mistakes :/
Last edited by opa334,
Why don't you try a hardmod? Having a few backups as you do you'll be able to restore everything you had.
Yeah, I'm considering a hardmod. It'll probably take 2 weeks before I get my 3DS back so I'll be watching the scene closely.
Sorry for troubling you but how do I restore them? I have them backed up in multiple locations but I'm lost on how restoring works.
Just as a final note: Thanks for the help guys!
Them? The SD Card? You probably want to delete the Nintendo 3DS folder and replace it with the one of your backup, if that's what you meant by restoring. If you want to restore the saves, I would suggest to wait, as it's pretty annoying to do. You would have to create each save on your new unit, get the xorpad of them and then decrypt the save from your orginal 3ds and reencrypt it with the xorpad of your new 3ds. (It might be possible to reinsert the decrypted save with some save manager, but don't quote me on that) If you have the SD xorpads, just restore the 9.2 NAND from Decrypt9 and send in the console, althrough they will probably update it, so you might have to hardmod.
Both of you are mistaken actually. NAND Chip failures are 100% a hardware problem which you can circumvent by using a redNAND setup.
Fixed that for you.
i wasnt mistaken if his system is still letting him load payloads and thus cfw he can use a emu/rednand. if the nand was totally dead it would blue screen with nand not found
ya as long as a9lh is still working the nand isnt totally dead so you can run emunand9 and make a rednand using the backup you have
You are mistaken saying if it would work yoh KNEW it wasn't hardware. Because you don't. It can be connection failures or a partially broken NAND chip. RedNAND would still work.
Similar threads
