Solved.
This is mostly due to NAND partition corruption or fragmentation. It's fixed by partition dump/copy the data/format/copy back/restore.
Done.
Hi, recently some of my friend buy 2DS and do a9lh setup by himself.
but somewhat mistake, he overwrite the nand backup by 2.1.0 nand.
And because of nerve situation, doing a system factory reset cause a 2DS semi-brick.
He was frightened ask me to a help.
[Condition]
- a9lh setup 2DS stuck on 2.1.0-4U USA region (that was Korean region console before)
- No nand backup (actually it has, but 2.1.0 ctrtransfer-ed nand)
- [FIXED] Boot in to 2.1.0-4U factory reset, stuck on setup menu. (2DS Semi-brick)
->>> Now it's boot on homemenu, upper screen is only show half of original resoultion.
- Luckily, a9lh is completed setup, so it work and can use hourglass9, decrypt9
- Use Luma3DS 6.6, and recent release of hourglass9, decrypt9
- Had a knowledge of 3ds system, CFW (Like luma3ds), secureinfo, brick situation and others so on.
- At least I was used the 3ds when the First CFW leaked (GovanifY/Palatine CFW) and used MTCard Emunand that 2 years ago. So, have experienced.
- I had a9lhed system 30 times or more. (So, Not a CFW newbie, but my friends are newbie )
[Goal]
1. Have a Recent updated Emunand or Sysnand with a9lh that same region.
2. And If I had done the first one, region changing. But first one is more priority.
[What I did]
I had oot3D and some other retail cartridge (Bravely Default, NES Remix, Fire Emblem)
So use a 2DSaver(recently release of https://gbatemp.net/threads/2dsaver-beta-fix-your-2ds-format-brick-testers-needed.457828) first to recover from semi-brick situation.
Few minutes later, it was fully recovered. I can see the main home-menu.
I thought it was easy as pie to fix it during this situation. but it was not much EASY as i thought.
[What I stuck]
After the recover from semi-brick, I do a lots of doing like this below
but all of my tries fail to work. see below
Sysnand (2.1.0-4U) -> System update to 11.3.0-36U
==> Error during the 60-70% download, aborted by system and just reboot.
I did many tries but It can't be complete. Always same situation.
Sysnand (2.1.0-4U) -> Recovery mode
====> Not supported SAFE Mode firm from Luma3DS, because it's below then 3.0.
Sysnand (2.1.0-4U) -> make a Emunand (2.1.0-4U)
===> Not supported Firmware by luma3DS (support 2.1 sysnand only), So can't boot
Sysnand (2.1.0-4U) -> Cartridge Update to 6.2.0-4U (Bravely Default)
==> Update complete, but After the reboot, it show a black screen error.
" An Error has occured, hold down the POWER~ blur blur~ visit support.nintendo.com"
Sysnand (2.1.0-4U) -> Cartridge Update to 8.1.0-4U (Ultimate NES Remix)
==> Update complete, but After the reboot, it show a black screen error.
" An Error has occured, hold down the POWER~ blur blur~ visit support.nintendo.com"
Sysnand (2.1.0-4U) -> Ctrtransfer 9.2.0J/E/U (Japan / Europe / USA / and even my own ctrtransfer 11.1.0-30K)
===> Blackscreen. I dunno why, but It just black screen. Same as Emunand
(I already deleted whole 'Nintendo 3DS' folder after the transfer completed, to prevent conflict of leftover homemenu extdata, so that not the reason)
People who reply the the mention about this that could be secureinfo_A or a region problem. (They guess).
So if they are correct, Why is not working 2.1.0-4U to 9.2.0-20U? Isn't it weird?
Emunand (2.1.0-4U) -> Ctrtransfer 9.2.0-20J/U/E (Japan / Europe / USA / and even my own ctrtransfer 11.1.0-30K)
===> Blackscreen. Same as sysnand, Even the Recovery Mode doesn't work
(I already deleted whole 'Nintendo 3DS' folder after the transfer completed, to prevent conflict of leftover homemenu extdata, so that not the reason)
Sysnand (9.2.0-20U/E/J Transfered, blackscreen) -> trying to get a Recovery mode
Sysnand (11.1.0-30K Transfered, blackscreen) -> trying to get a Recovery mode
Emunand (9.2.0-20U/E/J Transfered, blackscreen) -> trying to get a Recovery mode
Emunand (11.1.0-30K Transfered, blackscreen) -> trying to get a Recovery mode
====> D O E S N ' T W O R K
+++ ADDED (02-10-17) +++
Sysnand (2.1.0-4U) ===> H&S injection (FBI, Bigbluebox) using decrypt9
-----> Failed, I don't know why but the after the injection, app doesn't boot (Black screen)
and after the power off and reboot, app has been just disappeared!
(it seems like a very similar with injecting h&s app on virgin-3ds case.)
I tried to this for install sysupdater cia and try to update, but it can't be done.
Isn't that unsigned code running is possible on a9lh (maybe not on 2.1 firm?)?
A9lh running but it's not working... It's really weirdo....
Sysnand (2.1.0-4U) ====> Cartridge Update 4.2.0-4U (OoT3D)
------> Update Complete, Black screen, No error text. JUST BLACK
Sysnand (2.1.0-4U USA) ====> Ctrtransfer to 2.1.0-4U (USA Region)
-------> WORKING, BUT USELESS.
Sysnand (2.1.0-4U USA) ====> Ctrtransfer to 2.1.0-4J/E (Japan/Europe Region)
--------> NOT WORKING.
I did everything that i know, but all of them failed.
The only work nand is 2.1.0-4U. All other doesn't work.
Every ton of my effort useless, I always back to 2.1.0-4U nand after the tried.
It's still stuck on 2.1.0-4U now.
So, What happened...? Is it some kind of new brick?
Does any expert know this situation or have a solution?
Anyway, it's still work with a9lh binary (Luma3DS, Decrypt9, Hourglass9)
The only I didn't get is Higher firmware nand.
Last edited by marine5422,