Hacking Is my A9LHed 3ds bricked?

[Artur_Filho]

[SOLVED] I installed A9LH and luma, everything was great. There was rainbows and unicorns everywhere.

One day, my 3DS started refusing to boot to NAND and EMUNAND. I can still enter the menu and Hourglass and the other stuff. Just not NAND/EMUNAND.

Since I was in the 6.3 version of Luma, I tried downgrading to the old arm9loaderhax.bin.bak file. I tried using another SD card. I tried to inject the emunand in my SD card to the NAND. Nothing works, it simply won't boot

I ran out of ideas, could anyone lend me a hand, please

EDIT: Forgot to mention, when it tries to boot the nand, it goes to a black screen but when it tries to boot emunand it says:

An old unsupported EmuNAND has been detected. Luma3DS is unable to boot it.

Press any button to shutdown

EDIT 2: SOLVED! It was actually my R4i DS cartridge that somehow was preventing the NAND from booting, I took it off and know it works perfectly!

 

[Deleted-379826]

I installed A9LH and luma, everything was great. There was rainbows and unicorns everywhere.

One day, my 3DS started refusing to boot to NAND and EMUNAND. I can still enter the menu and Hourglass and the other stuff. Just not NAND/EMUNAND.

Since I was in the 6.3 version of Luma, I tried downgrading to the old arm9loaderhax.bin.bak file. I tried using another SD card. I tried to inject the emunand in my SD card to the NAND. Nothing works, it simply won't boot

I ran out of ideas, could anyone lend me a hand, please

EDIT: Forgot to mention, when it tries to boot the nand, it goes to a black screen but when it tries to boot emunand it says:

If you can't find the answer, I hope you have a backup to restore with hourglass9! This should definitely fix it!

 

[GilgameshArcher]

Backup SD, format SD completely, stop using EmuNAND, and restore a valid NAND backup to SysNAND.
The best combination for common gamers users are A9LH + Luma + up to date SysNAND

 

[proflayton123]

When removing sd card if it flashes blue then turns off you haven't bricked

 

[nechigawara]

When removing sd card if it flashes blue then turns off you haven't bricked

A9LH is running find cause he can boot to both Luma Menu & Hourglass.
The problem should be on EmuNAND or SysNAND.

 

[proflayton123]

A9LH is running find cause he can boot to both Luma Menu & Hourglass.
The problem should be on EmuNAND or SysNAND.

A backup restore prior to the problem should fix it


Sent from my iPhone using Tapatalk

 

[Sonic Angel Knight]

Excuse me i just like to point out something. While most people will agree with restoring a working nand from before problems occur, it doesn't me it will "ALWAYS" Fix the problem. Essentially this process can be seen as identical to system restore points or memory card save data or just "Check points" in your situation.

I have threads that explains why i am saying this as i have a current unknown problem with one of my 3ds that pressured me to buy a new one. While also i had the idea of using a working one to fix a not working on "Both using a9lh" I found no solution. Yet in most comments on the following page suggest as the first thing "Restore nand backup" Which did not work. So please do not assume it will 100% fix your problem.

https://gbatemp.net/threads/home-me...-and-freeze-system-with-music-playing.441259/

The second link was my idea of using working system to fix not working system, while i do not know so much of the problems that could happen with a9lh, i do know from reasonable deduction, that restoring nand did not fix my problem. I know that nand is not corrupt as i think it is, weather it be home menu or the entire firmware, since i did take a suggestion from another person to create emunand on working system, then ctrtransfer nand to emunand, which if the system did not load, would me the nand was the problem. So while i found it did indeed bear no results with the not working system, as well as changing cfw, not just using luma produces problem but corbenick (Skeith) does as well. There was also another person who calim to have same problem i have. HERE.

http://gbatemp.net/threads/possibil...-on-3ds-with-a9lh-using-a-working-3ds.443127/

Currently i still have no idea what to do about this, but i hope a problem is fixed. Perhaps is the system itself as hardwware, but i doubt it. I can still run a9lh payloads on boot. As far as i am concerned, perhaps this has nothing to do with the current OP problem but still i just wanted to state that is not right to assume one method will always be the solution, especially one i think is probably best suggested as the last option as it by far the most time consuming process, while perhaps a quicker one can be determined if possible.

Apprently only hope i have is enough people were to encounter the same problem, then enough reports about it will probably have people consider investigating this problem for a fix.

 

[Artur_Filho]

-------

Man, I followed your first link and someone asked if there was a DS cartridge inserted in tha thread. I did, so I took my DS card off and now IT WORKS!!!!

Real thanks to you and all of you who tried to help! Who knew it would be such a simple fix? xD

 

[Sonic Angel Knight]

Man, I followed your first link and someone asked if there was a DS cartridge inserted in tha thread. I did, so I took my DS card off and now IT WORKS!!!!

Real thanks to you and all of you who tried to help! Who knew it would be such a simple fix? xD

Your welcome? I guess... kinda maybe made my point, I'm currently in a state of confliction and confusion.

But i guess i did make a point. Glad i help.. i think.

 

[el_gonz87]

Excuse me i just like to point out something. While most people will agree with restoring a working nand from before problems occur, it doesn't me it will "ALWAYS" Fix the problem. Essentially this process can be seen as identical to system restore points or memory card save data or just "Check points" in your situation.

I have threads that explains why i am saying this as i have a current unknown problem with one of my 3ds that pressured me to buy a new one. While also i had the idea of using a working one to fix a not working on "Both using a9lh" I found no solution. Yet in most comments on the following page suggest as the first thing "Restore nand backup" Which did not work. So please do not assume it will 100% fix your problem.

https://gbatemp.net/threads/home-me...-and-freeze-system-with-music-playing.441259/

The second link was my idea of using working system to fix not working system, while i do not know so much of the problems that could happen with a9lh, i do know from reasonable deduction, that restoring nand did not fix my problem. I know that nand is not corrupt as i think it is, weather it be home menu or the entire firmware, since i did take a suggestion from another person to create emunand on working system, then ctrtransfer nand to emunand, which if the system did not load, would me the nand was the problem. So while i found it did indeed bear no results with the not working system, as well as changing cfw, not just using luma produces problem but corbenick (Skeith) does as well. There was also another person who calim to have same problem i have. HERE.

http://gbatemp.net/threads/possibil...-on-3ds-with-a9lh-using-a-working-3ds.443127/

Currently i still have no idea what to do about this, but i hope a problem is fixed. Perhaps is the system itself as hardwware, but i doubt it. I can still run a9lh payloads on boot. As far as i am concerned, perhaps this has nothing to do with the current OP problem but still i just wanted to state that is not right to assume one method will always be the solution, especially one i think is probably best suggested as the last option as it by far the most time consuming process, while perhaps a quicker one can be determined if possible.

Apprently only hope i have is enough people were to encounter the same problem, then enough reports about it will probably have people consider investigating this problem for a fix.

Wired I accidentally ran over my old 3ds with my car and a namd backup wouldn't work either... 'D

 

[Sonic Angel Knight]

Wired I accidentally ran over my old 3ds with my car and a name backup wouldn't work either... 'D

Two things i don't understand about this comment.

1. Reason for quoting my post.
2. What the heck does this even have to do with the quote or thread in general.

 

[el_gonz87]

Two things i don't understand about this comment.

1. Reason for quoting my post.
2. What the heck does this even have to do with the quote or thread in general.

Just having a laugh at the rant about people suggesting a nand backup.

Yeah it doesn't address most issues, but is an easy fix for 90% of issues. Why spend a week hunting down something that could have been resolved in 1 hour?

 

[Sonic Angel Knight]

Just having a laugh at the rant about people suggesting a nand backup.

Yeah it doesn't address most issues, but is an easy fix for 90% of issues. Why spend a week hunting down something that could have been resolved in 1 hour?

That is like asking "Should i just take the easy way out or the hard way?" Again, suppose the easy way doesn't work? Then you stuck with only trying to find another way. While this is a opinion suggested statement, i understand it makes total sense by this. But in the process of trouble shooting problem with multiple different methods, if you ever find yourself in same situation again, you know more methods that can fix your problem than just one.

Easy way = restore nand back up (Probablilty of fixing issue)
Hard way = Trouble shoot problem, learn more ways to fix problems.

Over the course of this you gain more knowledge that can be helpful in future, with more than one way to fix your problem. what are you gonna do if you only rely on one way to fix everything and it fails you? Give up or keep trying, either way pursuit of knowledge helps a lot.

Also this or the preveious comment wasn't a rant, just sharing a opinion about something i felt was necessary. Again, you are right, it could fix the problem and save time on other fixes that may fail but the key word is "COULD" meaning is possible, just like all other possible fixes, we don't know until we try. That how things work i guess.

Basically is up to the individual to take that risk, i just think that should always be the last option to be suggested.

 

[Artur_Filho]

That is like asking "Should i just take the easy way out or the hard way?" Again, suppose the easy way doesn't work? Then you stuck with only trying to find another way. While this is a opinion suggested statement, i understand it makes total sense by this. But in the process of trouble shooting problem with multiple different methods, if you ever find yourself in same situation again, you know more methods that can fix your problem than just one.

Easy way = restore nand back up (Probablilty of fixing issue)
Hard way = Trouble shoot problem, learn more ways to fix problems.

Over the course of this you gain more knowledge that can be helpful in future, with more than one way to fix your problem. what are you gonna do if you only rely on one way to fix everything and it fails you? Give up or keep trying, either way pursuit of knowledge helps a lot.

Also this or the preveious comment wasn't a rant, just sharing a opinion about something i felt was necessary. Again, you are right, it could fix the problem and save time on other fixes that may fail but the key word is "COULD" meaning is possible, just like all other possible fixes, we don't know until we try. That how things work i guess.

Basically is up to the individual to take that risk, i just think that should always be the last option to be suggested.

Actually I did try to flash a backup NAND. (The emunand's nand was basically that, I haven't touched the emunand since I installed A9LH and Luma)

It didn't work for me, because it was a hardware flaw. (Bad contacts in the cartridge slot I guess)

 

[el_gonz87]

That is like asking "Should i just take the easy way out or the hard way?" Again, suppose the easy way doesn't work? Then you stuck with only trying to find another way. While this is a opinion suggested statement, i understand it makes total sense by this. But in the process of trouble shooting problem with multiple different methods, if you ever find yourself in same situation again, you know more methods that can fix your problem than just one.

Easy way = restore nand back up (Probablilty of fixing issue)
Hard way = Trouble shoot problem, learn more ways to fix problems.

Over the course of this you gain more knowledge that can be helpful in future, with more than one way to fix your problem. what are you gonna do if you only rely on one way to fix everything and it fails you? Give up or keep trying, either way pursuit of knowledge helps a lot.

Also this or the preveious comment wasn't a rant, just sharing a opinion about something i felt was necessary. Again, you are right, it could fix the problem and save time on other fixes that may fail but the key word is "COULD" meaning is possible, just like all other possible fixes, we don't know until we try. That how things work i guess.

Basically is up to the individual to take that risk, i just think that should always be the last option to be suggested.

I understand, I just have a different view. If most issues are resolved by restoring a nand backup, then that is the first thing you should do. Think of it this way, if an issue is fixable by a nand reflash then it is a nand related issue (most will be), if it is not then it has nothing to do with nand. Why spend time on the nand related issues to learn about fixing the nand, how's that applicable to fixing say a failed A9LH install that messes up your firms. How will resolving a black screen in a menu help with fixing some critical issues not resolved by a nand reflash?

I guess I just think of it from a business perspective, always take the low hanging fruit first and problem solve the other major areas. For example I do biostatistics for a pharma company and we largely rely on a programming language for work (easy way) is it 100% dependable? No but, 95%. Why the hell would I spend time writing code from scratch? Sure I'd learn a lot about the backend of what I do, but it would cost my company triple the money. I wouldn't hire me if I took 2x the other guy to do the same project. 'd