Or by updating your sysNAND from a CFW that does not block firm0/firm1 updates.
Wouldn't this brick the console? as Firmo\Firm1 are corrupted to make al9h works?
Or by updating your sysNAND from a CFW that does not block firm0/firm1 updates.
Wouldn't this brick the console? as Firmo\Firm1 are corrupted to make al9h works?
if you read, i did, I had a nand backup from rx tools before i moved over to a9lh@yusuo Why you didnt take any NAND backups?
(Only a masochistic would do that when installing A9LH)
It shouldn't, but no guarantees. With stock firm0/firm1, it would just boot sysNAND as normal, assuming there is no unsigned content in sysNAND preventing it from booting.Wouldn't this brick the console? as Firmo\Firm1 are corrupted to make al9h works?
Yes.So short answer, flash 9.2 original sysnand using decrypt9, right?
It shouldn't, but no guarantees. With stock firm0/firm1, it would just boot sysNAND as normal, assuming there is no unsigned content in sysNAND preventing it from booting.
the key used to decrypt the firmware on New3DS would stay corrupted though, so it would brick in that instance. you'd need to restore that key somehow, or just flash a pre-arm9loaderhax NAND dump.It shouldn't, but no guarantees. With stock firm0/firm1, it would just boot sysNAND as normal, assuming there is no unsigned content in sysNAND preventing it from booting.
I'm no expert on a9lh, and I think I made that pretty clear. If anyone wants to try this they do so at their own risk.STOP giving this very bad advice !
Some people already tried it, it ends up with brick half of the time, since FIRM get corrupted. See Cakes thread and such, you'll see.
If you want to keep an exploitable sysnand you should downgrade with Sysupdater instead.I'm no expert on a9lh, and I think I made that pretty clear. If anyone wants to try this they do so at their own risk.
Aren't you the one who told me that i was asking stupid questions and that you think you are "superior" to me because you know how to use the forum's search function? That was hypocritical....Questions in the title
He doesn't have one.Aren't you the one who told me that i was asking stupid questions and that you think you are "superior" to me because you know how to use the forum's search function? That was hypocritical....
Anyways, back on topic, you can get rid of that by restoring from a nand backup created before installing a9lh.
Just sell it as a hacked 3DS.Selling the console, its my o3ds, and I hot a n3ds now
They didn't really I got, £84 and I advertised it as a 9.2 3ds, don't know eBay rules on advertising modded things.
I only removed the hack incase someone got it who doesn't know what they're doing and accidentally bricks the thing
You could have installed a bunch of CIAs and used a non-screen init version of a9lh and sold it as a console with installed games. The buyer wouldn't know the difference - you could just give them some general advice about backing up the SD card (which is a good idea anyway).
You could tell them it requires the files on the SD without telling them why. Unless they have some experience with 3ds consoles they'll take your word for it. Plus if you include a decent size card why would they ever want to swap it out?What if the owner swaps the SD card one day ? The console will not boot...