Hello everyone.
I have a successfully downgraded 9.2 OLD3DS XL on which I installed rxTools 3.0 using this guide: https://gbatemp.net/threads/tutorial-installing-rxtools-custom-firmware-3ds-and-2ds.390867/
I will write to you (if you wish to assist me in identifying what REALLY happened
) a explanation as to how I got to the point in which I am now. Or you can skip over the wall of text and simply explain to me how I can remove rxTools and everything that is associated with it, and bringing my console to just a simply downgraded OLD3DS so that maybe I can attempt to install rxTools again from scratch.
Just a note, I did backup my SD card's original condition, before doing anything from the guide and I did create a NAND backup.
I ran into some issues while following the tutorial. I did everything from section 1 though 7 without, what appeared to be, no problem. However when I tried to set up launching rxTools at boot using MenuHax, that is when things got a little strange. I already had a way to access the homebrew launcher (via BrowserHax) so I skipped ahead to step 8. After I installed MenuHax and opened up the ropbinpayload file using Notepad++ I started looking for the strings containing "boot.3dsx", I could only find just one. Not two, as specified in the tutorial. That left me with a console coldbooting into HBL and when ANY button was pressed, into sysNAND. After deleting MenuHax and and installing it again, I opened the ropbinpayload file once more to find two "boot.3dsx" locations. I changed those to "auto" and I was left with a console coldbooting into emuNAND, but whatever button I pressed it would always boot into sysNAND. And I could not access the homebrew launcher without an internet connection, even after I had the HBL.cia installed. So then I decided to try autobooting with MenuHax using this tutorial: https://docs.google.com/document/d/...ce7AWYmjp5Cq2LxfQ9cDr0/edit#heading=h.3whwml4 (via ThemeHax).
So I renamed my boot.3dsx to boot_hb.3dsx and replaced boot.3dsx and boot.cfg with the ones found in the CTRBootManager archive that was linked to in this guide and followed the remaining steps.
What I was left was a console supposedly launching rxTools at boot (I got the splash-screen), but it would just try and boot it again at which point it would freeze. Then I messed everything up by replacing, renaming, reinstalling everything which had to do with the MenuHax launch exploit and now I am lost as to were things went wrong.
Can I simply format my SD card and place the untampered backup files back on the SD? Would that just bring me back to a normal downgraded 3DS?
I have a successfully downgraded 9.2 OLD3DS XL on which I installed rxTools 3.0 using this guide: https://gbatemp.net/threads/tutorial-installing-rxtools-custom-firmware-3ds-and-2ds.390867/
I will write to you (if you wish to assist me in identifying what REALLY happened
) a explanation as to how I got to the point in which I am now. Or you can skip over the wall of text and simply explain to me how I can remove rxTools and everything that is associated with it, and bringing my console to just a simply downgraded OLD3DS so that maybe I can attempt to install rxTools again from scratch.Just a note, I did backup my SD card's original condition, before doing anything from the guide and I did create a NAND backup.
I ran into some issues while following the tutorial. I did everything from section 1 though 7 without, what appeared to be, no problem. However when I tried to set up launching rxTools at boot using MenuHax, that is when things got a little strange. I already had a way to access the homebrew launcher (via BrowserHax) so I skipped ahead to step 8. After I installed MenuHax and opened up the ropbinpayload file using Notepad++ I started looking for the strings containing "boot.3dsx", I could only find just one. Not two, as specified in the tutorial. That left me with a console coldbooting into HBL and when ANY button was pressed, into sysNAND. After deleting MenuHax and and installing it again, I opened the ropbinpayload file once more to find two "boot.3dsx" locations. I changed those to "auto" and I was left with a console coldbooting into emuNAND, but whatever button I pressed it would always boot into sysNAND. And I could not access the homebrew launcher without an internet connection, even after I had the HBL.cia installed. So then I decided to try autobooting with MenuHax using this tutorial: https://docs.google.com/document/d/...ce7AWYmjp5Cq2LxfQ9cDr0/edit#heading=h.3whwml4 (via ThemeHax).
So I renamed my boot.3dsx to boot_hb.3dsx and replaced boot.3dsx and boot.cfg with the ones found in the CTRBootManager archive that was linked to in this guide and followed the remaining steps.
What I was left was a console supposedly launching rxTools at boot (I got the splash-screen), but it would just try and boot it again at which point it would freeze. Then I messed everything up by replacing, renaming, reinstalling everything which had to do with the MenuHax launch exploit and now I am lost as to were things went wrong.
Can I simply format my SD card and place the untampered backup files back on the SD? Would that just bring me back to a normal downgraded 3DS?
