Hacking Booting CFW from Emunand fails when OFW on NAND updated and game in the slot

apoptygma

Well-Known Member
OP
Member
Joined
Mar 30, 2010
Messages
704
Trophies
0
XP
612
Country
Not an issue I need help resolving I'm just curious about this behavior - I updated my OFW to 11.0 last night and when booting 10.x CFW from Emunand I was getting an error which I later worked out was due to leaving a game cart (Diablo III) in the slot, removing it resolved the issue.

I'm just wondering why this happens - I mean, I guess the homescreen gets bypassed when a game is inserted at boot, but shouldn't the game just load (albeit under the CFW from the Emunand) what actually prevents it and causes atmosphere to crash?
 

JackTheFroster

Well-Known Member
Member
Joined
Feb 13, 2017
Messages
196
Trophies
0
Age
24
XP
527
Country
Germany
Had the same problem, after researching a bit i found out that the game cartridge slot was indeed updated. Updating emuMMC to 11.0, atmosphere to the pre-release 0.16 and hekate to 5.5.0 fixed everything
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
19,011
Trophies
2
Age
29
Location
New York City
XP
13,378
Country
United States
Not an issue I need help resolving I'm just curious about this behavior - I updated my OFW to 11.0 last night and when booting 10.x CFW from Emunand I was getting an error which I later worked out was due to leaving a game cart (Diablo III) in the slot, removing it resolved the issue.

I'm just wondering why this happens - I mean, I guess the homescreen gets bypassed when a game is inserted at boot, but shouldn't the game just load (albeit under the CFW from the Emunand) what actually prevents it and causes atmosphere to crash?
There is an update for the cartridge slot in firmware 11.0 that prevents firmware versions below 11.0 from using cartridges. This is also not the first cartridge slot update as two more were applied in firmware versions 4.0 and 9.0
 

urherenow

Well-Known Member
Member
Joined
Mar 8, 2009
Messages
4,778
Trophies
2
Age
48
Location
Japan
XP
3,674
Country
United States
Maybe use the search function, because you’re not the first person to have this problem. The solution is always to update to the same firmware version for both sys and emu, and make sure in BCT.ini nogc=0 and in hekate_ipl.ini autonogc=0.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    I @ idonthave: :)