Hmm, how strange that GodMode9 recognizes your SD cards but the 3DS firmware does not.
Idea (A) - Try a (simulated) Format System Memory;
don't do a real one in System Settings- In GodMode9, go in the [1:] SYSNAND CTRNAND directory. Hold (R)-shoulder and press (X) on data folder. Rename this to data2.
- Be careful. Pressing only the (X) button brings up the delete option. Do not delete!
- Press (START) button to exit GodMode9. The n3DSXL will ask to make a new user profile. Ignore this and go back to GodMode9.
- Press (HOME) button → Scripts... → CTRTransfer (Type D9) → Bypass Profile Setup
- This will make a new (blank) user profile.
- Press (START) button to exit GodMode9. The n3DSXL should now boot to HOME Menu.
Not good. I fear the worst. 5. Return to GodMode9. In the [1:] SYSNAND CTRNAND directory, press (X) to delete the (dummy) data folder.
6. Press (START) to exit GodMode9. When asked to make a new user profile, manually input all the required info. Just add in whatever name, date, time, etc.
7. If successful, the n3DSXL should boot to HOME Menu this time.
6. Press (START) to exit GodMode9. When asked to make a new user profile, manually input all the required info. Just add in whatever name, date, time, etc.
7. If successful, the n3DSXL should boot to HOME Menu this time.
(cont.)
8. Return to GodMode9 again, and press (X) to delete the (dummy) data folder in [1:] SYSNAND CTRNAND.
9. Hold (R)-shoulder and press (X) to rename the original data2 back to data.
9. Hold (R)-shoulder and press (X) to rename the original data2 back to data.
At this point, I have a suspicion your n3DSXL has a hardware failure. Prime suspects that any of these are possibly failing: RAM, eMMC (NAND chip), or ARM SoC
***
If you wish to continue to try to system update to 11.13E.
Idea (B) - GodMode9 inject FBI to H&S.
10. Download and add the CIA version of FBI onto the SD card.
11. In GodMode9, inject FBI into Health & Safety.
12. Press (START) to boot to HOME Menu. Assuming the n3DSXL doesn't crash again, find and open H&S (FBI).
13. Continue installing the system tickets (TIK) and DSiWare CIAs found in the step 13 of the CTRTransfer (Type D9)'s Instructions.
I'm going to guess your n3DSXL is likely to crash or get stuck at this post's step 16.11. In GodMode9, inject FBI into Health & Safety.
12. Press (START) to boot to HOME Menu. Assuming the n3DSXL doesn't crash again, find and open H&S (FBI).
13. Continue installing the system tickets (TIK) and DSiWare CIAs found in the step 13 of the CTRTransfer (Type D9)'s Instructions.
- Ignore the parts about using the faketik and Cthulhu homebrew apps. These can be resolved later.
- Restauration de Santé & Sécurité après avoir injecté un .cia (Restoring Health & Safety after injecting a .CIA app)
- (HOME) button → Scripts... → CTRTransfer (Type D9) → DSiWare CIAs & Saves → Restore Saves → choose the 'dsiware' folder.
Last edited by TurdPooCharger,
Where do you find the files for step 13?
Is it in SD or tickets menu in FBI?
Because I egt an error when I try to open the SD menu
Attachments
Last edited by Newe,
See the spoiler 'Install system tickets and DSiWare CIAS.'. They're found in:
- sdmc:/gm9/out/<date>_<serial>_dsiware_000
- sdmc:/gm9/out/<date>_<serial>_system tickets_(<region>)_000
I'm currently unbricking my n3DSXL for a separate issue. Check back on this post #30 in a few minutes when ready and edited for further instructions. Trying to verify if a certain actions are feasible.
Edit - Additional instructions are found below in post #32.
Last edited by TurdPooCharger,
Ah fucking hell. Desperate times require desperate measures. Since access to the SD card is not available,
17. Return to GodMode9. Go to the [0:] SDCARD ()/gm9/out directory.
18. Press (L)-shoulder on both of these folders to highlight select them yellow. Press (Y) to add them to the [CLIPBOARD].
22. Continue with steps 14-16 found in the above post #26.
18. Press (L)-shoulder on both of these folders to highlight select them yellow. Press (Y) to add them to the [CLIPBOARD].
- <date>_<serial>_dsiware_000
- <date>_<serial>_system tickets_(<region>)_000
- If a mistake occurred, press (SELECT) to reset items selection.
- This makes copies of those folders to the NAND.
- <date>_<serial>_dsiware_000 → <current directory> → Install all CIAs
- <date>_<serial>_system tickets_(<region>)_000 → <current directory> → Install all tickets
22. Continue with steps 14-16 found in the above post #26.
Last edited by TurdPooCharger,
While doing step 15, when I choose the dsiware folder it tells me that;
The 'extracted saves' subfolder was not found.
Either the wrong folder was selected or no backed up saves exist.
(<A> to continue)
This message will appear if you've never played DSiWare games before and thus have no saves to restore.
Edit - Proceed to step 16. Also try to system update with and without the SD card.
Last edited by TurdPooCharger,
This probably won't work either, but try the update from System Settings → Other Settings → System Update.
Be ready for bad news.
I'm go downstairs for a quick bite. Post an update if the n3DSXL manages to complete the 11.13E system update or gets indefinitely stuck.
Last edited by TurdPooCharger,
So the bad news.
Other than a SysNAND Restore (with a known to be clean backed up BIN image) and this other firmware repair option known as Lazarus3DS, the CTRTransfer (Type D9) you performed leaves very little room for mishaps when it comes to fixing typical software errors. There are very specific scenarios of extreme bricking (ie, purposefully restoring garbage SysNAND image or messing with the NSCD nand header) or running it on a bad SD card where CTRTransfer (Type D9) might not work. The only other area that can cause softbricks that (Type D9) leaves alone is that data folder in [1:] SYSNAND CTRNAND, which was already ruled out with the temporary (simulated) Format System Memory.
I think your n3DSXL has a dying eMMC (NAND chip). That component on the motherboard is like the hard drive found on a computer. The eMMC (embedded memory card) is very much alike as the SDMC (secure digital memory card). Both are flash memory that can degrade and fail over time. If you recalled your experience using H2testw, the purpose of that program was to ensure your SD card was fully functional and up to the task in reliably backing up your NAND files and restore them all intact.
Here's an example n2DSXL of a possibly failed eMMC. Cause of failure was never explicitly determined.
Edit - If it was the ARM SoC or RAM, that n3DSXL most likely would have never completed the CTRTransfer. If the WiFi chip was bad, the system update couldn't have reach 30% progress. Lastly, if the SD card slot reader was truly faulty, GodMode9 wouldn't be able to read and write to it.
***
I am currently working on a v1.6 of that (Type D9) script that includes a new feature dubbed eMMC Status Checker. This basically serves as the H2testw counterpart for the 3DS systems' NAND chips. While that feature has been finished and successfully tested on my n3DSXL, I am reluctant about publicly releasing the script at this moment due to wanting to make sure it is as safe as possible to use.
You may be eligible to be an early tester depending on your circumstances and how comfortable you are about using it. Due to how the test works, there's a small window frame where if GodMode9 or the script crashed in the middle of reflashing, the n3DSXL could end up super bricked. It's a double edge sword scenario.
Do you own an ntrboot flashcart by any chance?
Last edited by TurdPooCharger,
Ok so from what I read, it scared me a bit because it touch to hardware that can't be replaced without great knowledge.
At the moment, is there a way to restore the systems I got before using CTRTransfer?
It would be an honour to be a test for your new scripts. What are the factors that Godmode9 or the script crashed while reflashing and what is a super brick?
Now I don't have one of those NTRboot flashcart.
At the moment, is there a way to restore the systems I got before using CTRTransfer?
It would be an honour to be a test for your new scripts. What are the factors that Godmode9 or the script crashed while reflashing and what is a super brick?
Now I don't have one of those NTRboot flashcart.
Correct. The eMMC is not something that is easily replaceable. While it's possible to remove and solder in a replacement NAND chip,
, this is not something the average 3DS homebrewer or modder is capable of doing. Requires professional electronics repair.
If the eMMC was the issue, most people would do one of these:
- (A) Buy another 2DS or 3DS system and/or System Transfer their game library over.
- (B) If System Transfer is not possible, backup all the saves + extdata with Checkpoint, JKSM, GBAVCSM, and/or CTRTransfer (Type D9) - DSiWare CIAs & Saves. GodMode9 dump the games, updates, and dlcs into CIAs, and reinstall them with FBI.
- (C) If both (A) and (B) are not possible, there are SDTransfer and related methods.
- (D) Replace the motherboard. Requires (A), (B), or (C) in regards to preserving the saves, extdata, and titles.
- (E) Try to salvage the motherboard despite bad eMMC. Switch over to EmuNAND setup; install and run the 3DS firmware on the SD card.
- See GodMode9 release page (SD card handling) or 3DS Multi EmuNAND Creator.
If you made the SysNAND *.bin image from step 8 in the (Type D9)'s Instructions,
However, before you restore the state of the 3DS firmware (before the CTRTransfer), backup the current SysNAND in case we may to need to revisit how the n3DSXL is now (after the CTRTransfer).
A "super (soft)brick" is when a 3DS has its firmware completely trashed or erased. Although this scenario happens very rarely, this type of brick usually occurs when someone tries to (forcefully) restore a NAND image onto a different 3DS than the one it was made from. They do this with the wrong assumption that their entire setup can be migrated from their broken or dead 3DS without knowing this can't be done due to console unique encryption. GodMode9 and related programs made by d0k3 have safety measures put in place to prevent this from accidentally happening, but there's nothing really stopping someone from totally messing up on this if they were inclined to do so.
How one recovers from a 'super brick' would be to ntrboot launch their 3DS to GodMode9 and restore a previously backed up SysNAND *.bin image. If one did not make that system's image beforehand or received/bought the 3DS already bricked like that, recovery requires borrowing a donor system's decrypted NAND files and reflashing these with Lazarus3DS.
If a 3DS system is otherwise perfectly fine in terms of hardware, a 'super brick' manifests itself as a bootrom 8046 error (Blue Screens of Death). Keep in mind not all bootrom 8046 errors are the same. Most of these are easily fixable with ntrboot and almost none of them are as severe as 'super brick'. The only exception is when the bootrom 8046 is due to a physically dead eMMC that was fried from a failed hardmod.
***
Due to how eMMC Status Checker (temporarily) reflashes the entire (minsize portion of the) NAND with null values (00) and (FF), a 3DS system that manages to crash during the writing phase of the test will end up 'super bricked'. Recovering from this requires a ntrboot flashcart to access GodMode9 and restore the sysnand image made by the script before the start of the writing phase.
I have coded the 'eMMC Status Checker' as best I could to be as idiotproof and bug-free as possible, even with the ability for the user to early cancel (ie, emergency situation where the battery is about to die). For those 30 minutes when the testing is underway while the 3DS is left alone for the script to do its job undisturbed, the 3DS is in danger of super bricking should GM9 or the script decides to crash for whatever reason.
***
If you agree to try 'eMMC Status Checker' especially without a ntrboot flashcart on hand, just know I make no guarantees or promises your experience will be trouble-free. Because the script v1.6 is not ready for public release, I would have to share it to you by PM and ask that you delete it after using the test.
Other than for playing DS games, consider buying one as a safety tool. You never know if you might need one for brick recovery if your 3DS ever has a nonworking CFW.
- R4i Gold 3DS Plus (recommended)
- R4iSDHC series (shitty; time bomb requires YSMenu kernel)
Last edited by TurdPooCharger,
Similar threads
- No one is chatting at the moment.
-
-
-
@
Veho:
Once again I fell down the martial arts rabbit hole and am plumbing the murky depths of the internet's various martial arts and fighting crafts echo chambers. -
@
Veho:
I like to get up to speed on that every now and then, see what the newest high wisdom everyone is spouting nowadays.
-
@
Veho:
If you're not actively involved and only get up to speed every few years or so, you can see the tide of public opinion flapping worse than my dong while I'm skipping naked down a hallway.
-
-
-
-
@
Veho:
Like most forced updates, this one has terrible support and was very poorly received by the userbase.
-
-
-
-
-
-
@
FAST6191:
How do you know the giant wasn't on walkabout https://c8.alamy.com/comp/ADKT2C/ce...carving-in-dorset-uk-thought-to-be-ADKT2C.jpg -
@
Veho:
That's what I said, maybe they were just doing a recreation of the Cerne Abbas giant but didn't finish it in time.
-
-
-
-
-
-
-
@
Psionic Roshambo:
https://imgur.com/gallery/ZfBfPgk 100 million... Can think of better uses but OK lol -
-
