This seems to imply that Luma is starting up, but then hits an unrecoverable error and powers off.
What happens if you hold Select while turning it on?
Nothing happens. Blue light comes on and goes off.
This seems to imply that Luma is starting up, but then hits an unrecoverable error and powers off.
What happens if you hold Select while turning it on?
Light comes on, stays on.Can you try this build of Decrypt9WIP as arm9loaderhax.bin: https://github.com/d0k3/Decrypt9WIP/releases/download/20160309/Decrypt9WIP-20160309-160637.zip
It's the first release with full A9LH support from last year.
That wouldn't explain why it shuts off when Luma is the A9LH payload on the SD.Light comes on, stays on.
I visually inspected all ribbon cables internally and checked to ensure they were properly seated. Does this sound to anyone like a hardware problem with the screens? Maybe it's booting up, but I can't see anything because the screens or cables have gone bad?
I'm thinking for this specific one, the old build of Decrypt9WIP doesn't have screen init, and the build of A9LH that's installed doesn't have it.Light comes on, stays on.
I visually inspected all ribbon cables internally and checked to ensure they were properly seated. Does this sound to anyone like a hardware problem with the screens? Maybe it's booting up, but I can't see anything because the screens or cables have gone bad?
I'm thinking for this specific one, the old build of Decrypt9WIP doesn't have screen init, and the build of A9LH that's installed doesn't have it.
Try setting up BootCtr9 with screen init enabled in the configuration:
https://github.com/hartmannaf/BootCtr9/releases
Copy over arm9loaderhax.bin and the boot config file. Edit the config file to ensure screen init is enabled and that the default entry is something like Decrypt9WIP.bin. You'll also want to copy Decrypt9WIP.bin to the card.Just copy over the .bin and rename it to arm9loaderhax.bin? Tried this and the blue light comes on, shuts off, lower screen flashes.
[BOOTCTR9]
key_delay = 1000
boot_splash = 0
enableAutosoftboot = 1
enableArm9CompanionBoot = 0
[DEFAULT]
path = /Decrypt9WIP.bin
delay = 1000
splash = 0
screenEnabled = 1
screenBrightness = 0x30
Copy this into boot_config.ini:
Then copy Decrypt9WIP.bin to the root of the SD card, and BootCtr9's arm9loaderhax.bin as well. Then try turning it on.Code:[BOOTCTR9] key_delay = 1000 boot_splash = 0 enableAutosoftboot = 1 enableArm9CompanionBoot = 0 [DEFAULT] path = /Decrypt9WIP.bin delay = 1000 splash = 0 screenEnabled = 1 screenBrightness = 0x30
How will that help if he can't get into SafeArm9Installer?Do you have a folder named a9lh with payload stage files located in it? Payload stage 1 and so on. If not, get every required file from the 3ds.guide. You'll need a torrent client to download some of the files though.
He actually has to load the payload. He needs a9lh to to so.How well that help if he can't get into SafeArm9Installer?
If you read the thread you'll see he can't get into any payloads.He actually has to load the payload. He needs a9lh to to so.
I know. That's why I said he needs a9lh to load them.If you read the thread you'll see he can't get into any payloads.
Do you have a folder named a9lh with payload stage files located in it? Payload stage 1 and so on. If not, get every required file from the 3ds.guide. You'll need a torrent client to download some of the files though.
The /a9lh/ directory is only used during A9LH installation. Once installed, that directory isn't used.I know. That's why I said he needs a9lh to load them.
Well, I'm dumb. I've exhausted everything I can do to help.The /a9lh/ directory is only used during A9LH installation. Once installed, that directory isn't used.
You don't need /a9lh/ on a system that already has A9LH installed.
It's starting to sound like there's some sort of hardware problem, possibly a small tear in one of the LCD ribbon cables.