about hekate ..

  • Thread starter Thread starter HardMind
  • Start date Start date
  • Views Views 1,064
  • Replies Replies 5

HardMind

Well-Known Member
Newcomer
Joined
Jul 29, 2018
Messages
92
Reaction score
10
Trophies
1
Age
31
XP
763
Country
United Kingdom
Hi, when i enter launch option in hekate v6.0.2 I find only CFW (V1) - CFW (V2) both lead me to EmuNand.
How i can go to custom original Nand from there ?
I remember there was an option lead to there in older version.
 
You need to edit your hekate_ipl.ini file if you wanna go to your sysnand.

For example:

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
kip1=atmosphere/kips/loader.kip
 
  • Like
Reactions: laz305
I will try and come back
but it is a strange, why they removed such an option.
 
You need to edit your hekate_ipl.ini file if you wanna go to your sysnand.

For example:

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
kip1=atmosphere/kips/loader.kip
Hi. I tried this one (added it to file) and got this error when try to launch sysNAND
error whild loading kip1:
atmoshpare/kops/loader.kip
wrong ini cfg or missing/corrupt files/
failed to launch HOS/
 
Hi. I tried this one (added it to file) and got this error when try to launch sysNAND
error whild loading kip1:
atmoshpare/kops/loader.kip
wrong ini cfg or missing/corrupt files/
failed to launch HOS/

If you trying to boot stock OFW (no CFW) use

{--- Stock ---}
[Stock (SYSNAND)]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
{}
 

Site & Scene News

Popular threads in this forum