Hacking [Release] lesshax - CFW Optimized 9.2 Payload
- Thread starter gameking66
- Start date
- Views 75,852
- Replies 426
- Likes 79
Pretty sure no one really tried and op won't post them anymore because of the shit he got for adfly links
I would have said "no one cares anymore about bootrate and debug prints with arm9loaderhax", but maybe your argument works too.
Yeah, like a9lh is installed on right about every device now, is it. I'll stay the hell away from it until it's completely bricksafe.
I didn't mean "it's everywhere", just that the ones who care the most about boot rate and silent boot have it.
And it will probably never be more bricksafe than what it currently is. It used to ask you to downgrade your sysNAND directly (which is something you only do if you have a death wish) but now the OTP guide gives the most bricksafe method there can be to get your OTP (downgrade an emuNAND (no one cares if it fails, you can do it over and over) then send it to sysNAND). Then, installing arm9loaderhax once you have will always write something to your 3DS, which will always be the same amount of dangerous, no matter what.
Actually there is something you can do to make it nearly 100% bricksafe.
Currently downgrading emuNAND only ensures you don't get a partial downgrade. You still can't boot the emuNAND to verify it's successful. If we get emuNAND to launch 2.1 (it's obviously possible - it's just no one has worked on it yet), we can verify that it will really boot before flashing. That would make it pretty damn brick safe.
That's what I was thinking of.
It should work in theory, if only we had a way to verify that the downgraded emuNAND boots, then we'll be bricksafe without a doubt.
What stops emunand from booting up after the 2.1 downgrade though?
On n3DS you have to patch some stuff to make it work with n3DS. But that's a non-issue and we have that scripted/automated already.
Beyond that, it's the same reason not all CFW supports 10.6 emuNAND. Different NATIVE_FIRM, different offsets, and generally just not tailored to work with that FIRM version.
Oh I see.
So the reason why the 2.1 emunand works is basically because the CFW availables are only focused on 9.0 and above FIRMs, right?
If they added the offsets, NATIVE_FIRM and other required stuff for 2.1, then the emuNAND would boot and we would have a way to verify that we are completely brick safe.
True this. Still not as bricking as the old method but booting the 2.1 emuNAND would help. Now that you mention it, I also have a friend who downgraded his 3DS to 9.2 and everything seemed to work until we tried the browser (I don't remember what it did exactly but browserhax did not work). Same here, if everything works on 2.1 except the browser, it's pretty much a complete loss.
Now, I don't know if someone would make a change to their CFW to support 2.1 "just" for testing purposes while OTP dumping...
Now, I don't know if someone would make a change to their CFW to support 2.1 "just" for testing purposes while OTP dumping...
I am...
confused?
I came here after:
A. Reading about it on wurstpistole's N3ds Emunand guide
B. Seeing it on "that 3ds iso site"
and C. downgrading and setting up an emunand on my little brother's 3ds that I decided I don't want him to screw up
And, I follow the directions to make the payload generation work
and, nothing happens
Python just opens up for a fraction of a second and closes, and there's no "payload" folder to be found. any help? Or is help pretty much done for this project?
confused?
I came here after:
A. Reading about it on wurstpistole's N3ds Emunand guide
B. Seeing it on "that 3ds iso site"
and C. downgrading and setting up an emunand on my little brother's 3ds that I decided I don't want him to screw up
And, I follow the directions to make the payload generation work
and, nothing happens
Python just opens up for a fraction of a second and closes, and there's no "payload" folder to be found. any help? Or is help pretty much done for this project?
I mainly stayed away because you can't boot your n3ds without an SDcard after you install a9hl.
Also.
On this.
As an idiot with the N3ds, what the heck is a9hl?
I'm passably literate (I think) on O3ds terminology, but I've never heard of this :/
Arm9LoaderHax.
It enables Hax before your 3DS "boots" up. Unlike Menuhax which is enabled once theme data from your sysNAND is loaded.
Arm9LoaderHax also has a 100% boot rate and faster boot times. You need to obtain your 3DS' OTP to use Arm9LoaderHax though.
yeah, lol
As for my problem, I don't know and actually don't care anymore because I got the loads from a second source, so I don't need to build them anymore
though it does but me that all these things that should work for me don't work (rxtools n3ds, this, and many other things)
--------------------- MERGED ---------------------------
My 3ds... OTP...
ok
I'm just going to say I'm confused because it seems our definitions of "OTP" are likely different
would you care to inform me of yours? XD
What? One True Pairing of course!
Oh wait? We're talking about the 3DS...
It's a console specific key. It's needed to compile Arm9LoaderHax, using someone else's OTP would brick your 3DS.
To obtain your OTP, you'd need to downgrade to 2.1, as the OTP gets locked at boot >3.0.
Here's a guide in case you wanna give it a shot!
https://plailect.github.io/OTP/
I call it One True Pain of a file to dump.
Dropping some info on this, I downloaded the latest version available posted, it does have low boot rate.
I do hope the compiling errores for the latest commits can be sorted out so that we can have the compiled ropbin available here.
Last edited by ShadowOne333,
Similar threads
-
- Article
-
- Portal
- No one is chatting at the moment.
-
@
Skelletonike:
I'll be picking up my Zelda LE after work. <3+1
The store did not let me down this time
. -
-
-
-
-
-
@
Skelletonike:
Pondered about the switch, but had bought the pokemon one not long ago and I don't really need two switches (gave my previous one to a cousin).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
