https://github.com/dukesrg/rxTools/releases/Where is the link?
https://github.com/dukesrg/rxTools/releases/Where is the link?
thanks but there is not a9lh support sniff
is there chance for brick, if there is how do i restore from that?Make sure you are in emuNAND.
Go to the setting and check if it says RX-E before the firmware number (RX-E 9.2-??? in your case), you can then proceed to update like you would normally do from the options.
P.S change the ??? with whatever it says in your firmware.
As far as i know there isn't a chance for brick, i'm in the latest firmware without any issues.is there chance for brick, if there is how do i restore from that?
Is it normal for it to say "this update can be performed without connecting to the internet" then process update but fail to boot in to emuNAND (blackscreen after the rxtool logo).Make sure you are in emuNAND.
Go to the setting and check if it says RX-E before the firmware number (RX-E 9.2-??? in your case), you can then proceed to update like you would normally do from the options.
hmm, i remember i used this guide to install cfw, rxtool and CtrBootManager, however i didn't install luma3DS. I tried to update rxtool to 3.0 beta and when boot it showsThat's weird, i guess the update was already downloaded.
Download a new version of rxtools.
Failed to load keys for N3DS
CodeL 4
RxMode will not boot. Please include key_0x16.bin and key_0x1B.bin at the root of your SD card
hmm, i remember i used this guide to install cfw, rxtool and CtrBootManager, however i didn't install luma3DS. I tried to update rxtool to 3.0 beta and when boot it shows
Code:Failed to load keys for N3DS CodeL 4 RxMode will not boot. Please include key_0x16.bin and key_0x1B.bin at the root of your SD card
Oh, didn't see any mention about them in the quick guide pdf so i assumed something in mine 3ds broke.You need those keys to boot newer emunand on a new3ds
No changes to CFW at all, currently only tools parts is changing. Someone else is needed to work with CFW part.so no a9LH recent build ?
I think you're gonna need some of this :^)
If you are not working on the CFW part, then what's the point of keeping this project alive?No changes to CFW at all, currently only tools parts is changing. Someone else is needed to work with CFW part.
Exactly.If you are not working on the CFW part, then what's the point of keeping this project alive?
You are better off working on Luma or Cakes.
You should really make another thread for your spin on the project? It would make it easier to keep up with updates. Also just ignore the Salty tempers, they will never be satisfied and just want to stomp around like spoiled children.I don't care how it's called, other projects don't care how it actually works. There is nothing to do in other projects, all of them uses the same libraries not refactored for years. Just try and check how it looks like and how fast is it now. It is much faster to port all additional features from all existing projects to my fork now, then to port new GUI into them. Believe me, I'm an old fart with programming experience started before some of other projects devs not even born.
upd: *NAND and partitions dump/inject is on its way.
I second both of these. At this point, a new thread makes the most sense, as this thread is nearing 1k pages anyways. Keep a link to this thread in the new one for historical purposes, but otherwise it's high time for cleaning up the clutter.You should really make another thread for your spin on the project? It would make it easier to keep up with updates. Also just ignore the Salty tempers, they will never be satisfied and just want to stomp around like spoiled children.
You should really make another thread for your spin on the project? It would make it easier to keep up with updates. Also just ignore the Salty tempers, they will never be satisfied and just want to stomp around like spoiled children.