Hacking Coldboothax - solving infinite loop with sysNAND CFW
- Thread starter ::Phoenix::
- Start date
- Views 35,369
- Replies 239
- Likes 28
for me it is. I figured out how to load into 3 different fw.img from haxchi app but this one wont boot up fully. no matter how i compile
dimok789:master and marco-calautti:master are identical.
All of your changes have been committed to the master. Congratulations!
All of your changes have been committed to the master. Congratulations!
D
Deleted User
Guest
This requires to have syshax.XML in your sysnand. The whole point was to enable coldboothax.
D
Deleted User
Guest
D
Deleted User
Guest
Did you mess up anything during the installation? If not, do you have the correct fw.img on your SD Card?
D
Deleted User
Guest
Well, the system has to first boot, load original IOSU and original IOSU will load system.xml by loading haxchi. Then, haxchi will load fw.img in memory and force a full relaunch.
patched IOSU is in memory (and this is the unexplained part) and it loads again system.xml from sysnand. Haxchi runs again, reloads fw.img in memory, reboots, and now fw.img loads syshax.xml, then moving to System Menu.
I kknow how to solve the double haxchi loading But I did not have much time to find the code part of fw.img to change. In essence, the idea is to modify the code that loads the default title id and force it to the system menu id. In this way there is no way for fw.img load again haxchi bacause the defualt title id is already in memory and even better, we will not need to put a secondary xml in sysnand, cause fw.img will already know what title to launch at boot.
patched IOSU is in memory (and this is the unexplained part) and it loads again system.xml from sysnand. Haxchi runs again, reloads fw.img in memory, reboots, and now fw.img loads syshax.xml, then moving to System Menu.
I kknow how to solve the double haxchi loading But I did not have much time to find the code part of fw.img to change. In essence, the idea is to modify the code that loads the default title id and force it to the system menu id. In this way there is no way for fw.img load again haxchi bacause the defualt title id is already in memory and even better, we will not need to put a secondary xml in sysnand, cause fw.img will already know what title to launch at boot.
Yes, but I don't think it is very maintenable. It roughly copies the raw bytes of the patches in memory. Every new stuff on iosuhax will need to be ported to the sign patcher. Anyway, it should work for coldboothax if also the syshax.XML change is ported (which I don't see in the current code).
Last edited by ::Phoenix::,
The good thing is that you don't need to compile iosuhax.
Similar threads
-
-
-
-
-
-
-
-
-
-
-
@
BigOnYa:
For reference, so everyone knows we are not racist, just like to pick on Juan, and he gives it back to us 'murdicans in return. I love me some latinos.+1 -
-
-
-
@
Morganna:
i dont want to sound silly, but im kind of lost, im new to this community and i have a lot of question and idk where to start -
-
-
-
@
Sicklyboy:
Can't wait for the inevitable power outage where it's initially funny because I have half of my apartment on UPSes, then I realize I have literal minutes to start shutting down all of my servers. -
@
BigOnYa:
You must be north of me, Im in Ohio.. It been storming on off all day here, coming from the north
-
-
-
@
Morganna:
@BigOnYa well, starting with, idk which emulator should i use for switch, i got a gtx 1650, do you know which one would it better for my pc?
-
@
BigOnYa:
The switch emulators on pc rely on your CPU mostly, and they only use a single core, so GPU not as important as a good CPU. I don't use switch emulator, but many here do, and willing to help.
-
