Hacking [Pre-release, WIP] Yet another rxTools?

  • Thread starter Thread starter duke_srg
  • Start date Start date
  • Views Views 89,998
  • Replies Replies 659
  • Likes Likes 68
I don't know how to fix a9lh boot loop and have no time to see into. Revising tmio module now at work as a background task. Can speed up band/SD operations, maybe not even noticeable.
Thanks for the update. Any plans on implementing stuff that's not there yet? (Like H&S injection)
 
Thanks for the update. Any plans on implementing stuff that's not there yet? (Like H&S injection)
All framework was ready long time ago, features just waits to be implemented. Also planned to relocate all downloaded NUS content to one tree structure and check validity in of the original signatures.
 
  • Like
Reactions: Madridi
Thanks for the update. Any plans on implementing stuff that's not there yet? (Like H&S injection)
Why does anybody want H&S injection? It was a necessity before (if you didn't own a Gateway), but with Fasthax, you don't need it... do you? Can't you just launch soundhax->HBL->Fasthax->FBI.3dsx and install FBI.cia?

Serious question. I'm on a9lh and somewhere where I don't have my dongle with me to flash my original nand for testing.
 
Last edited by urherenow,
Why does anybody want H&S injection? It was a necessity before (if you didn't own a Gateway), but with Fasthax, you don't need it... do you? Can't you just launch soundhax->HBL->Fasthax->FBI.3dsx and install FBI.cia?
soundhax won't last forever. h&s injection is a more long term solution that works on any version.
 
  • Like
Reactions: Madridi
Why does anybody want H&S injection? It was a necessity before (if you didn't own a Gateway), but with Fasthax, you don't need it... do you? Can't you just launch soundhax->HBL->Fasthax->FBI.3dsx and install FBI.cia?

Serious question. I'm on a9lh and somewhere where I don't have my dongle with me to flash my original nand for testing.
Well, here is your answer :)
Well, just because we can do that is quite enough reason :)
Yeah, I'm just in favor of variety. Why limit ourselves? It's certainly a viable option

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

All framework was ready long time ago, features just waits to be implemented. Also planned to relocate all downloaded NUS content to one tree structure and check validity in of the original signatures.
Maybe the fact that firmware.bin can't be downloaded from NUS anymore should be addressed at some point?
I seriously can't wait to see how this develops. Good luck :)
 
Excellent!
I'm OK with 11.2.0-35, but this NativeFirm update actually means we'll got updated firmware patches soon™.
No, I won't personally fix CFW, I don't have THAT much time to do it from the scratch.
 
Excellent!
I'm OK with 11.2.0-35, but this NativeFirm update actually means we'll got updated firmware patches soon™.
No, I won't personally fix CFW, I don't have THAT much time to do it from the scratch.
It also broke older reboot patches, so there's that to watch out for.
 
A quick-fix attempt for NATIVE_FIRM 11.3 with EmuNAND patch ONLY.
https://github.com/dukesrg/rxTools/tree/dev-nf113
Should boot EmuNAND with updated firmware file, need to check, I'm away from 3DS now.
In case it boots, don't try to update EmuNAND with no hardmod, have no idea what could also be broken with the new fw.

Upd: nope, this is not enough to boot with new firmware.
 
Last edited by duke_srg,
Good Bad news everyone!
First: no, still no fix for NATIVE_FIRM 11.3
Second: sd/mmc access module used in almost every CFW is configured to work two times slower than actual hardware could. Yes, all your nand dumps/injects could be done almost twice as fast.
 
Last edited by duke_srg,
Good Bad news everyone!
First: no, still no fix for NATIVE_FIRM 11.3
Second: sd/mmc access module used in almost every CFW is configured to work two times slower than actual hardware could. Yes, all your nand dumps/injects could be done almost twice as fast.
That's amazing! I'm pretty sure I read somewhere that the speed was a hardware limitation. I guess you're proving otherwise :D
 
That's amazing! I'm pretty sure I read somewhere that the speed was a hardware limitation. I guess you're proving otherwise :D
EmuNAND dump to SD in less than 6 minutes :)
Would be great if we can use your time to perform a dump time test: master vs dev-a9lh vs something commonly used now (GW or *9?), would be great.
 
Good Bad news everyone!
First: no, still no fix for NATIVE_FIRM 11.3
Second: sd/mmc access module used in almost every CFW is configured to work two times slower than actual hardware could. Yes, all your nand dumps/injects could be done almost twice as fast.
bummer do you think you would be able to make Rx compatible with A9LH eventually?
 
bummer do you think you would be able to make Rx compatible with A9LH eventually?
I wish I could, but need much time for investigation which is not even started since I concentrated on the core of the tools part. I'm used to say, there are plenty of people able to work with patches, but none wants to bother with core or interface.
 
  • Like
Reactions: BADDINOROX99
I wish I could, but need much time for investigation which is not even started since I concentrated on the core of the tools part. I'm used to say, there are plenty of people able to work with patches, but none wants to bother with core or interface.
oh ok, well at least you're trying and that's anything anyone can ask for [emoji106]
 
EmuNAND dump to SD in less than 6 minutes :)
Would be great if we can use your time to perform a dump time test: master vs dev-a9lh vs something commonly used now (GW or *9?), would be great.
Sure yeah will do 7 tests later tonight
Sysnand dump from master
Emunand dump from master
Sysnand dump from dev-a9lh
Emunand dump from dev-a9lh
Sysnand dump from gateway
Sysnand dump from decrypt9
Emunand dump from decrypt9

And I'll report back with the times I get once I do :)
 
  • Like
Reactions: duke_srg

Site & Scene News

Popular threads in this forum