Hacking Error after trying to recover stock sysnand

[hurtlocker90]

Hello everyone,

i'm willing to sell my 2DS and therefore i wanted to get rid of the Luma CFW and get everything back to stock.

I tried to find an easy way to recover from my nand backup but unfortunately every tutorial i find seems to be based on a newer CFW or whatever. so i tried to recover via godmode9 but it didn't show me any scripts. after trying to install them nothing changed. so i just pointed to where i stored the nand backup, choosed the .bin file and it gave me the option to do a nand recover (safe).

well.. after i did so and rebooted, only an error showed up. "ctrnand firm corrupted" or something on these lines.

godmode9 still seems to be working fine since i can normally start it with the power/start buttons.

when i tried to put in my original SD card it won't even boot up.

i have 2 directories in my "nand backup" folder, one is called "a9lh" and the other one "ctrtransfer" where I used the .bin file from.

is there any way I can get the 2ds working again (on stock firmware) or did i brick it? hope someone is able to help me out with this.

 

[jeffyTheHomebrewer]

not sure, but you probably bricked your 2DS. Can you get to the home menu? (If not, Hold down L+R+UP+A (Up is for the Dpad) and press the power button. then update. that should unbrick it, but CFW will still be there. sorry!)

 

[wormdood]

you bricked it all right (fyi you should have updated cfw from a9lh to b9s so you could run the script to remove cfw properly) but you can still access gm9 so their is still hope for recovery . . . so to start i want you to use godmode9 to perform a ctr transfer CTRTransfer - 3DS Hacks Guide

 

[jeffyTheHomebrewer]

you bricked it all right (fyi you should have updated cfw from a9lh to b9s so you could run the script to remove cfw properly) but you can still access gm9 so their is still hope for recovery . . . so to start i want you to use godmode9 to perform a ctr transfer CTRTransfer - 3DS Hacks Guide

I remember when I sorta bricked my 3ds, hah. It happened the other day, I somehow corrupted the home menu most likely, then on boot it would show the luma splash, (if the SD was inserted.) then just a black screen. nothing. I could still access luma config and gm9, but I tried everything. then I remember L+R+UP+A, and thank iwata that they put that in, it can come in really handy.

 

[wormdood]

I remember when I sorta bricked my 3ds, hah. It happened the other day, I somehow corrupted the home menu most likely, then on boot it would show the luma splash, (if the SD was inserted.) then just a black screen. nothing. I could still access luma config and gm9, but I tried everything. then I remember L+R+UP+A, and thank iwata that they put that in, it can come in really handy.

yeah the recovery mode can work but it does not work for every corruption case however. i find that often when luma gives an error when booting there is no accessing the recovery mode, so i dont even consider it when passing out advice and move on to ctrtransfer(s) first via gm9, and if that wont work then via decrypt9, then if that wont work via lazarus3ds

 

[hurtlocker90]

OK, first off, thank you guys for helping me out so quickly.

I tried the recovery-mode first, doesn't work though. still shows: "the ctrnand firm is corrupted. press any button [...]"

next step is to try the ctrtransfer as wormdood mentioned. fingers crossed!

 

[wormdood]

when done with that recovery attempt post your results and i will advise you further

 

[hurtlocker90]

I replaced the Godmode9-Files as mentioned in the How-to and followed the instructions. The "11.5.0 CTRTransfer image" (in my case it'd be the old DS EU-file) download links didn't work. So while searching for another mirror of that file i came across another tutorial which said one should use the backuped .bin-file if possible. In my "NAND backup folder" there was a file named like this: "2.1.0-4E_ctrtransfer_o3ds.bin". Well.. i tried following the instructions of ctrttransfer and just load that file instead.

I got to Section II - Step 10. Step 11 didn't even show up for me (relocking write permissions). Also, i still couldn't run any scripts in gm9 mentioned in the following steps.

After i rebooted, instead of the error message, it just shows a black screen now. However, i can still launch godmode9 as before.

By the way, if that helps: Godmode version is the following: GodMode9 Explorer v1.2.1
so it looks like it didn't properly update gm9, although i replaced the .firm-file and the gm9-folder.

And my nand backup folder contains the following:
a9lh: otp.bin
CTRTransfer: 2.1.0-4E_ctrtransfer_o3ds.bin, AEM12002635_nand.bin, AEM12002635_nand.bin.sha

 

[wormdood]

By the way, if that helps: Godmode version is the following: GodMode9 Explorer v1.2.1
so it looks like it didn't properly update gm9, although i replaced the .firm-file and the gm9-folder.

thats an issue a9lh uses .bin format payloads and thats written for b9s payloads (.firm) you can just find the .bin version of the app and use that

I replaced the Godmode9-Files as mentioned in the How-to and followed the instructions. The "11.5.0 CTRTransfer image" (in my case it'd be the old DS EU-file) download links didn't work. So while searching for another mirror of that file i came across another tutorial which said one should use the backuped .bin-file if possible

this is recommended not because its more likely to work but because its yours and technically a ctrtransfer has you use firmware files not licensed to you (as in nintendo the copyright protected files owner never gave you permission to use) but if you backed up your own then its more legally grey

In my "NAND backup folder" there was a file named like this: "2.1.0-4E_ctrtransfer_o3ds.bin". Well.. i tried following the instructions of ctrttransfer and just load that file instead.

this is a file you used long ago to install al9h (well obtain the otp) and if you/it actually installed the files at this point then your system is now on 2.1.0-4

After i rebooted, instead of the error message, it just shows a black screen now. However, i can still launch godmode9 as before.

so as i said get the .bin version of the app and as far as getting the correct ctrtransfer image go to "that iso site" you can find it there

and i cant stress this enough if there are any other inconsistency dont act instead come back here and ask

 

[hurtlocker90]

OK the latest version of gm9 which still comes as a .bin-file was 1.2.8. I got the 11.5.0 image for old3DS/2DS for europe as well.

I followed the how-to again and this time it asked me if i want to relock the write permission or not. i declined that. after that, i tried to start up gm9megascript but got the following message:

0:/gm9/scripts/GM9Megascript.gm9
line 3: too many arguments
if°not find ${GM9IN] NULL

(<A> to continue)


if i press A i just get back to the home screen of gm9, so nothing happens.

 

[wormdood]

OK the latest version of gm9 which still comes as a .bin-file was 1.2.8. I got the 11.5.0 image for old3DS/2DS for europe as well.

I followed the how-to again and this time it asked me if i want to relock the write permission or not. i declined that. after that, i tried to start up gm9megascript but got the following message:

0:/gm9/scripts/GM9Megascript.gm9
line 3: too many arguments
if°not find ${GM9IN] NULL

(<A> to continue)


if i press A i just get back to the home screen of gm9, so nothing happens.

this error i have never seen . . . @TurdPooCharger . . . you have any idea what that error means?

 

[hurtlocker90]

i did a reboot, just to try it again and see if i missed something. if i now boot the 2DS just normally, it seems like its all back to normal now! it started just like a fresh new 2DS. under system firmware it now shows me Sys 11.5.0-38E.

of course gm9/luma3DS chainloader is still there, so i'm not 100% back on stock yet. anyway, you already helped me a lot(!) wormdood, i really thank you for that! hope you can take me through the last final(?) steps now in order to have a clean 2DS, ready to sell.

 

[wormdood]

i did a reboot, just to try it again and see if i missed something. if i now boot the 2DS just normally, it seems like its all back to normal now! it started just like a fresh new 2DS. under system firmware it now shows me Sys 11.5.0-38E.

ok you had me worried there for a moment with that error message . . .

of course gm9 is still there, so i'm not 100% back on stock yet. anyway, you already helped me a lot(!) wormdood, i really thank you for that! hope you can take me through the last final(?) steps now in order to have a clean 2DS, ready to sell.

ok so next you want to do the steps outlined here A9LH to B9S - 3DS Hacks Guide ... afterwards you can follow this section Uninstall CFW - 3DS Hacks Guide ... although in my opinion its more valuable to sell with cfw still installed (you just cant include any pirated games)

 

[hurtlocker90]

OK i'll do that and let you know. Yes.. well.. it's illegal to sell it in my country with CFW pre-installed. I'm a little bit worried about that tbh, so i decided to sell it just with a stock firmware version still ready to install a CFW if wished.

 

[wormdood]

so i decided to sell it just with a stock firmware version still ready to install a CFW if wished.

ok but as a precaution you should tell the buyer that the system once had cfw installed, the reason for this is the b9s cfw installer will give them an error screen (/brick warning) they will manually need to bypass due to having cfw removed in the past

 

[hurtlocker90]

Oh alright good to know. Just in case: If i decide to do a fresh reinstall with the newest CFW and sell it then - how do i get the preinstalled game which came with the bundle (super mario bros. 2) back on the device after i installed the CFW? i can't do a dump of it since that's only possible after the hack, right? i lost it the first time and don't want to install a ripped file from the internet because then i definitely won't be able to sell it.

 

[wormdood]

Oh alright good to know. Just in case: If i decide to do a fresh reinstall with the newest CFW and sell it then - how do i get the preinstalled game which came with the bundle (super mario bros. 2) back on the device after i installed the CFW? i can't do a dump of it since that's only possible after the hack, right? i lost it the first time and don't want to install a ripped file from the internet because then i definitely won't be able to sell it.

sadly you cant, and furthermore if you ever put a nnid on the system (like you need to do to use the eshop) then the game is now attached to that nnid and only by linking your nnid could you legally redownload the game from the eshop, i dont know about the legality of selling accounts in your country but you could include the associated nnid. i dont know what all you have on your nnid and how viable a solution that would be to (may or may not be legal and you may have never had a nnid for all i know) . . . or you could get a "legit cia" of the game and install it before removing cfw and after removing cfw it will still boot the game, but then you could not legally sell the system unless you deleted the game so thats not a practical option for you

 

[hurtlocker90]

OK. In that case i'll just continue do delete the CFW completely and then re-download the game from the eShop. After that, i'll reset the 2DS to stock settings and that way there shouldn't be any traces of my Nintendo-profile while the game should still be installed and playable - right?

I'm at section IV now at the tutorial and it asks me to go the system settings and update the system firmware. so i'm updating to the latest firmware - which is, according to the tutorial, safe to do since i'm on the CFW. but if now delete the CFW completely afterwards - i should be on the latest, original firmware. and there is no hack/CFW for that latest original FW yet, right? so am i/the buyer losing the potential to install the CFW then?

edit: i still have the original SD-card with its unchanged content that came with the 2DS when i bought it. any reason to believe i could install it from there without the need to visit the eShop?

 

[wormdood]

OK. In that case i'll just continue do delete the CFW completely and then re-download the game from the eShop. After that, i'll reset the 2DS to stock settings and that way there shouldn't be any traces of my Nintendo-profile while the game should still be installed and playable - right?

not exactly when you use the settings app for that purpose it will loose the establishment with your nnid and as such it could not play the game . . . if i recall correctly the game will be deleted
the only way i can think to sort of accomplish your goal is to reinstall it from the eshop then call nintendo to have them remove your nnid telling them that you lost the system they will remove your nnid from the console on their servers making it so they cant access the eshop on that console and as the console still believes its nnid is valid it will still boot . . . but this sounds legal gray (a dark grey) at best as you will be selling the game you own alongside the console and retaining the ability to redownload it . . . and when they input their nnid they wont be able to boot the game anymore

I'm at section IV now at the tutorial and it asks me to go the system settings and update the system firmware. so i'm updating to the latest firmware - which is, according to the tutorial, safe to do since i'm on the CFW. but if now delete the CFW completely afterwards - i should be on the latest, original firmware. and there is no hack/CFW for that latest original FW yet, right? so am i/the buyer losing the potential to install the CFW then?

there actually is a free hack for 11.9 to install cfw (frogminer is the method) so you should be happy to know you are incorrect on this point

furthermore updating ofw will fill any holes in the firmware skipped over with the ctrtransfer (gm9 has safety checks in place that do make it safer but also makes it skip some files during a ctrtransfer if it deems it unnecessary to replace them)

 

[hurtlocker90]

not exactly when you use the settings app for that purpose it will loose the establishment with your nnid and as such it could not play the game . . . if i recall correctly the game will be deleted
the only way i can think to sort of accomplish your goal is to reinstall it from the eshop then call nintendo to have them remove your nnid telling them that you lost the system they will remove your nnid from the console on their servers making it so they cant access the eshop on that console and as the console still believes its nnid is valid it will still boot . . . but this sounds legal gray (a dark grey) at best as you will be selling the game you own alongside the console and retaining the ability to redownload it . . . and when they input their nnid they wont be able to boot the game anymore

sorry for asking again but since i'm not a native speaker i sometimes have a hard time in understanding it to a full extent. in other words: since i installed the CFW in the past, there's literally NO (easy) way i can reset the 2DS to the point when i first turned it on after i bought it? without any nintendo ID entered, any personal data - just a fresh 2DS with mario bros. 2 preinstalled. so even if i wanna sell it without the CFW, i can't sell it as i initally bought it - since people will wonder why the game shown on the packaging is not on the device and can't be downloaded again either. i pretty much have to sell it with the CFW now since thats the only proper reason why the game is missing :_)

furthermore updating ofw will fill any holes in the firmware skipped over with the ctrtransfer (gm9 has safety checks in place that do make it safer but also makes it skip some files during a ctrtransfer if it deems it unnecessary to replace them)

so the best thing, if i wanna sell it with the CFW installed, is to deinstall the CFW properly, update to the latest OFW to make sure everything is in it's right place again and then use the frogminer method to get back on the latest CFW again. please confirm, thanks and, again: thanks a lot for your patience and help!

edit: im done with the b9s update and already deleted the CFW (for now). worked without a single error, everything is back to normal now (besides the missing preinstalled game).