Homebrew Question Autorcm-Launching OFW

  • Thread starter Thread starter Basketto
  • Start date Start date
  • Views Views 5,715
  • Replies Replies 11

Basketto

Well-Known Member
Member
Joined
Jun 25, 2019
Messages
567
Reaction score
181
Trophies
0
Age
35
XP
648
Country
Australia
Up until recently I've used certain smaller SD cards to run purely Switchroot ubuntu/android. I always prefer using Auto-rcm over removing a joycon each time, therefore I have always booted stock from rcm. Up until now on these SD cards, I would store the latest SX OS boot.dat, as is comes bundled in with and "Original FW" boot option. Given recent events, it is more than likely Team Xecuter dont release anything within the coming months if they do in future at all.
My Question is therefore, what are the minimum required files needed for Hekate to boot OFW/stock. Also given that on these SD cards, I am not interested in launching CFW is their any alteration I need to make to the hekate.ini.
Any kind of insight or help is always appeciated, thankyou.
 
Last edited by Basketto,
Basically just atmosphere + hekate. Boot with hekate then select stock. The problem would be that updating through OFW will remove RCM.
 
  • Like
Reactions: Basketto
Basically just atmosphere + hekate. Boot with hekate then select stock. The problem would be that updating through OFW will remove RCM.

Thnx, I thought as much ;). Do you know if its possible to remove launch CFW as a default launch option? My current other SD setup uses emummc so it is pretty safe. I know that autorcm is removed with updates, thankfully thats generally only required once every several months.
 
Last edited by Basketto,
You mean auto boot? Autoboot is disabled by default. If you meant first option, you would probably have to edit the order in the ini file.
 
You mean auto boot? Autoboot is disabled by default. If you meant first option, you would probably have to edit the order in the ini file.

I meant literally remove Launch CFW as a possible choice, so that when I run the Hekate payload, & choose Launch,
I can't accidently tap boot CFW.
I know its being paranoid :P, but on that particular SD card, I would prefer removing CFW as an option at all.
 
I meant literally remove Launch CFW as a possible choice, so that when I run the Hekate payload, & choose Launch,
I can't accidently tap boot CFW.
I know its being paranoid :P, but on that particular SD card, I would prefer removing CFW as an option at all.

I guess you could remove it from the ini file and remove the entries for:

[CFW - sysMMC]
[CFW - emuMMC]
then maybe set autoboot once you are sure stock is the only one listed. I guess you can just put Hekate only to ensure CFW won't boot.
 
Last edited by fvig2001,
  • Like
Reactions: Basketto
I guess you could remove it from the ini file and remove the entries for:

[CFW - sysMMC]
[CFW - emuMMC]
then maybe set autoboot once you are sure stock is the only one listed. I guess you can just put Hekate only to ensure CFW won't boot.

Deleted the boot entries from the .ini and all seemed to work fine, tyvm. I thought doing so might mess something up but worked like a charm.
 
Deleted the boot entries from the .ini and all seemed to work fine, tyvm. I thought doing so might mess something up but worked like a charm.
To be sure verify that the [stock] profile in hekate_ipl.ini only contains "stock=1" and not fss0, atmosphere, kips, kip1patches...
 
To be sure verify that the [stock] profile in hekate_ipl.ini only contains "stock=1" and not fss0, atmosphere, kips, kip1patches...

I left the default profile from sd setup for stock. I imagine it is correct. There is more than 1 line, but I am guessing the others are either required, or will not make a difference? I presumed the fss0=atmosphere/fusee secondary line is required to boot from hekate.
 
Last edited by Basketto,
I left the default profile from sd setup for stock. I imagine it is correct. There is more than 1 line, but I am guessing the others are either required, or will not make a difference? I presumed the fss0=atmosphere/fusee secondary line is required to boot from hekate.
the line saying fss0=atmosphere/fusee-secondary will boot cfw. You want that line gone
 
Are you 100% sure? Because it is in every hekate “stock” template and i also
managed to dig this up

https://github.com/CTCaer/hekate/issues/292

Although its from last year, it includes that line in the template.
it definately isn’t CFW in the sense it allows homebrew to be run through the album.

Supposedly it is one of the template lines that should be used in every firmware above 7.0.
 
Last edited by Basketto,
Last edited by lisko,

Site & Scene News

Popular threads in this forum