Hacking 3DS cant boot into home menu

[Schmatz]

hey guys, im very depressed. i researched many homepages to fix the problem, but i dont find the right answer yet.

heres the story: a friend installed cfw 6 months ago (following this guide 3ds.hacks.guide/). everything worked fine and the system runs. after he finished the process, i didnt used the 3ds the last 6 month.

when i wanted to start the 3ds a fews days ago, i just became black screen and no sound. i tried this guide (3ds.hacks.guide/troubleshooting) to fix the problem. i have to break up the ctr transfer at th time the guide says "boot into home menu", because the 3ds dont boots to home menu.

after some tries of the friend to fix it, i dont get black screen anymore (he pushed L/R/B/down while push power on). now the message "home menu is going to start. dont power off the system" appears for hours.

even the try to uninstall cfw didnt worked, because at one point the guide says "boot into home menu" and that just NOT work.

has anybody an idea?

 

[fmkid]

Uninstall the CFW is almost never a good idea. For now, it would be better to discard any problem with the SD card. Follow this post in order to analyse your actual console SD card.

On the other hand, try to put the latest Luma "boot.firm" from the SD card on CTRNAND root, following this guide (you must have access to GodMode9). When you get that, take the SD card out from the console and then turn on the console (pressing SELECT at the same time, if neccesary); Luma config menu should be prompted, then just press START and see if HOME Menu is loaded normally from this way.

If error persists, please tell us

 

[Schmatz]

hello. thx for your anwser.

i follwed the 2 guides successfully so far ... but in the end the home menu dont appear. just the same window with the message "home menu is going to start. dont power off the system."

 

[fmkid]

hello. thx for your anwser.

i follwed the 2 guides successfully so far ... but in the end the home menu dont appear. just the same window with the message "home menu is going to start. dont power off the system."

Even with the SD card off from the console?

Try then with this post says. If not, finally try with this other post says

Edit: Another thing that you can try is:

• Open GodMode9
• Enter to "[1:] SYSNAND CTRNAND"
• Choose the "data" folder and rename it (i.e. as "data1" or "data2", or as you want), pressing the combo R+X
• If a message about unlock is prompted, then accept it and perform the button sequence showed in screen
• Reboot the console (pressing START) and see what happens now

 

[Schmatz]

Hi, well yes, even with the SD card off from the console.

Here is the report for the first post you mentioned:

1. not working points: home menu, recover mode (= black screen)
   
   
2. i dont had the file for my region in the folder. The only files were 00000001, 00000002, 00000003 – probably because i deleted the exdate yesterday

3. have to stop the guide at point 4, because home menu didnt appear

4. not working, just black screen

5. at point 6 (updating B9S) the installation was successfull, but at point „Once it has completed, hold (Start) while pressing (A) to reboot your device to the Luma3DS chainloader. If you encounter an argc = 0 error booting your device after the B9S update, just continue to fix it“ --> when i wanted to press start +A, the installation always repat and it dont boot to the luma chainloader. So i turned the power off and follwed the next step (Section III - Update Luma3DS)


result: i followed all steps from point 1 to 5 and after all this, the home-menu-opening-window still appears all the time.



Next step: Trying your third mentioned method: i got a black screen
but godmode and luma config is still available



so whats next? Rename the „data1“ folder back to „data“ and continue with your second mentioned post?

 

[fmkid]

Yes. Try with the second suggestion I gave you (mainly with the CTRTransfer - Type D9 method).

If after all problem continues, then I really give up. Perharps @TurdPooCharger could provide you better and specific assistance about, but he's resting for now (afaik)

 

[Schmatz]

I followed he CTRTransfer (Type D9)-guide until point 11.

→ i checked whether i have a "gamecoin"-type brick. At point 7 (Go into 1:/data/<ID0>/ directory. You will see two subfolders

• extdata
  
  
• sysdata
  
  ...

i only had the sysdata folder. So i followed the (B) steps.

I deleted all folders in descending order. But after deleting the last one (5 folders) the home menu dindt come up. I always just got black screen on every step



is there another way to uninstall the cfw (beside the guide at 3ds.hacks.guide)??? a method where i dont need to boot the home menu. maybe the problem can be solved by uninstalling the cfw. its better to have a functional 3ds without the cfw instead of a non-usable 3ds with cfw.

 

[KleinesSinchen]

Is there another way to uninstall the cfw (beside the guide at 3ds.hacks.guide)??? a method where i dont need to boot the home menu. maybe the problem can be solved by uninstalling the cfw. its better to have a functional 3ds without the cfw instead of a non-usable 3ds with cfw.

No. Fullbrick guaranteed. Uninstalling CFW is almost never a solution for a 3DS software problem and will make problems worse.

Removing CFW means you'll have no way to fix it. Like throwing away the spare tyre because you got a flat.

(I can set up a scenario where uninstall CFW would help but still would be a bad solution)

The part with "boot into Home Menu" on the guide is a safety measurement. It simulates uninstallation of CFW. If it does not boot into Home Menu in the safety test, the uninstall script will 100% fully brick the 3DS to the point where only ntrboot can potentially safe it.

 

[Schmatz]

(I can set up a scenario where uninstall CFW would help but still would be a bad solution)

why is it a bad solution?

what does this post mean to me? what can i further try, to solve the problem?

 

[KleinesSinchen]

why is it a bad solution?

what does this post mean to me? what can i further try, to solve the problem?

I expressed that poorly. I can setup a scenario on a currently working device and brick in on purpose in a way that uninstall CFW will revive it. It is not a solution, not even a bad one, for your problem. And it generally is a bad solution since a 3DS without CFW can do less than one with it.

I'll try to explain in short why uninstalling CFW will not do anything good:
For some years now we have a boot time exploit called boot9strap (B9S). It allows us to modify the boot partitions in a way the CFW (Luma3DS) is loaded automatically on each boot. The uninstall script removes B9S, restores the boot partitions to the previous state and Luma3DS isn't loaded anymore. Uninstalling B9S has zero impact on the operating system and its data (on CTRNAND) it does not magically repair a damaged OS – but removes access to all tools like GodMode9.
The safety test on the guide makes the console boot without Luma3DS once – to show what would be the result of really removing B9S. If a 3DS goes black screens on the safety test, it will go black screens on uninstall CFW.

I'm at a loss here about your problem. If CTRTransfer Type D9 following the instructions to the letter didn't do the trick… I have no idea where to go next. After all @TurdPooCharger is the 3DS genius here. We will have to wait for his return. 2|3DS consoles behave erratically on hardware failure as well so I would not rule out that. If you put away a working console and did not touch it (and did not change anything) and now it didn't work this sounds strange.

 

[Schmatz]

okay, i inderstand. thx to all of your for yor help. so then i am going to wait for the return of turdpoocharger.