SciresM
commented
4 years ago I cannot reproduce on my end -- sleep works fine in my emummc partition and my emummc file-based.
A separate (?) problem is that sysnand won't work either. When trying to start I get "Unknown pkg1 version. Hos version not supported! Failed to launch HOS". I have tried booting this with a new sd card and only the required stuff but I get the same message.
Sounds like sysmmc is possibly corrupted, though (or you're using outdated hekate)?
When booting sysnand with fusee-primary, does sleep work?
MatteKalle
shchmue
pabz88
Sleino85
Bug Report
[ If any section does not apply, replace its contents with "N/A". ] [ Lines between [ ] (square brackets) should be removed before posting. ]
[ * ] [ Note: If the bug or crash you encountered is related to; ] [ - software used to make "backups", ] [ - software explicitly distributed for piracy, etc ] [ then contributors will not provide support for your issue and your issue will be closed. ]
What's the issue you encountered?
When pressing power button one time the switch instantly goes to rcm mode instead off sleep mode. Also when I start up I have to spam the home button because else it tries to go to sleep mode and then it goes to rcm mode.
[ Describe the issue in detail and what you were doing beforehand. ] Setup before begining: Unpatched switch. exfat formated sd-card Firmware 10.1.0 Atmosphere 0.13.0 The error message about game cart slot appearing now and then. Auto RCM Probably some burnt fuses
So this is how it went down. I hope I remember to write all the crutial steps and the order which i did them in.
I located the necessary rawnand.bin, boot0 and boot1 for making the nand restore. This is a backup I made before going CFW. I dont know what firmware version I was on when I made this backup but I can see that the files are dated december 2017.
I downloaded hekate_ctcaer_5.3.2_Nyx_0.9.3 and put the bootloader folder on the SD card root.
I transferred a copy off all my SD files to my computer.
I started hekate by using hekate_ctcaer_5.3.2.bin.
I used "partition SD Card" in Hekate and created a HOS (FAT32) and emuMMC (RAW).
I created emuMMC SD Partion in Hekate and it says Enabled!.
Copied back all the backuped SD card files to the root off the SD card.
Tried to launch by entering RCM-mode and injecting fusee-primary.bin. It worked and I checked system firmware and saw that I was on E (emunand).
Tried going in to hekate again to launch from there but at first it did not work. Tried a bit and I think what got it working was when I added fusee-primary.bin to the payloads folder in bootloader folder (it was empty before) and also adding code to the hekate.ipl.ini. The code I added was some lines found in a forum thread. One for starting CFW (EMUNAND) and one for Stock (SYSNAND).
Renamed the hekate_ctcaer_5.3.2.bit to reboot_payload.bin and overwrote the file in the atmosphere folder (for being able to reboot to hekate).
Copied the backuped Nintendo-folder to emuMMC\RAW1 and comfirmed that my installed games was working again on emunand.
Now when emunand was working I was convinced it was safe to restore my nand backup. I followed this guide https://suchmememanyskill.github.io/guides/nandrestore/ and did not get into any trouble.
Entered RCM-mode and injected (the same) fusee-primary.bin as before sysnand restore but now nothing happens. The screen is black and TegraRcmGui shows that it is ready to inject again after like 2 seconds.
Trying to inject hekate_ctcaer_5.3.2.bin again and it works.
Trying to launch CFW (emunand) through Hekate exactly as I did before restoring the sysnand. Now it seems to start up, it shows the Atmoshpere logo, it shows the Nintendo Switch logo, it shows the battery status symbol and then for a short moment the sleep screen (the screen where you have to press a button 3 times for it to wake up). Here I have found that I have to spam home button or else it will go to rcm mode. When doing so everything seems to be working until I try to go into sleep mode again. Then it goes to rcm.
[ Did you make any changes related to Atmosphère itself? ] Not before just after to try to fix the problem. I have tried removing atmosphere and replace it by the newest version.
[ If so, make sure to include details relating to what exactly you changed. ]
How can the issue be reproduced?
See the description above. Not sure though. I can't seem to find anyone else that had this problem.
[ * ] [ Include a detailed step by step process for recreating your issue. ] See above.
Crash Report
[ Crash reports can be found under
/atmosphere/crash_reports. ] Can't find that folder. I suppose that means that it have not created any report.[ If your issue caused Atmosphère to crash, include the crash report(s) by creating a gist and pasting the link here. ] [ If you don't include a crash report in instances of crash related issues, we will ask you one to provide one. ]
System Firmware Version
10.2.0 AMS 0.14.3 E When setting up emunand I was on 10.1.0. Now I have updated to 10.2.0 but that did not change anything.
[ Replace X's with system firmware version at time of crash. ] [ You can find your firmware version in the Settings -> System, under "System Update". ] [ If it says "Update Pending", you can clear the pending update by rebooting to Maintenance Mode. ]
Environment?
What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate ctcaer 5.3.3. From there I am running fusee-secondary (from the atmosphere folder). I have also tried launching fusee-primary but I can't get that to work since after the sysnand restore.
Official release or unofficial build:
Do you have additional kips or sysmodules you're loading: No
Homebrew software installed: [ * ] Tinfoil
Additional context?