Hacking How many paperweights have created A9LH?

[Deleted-379826]

A nice clean install on my O3DS (when it was a lot riskier though), N3DS, my friends N3DS, my brothers O3DS and tomorrow will be my cousins O3DS

 

[N7Kopper]

It's really the downgrade to 9.2 that's the "riskiest" part. My own install for my brand New 3DS landed me with a frankenfirmware consisting of a whopping one undowngraded title. By comparison, forcing the poor thing to run a firmware not even designed for it went without a single hitch.

Of course, that's because of the reason that 9.2 is the magic version in the first place. Reliable exploits. You can end up with a soft brick forcing you into SAFE_MODE_FIRM through no fault of your own on very rare occasions while getting to 9.2. Messing up from there is pure user error. So people who stick with menuhax and emunand or whatever are basically bailing out halfway, after they've done the actual dangerous part. Kind of like being fine with driving a massive lorry over potentially thin ice, but then bailing out of doing the tightrope walk once you get there... even though there are three safety nets below you.

 

[Urbanshadow]

It's really the downgrade to 9.2 that's the "riskiest" part. My own install for my brand New 3DS landed me with a frankenfirmware consisting of a whopping one undowngraded title. By comparison, forcing the poor thing to run a firmware not even designed for it went without a single hitch.

I have to disagree. The worst part is the actual a9lh install in 2.1. Just one, single, hiccup with 2xrsa (and it's not like the most stable exploit ever, either) and your firms can be screwed for good. Just remember you are in fact bricking the system on purpose. The kind of brick a9lh generates is very useful to us because the obvious code execution really early but just one step wrong in the setup and bam, dead system only recoverable with hardmod. Plailect, d0k3 and the other devs did a really good job paving a safe path for us, with little to no chance of random failures. The failures are usually linked to weird system states or user mistakes.

 

[N7Kopper]

I have to disagree. The worst part is the actual a9lh install in 2.1. Just one, single, hiccup with 2xrsa (and it's not like the most stable exploit ever, either) and your firms can be screwed for good. Just remember you are in fact bricking the system on purpose. The kind of brick a9lh generates is very useful to us because the obvious code execution really early but just one step wrong in the setup and bam, dead system only recoverable with hardmod. Plailect, d0k3 and the other devs did a really good job paving a safe path for us, with little to no chance of random failures. The failures are usually linked to weird system states or user mistakes.

So, as far as the end user is concerned, what I said is basically correct. There's about as much chance of a random failure that isn't your fault as there is of you being hit by lightning or something.

 

[Urbanshadow]

So, as far as the end user is concerned, what I said is basically correct. There's about as much chance of a random failure that isn't your fault as there is of you being hit by lightning or something.

Yeah. Like a thousand times more likely than a lightning. But yeah. I won't be the one ignoring the chance (again), though. Call me paranoid if you must.

 

[GreaterDog]

went well on my 2ds and my n3ds, but am keeping my o3ds with menuhax and
crtbootmanager i got some project in mind.

 

[Sumea]

Thank you English Good for GBAtemp is understand very good.
It is very good to be in a thread create by Marko.

 

[Amapola62]

No paperweights for me so far...It's actually water that could have killed my consoles and not A9LH...