Hacking RxTools on N3ds (Help)

  • Thread starter Thread starter Ordim3n
  • Start date Start date
  • Views Views 3,790
  • Replies Replies 56
you are better off doing the guide now while 10.8 is not out yet. If you manage to get stuck in a partial downgrade situation that requires updating and trying again after 10.8 is out, you will be stuck as the chances of that patching the downgrade to 9.2 are very high.
Does the system need to be formatted when installing a9lh? I already removed all my girlfriend's saves once (I wasn't able to recover them to the new emunand yesterday no matter how hard I tried) and she just started a new game on harvest moon for the second time which I really wouldn't want to lose.
 
Does the system need to be formatted when installing a9lh? I already removed all my girlfriend's saves once (I wasn't able to recover them to the new emunand yesterday no matter how hard I tried) and she just started a new game on harvest moon for the second time which I really wouldn't want to lose.
u have an emunand? Install jk's save manager and backup her saves so if u do lose them u can restore
 
Does the system need to be formatted when installing a9lh? I already removed all my girlfriend's saves once (I wasn't able to recover them to the new emunand yesterday no matter how hard I tried) and she just started a new game on harvest moon for the second time which I really wouldn't want to lose.

If you follow @Plailect's guide all the way, you will not lose any data when you finish the guide.
 
Pfffftttt brickproof, bricked my o3ds today its still luck based on the otphelper part, did everything as mentioned in the guide got to the one click setup all stages failed injected firm into both emuNAND and sysNAND one stage passed another failed, led to a ineviteble brick, the only thing which has been made better is the otphelper app, before it was much worse when trying to inject the emuNAND into sysNAND, otphelper only saves you because it has the ability to restore sysNAND and thats all it still is dangerous as it will always lead to a brick if all stages fail regardless, so its not as brickproof as people here want to make you believe.
 
Last edited by Treeko,
Pfffftttt brickproof, bricked my o3ds today its still luck based on the otphelper part, did everything as mentioned in the guide got to the one click setup all stages failed injected firm into both emuNAND and sysNAND one stage passed another failed, led to a ineviteble brick, the only thing which has been made better is the otphelper app, before it was much worse when trying to inject the emuNAND into sysNAND, otphelper only saves you because it has the ability to restore sysNAND and thats all it still is dangerous as it will always lead to a brick if all stages fail regardless, so its not a brickproof as people here want to make you believe.
What? If the stages failed why the hell did you continue?
 
  • Like
Reactions: exangel
What? If the stages failed why the hell did you continue?
I did not want to continue as the guide said, but I didn't know what to do in the heat of the moment+the fear of getting bricked, what I should have done was unmount sd card put sysnand backup on there and restored, but the guide didn't say that to avoid a brick I just assumed if I shut it down and not try again it won't be a brick silly me.

--------------------- MERGED ---------------------------

I would advise anyone to not try a9lh as it is now, unless they come up with cfw for 2.1.0 to allow us to obtain the otp through emuNAND atleast for the o3ds users, or they could completely ignore all the emuNAND and all cfw installation and make o3ds users downgrade to 2.1.0 directly and obtain otp and from there allow them to restore sysNAND or allow sysupdater to run through the browser just like they get otphelper to run through the 2.1.0 browser, if I were to give it a fair rating its 70% brickproof, you can still get bricks through it+its lower for N3DS because of the extra steps there it would be around 60-50% brickproof considering a N3DS normally won't be able to run 2.1.0, so unless there's emuNAND support for 2.1.0 for o3ds users or other shorter methods its still dangerous.
 
Last edited by Treeko,
oh wow I just got my other o3ds easily downgraded to 2.1.0 directly through sysNAND and then got it to dump otp no problems saved 2 hours of time no need for the multiple emuNAND BS so that means I killed my other 3ds for no reason? can someone help me revive it? I have NAND backups for both emuNAND and sysNAND of it just need someone to point me to a hardmod guide or if someone is willing to do it for me??
 
I would advise anyone to not try a9lh as it is now, unless they come up with cfw for 2.1.0 to allow us to obtain the otp through emuNAND atleast for the o3ds users, or they could completely ignore all the emuNAND and all cfw installation and make o3ds users downgrade to 2.1.0 directly and obtain otp and from there allow them to restore sysNAND or allow sysupdater to run through the browser just like they get otphelper to run through the 2.1.0 browser, if I were to give it a fair rating its 70% brickproof, you can still get bricks through it+its lower for N3DS because of the extra steps there it would be around 60-50% brickproof considering a N3DS normally won't be able to run 2.1.0, so unless there's emuNAND support for 2.1.0 for o3ds users or other shorter methods its still dangerous.
The guide is 99% brickproof right now. Even if they came out with 2.1 EmuNAND, you couldn't get OTP through it because 9.2 SysNAND would've already locked OTP.
 
The guide is 99% brickproof right now. Even if they came out with 2.1 EmuNAND, you couldn't get OTP through it because 9.2 SysNAND would've already locked OTP.
Well after trying it on my other o3ds it did change my opinion about it but there are flaws in the guide, the first section of the guide is for people who want complete security while downgrading to 2.1.0 specifically for o3ds owners, because of the unnecessary extra steps for secure downgrading it leads to confusion and the otphelper app I don't like it, it just does the job well I guess that's what it was made for anyways, but if anyone is doing A9lh on a o3ds save yourself the time and downgrade straight to 2.1.0 from sysNAND don't try to inject downgraded emuNAND if you are using rxtools 2.6 on there cause rxtools is crap and gives random errors while injecting the emuNAND to sysNAND.
 
Well after trying it on my other o3ds it did change my opinion about it but there are flaws in the guide, the first section of the guide is for people who want complete security while downgrading to 2.1.0 specifically for o3ds owners, because of the unnecessary extra steps for secure downgrading it leads to confusion and the otphelper app I don't like it, it just does the job well I guess that's what it was made for anyways, but if anyone is doing A9lh on a o3ds save yourself the time and downgrade straight to 2.1.0 from sysNAND don't try to inject downgraded emuNAND if you are using rxtools 2.6 on there cause rxtools is crap and gives random errors while injecting the emuNAND to sysNAND.

I watched MrMario's guide on YouTube today and it does seem to be more of just moving files around like people have said really. I do intend to keep using emuNAND when I install it though.
 
I watched MrMario's guide on YouTube today and it does seem to be more of just moving files around like people have said really. I do intend to keep using emuNAND when I install it though.
Its is moving files around without being silly like me and toasting a 3ds, you just need to manage the files properly, know what you are doing before pressing start, I did that with my other 3ds and got it to flawlessly give me the otp and update back to sysNAND 9.2 without ever touching my emuNAND I didn't even back it up until the guide asked me to just to get everything setup on sysNAND just as it was on my emuNAND I really regret going the emuNAND route on my other 3ds though.

Edit: this is only for the o3ds if your on a n3ds then you have to absolutely go through the emuNAND method.
 
Last edited by Treeko,
Does backing up the emuNAND before wiping it and then restoring the emuNAND backup mean that old saves still work.

Very little related to save backups is included in that guide except for a link to an application on github that has one of the weirdest naming conventions I've ever seen.
 
Does backing up the emuNAND before wiping it and then restoring the emuNAND backup mean that old saves still work.

Very little related to save backups is included in that guide except for a link to an application on github that has one of the weirdest naming conventions I've ever seen.
Yes. The back up before the wipe will restore waves and games
 
  • Like
Reactions: BloodRose
Perfect, thanks. I thought that might be the case. I wonder why Plaitec's guide recommends using a save manager app before taking the backups then :huh:
Maybe a secondary precaution. So if something does go wrong you at least still have the saves. Something like that happened to my wifes 3ds when I downgraded it to 9.2 back when 10.3 was the current fw. Her games still showed but the saves where gone. I did the same exact steps and what not on my 3ds and everything was fine. So you know better safe than sorry. When I did a9l for my 3ds I used a second sd card so I didn't have to back up anything but the sysnand.
 
  • Like
Reactions: BloodRose

Site & Scene News

Popular threads in this forum