Blank screen when running Atmosphere from Hekate (formerly on SXCORE)

Quqember

New Member
OP
Newbie
Joined
Nov 5, 2021
Messages
4
Trophies
0
Age
44
XP
44
Country
Israel
Hi,

I'm trying to migrate from SXCORE to Atmosphere. I got Hekate working, but get an Atmosphere logo + blank screen when launching CFW
- Mariko switch
- FW: 11.0 installed, Hekate tools reports 10.0.0-10.2.0, Deepsea-advanced-v3.3.1, using sysnand
- Originally on SxOS migrated using a guide I can't link to :)[
- Originally updated using ChoiDuJourNx, BOOT0 fixed by generating a new BOOT0 with EmmcHaccGen 2.2.3
using FW 10.2.0 + 10.2 prod.keys (also tried using universal_prod.keys with the same effect)
- Clean sdcard with license.dat, license-request.dat and the DeepSea package alone fails to boot. The SDCard is formatted as fat32
- Clearing the archive bits using the DeepSee CommonProblemResolver does not resolve the problem
- Tried updating to the latest Atmosphere (1.2.4) - same

Current status:
* A bit of a hodpodge sdcard - original SXOS + DeepSea on top.
* Can boot to Hekate, can boot to the original sysnand, when booting to Atmosphere, I can see the Hekate and Atmosphere logos (plus the DeepSea banner) and then a blank screen.

When enabling logs before booting to CFW, I get the following:
1636096959647.png


How can I proceed from here?

Thanks!
 
Last edited by Quqember,

wiiNinja

Well-Known Member
Member
Joined
Jan 13, 2009
Messages
645
Trophies
1
XP
1,843
Country
United States
In later versions of Atmosphere, 1.0.0 and later, fusee-secondary.bin has been renamed. Install the latest Hekate and be sure to read the release note to know what to do with the renaming of fusee-secondary. I also didn't see mentions of sigpatches in your post; you'll need to install those if you haven't done so.
 

Quqember

New Member
OP
Newbie
Joined
Nov 5, 2021
Messages
4
Trophies
0
Age
44
XP
44
Country
Israel
Following your advice:
* Re-installed Hekate v5.6.5,
* Wiped and re-installed Atmosphere v1.2.4
* Re-applied ITotalJustice sig patches (release tag: 13.1.0-1.2.4)


The contents of hekate_ipl.ini is:
Code:
[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1

{DeepSea}
{Github: Team-Neptune (edited since I'm not allowed to post URLs :) }

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}


[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}



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


I get the same result - blank screen after launching CFW
 
Last edited by Quqember,

Quqember

New Member
OP
Newbie
Joined
Nov 5, 2021
Messages
4
Trophies
0
Age
44
XP
44
Country
Israel
Did some more tests:
* From the original sysnand - formatted the sdcard (and then copied the backup back to the card) - same result, Atmosphere does not load, blank screen
* From the original sysnand - did a factory reset. No luck here either.

* I strongly suspect that the problem is with BOOT0/BOOT1, the current FW is 11.0, Hekate tools reports 10.0.0-10.2.0

Any ideas? Should I generate a new BOOT0/BOOT1 from 11.0 instead of 10.2?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • crafthp434 @ crafthp434:
    like i searched all folders
  • NinStar @ NinStar:
    are you using haxchi, tiramisu or aroma?
  • crafthp434 @ crafthp434:
    yeah
  • NinStar @ NinStar:
    no, I'm asking which one of them you are using
  • crafthp434 @ crafthp434:
    aroma
  • NinStar @ NinStar:
    in that case, there is no such thing as homebrew launcher for aroma
  • NinStar @ NinStar:
    you have to launch your homebrews directly from the wii u menu
  • NinStar @ NinStar:
    there is a plugin that display them on the wii u menu, pretty sure it is enabled by default
  • crafthp434 @ crafthp434:
    so like it doesnt exist
  • crafthp434 @ crafthp434:
    yeah
    ?
  • NinStar @ NinStar:
    it doesn't exist, at least not for aroma
  • crafthp434 @ crafthp434:
    ohhhhh
  • NinStar @ NinStar:
    on tiramisu you can access it by opening mii maker
  • crafthp434 @ crafthp434:
    okay
  • NinStar @ NinStar:
    I don't have a wii u anymore to test it myself, but if homebrews are not visible on the wii u menu I think you can press L + R + minus to open the plugin menu, there should be an option called "homebrews on wii u menu" or something similar
  • crafthp434 @ crafthp434:
    nope
  • crafthp434 @ crafthp434:
    it is L+dpad down+ select
  • crafthp434 @ crafthp434:
    but homebrew is appearing in the home menu btw
  • NinStar @ NinStar:
    yes, now I remember it
  • NinStar @ NinStar:
    then it is working, I also don't like that they did this but it is the only option you have if you are using aroma
  • crafthp434 @ crafthp434:
    i just didint know the homebrew launcher didint exist in aroma
  • crafthp434 @ crafthp434:
    thanks btw
  • Xdqwerty @ Xdqwerty:
    Im downloading fallout 3 goty edition
    +1
  • BigOnYa @ BigOnYa:
    I'm downloading more ram for my hamster pc
    BigOnYa @ BigOnYa: I'm downloading more ram for my hamster pc