Hacking Help I get ErrDisp error on startup
- Thread starter KirppuAapo
- Start date
- Views 4,379
- Replies 19
So what happened is I tried to downgrade to 9.2 on DsIWare hax 11.8. So then it failed to install and what happened is that this happens on startup
An error occured (ErrDisp)
Error type: generic
Process ID: 21
Process name: qtm
Process title ID: 0x0004013000004202
Address: 0x00103c60
Error code: 0xf96183fe
Press any button to reboot.
So what do I do with this?
An error occured (ErrDisp)
Error type: generic
Process ID: 21
Process name: qtm
Process title ID: 0x0004013000004202
Address: 0x00103c60
Error code: 0xf96183fe
Press any button to reboot.
So what do I do with this?
I wanted to play with my friends btout I had fbi and such so my stupid ass is thinking that if I downgrade the chances of a ban would be way less
Do you have a SysNAND *.bin back up image?
If you have Luma3DS with boot9strap and GodMode9 custom firmware, you can try recovering your 3DS with CTRTransfer.
If you have Luma3DS with boot9strap and GodMode9 custom firmware, you can try recovering your 3DS with CTRTransfer.
It's about 1.2 GB in size named something like this: ######_XX########_sysnand_000.bin
Did you ever put a copy of it safely away on your computer or external flash drive/hard drive?
IF you can find it, use GodMode9 to do a SysNAND Restore (Safe).
If not, pray for your sake if the CTRTransfer method pulls through.
Thanks Ill try that
--------------------- MERGED ---------------------------
Both of the CTRNAND transfer and Restore options restore sysnand safe say No usable entries found
--------------------- MERGED ---------------------------
Oop forgot to add the files but Idont even have them
Try putting your SysNAND *.bin image file in gm9/out folder. In GodMode9, press (A) on it. You see NAND image options... If that NAND came from the same 3DS, it should allow you to Restore SysNAND (Safe).
Another thing you should look out for is if your 3DS is using the older a9lh (arm9loaderhax) form of custom firmware. If you're using really old stuff, try updating to boot9strap first.
Another thing you should look out for is if your 3DS is using the older a9lh (arm9loaderhax) form of custom firmware. If you're using really old stuff, try updating to boot9strap first.
If your 3DS was originally hacked by you, the 3ds.hacks.guide (the one true source for hacking your 3DS) would have instructed you to make a backup of your SysNAND for safe keeping in case anything ever happened.
You're not in a good position if this was never done. If someone else hacked your 3DS, your seller failed to provide you a copy of it.
Your next available option is to try CTRTransfer.
Last edited by TurdPooCharger,
Try it with the older 9.2.0 CTRTransfer,
I think I got it
I used recovery mode to install back the latest update
--------------------- MERGED ---------------------------
Thanks for your help I am honored
Make sure your custom firmware is up to date: Luma3DS v9.1, GodMode v1.7.1, and boot9strap v1.3
And also, back up your SysNAND and put a copy (or several) some place safe!
All right tanks from Finland
--------------------- MERGED ---------------------------
Also can I get banned if I use wifi or should I use wifi
You have a lot of researching and catching up to do.
