I Just used 2.6.4 and I still got the invalid or corrupted error
When you did the install did it change from 2.0.3 to 2.6.4? like on the install screen?
I Just used 2.6.4 and I still got the invalid or corrupted error
2.0.3 Gives the corrupted error, so I tried using 2.6.4 and 2.6.6. Both of those also give the errorWhen you did the install did it change from 2.0.3 to 2.6.4? like on the install screen?
The guide was updated 15 minutes ago!! o3DS users need data_input_v3 instead of data_input_v4yep, me too. "getting firm1.bin is invalid or corrupted press any button to shutdown" used all the correct files for my O3DS. so it's 2.0.3 that's giving me the error. is there any other compatible version with the o3ds?
The guide was updated 15 minutes ago!! o3DS users need data_input_v3 instead of data_input_v4
Quick question. So then for this we can just rename new3ds90.firm to firm0.bin and same for firm1.
However, for Payload_stage1.bin, would this need to then be compile from the A9LH git? Or is this a universal file?
In the past couple of days I've been developing a brand-new A9LH installer.
It loads all the needed files from the SD card (no more need to build console-specific installers), and it's really fast. Other than that, it's way safer than the original one, as it does the following checks:
- Checks that it's able to encrypt FIRM partitions properly
- If you have a New 3DS and you're doing a first install, it validates your OTP. Sadly I have no way of validating the OTP on an Old3DS.
- If updating from A9LH, it verifies that the NAND keystore is the correct one (just in case) and that FIRM0 is correct before using it.
- Hashes the secret_sector, FIRM0 and FIRM1 from SD (if needed) to verify their integrity.
- Checks that stage1 and stage2 don't exceed a maximum size.
How to use:
- Copy the 3ds folder and the .dat if making a first install, and run the program from a vulnerable firmware; or load the .bin using A9LH itself. Press SELECT for a full install, or to update A9LH if booting from it.
- If you already have A9LH and are thus updating, copy a payload_stage2.bin (which was originally named stage0x5C000.bin) and a payload_stage1.bin to the a9lh folder on the root of the SD.
- If doing a full (first) install, you also need to copy these files to the a9lh folder: firm0.bin (which was new3ds90.firm), firm1.bin (which was new3ds10.firm), secret_sector.bin (only needed on Old 3DS) and your personal otp.bin.
Thanks go to everyone in #cakey on IRC, to delebile for his A9LH implementation, and to StandardBus who hardmodded my consoles and made this possible. Code for writing to the screens is from CakesFW.
Download: https://github.com/AuroraWright/SafeA9LHInstaller/releases
Use Plailect's guide.So we just need downgrad in 9.2. Use otp dumper and install with hbl?
We don't need create emunand, 2 format etc?
Use Plailect's guide.
Rename arm9loaderhax.bin to arm9loaderhax_si.bin@Aurora Wright : I use the guide i install arm9loader but its noscreeninit where can i download with screen init for boot animation?
Thanks
It will autodetect if you have old3ds and say the exploit failed. However you should be using the a9lh guide as otpless is considered unsafe as of right now. https://3ds.guide/Will SafeA9LHInstaller v2.6.7.7 work with O3DS or only N3DS, also will it auto-detect if you have an Old or New 3DS?
Anyone knows how to solve this?On section 2 of the updating luma guide, i hold down on the dpad and it opens the luma settings. when i press select nothing happens in the luma settings. Is that supposed to happen?
EDIT: nvm, got it to work.
There's been some talk recently about bringing it back, but nothing definitive yet. I don't think running otpless on 11.2 is inherently any safer.@Aurora Wright With the release of SafeHax and being able to gain ARM9 on 11.2, has any research or testing been done to see if the stability of OTPless install increased due to not needing to downgrade? I don't have a hard mod or else I'd be trying it repeatedly.
Dang, it would really streamline the install of n3DS and I would totally do it on my own devices but for my friends I'll be doing the 2.1 downgrade just in case. Don't need the liability on my hands.There's been some talk recently about bringing it back, but nothing definitive yet. I don't think running otpless on 11.2 is inherently any safer.