Thanks to liomajor for the work around, but GW team still did not fix 3D tracking........
Weird, works for me, no more annoying close-lid-open-lid workaround. I'm using the 4.0a leaked launcher.dat, sysnand 11.0.
Thanks to liomajor for the work around, but GW team still did not fix 3D tracking........
Easy Install using safeA9LHinstaller
This allows to have three stage 2 inside nand to load them
using button combinations while powering your console on!
This includes only stage 1/2 files and installer!
A hardwaremod is highly recommended - use at own RISK!
Toshiba worked, Samsung NAND problem should be gone!
Before installing this mod, please make a backup of your sysNAND!
You will need your very own private otp.bin and other files.
Details:
Code:Stage 2 Button Sector Offset Path File to load payload_stage2.bin = Default = Sector 5C000 = (5C000 * 200 hex) Offset B800000 \ arm9loaderhax.bin payload_stage2_2.bin = X + Y = Sector 5A000 = (5A000 * 200 hex) Offset B400000 \ launcher.dat payload_stage2_3.bin = X + A = Sector 5A100 = (5A100 * 200 hex) Offset B420000 \a9lh arm9loaderhax.bin
1. Extract the rar file to your memorycard!
2. Copy the following files to A9LH folder: OTP.BIN (your own!) / firm0.bin / firm1.bin / secret_sector.bin
3. Either use your desired entry point to load Homebrew Launcher and start safeA9LH installer or update with included arm9loaderhax.bin
4. Press select to install/update a9lh
Already using a9lh? Use arm9loaderhax.bin to update!
Tested and works with my own new3DS XL, Columbo2811 tested his Samsung NAND (old3DS)!
Video from Columbo2811's old3DS booting CFW/GW: > CLICK <
Restoring NAND:
Either, use decrypt9/emunand9 and reinstall your backup nand.bin
or use unedited safea9lhinstaller to update the current installation.
Backing up your sysNAND will include all changes you did!
Known Bugs:
All the bugs inside launcher.dat and thats nothing to fix for me.
Example: launcher.dat doesn't detect region properly for nand.bin restore.
Button Combinations:
Want different combos? Please consider using a boot manager or take one from this!
You can freely change their configuration files and use it as default \arm9loaderhax.bin
I don't suggest to swap launcher.dat's stage 2 to boot by default,
but thats up to you. Currently i'm not taking requests.
Can i change Screen-Init Brightness?
For A9LH loading arm9loaderhax.bin it's possible, example:
payload_stage2.bin / payload_stage2_3.bin offset: 1C88
Currently it's 39, change it to whatever you want.
Have Fun
Yes, you need it. Don't delete it. Unless you want to replace it for another button combination payload_stage1.bin.i need payload_stage1.bin in a9lh folder?
this is my files inside the a9lh folder
i need payload_stage1.bin in a9lh folder?
this is my files inside the a9lh folder
View attachment 51265
Here are variations to Stage 1:
payload_stage1-1st-2nd.bin > 1st loads sector 5A000, 2nd sector 5A100
payload_stage2 = default
payload_stage2_2 = 5A000
payload_stage2_3 = 5A100
Take the stage 1 you desire to load it the way you want
and rename the file to payload_stage1.bin for installation.
This file contains: A/B/X/Y/START, LEFT/RIGHT/UP/DOWN
and for non Luma3DS SELECT/START.
Now you know all buttons, you could even hex edit it.
is the following table correct/safe to use?
Compared, looks right for the current Stage 1.
The offset will change when Stage 1 gets
updated, check if it does match and don't
install if if it doesn't!
it actually works with 4.0a.Thanks to liomajor for the work around, but GW team still did not fix 3D tracking........
Does gateway's arm9loaderhax.bin harms the console?
If no, I would like to have this (even without a gateway flashcard).
I was actually serious.yes
no
maybe
who knows
Who actually knows what Gateway's doing now. Maybe they're trying to fix all of these bugs and compiling a stable release or they're planning a third wave of betas... The only thing we can do now is patiently waiting for their announcement.I was actually serious.
48 hours after the weekend would be then.. right?
I see. You are right.Who actually knows what Gateway's doing now. Maybe they're trying to fix all of these bugs and compiling a stable release or they're releasing a third wave of betas... The only thing we can do now is patiently waiting for their announcement.
9.0 was fine,i'll doing mine without any problemSo just checking, do I need to be on 9.2 or can I be on 9.0 to use the a9lh exploit and guide?
Sent from my Nexus 6 using Tapatalk