Fusee.bin to boot.dat conversion

  • Thread starter Thread starter cg3991
  • Start date Start date
  • Views Views 2,406
  • Replies Replies 11
I strongly suggest using hekate instead of fusee.bin.

1) you won't need to convert the payload on every update of atmosphere or hekate. (Hekate will load up then check and see if the payload is up to date compared to the update.bin. if update.bin is newer, it'll load that version instead)

2) ever since ams 1.7.x. ams doesn't support ips patching anymore, so sigpatches won't fully work. To make sig patches work again, you either gotta
A) Use a modified version of fusee.bin that re-enables this
B) Boot atmosphere by hekates fss0 method
C) Use a sysmoduel called sys-patch, does the same thing as sig patches but as a sysmoduel instead
 
  • Like
Reactions: draftguy123
Will post a link to Python scripts which convert fusee and hekate to boot.dat
Post automatically merged:

There are 2 scripts, one for Hekate and the other for Atmosphere.
 
Official chain loader. I have been using this all this time:
-Search for sxgear v1.1
-this contains two files boot.dat + boot.ini
-edit Boot.ini with notepad and write "fuse.bin" there
-Both files remain static when you upgrade CFW

Personally I don't use Hekate in my non-Android SD because I don't need any of its features. If you will use that, then you will have to edit boot.ini every time Hekate payload gets renamed.
 
Official chain loader. I have been using this all this time:
-Search for sxgear v1.1
-this contains two files boot.dat + boot.ini
-edit Boot.ini with notepad and write "fuse.bin" there
-Both files remain static when you upgrade CFW

Personally I don't use Hekate in my non-Android SD because I don't need any of its features. If you will use that, then you will have to edit boot.ini every time Hekate payload gets renamed.
Nice thanks! And this wont require a new boot.dat file every time there is a OS upgrade, is that what you meant?
 

Site & Scene News

Popular threads in this forum