Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,813,948
  • Replies Replies 9,426
  • Likes Likes 93
Having a piHole or similar setup for the whole home is worth it any day, just for ads and malware. But on days like this, it pays off extra.

Bigdrago said:
Enable prodinfo-blanker. Glad I have that as default on my configs:)
Click to expand...
Checking just in case. Having cal0blank=1 on all relevant boot entries in hekate_ipl.ini should blank it, right?
 
  • Like
Reactions: impeeza, BigOnYa and Bigdrago
sure is a newbie question
update hekate and atmosphere
Boot Hekate 6.5.4 and boot Emummc working but not sys MMC, error

it could be Mission Control "content folder"

[Atmosphere (Emummc)]
fss0=atmosphere/package3
emummcforce=1
atmosphere=1
icon=bootloader/res/Atmoslogo.bmp
usb3force=1

[Atmosphere (sysMMC)]
fss0=atmosphere/package3
emummc_force_disable=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
usb3force=1
 
Last edited by alfonsovin,
Nephiel said:
Having a piHole or similar setup for the whole home is worth it any day, just for ads and malware. But on days like this, it pays off extra.


Checking just in case. Having cal0blank=1 on all relevant boot entries in hekate_ipl.ini should blank it, right?
Click to expand...
Just new to the whole thing but stuff like this makes my head spin. I'll just wait for the updates before I take the Switch out of Airplane Mode.
 
Nephiel said:
Having a piHole or similar setup for the whole home is worth it any day, just for ads and malware. But on days like this, it pays off extra.


Checking just in case. Having cal0blank=1 on all relevant boot entries in hekate_ipl.ini should blank it, right?
Click to expand...
Yes, I have custom DNS as well :) Removing malware and ads. But I feel sad for people not knowing this issue right now. Ninjas are celebrating.

In exosphere.ini
blank_prodinfo_emummc=1

and in hekate_ipl.ini :
[CFW - emuMMC]
pkg3=atmosphere/package3
emummcforce=1
cal0blank=1
 
  • Like
Reactions: Nephiel
Bigdrago said:
Yes, I have custom DNS as well :) Removing malware and ads. But I feel sad for people not knowing this issue right now. Ninjas are celebrating.

In exosphere.ini
blank_prodinfo_emummc=1

and in hekate_ipl.ini :
[CFW - emuMMC]
pkg3=atmosphere/package3
emummcforce=1
cal0blank=1
Click to expand...
If I add these lines (or replace old ones) I'm good?

Don't wanna F things up.
 
  • Like
Reactions: Bigdrago
alfonsovin said:
sure is a newbie question
update hekate and atmosphere
Boot Hekate 6.5.4 and boot Emummc working but not sys MMC, error


[Atmosphere (Emummc)]
fss0=atmosphere/package3
emummcforce=1
atmosphere=1
icon=bootloader/res/Atmoslogo.bmp
usb3force=1

[Atmosphere (sysMMC)]
fss0=atmosphere/package3
emummc_force_disable=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
usb3force=1
Click to expand...

The fss0 configuration key was deprecated in Hekate v6.3.0 and replaced by the pkg3 key

I have this for hekate_ipl.ini
Code: 
[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=100
noticker=0
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[CFW - emuMMC]
pkg3=atmosphere/package3
emummcforce=1
cal0blank=1
icon=bootloader/res/emu_boot.bmp

[Stock - sysMMC]
pkg3=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/stock_boot.bmp


And exosphere.ini
Code: 
[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
enable_mem_mode=0
blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0
 
  • Like
Reactions: johw, impeeza and Shaki123

Site & Scene News

Go to forum More news

Popular threads in this forum