on 2.1 sysnand, obviuslyI think OTP is locked before a9lh is loaded, so it wont work...
the patches are what make it impossible to boot 2.1 on cfw right? then a cfw WITHOUTH any patch, should work, right?on 2.1 sysnand, obviusly
mayybe YOU are the noob here. we can't boot emunand 2.1 in cfw, or sysnand 2.1 in cfw, BECAUSE OF THE PATCHES! so, if we hadn't had any patch, we could boot 2.1 sysnand in a9lh. and i accidentally deleted my OTP.bin withouth noticing...-snip-
you cannot boot 2.1 from any form of cfw/emunand and you cant boot it without cfw from a9lh eother -snip-
and if you had a9lh you would aleady have an otp
xdmayybe YOU are the noob here. we can't boot emunand 2.1 in cfw, or sysnand 2.1 in cfw, BECAUSE OF THE PATCHES! so, if we hadn't had any patch, we could boot 2.1 sysnand in a9lh. and i accidentally deleted my OTP.bin withouth noticing...
i am saying, a placeholder .bin, that does not apply ANY KIND OF PATCHES and ONLY boot sysnand...xd
u cant use a9lh without patches right now
Unless someone manages to make the normal FW loader as an A9LH payload, I don't see this happening...would it be possible to boot 2.1 on a9lh sysnand, in case someone loses the OTP?
Withouth any kind of patches, not even signature check, or firm protection, only a sysnand booter (and to go back to 9.2+ obviusly it is needed a nand backup)
it's actually pretty simple.the PATCHES are what make it impossible to boot 2.1, so, if you had a cfw with NO PATCHES AT ALL (not even sig check or firm protection) it should be able to boot 2.1 sysnandUnless someone manages to make the normal FW loader as an A9LH payload, I don't see this happening
Which means we would need the stock FW loader as an A9LH payload...it's actually pretty simple.the PATCHES are what make it impossible to boot 2.1, so, if you had a cfw with NO PATCHES AT ALL (not even sig check or firm protection) it should be able to boot 2.1 sysnand
no, a CFW with no patches at all, that ONLY boots sysnand is enoughstock FW loader as an A9LH payload...
"Stock"no, a CFW with no patches at all, that ONLY boots sysnand is enough
thar is NOT NEEDED. that is what i meant, it is NOT NEEDED! just a cfw that acts like one!"Stock"
I was refering to what Ninty has always used
if someone willing to do....no, a CFW with no patches at all, that ONLY boots sysnand is enough
yeah, obviusly ONLY if someone wants to do it, otherwise, i guess it will be possible to survive even withouth it.if someone willing to do....
Pratically the official firm loader but that can be loaded by stage2 of a9lhthar is NOT NEEDED. that is what i meant, it is NOT NEEDED! just a cfw that acts like one!
1.) the reason is to go back on the main branch (i am in a franken a9lh between delebile and dark samus3 that i installed when the screen init was first released)If you have you used a arm9loaderhax.3dsx long ago when you compile your otp with it, you can use otp helper to extract it but why would you need your otp again? Also if your successfully downgraded then don't you have a working 2.1 downgrade files in you computer?
The same happened to me, I followed the same guide, the same day, and the day tomorrow I did it once again as I lost my otp1.) the reason is to go back on the main branch (i am in a franken a9lh between delebile and dark samus3 that i installed when the screen init was first released)
2.) at the time, in the guide before otphelper was even a thing, i COMPLETELY forgot to do a NAND backup, because the guide didn't told me...