I am new here and starting with a help request ?

  • Thread starter Thread starter janicleader
  • Start date Start date
  • Views Views 955
  • Replies Replies 11

janicleader

Member
Newcomer
Joined
Feb 4, 2025
Messages
12
Reaction score
10
Trophies
0
Age
47
XP
31
Country
Australia
Hello everyone,

I am new to this forum and this is my first post. I need help from the community. I just modchipped my first electronic device NS (technically second after my phone) and have locked myself out in a software update.

When I installed Hekate 6.2 2 and booted into EmuMMC a software update was already available. I accidentally updated it and now my EmuMMMC is updated to 19.0.1 and AMAS 1.8.0, I do see the E at the end of the software version and able to boot into Hekate and SysMMC CFW's.

As this is the first time I have installed and modded my NS. I am not sure what to do going forward. Please guide if

1. I should reinstall the software update on EmuMMC via Daybreak and then on SysMMC CFW, OR

2. Install the software update on SysMMC CFW to 19.0.1 via Daybreak and leave the EmuMMC CFW as it is. Do I need to clear the current theme ?

3. Do i need to install the update on the stock firmware too to 19.0.1.

4. I am unable to play any of my previous installed games which is due to the firmware mismatch. Would updated sys_patches work ?

My sincere thanks in advance
 
[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=2
autonogc=1
updater2p=1

[SEMI-STOCK (SYSMMC)]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp
usb3force=1
{}

[CFW (SYSMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
usb3force=1
{}

This was the initial entried used to setup hekate 6.2.2
[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
usb3force=1
{}
 
[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
usb3force=1
{}

If you had an emunand then you need to use this.
 
  • Like
Reactions: BigOnYa
[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
usb3force=1
{}

If you had an emunand then you need to use this.
Thank you. I made an eMMC backup when I was on the previous firmware and saved prod.keys. Can I downgarde(restore eMMc back to intial state) or will it cause issues.

Little confused what you mean by "
then you need to use this.
 
Thank you. I made an eMMC backup when I was on the previous firmware and saved prod.keys. Can I downgarde(restore eMMc back to intial state) or will it cause issues.

Little confused what you mean by "

That config boot emummc if you have an emummc setup.
 
  • Like
Reactions: BigOnYa
That config boot emummc if you have an emummc

I have both the EmuMMC & SysMMC CFW.

I am not sure if I should update the SysMMC to reflect the same firmware version as EmuMMC as I dont want a ban ! Have also updated exosphere.ini to reflect [blank_prodinfo_sysmmc=0]

What i was enquring was that what order should I update the firmware version.

EmuMMC version is already 19.0.1, so
EmuMMC<SysMMC<OFW ?
 
I have both the EmuMMC & SysMMC CFW.

I am not sure if I should update the SysMMC to reflect the same firmware version as EmuMMC as I dont want a ban ! Have also updated exosphere.ini to reflect [blank_prodinfo_sysmmc=0]

What i was enquring was that what order should I update the firmware version.

EmuMMC version is already 19.0.1, so
EmuMMC<SysMMC<OFW ?

You should use Nintendo server to do Sysmmc update if the NAND is clean.
 
  • Like
Reactions: BigOnYa

Site & Scene News

Popular threads in this forum