Closed Recurem closed 3 years ago
I can confirm that my switch is unpatched since it smashed the stack with ID code ox7000 byte
I was able to run the hekate_ctcaer_5.5.5.bin if I do not have contents on my SD card folder. Now I am not sure anymore which is the cause.
I can load the payload just fine if there are no contents on my SDCard as shown above
You didn't show a pic of the sys folder, you haven't established that your card is formatted correctly and tested for errors and being fake (h2testw), or that your sd card socket isn't damaged.
Are you able to see the contents on your card when you launch OFW? Take screenshots and then check your album, while in OFW...
Your error clearly states that it can't find nyx (which should be nyx.bin in your sys folder).
@urherenow Which sys folder?
I can verify my card is formatted correctly. I am using this card on may separate Switch (which is already running homebrew).
Yes, the nyx is not there because I am showing that I am able to load the hekate_ctcaer_5.5.5.bin (which is above screenshot) if I did not put the bootloader files into my SD Card.
It is only having issues when I put the bootloader files into my SD Card then load it using TegraRcmGUI the payload hekate_ctcaer_5.5.5.bin showing as black screen afterwards.
bootloader/sys
What is in your hekate_ipl.ini?
Are you bypassing nyx by auto-loading something? If nyx itself is not loading, those are your only options. Corrupt/bad card, bad socket on the Switch itself, or you're bypassing nyx. nyx loads before ANYTHING, so it should boot even with your emmc physically removed.
@urherenow Here is the configuration for the hekate_ipl.ini. No I am not bypassing nyx, the screenshot I showed earlier loads when I tried to load the hekate_ctcaer_5.5.5.bin without any files in my SDCard that is why it is saying the nyx is probably missing.
When I put all the bootloader files into my SDCard and tried to load the hekate_ctcaer_5.5.5.bin. It only black screens after attempting to load the payload successfully based on the input from Tegra payload loader.
[config] updater2p=1 {------ Atmosphere ------} [Atmosphere FSS0 EmuMMC] fss0=atmosphere/fusee-secondary.bin kip1=atmosphere/kips/ emummcforce=1 icon=bootloader/res/emu_boot.bmp {} [Atmosphere FSS0 SYS] fss0=atmosphere/fusee-secondary.bin kip1=atmosphere/kips/ emummc_force_disable=1 icon=bootloader/res/sys_cfw_boot.bmp {} {-------- Stock ---------} [Stock SYS] fss0=atmosphere/fusee-secondary.bin stock=1 emummc_force_disable=1 icon=bootloader/res/stock_boot.bmp
Black screen in my switch still.
Any reason why you're missing most of the basic config settings?
[config] autoboot=0 autoboot_list=0 bootwait=3 backlight=100 autohosoff=0 autonogc=1 updater2p=1 bootprotect=0
@urherenow I already tried adding the basic config settings. And loaded hekate_ctcaer_5.5.5.bin still on blackscreen after Tegra saying payload successfully injected.
dm me on gbatemp. we should pick this up there because this isn't meant to be a forum. Have you tried launching OFW yet? You can take a screen shot and see it in the album? If so, what is the crc32 of your nyx.bin (check on the card, not within the .zip... I use hashtab for windows, myself...).
Also, I haven't heard of this being a problem in a long time, but if you look at the properties of hekate_ctcaer_5.5.5_Nyx_1.0.2.zip, does a check box appear near the lower end of the window, giving you the option to "unblock" it? iirc, if that was even a problem on your system, then the crc32 of the file extracted to your card would be incorrect...
Seems like the issue is on the libsys_minerva.bso file which causes to blackscreen when loading any payloads. After I tried to rename or remove the file I was already able to load Hekate but it prompts as a warning page screen in which the file is missing for Minerva.
I am not sure what is causing this. Attaching screenshot for refence
I've already told you, github is not a help forum. It's for actual bugs.
The date/time thing is normal for a first run. You need to delete your hekate .zip file then download it again, because something is wrong with the file(s) you're using. CTCaer would probably want you to to post a screenshot of your sd information as nyx shows it, since it appears you've been able to at least boot to the gui...
@Recurem you either have corruption or your sd card reader connector has issues. Or your cable might have issues. I would check for these in your case.
If it's corruption, repaste release and make sure you safely eject. If the dir was corrupted, then you need to copy the contents of your hekate ini, delete bootloader folder, repaste anew and run once. If it's fixed, paste the ini contents back.
Hi @CTCaer
Thank you for attending to my concern. I am not sure anymore this might be a hardware/software specific on my Switch since this is my first time in attempting homebrew on that specific switch unit (this is a V1 unpatched), because I have another separate V1 unpatched Switch here (FW 11.0.1). I was able to load the Hekate without issues with Minerva contents successfully by putting same SDCard I used on that specific switch. Literally what I did is to put the SDCard into it. If there was really a SD Card Reader corruption then my another switch should not be able to load the payload but it was able to load without issues. I also noticed when the Minerva module is there it prevents me to load other payload successfully (e.g TegraExplorer or Lockpick) but I am able to load it on my other separate switch as well.
I would also like to understand is this Minerva module (libsys_minerva.bso) being loaded automatically when I tries to load any payload in the background process?
I hope we can agree at some point that it might be a Switch unit specific (it maybe a hardware or software related) since we already know the SD contents with Minerva module I used works on a separate switch I am using. If it was not working then I would agree this is really a corruption on the SD Card/memory card.
Its very likely to be your sd card reader, as they fail pretty easily and cause all sorts of issues when you do anything with the sd card. Good news is the reader is super easy to replace, it's just plugged in under the back panel and can be easily removed and replaced
I just want to iterate If this was a card reader issue then both switches that I have should have black screen when I load the payload using same SD card, I just literally swapped the SD Card to my another switch and load the Hekate payload and it was able to load it successfully without any issues or black screen.
I am not sure anymore what do do this unit I am trying to homebrew. I might have bad luck.
Why would it be both switches? If the same sd card loads on one switch but not the other, one would assume that the card reader on the switch that didn't load correctly is probably faulty
Yes, Now I understand and would agree it might be a card reader on the Switch itself. But one thing for sure I am wondering it is only affecting libsys_minerva.bso preventing any payload/s from being loaded.
I guess I just really have a bad luck with this unit and have this to be checked on my retail store since I just recently got this unit X days ago.
@Recurem put back minverva and try this in nyx.ini newpowersave=0
Tell me results.
Hi @CTCaer where do I modify this newpowersave=0? I cannot seem to find nyx.ini in my bootloader folder.
Sorry I am quite new to this.
It should have been already created if you clicked done on that screen https://github.com/CTCaer/hekate/issues/596#issuecomment-818697468
Just create a new file named nyx.ini
in /bootloader
folder
With these contents:
[config]
timeoff=1
newpowersave=0
I tried setting it up to that configuration mentioned @CTCaer still the same with black screen when I tried to load the hekate_ctcaer_5.5.5.bin payload with the Minerva module.
Do you need more details?
Well that's weird. And more importantly screen artifacts you get when you are finally in Nyx. I can possibly pinpoint if the issue is your RAM chips or SD card reader connector (not the reader itself as others pointed here. That one is difficult to break), or something else. But you will need to contact me in retronx discord server. Join in and pm me.
Hi @CTCaer I contact you via PM.
Thank you.
Issue is that a RAM chip is faulty. Specifically a ram bank of one of the 2 chips. User was advised to repair it or try to return it back.
Yea, sorry the extra help started when I was asleep. I would have mentioned that he "received it with FW 12 on it already". So it's used. Nobody is going to sell an unpatched unit unless it's broken or you agreed to pay way more than retail...
tegrarcm saying successfully injected payload and nothing popping up on my switch any tips?
Please don't post on dead issues. Either your switch is patched or you are doing something wrong, likely the first one though. Regardless, it's not an issue with Hekate.
Ok thanks
On Wed, Jul 19, 2023, 8:06 PM Masamune3210 @.***> wrote:
Please don't post on dead issues. Either your switch is patched or you are doing something wrong, likely the first one though. Regardless, it's not an issue with Hekate.
— Reply to this email directly, view it on GitHub https://github.com/CTCaer/hekate/issues/596#issuecomment-1642451233, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYRDTG6TU6EWK4VNIH3BT4TXRAH27ANCNFSM42Z5OKPQ . You are receiving this because you commented.Message ID: @.***>
Hi,
I am experiencing issues when loading hekate_ctcaer_5.5.5.bin payload it is giving me a black screen only for Switch Version 12.0.0 when loading the payload via the TegraRcmGUI (version 2.6). It is saying that I injected the payload successfully but nothing happens just black screen.
The bootloader folder contains the folder below in my SD Card. There are some other files but it is related already to the latest version of Atmosphere which is Atmosphère 0.19.0
emummc.kipm libsys_lp0.bso libsys_minerva.bso nyx res.pak
I already ensured I copied the latest files into the bootloader folder in the SD Card.
I can guarantee as well my switch is unpatched given I was able to load also the latest TegraExplorer.bin with no problems and also loading @CTCaer check.bin file provided here it says "RCM Exploited Device/ VBAT:"