- Joined
- Jan 13, 2015
- Messages
- 3,825
- Trophies
- 1
- Location
- The State of Denial
- Website
- gbatemp.net
- XP
- 5,666
- Country
What were you going to say?
#1 rule if homebrew or hacks is something you want, is look before you update, gateway had already said stay on 9.2 and 9.3 was patching exploit, yeah gateway might not be what you where after, but exploits are exploits, if your on an exploitable FW you stay there, especially if you are explicitly warned that the update will block exploits......blocked exploits are never a good thing, and ninjhax was public when 9.2 was the newest FW, if homebrew was your #1 concern you would of stuck on 9.2, hacks dont just grow on tree's when they are announced you just dont update, its as simple as that,even if they arent exactly what you want yet you need to wait for them to be developed, this is basic stuff that for some reason people never seem to grasp
Yes. But only on RX-E, not RX-S or ver.Ok, just to be clear, you update it from System Settings/Other Settings/System Update while its on RX-E 4.5.0 right?
rxtools is launched off of gateway's payload which refers to itself. In this case, "sdmc/:rxTools.dat", is in the decrypted payload code.Roxas, I ended up figuring out why it would whitescreen for me. The rxTools launcher seems to do that if you rename it to Launcher.dat, for some reason.
Roxas, I ended up figuring out why it would whitescreen for me. The rxTools launcher seems to do that if you rename it to Launcher.dat, for some reason.
Can I downgrade correctly even if I have RxTools.dat, firmware.bin, slot0x25keyx.bin on my SD Card?
Because Gateway's loader.dat contains modified Nintendo FIRM integrated into it, and rxTools uses firm.bin?So for mset usage it requires an exclusive exploit installer?
Why can't it use the standard "Launcher.dat" one? (it's not like we can have 2 rop chains installed at the same time)
I just worked up the balls to try this, but as others have reported, injection to sysNAND had no effect. I compared the sysNAND ticket.db before and after "injection", and their SHA-1s matched.Yeah, I should have mentioned that in my post. Though really, this is only useful for linked nands anyway. If unlinked then the sysnand wont see the installed content from emunand and it's not like you can install it manually in rxMode.
Worked though. I have online in Smash on 9.2.
Newly installed games don't show up, likely need to force the 3DS to see it. I have an idea why it isn't showing up so I'll check it out. (I'm pretty tired so I'm probably wrong though lol)
- Use rxTools and dump all the important NAND files. Just because you can. Copy them to a computer for safe keeping.
- Boot into rxMode and update via settings app to 9.6. (Make sure you're in RX-E, not RX-S or ver.)
- Update games, install stuff.
- Reboot and start rxTools again.
- Dump ticket.db from emuNAND, inject into SysNAND. Ignore the "Dumping..." text when injecting.
- Exit and enjoy the updates.
Well, rxTools includes an executable to download the necessary firm file.Because Gateway's loader.dat contains modified Nintendo FIRM integrated into it, and rxTools uses firm.bin?
The two loaders are different and therefore not compatible. You could always load one via MSET and the other via websploit.
Well, rxTools includes an executable to download the necessary firm file.
Gateway's ROP could launch other tools... I wonder why rxTools can't work with it.
Yeah, for now the mset option is pretty much useless, siince we can't boot the other CFWs with it.Because those other tools were built to launch via Gateway's ROP. rxTools is not. It probably *could* be, but it isn't.
I can't see Roxas75 going out of his way to make rxTools' MSET support play nice with Gateway's launcher.Yeah, for now the mset option is pretty much useless, siince we can't boot the other CFWs with it.
Roxas75 did say that he had write protection for emuNAND and sysNAND for debug purposes, but forgot to remove them for the release. It will be fixed in the next release.I just worked up the balls to try this, but as others have reported, injection to sysNAND had no effect. I compared the sysNAND ticket.db before and after "injection", and their SHA-1s matched.
Also, if injection did work, how would I go about getting sysNAND to accept the eShop downloads from emuNAND?