I note than we can now install a9lh from 2.1.0 directly. However, we need to have a backup to restore after the install since Luma3DS can't boot a 2.1.0 system.

Would it be possible to install a9lh on an old 3DS that is already on 2.1.0, then use a cartridge and boot into it with A+B+X+Y+R to update, or with update it recovery mode, going straight to 11.0? So basically, whether Luma not being able to boot into 2.1.0 will affect automatic cartridge loading or recovery mode, and if you can still update from a cartridge you'd loaded like that.

I was thinking I could 1) Install a9lh, 2) Update to 9.2 with Gardening Mama, then 3) Use Ninjhax for homebrew missing a high browser version to inject or install FBI
OR 2) Update to 11.0 with recovery mode, and 3) Use FreakyHax to inject or install FBI (should work since I would have a9lh at this point, right?)

Thanks if anyone can answer :-)

 

Is it possible to find an earlier version of the guide where you did install a9lh on 9.2? That's what I was going to do, but the guide has changed a LOT since I did mine in March.

 

Click the "75 revisions" link at the top and pick one from March
Click the hex number on the right to view that revision.

 

Follow this guide to get your OTP.bin:
Link: https://github.com/Plailect/Guide/wiki/9.2.0-Update-(Browser-OTP)

Or with Cubic Ninja, use this to get your OTP.bin
Link: https://github.com/Plailect/Guide/wiki/9.2.0-Update-(Cubic-Ninja-OTP)

Then you'll need a 4.x.x or 6.x.x cart game update. (use 3dsdb.com to find one)
Using this part to apply the cart update: https://github.com/Plailect/Guide/wiki/9.2.0-Update-(Cart-Update)

Then after that, you want to follow this part to safely get to 9.2.0.
Link: https://github.com/Plailect/Guide/wiki/9.2.0-Update-(rxTools-2.5.2)

Then as the first link I showed you says, do the following:
Do Part 5 - arm9loaderhax

• Copy SafeA9LHInstaller's 3ds folder instead of the arm9 and arm11 bin files
• Launch SafeA9LHInstaller from Homebrew menu instead of browser
• Skip steps related to "emergency files"
• Skip steps related to "RedNAND"
• Skip Section IV and Section V
• Update to the latest system version after completing Section VI

And you should be all set.

 

I could be wrong, but might they not be able to install a9lh on 2.1 directly, then just do an emergency restore or whatever?

**EDIT**
Yup, was wrong. This wont work

 

Recovery mode wont boot either?

 

Recovery mode does NOT remove A9LH, however I did get confirmation from Plailect that it wont work anyways, because LUMA wont boot the recovery mode from 2.1 either.

So ignore the suggestion

 

If Ninjhax 2 still requires the browser, so he can't cart update to 9.2 and use Ninjhax, wouldn't cart updating to 9.3-10.4 and using Ninjhax have the same problem?

(But if he has OOT+Powersaves, or Freakyforms, would it work if he cart updated to 9.2 and then downgraded using Freakyforms or OOT?)

 

Then it looks like the guide isn't quite right. That whole section of the guide is odd, actually:
-- The 2-6 browser column doesn't mention cart updating to 9.3-10.x, even though there are rare cases where it could be useful (i.e. they need a 4.x or 6.x cart update to use rxtools, do not have one, but do have OOT, Powersaves, and a 9.x-10.x cart update. This scenario is only possible with OOT since Freakyforms will update them to 4.x)
-- Neither column mentions cart updating to 9.0-9.2 and then using OOT/Freakyforms as a homebrew entry point. (Would using OOT/Freakyforms work to run the a9lh installer on 9.x?)
-- The 4.x section has an option "6.X.X-0 Cart Update then 6.X.X-0 MSET"; this option is never useful under 4.x (since you could do 4.x mset instead). I asked Plailect about this one and he wouldn't fix it.
-- The entire guide fails to state that Ninjhax requires the browser and can fail if they upgraded all the way to 9.x-10.x and still have no browser at all.
— Posts automatically merged - Please don't double post! —

Actually, if he started on 2.1 and got the OTP already, the question wouldn't be downgrading using OOT/Freakyforms, the question would be running the a9lh installer using OOT/Freakyforms. Although the question of downgrading using OOT/Freakyforms would still exist in other cases.

 

The point about the 6.x is that you would have no reason to update to 6.x and use 6.x mset, since you can already use 4.x mset.