Have you tried contacting the seller yet? Have you tried booting Decrypt9WIP or Hourglass9 according to what I said yet?
Haven't heard from the seller yet, but hope to soon. I had no luck with either the start button or the up on the direction pad.
Have you tried contacting the seller yet? Have you tried booting Decrypt9WIP or Hourglass9 according to what I said yet?
Well, that figures. From what people are saying, it's a messed up a9lh update. I can't help you there, because I don't plan on updating a9lh unless there's a huge feature added or a massive bug fix.Haven't heard from the seller yet, but hope to soon. I had no luck with either the start button or the up on the direction pad.
In case these haven't been suggested, these are from the 3ds.guide Troubleshooting section:
Try deleting the config.bin in the Luma folder (back it up to your computer first) and see if that helps.
Try other payloads. You've tried Luma and Hourglass9, maybe try GodMode9 and Decrypt9 just to be sure.
Try booting without any cartridges inserted, if you haven't done so already.
Yeah you just need the bin file renamed to up_Decrypt9.bin etc in your payloads folder.Thanks for the suggestions! I have tried booting without a cartridge already and tried deleting the file you suggested without success. How, exactly, do you install other payloads like GodMode9 or Decrypt9? Is it as simple as copying over files from the build's zip file?
In case you didn't know, if you use the payloads folder and filenames like up_Decrypt9.bin you will have to hold the respective button (i.e. UP on D-PAD) while turning on your 3DS to launch them.
It's in your luma folder.Which one is the payloads folder? There isn't a folder named "payloads"...is it the "files9" folder?
Thank you!It's in your luma folder.
It's in your luma folder.
I will post everything everything I had with a similar problem, regardless of it's been mentioned prior or not.Thank you!
--------------------- MERGED ---------------------------
Yeah. Get nothing. Either blue light comes on and then shuts off, blue light comes on and shuts off with lower screen flashing, or the blue light stays on with nothing on screens no matter what payload I try (up, start, down, etc). I've tried hourglass, decrypt9, and godmode.
I honestly think something is fubar'd in the hardware.
You don't 'install' payloads; they're run from the SD card. Download the appropriate .zip, extract the .bin file, rename it to arm9loaderhax.bin, put it on the root of your SD card and boot your 3DS.How, exactly, do you install other payloads like GodMode9 or Decrypt9? Is it as simple as copying over files from the build's zip file?
If you hold down the Power button for ten seconds the 3DS should shut off.Only way to turn blue light off is to remove the battery.
That's really strange. The blue light turning off suggests that A9LH is installed correctly, but it can't find a payload, but the blue light staying on with non-Luma payloads suggests a brick. No idea what makes the lower screen flash.When I the arm9loaderhax.bin (latest version from luma) the blue light comes on and then off again. With older versions of luma (and I've tried all of them) the blue light comes on and off and the lower screen flashes.
homebrew/3ds/boot.bin
If you hold down the Power button for ten seconds the 3DS should shut off.
That's really strange. The blue light turning off suggests that A9LH is installed correctly, but it can't find a payload, but the blue light staying on with non-Luma payloads suggests a brick. No idea what makes the lower screen flash.
Have you tried using a formatted SD card that only has a payload, and nothing else? Do you have any information regarding what firmware the 3DS was on before you bought it?
Also, reading your first post, when you say "with my N3DS XL I bought broken via ebay", do you actually mean that it was advertised as being broken, or that it was advertised as working and only discovered that it was broken after you received it?
Thanks, I will look into finding one.I think that the seller did an a9lh update and put wrong files on it (incompatible payload/different OTP) and that bricked the console. Nothing you can do without nand-backup. A hardmod could work if you exploit the firm partition and replace it with a valid one but I'm not sure because firm0/1 is broken (you can do it because the firm partition is always the same on all console+has always the same offset and you can recalculate the firm without xorpads)
I recommend buying a new mainboard and not messing around with it anymore.
is the blue light fading off or just abruptly turning off, it could be something really simple like a faulty sd slot, or even just a loose connector, and if the led is just fading off it means a9lh is setup and running, I think there has been a couple of a9lh builds that have used alternate boot paths like shadownand uses
although shadownand should boot without a sd card inserted
I think the seller updated it from 2.1 or used a wrong OTP. You can try to ctrtransfer to 9.2 via hardmod.
Sent from my iPhone using Tapatalk
To me this sounds like a really old Arm9LoaderHax installation that isn't compatible with any of the more recent payloads.
Try following this.
https://3ds.guide/updating-a9lh.
If I recall correctly SafeA9LHInstaller should probably boot properly on any A9LH install.
This seems to imply that Luma is starting up, but then hits an unrecoverable error and powers off.Interesting thing I noticed today: when I remove everything from the sd card and only put arm9loaderhax.bin on the card and I try to boot it, the blue light comes on and tuns off...but when I put the sd card back into the computer there is now a "luma" folder on the sd card that wasn't there before.