Hacking 2DS is not functioning properly.

My sister purchased this 2DS from Walmart about 1.5 to 2 years ago, right out of the box it was the perfect firmware for soundhaxx, so I followed the guide, and successfully installed Luma (About a week after purchase) It worked fine until January of 2018 (Possibly December of 2017, I'm not sure)

--------------------- MERGED ---------------------------

Not sure if you post your cfw or if you are really on A9LH instead of B9S.
I've never used A9LH. Only B9S. I've hacked like 10 3DS's from the original model to the galaxy n3dsxl. This is the only one I've ever had trouble with
 
  • Like
Reactions: NoNAND
My sister purchased this 2DS from Walmart about 1.5 to 2 years ago, right out of the box it was the perfect firmware for soundhaxx, so I followed the guide, and successfully installed Luma (About a week after purchase) It worked fine until January of 2018 (Possibly December of 2017, I'm not sure)

Boot9strap came out May of last year, depend when you installed cfw.
 
Boot9strap came out May of last year, depend when you installed cfw.
Well, then I honestly don't remember, I know I've never used A9LH, because my friend used it and he told me it was messy. So, it must've been last summer, when I hacked it. Because I remember downloading B9S, and it being fresh.
 
Well, then I honestly don't remember, I know I've never used A9LH, because my friend used it and he told me it was messy. So, it must've been last summer, when I hacked it. Because I remember downloading B9S, and it being fresh.

Try the Luma3ds 7.0.5
 
Well I would see if you can get it to boot any other firms.

boot9strap should try to boot any firm on root of sd card with the boot.firm
so perhaps try downloading godmode9 firm and putting it on root and renaming it to boot.firm and see if that app will start.
I tried changing the gm9 firm to boot.firm, and no dice.

--------------------- MERGED ---------------------------

Yea 7.0.5 is the last version of luma that support A9LH.
What do I do with the files, just put them on root? I've never seen Luma arranged like this
 
Yea 7.0.5 is the last version of luma that support A9LH.
I tried changing the gm9 firm to boot.firm, and no dice.

--------------------- MERGED ---------------------------


What do I do with the files, just put them on root? I've never seen Luma arranged like this

Just put it on the root, for now we are just checking for if you have A9LH or B9S.
 
"TheSecurityGuy, post: 8264427, member: 432268"]I tried changing the gm9 firm to boot.firm, and no dice.

Well that's no good...
Thinking to myself; but sharing my thoughts here

if it is on b9s and we can't boot off the sd card... what could be the issue... It could also just be a weird booting issue
  • could be the SD card itself (make sure it is formatted to fat32 most 4gb to 32gb cards are already) and/or try a different sd card (I believe you already tried some of this earlier in the thread).
  • b9s could of got corrupted (which would be weird as I have not heard of this happening); To fix this one you would probably have to boot off of ntrboot using a ds flashcart and reinstall or upgrade to the latest b9s 1.3; but you would need a ds flashcard of specific type to even try it.
  • The SD card reader itself could be broken... not really sure how to troubleshoot that.
  • weird booting issues are sometimes fixed by removing the device from power; then removing the battery from device, with the battery removed holding down the power button for 30 seconds to drain all excess power from the device, optionally cleaning any contact points on battery and device with isopropyl alcohol, letting dry and then putting back together and powering back on.
  • deleting the luma config and holding select on boot (boot.firm needs to be put back to luma instead of godmode9) to recreate fixed an odd booting issue for me once; but not sure it would help in this case as we couldn't boot to godmode9
  • could be some unrelated faulty hardware issue of some sort; example: wifi card knocked loose after dropping?
  • if you were on normal firmware you could try using recovery mode. Press R+L+A+(D-PAD)-UP while booting; not sure this is an option under b9s.

These are all the things that come to mind; maybe something useful in there...
 
Last edited by SonicMC,
"TheSecurityGuy, post: 8264427, member: 432268"]I tried changing the gm9 firm to boot.firm, and no dice.

Well that's no good...
Thinking to myself; but sharing my thoughts here

if it is on b9s and we can't boot off the sd card... what could be the issue... It could also just be a weird booting issue
  • could be the SD card itself (make sure it is formatted to fat32 most 4gb to 32gb cards are already) and/or try a different sd card (I believe you already tried some of this earlier in the thread).
  • b9s could of got corrupted (which would be weird as I have not heard of this happening); To fix this one you would probably have to boot off of ntrboot using a ds flashcart and reinstall or upgrade to the latest b9s 1.3; but you would need a ds flashcard of specific type to even try it.
  • The SD card reader itself could be broken... not really sure how to troubleshoot that.
  • weird booting issues are sometimes fixed by removing the device from power; then removing the battery from device, with the battery removed holding down the power button for 30 seconds to drain all excess power from the device, optionally cleaning any contact points on battery and device with isopropyl alcohol, letting dry and then putting back together and powering back on.
  • deleting the luma config and holding select on boot (boot.firm needs to be put back to luma instead of godmode9) to recreate fixed an odd booting issue for me once; but not sure it would help in this case as we couldn't boot to godmode9
  • could be some unrelated faulty hardware issue of some sort; example: wifi card knocked loose after dropping?
  • if you were on normal firmware you could try using recovery mode. Press R+L+A+(D-PAD)-UP while booting; not sure this is an option under b9s.

These are all the things that come to mind; maybe something useful in there...

As nothing else has really worked. I dont see why, and why it hasnt been mentioned yet, or a ctrtransfer for the console.
 
yes that is one of my bullet points as a possibility :)
Ya, it sounds like OP has one of those weird mucked up cfw settings as they mentioned they had to hold l or r on power. Altho It may also mean they simply had a key combo set up to launch said file they have.
 
"TheSecurityGuy, post: 8264427, member: 432268"]I tried changing the gm9 firm to boot.firm, and no dice.

Well that's no good...
Thinking to myself; but sharing my thoughts here

if it is on b9s and we can't boot off the sd card... what could be the issue... It could also just be a weird booting issue
  • could be the SD card itself (make sure it is formatted to fat32 most 4gb to 32gb cards are already) and/or try a different sd card (I believe you already tried some of this earlier in the thread).
  • b9s could of got corrupted (which would be weird as I have not heard of this happening); To fix this one you would probably have to boot off of ntrboot using a ds flashcart and reinstall or upgrade to the latest b9s 1.3; but you would need a ds flashcard of specific type to even try it.
  • The SD card reader itself could be broken... not really sure how to troubleshoot that.
  • weird booting issues are sometimes fixed by removing the device from power; then removing the battery from device, with the battery removed holding down the power button for 30 seconds to drain all excess power from the device, optionally cleaning any contact points on battery and device with isopropyl alcohol, letting dry and then putting back together and powering back on.
  • deleting the luma config and holding select on boot (boot.firm needs to be put back to luma instead of godmode9) to recreate fixed an odd booting issue for me once; but not sure it would help in this case as we couldn't boot to godmode9
  • could be some unrelated faulty hardware issue of some sort; example: wifi card knocked loose after dropping?
  • if you were on normal firmware you could try using recovery mode. Press R+L+A+(D-PAD)-UP while booting; not sure this is an option under b9s.

These are all the things that come to mind; maybe something useful in there...

I will try the NTRboot method, next time I see my friend, the wifi card works fine (I've received streetpass data from it on a different 3ds)
I tried the recovery mode, both with the SD in and with the SD card out.
Both SD's are formatted FAT32
Just put it on the root, for now we are just checking for if you have A9LH or B9S.
Additionally, I know for a fact that I have b9s because the original SD had the b9s.firm on it, and I also tried the A9LH thing and it didn't work
 
I will try the NTRboot method, next time I see my friend, the wifi card works fine (I've received streetpass data from it on a different 3ds)
I tried the recovery mode, both with the SD in and with the SD card out.
Both SD's are formatted FAT32

Additionally, I know for a fact that I have b9s because the original SD had the b9s.firm on it, and I also tried the A9LH thing and it didn't work

Try reformat the card using guiformat or minitool partition wizard, back to what I asked before, can your 3ds pick up the SD card in SD card management?
 

Site & Scene News

Popular threads in this forum