I just learned about homebrew about a month and a half ago. I was using browser hacks while on 11.0 but the update ruined that. I have two old 3DSs one on 11.1 and one on 6.2. I have never had homebrew launcher on either one. I tried upgrading to 9.2 on the 6.2 firmware but rxTools would not download firmware.bin and I could not find a fix to this problem. I've read something about luma but found no information I knew what to do with. I have absolutly no idea where to start right now. Please someone help!
Homebrew Lost and confused newb :(
- Thread starter NoticeMeGenki
- Start date
- Views 1,223
- Replies 17
First hack the 9.2 3ds using https://plailect.github.io/Guide/
Then hack the 11.0 3ds with https://plailect.github.io/Guide/dsiware-downgrade
edit: ninjaed. as those above me said.
As far as the 6.2 firmware device, I suggest you follow this guide:
https://plailect.github.io/Guide/
it will also help you with the 11.1 device, but you need to complete the guide with the 6.2 device first.
Ok so I got as far as section III configuring Luma3DS, but on section IV i'm confused. I already have a NANDmin.bin file in files9. And I don't know of any other NANDmin.bin file I could replace it with... I opened hourglass and restored and rebooted but now the screen wont turn on. The blue light is working but the screen stayes blank.
I'm pretty sure I did everything correct before section IV. I just have no idea the other NANDmin.bin file is ment to come from.
Can you still boot into hourglass9? You may have flashed the wrong NAND, but if you used hourglass9, it should allow you to still boot into your A9LH payloads.
Yah. Select+boot brings up Luma just fine, select+start brings up hourglass just fine too.
Try if you still have the emuNAND on your SD card, do a full back up, not a min one. Then flash that full back to your sysNAND, obviously still using hourglass9.
Always restore your NANDs using hourglass9. Decrypt9 is a great tool, but it can easily replace your A9LH if you don't know what you are doing.
Plus better safe than sorry.
Blue screen on boot with bootrom error = brick
black screen with blue light on = not brick
There are several different forms of bricks. If your system boots to just a black screen with only a blue light, it's bricked. It's a different type of brick, but it's still a brick
Bricking an umbrella term, it's not just one thing.
I do have a second sd card is there anything I can do with it to bring it back to it's standered state?
Just a tip to avoid this in the future. Rename your NAND backups after dumping them with something like (sysNAND-date-firmware-DS Model) then you'll never be "unsure" of which backup is which. Also, always check the size of your NAND backups, never just assume it a good dump (the .sha files dumped with the .bin verify the dump on restore) and make two if necessary. To me it just looks like you have a bad dump but without another one I'm not sure what you could do at this point. Maybe a CTRTransfer.
-
@
Maximumbeans:
Man, that's beyond my brain
I'm no good with hardware for now. I'd like to get into hardmods in future though -
@
SylverReZ:
@Maximumbeans, Maybe start practice soldering. Get a cheap-ass soldering iron and follow some good YouTube tutorials.+1 -
@
SylverReZ:
Least my experience has gotten better than over a decade ago. My iron would constantly bump into components and break them.
-
@
Maximumbeans:
Sounds good. I actually did soldering but like 16 years ago for school so uuuuh probably rusty haha
-
@
SylverReZ:
@Maximumbeans, Same here. I did soldering at school from a teacher who I honestly liked since he had plenty of good electronics experience.+1
-
-
-
-
-
@
SylverReZ:
It was like all clear and fancy. Tbf I'm not too experienced with chess, but would like to learn someday.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
