Hardware SysNAND broken, EmuNAND fine on a9lh.

[remix2k]

So when I A9LHAXed my system part of the process was to configure CakesCFW to "Block firm partitions updates".
Did you use CakesCFW and enable this patch as well?
If you did, maybe you need to disable this before flashing back a non-a9lh bin?

 

[Dennis G]

So when I A9LHAXed my system part of the process was to configure CakesCFW to "Block firm partitions updates".
Did you use CakesCFW and enable this patch as well?
If you did, maybe you need to disable this before flashing back a non-a9lh bin?

Yes aureinand also has firm blocking and yes i also have cakesfw and yes i've tried that too, and my hardmod ignores the firm protections of cfw so i've restored also with them disabled :s

 

[Dennis G]

inserted video, please watch if you want to see the problem

 

[Dennis G]

pretty sure this goes in the custom firmware section

no because it's not cfw related, it's more about the nand, which makes it more close to nand then cfw :s that's why i choose this section

 

[Dennis G]

really no-one has a clue/solution? :c

 

[Dennis G]

bump, it's still not solved please someone

 

[Just Passing By]

bump, it's still not solved please someone

I have no idea what happened. Sounds like it's either internal or a cfw problem. Try out the newest Aureinand test build. Some things may be broken, but at this point, it sounds like you just want it to work:
http://gbatemp.net/threads/aureinand-n3ds-o3ds-a9lh.411110/page-372#post-6248500

 

[Dennis G]

I have no idea what happened. Sounds like it's either internal or a cfw problem. Try out the newest Aureinand test build. Some things may be broken, but at this point, it sounds like you just want it to work:
http://gbatemp.net/threads/aureinand-n3ds-o3ds-a9lh.411110/page-372#post-6248500

Tried the Beta, sysnand still black screening, emunand still working thogh :s

 

[Just Passing By]

Tried the Beta, sysnand still black screening, emunand still working thogh :s

Mmm I'm sorry, but I have no solution. I've read over the op and what other people have said and I can't tell what's wrong. It sounds like an internal problem, but I'm not sure.

 

[Dennis G]

Mmm I'm sorry, but I have no solution. I've read over the op and what other people have said and I can't tell what's wrong. It sounds like an internal problem, but I'm not sure.

I'm Pretty sure that's something NAND related, like my partition issen't fullt working or something since all the stuff can be put working on emunand then transfered to sysnand and wont

 

[driverdis]

If the NAND is bad but FIRM is intact with A9LH, it makes sense that EmuNAND boots and that copying a working EmuNAND to SysNAND fails to bootup. I would either stick to EmuNAND only for now until you can get a New/Old 3DS to system transfer to.

Using EmuNAND only will not work for GBA and DSi games as these need to be installed while under SysNAND first before they will boot on EmuNAND.

You could install GBA and DSi games to EmuNAND then copy EmuNAND to SysNAND. This may allow GBA and DSi support to work while in EmuNAND but it may not work depending on what part of SysNAND is corrupted.

 

[Yami Anubis ZX]

I'm not good with some stuff but could the sysnand have just died on you? Or would the whole system be useless, if sysnand died? Maybe it's still alive cause you have Emunand and that's why it's still working.

Perhaps you restored sysnand too many times and it just died.

 

[driverdis]

I'm not good with some stuff but could the sysnand have just died on you? Or would the whole system be useless, if sysnand died? Maybe it's still alive cause you have Emunand and that's why it's still working.

Perhaps you restored sysnand too many times and it just died.

It would take hundreds of restores to kill the NAND itself. If SysNAND was fully bad, it would not work at all. However, if it were partially bad and FIRM could be read from the NAND, A9LH could boot into EmuNAND.

 

[Yami Anubis ZX]

It would take hundreds of restores to kill the NAND itself. If SysNAND was fully bad, it would not work at all. However, if it were partially bad and FIRM could be read from the NAND, A9LH could boot into EmuNAND.

When I get my Majoras Mask New 3dsxl back from Hundshamer, I'll make sure just to use Emunand and not sysnand, just in case, I don't want my sysnand going bad, I guess I'm just being overprotective but seeing what happened to this guy, its better safe than sorry.

 

[Dennis G]

It would take hundreds of restores to kill the NAND itself. If SysNAND was fully bad, it would not work at all. However, if it were partially bad and FIRM could be read from the NAND, A9LH could boot into EmuNAND.

Yes i agree but here is the odd thing, if 9.2 sysnand with a9lh would only cause the black screen, okay. but it's litterly every single restore i have even the non a9lh one's they all boot black screen on sysnand :s and only the a9lh can boot emunand , but that's working.

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

When I get my Majoras Mask New 3dsxl back from Hundshamer, I'll make sure just to use Emunand and not sysnand, just in case, I don't want my sysnand going bad, I guess I'm just being overprotective but seeing what happened to this guy, its better safe than sorry.

my emunand works fine, i have no real disadvantages exept for i can't nativly install Nds cia files, because they need to be on sys and emunand. The rest works fine though

 

[Marth_is_Best_Princess]

Something tells me this is a physical NAND damage that no one can really do anything about. Like, at all.
Maybe one of the pins or connections were accidentally bridged/shorted, meaning the internal NAND chip is actually completely dead. Using a hardmod to restore a NAND image doesn't require a working NAND. And since A9LH is run before a NAND is loaded, it can easily boot into a working SD Card's emuNAND.
In all your nand chip is most likely dead due to an error in the hardmod that got worse over time.
All I can think of.

 

[dg_dex]

I wasn't going to login tonight, but your case has peaked my interest. Ok, how did you back your sys nand up originally? Also, can we take a look at your soldering work? This could be a case of bad wiring/soldering.

 

[Expliciate]

Not sure if this has been mentioned, but have you tried deleting the patched_firmware.bin files in aurei?
This may not be as relevant, but was a common issue for those with updated sysNAND trying to boot a 9.0 FIRM. (mixing up FIRM bins)
Seeing that you're on 9.2 sysNAND, it shouldn't be the case, but worth a try?

 

[ChaosRipple]

Maybe because you have MenuHax installed on Sysnand? Look at this thread.

 

[jerrmy12]

Can you flash emunand to sysnand? If you can't boot emunand9, rename your file to be able to flash it