Hacking N3DS Won´t boot into CFW

  • Thread starter Thread starter destructor1
  • Start date Start date
  • Views Views 1,431
  • Replies Replies 17

destructor1

Well-Known Member
Newcomer
Joined
Feb 13, 2016
Messages
61
Reaction score
5
Trophies
0
Age
46
XP
119
Country
Gambia, The
Hi all,

i don´t understand what is happening with my N3DS. I used it on REInand with emunand 10.5 (or 10.7?)
and everything worked without an problems. I used it for about 4 weeks and all of a sudden it didn´t boot into CFW anymore. It will boot into sysnand (9.2.0-20E) though. I tried to diferent CFW´s but none of them work?

What can cause this issue and what can i do to fix this without loosing my savegames and Eshop things?

Thanks for your help in advance.
 
Hi all,

i don´t understand what is happening with my N3DS. I used it on REInand with emunand 10.5 (or 10.7?)
and everything worked without an problems. I used it for about 4 weeks and all of a sudden it didn´t boot into CFW anymore. It will boot into sysnand (9.2.0-20E) though. I tried to diferent CFW´s but none of them work?

What can cause this issue and what can i do to fix this without loosing my savegames and Eshop things?

Thanks for your help in advance.
Hello! Did you make a NAND backup at all? Or did you do anything to the emuNAND?
 
just trying to get this right. we are not talking bout sysnand backup here, but a backup from the emunand partition from the sd card?
 
yah, then i think i´m outa luck. so gonna start from scratch ? i made a backup once but i think it was sysnand. and emunand.... i didn´t back it up i think. gonna start over from scratch just to make sure.
 
Here is my tip:

Follow this guide: http://gbatemp.net/threads/tutorial-manual-system-transfer-for-saves-content.388033/

1. sysNAND
2. New emuNAND cloned from sysNAND(1)
3. Bricked emuNAND

You only need the movable.sed if you don't need the system title saves.
This will make you able to use the games, saves from your old emuNAND(3) in your new one(2).

I suggest cloning your sysNAND(1) to emuNAND(2) and format the emuNAND(2) using tinyformat to unlink. Use that emuNAND(2) as the target for the system transfer.
This works even with a bricked emuNAND.
If you need help just ask :)


Or just do as already suggested:

What about cloning your SysNAND to your EmuNAND? Then unlinking them.
 
Last edited by Cinnamon,
gonna try this in a while and will report back as soon as i have a result.
Thank you guys in advance. This is the best board for all 3ds needs ;) with the best and most active users. U guys are simply awesome.
 
ha, don´t know if i wanna "help" out more ;):yay3ds:
8vx0na.gif
 

Site & Scene News

Popular threads in this forum