Hacking Black screen after installing A9LH

Capitán Retraso

GBATemp's Retard
Member
Joined
Nov 5, 2015
Messages
161
Reaction score
134
Trophies
0
Location
The Abyss
XP
1,042
Country
Spain
I recently installed A9HL on my o3ds and everything wroked fine, got the otp, restored the nand...
But when i installed a9lh, after the installation there was a black screen for about 5 minutes (that didnt happen to my other 3ds when I installed it), so i rebooted the 3ds and it keeps with the same black screen, there isnt any backlight either
And yes, I have the arm9loaderhax.bin and Luma3ds' files on the sd card
I also tried recovery and it doesnt work, nothing happens, tried to remove the sd and power on and do recovery without it but nothing happens, everything stills black.
Anything I can do to fix this or any suggestions?
 
No, just opened the arm9loaderhax.3dsx from ctrbootmanager
Well, that's probably why. I hate to say it, but you've bricked. (Unless plai's guide has been updated and it doesn't say anything about booting into minipasta before installing a9lh.)
 
Well, that's probably why. I hate to say it, but you've bricked. (Unless plai's guide has been updated and it doesn't say anything about booting into minipasta before installing a9lh.)
Its strange because i first installed a9lh on my other 3ds using the same method, not plais guide but a youtube guide and it worked perfectly
 
Its strange because i first installed a9lh on my other 3ds using the same method, not plais guide but a youtube guide and it worked perfectly
NEVER USE YOUTUBE GUIDES.

They get outdated, Plai's guide is the safest possible install because it's updated often.
 
So what? Do we need to do it or not? I'm already wary of doing the OTP process, if the steps in the guide aren't even consistent then...I'm not sure I will take the plunge...
 
So what? Do we need to do it or not? I'm already wary of doing the OTP process, if the steps in the guide aren't even consistent then...I'm not sure I will take the plunge...
If it's not in the guide anymore then you don't need to. It's constantly altered as the tools we have change and things become easier.
 
So what? Do we need to do it or not? I'm already wary of doing the OTP process, if the steps in the guide aren't even consistent then...I'm not sure I will take the plunge...
Just follow the guide - I got A9LH on my 3DS with MiniPasta and A9LHInstaller on an older guide version, and installed A9LH on a friends 3DS without MiniPasta and SafeA9LHInstaller. It changes, but as long as you read the guide, you'll be fine.
 
But that guy/girl apparently bricked after NOT booting Minipasta...
It could've been due to something else, such as their OTP not being extracted correctly. (That's why you always check the size of your OTP.)
 
Try recovery mode? Take out your SD card, reboot your system while holding onto the L/R, A and Up on the d-pad.

I had a similar situation - had to reflash a system when I took off A9LH (getting a "stock" 9.2 sysnand backup), and ended up with a black screen upon reboot.

I tried a couple of times and got it working again.
 
Black screen on SysNAND boot after installing arm9loaderhax
  1. Ensure you have a working payload.
    1. Check for the existence of arm9loaderhax.bin in the root of your SD card.
    2. If you are following the Luma3DS guide, check that
      1. /luma/firmware.bin exist; and
      2. /luma/firmware.bin is the correct one for your console.
    3. If you are following the CakesFW guide, check that
      1. /arm9bootloader.bin exists;
      2. /Cakes/firmware.bin and /Cakes/firmkey.bin exist and are the correct ones for your console; and
      3. /boot_config.ini exists.
  2. Test booting Decrypt9
    1. On CakesFW, hold X on boot
    2. On Luma3DS, hold Start on boot
  3. Try this test payload (mirror).
    1. Rename /arm9loaderhax.bin, if it exists, to something else.
    2. Place the arm9loaderhax.bin from the archive linked above in your SD root.
    3. Insert your SD card into your 3DS and power on.
    4. Press A. Your 3DS should power off; this means arm9loaderhax is working and something else is broken; your device is not bricked.
  4. Your 3DS may be bricked. For real time support, contact me or any other channel operator at #3dshacks on Rizon IRC
Taken from Plailect's Guide
 
  • Like
Reactions: Deleted User

Site & Scene News

Popular threads in this forum