Homebrew Did I brick my 3DS?
- Thread starter GoldenTreesYT
- Start date
- Views 1,956
- Replies 16
By the way, I have tried deleting luma's config file. No luck, just had to reenable the setting it told me to when I modded it.
I got this the other week when I updated my 3ds system. Update Luma on your SD card and essentially re-CFW your system using the original guide.
Here's a pic of my 3DS micro SD card. This is all the files, I removed the cias folder to show everything. Also I've got a new 3ds xl usa region.
--------------------- MERGED ---------------------------
--------------------- MERGED ---------------------------
I will try re-modding my 3ds. I use NTRboot to do so, do I need to redo that part?
--------------------- MERGED ---------------------------
I thought doing that Might fix it but I didn't try because I was worried it might make it worse.
--------------------- MERGED ---------------------------
I will try re-modding my 3ds. I use NTRboot to do so, do I need to redo that part?
Attachments
Did you ever make a image *.bin backup of your SysNAND and saved that file somewhere safe on your computer?
If you hacked your n3DSXL yourself, here's a refresher in what's being referring to:
If you hacked your n3DSXL yourself, here's a refresher in what's being referring to:
Follow the guide from here:
3ds.hacks.guide /installing-boot9strap-(ntrboot)
You shouldn't have any more problems after that.
Yes
--------------------- MERGED ---------------------------
I think that maybe redoing Ctrtransfer to get back to 11.8 might fix it
--------------------- MERGED ---------------------------
Lol just saw this. I do have 2 other working devices, one on 11.8, I will create a file from that one later. I don't have it with me right now. Thanks! I have a feeling this might be it1
You can't use the SysNAND backup from a different 3DS. That image file is tied to the specific 3DS it came from.
No, don't create it from another device. Don't restore the NAND of another device or you'll brick. He means a backup of this device. If you don't have one, you should try another CTRTransfer.
Also, can you try this Luma version? I have a little doubt about something, maybe it will work.
@GoldenTreesYT, you might want to copy everything off your SD card, reformat it as FAT32 + 32 KB cluster size (use guiformat if bigger than 32 GB), and run it through with H2testw in a Full Write + Verify Test.
A possibility for why your CTRTransfer failed is that your card could be fake. If that's the case, you flashed your NAND with corrupted files.
A possibility for why your CTRTransfer failed is that your card could be fake. If that's the case, you flashed your NAND with corrupted files.
- Joined
- Apr 13, 2018
- Messages
- 111
- Trophies
- 0
- Location
- In your computer
- Website
- overhax.fun
- XP
- 275
- Country
The card is 8GB, and it worked until I tried to NTRboot. If it helps, it's a SanDisk SCHC class 4. I doubt it fake
Anything can be fake unless you test it, that why the recommendation of H2testw.
Last edited by Hayato213,
Wait why'd I say NTRboot I meantmeant ctrtransfer
--------------------- MERGED ---------------------------
Also, it said it was successful but after it wouldnt start luma
At this moment, forget what GodMode9 told you about your CTRTransfer being successful.
***
If you have an o3DS with a standard type SD card, make sure the write protection slide isn't in the lock position.
Do the H2testw so that all of us know for sure we're not dealing with faulty hardware. This is the foundation of your entire 3DS game library and CFW setup at stake here! If this is unknowingly bad, you're going to find yourself in a world of hurt losing game progress and saves!
Things to look out for when using H2testw
If your card instantly or quickly passes the test without writing anything to it, your SD card has died and entered read-only mode (too many worn out NAND cells). This can't be fixed with any software. You would have to buy a replacement card (check my signature!)
At any moment the test goes red like this, the card is no good. Trash it.
A passing card (that took time to write & verify) will have a result resembling this.
If and only if your card isn't to blame after checking, should you then proceed with any further attempts at CTRTransfer and other recovery attempts.
Similar threads
(
