Hacking Error after update Switch GTP:0x00177a002

[slyraccoons]

Previously I was on
12.1 firmware
atmosphere ams 1.1.1.
deep sea

I decided to update with
deepsea-advanced_v4.2.0
atmosphere 1.3.2
hekate_ctcaer_5.8.0_Nyx_1.3.0

It was working and so I updated to firmware 14.1.2 using daybreak

before rebooting again I pulled the sd out and updated the sigpatches and it hasn’t worked since.

After running fusee I get the atmosphere logo then fatal error. failed to read GPT0x0177a02

I suspected my sd card is corrupted because I get errors trying to access folders and have issues when copying files off it. So I got a new sd card, then created a emuMMC partition I transferred a copy of my sd card (this is the larger drive that you can access on pc not the emmunand partition) I made prior to the update and modded the files again the same as I did before, update deep sea then atmosphere Hekate. But cant get it to boot.

Interestingly in Hekate I can launch CSW sysnand which I can see is running 4.1.0 (AMS 1.3.2)S

I tried deleting atmosphere and bootloader folders and installing a new copy of atmosphere and hekate files a few times but no luck.

I tried just starting from a empty sd and put atmosphere and Hekate and fusee on but that didn’t work either.

Is my emuMMC corrupted perhaps? I don't care if I lose my save files as long as my switch works again.

 

[slyraccoons]

Been doing some reading and I got emutools and tried copying my old sd emummc partition but i get error "reading disk need admin rights" (i did already open it with admin rights) when i click ok it kept copying and finished.

So i tried copying with emutools to my new sd card and i get error boot0 not found.

I tried using nandmanager to copy but after a while im getting errors copying with that as well.

below is my old sd card info if thats of any help

I also noticed my emummc.ini text looks weird, its not ment to be like this right?

Do i need to keep my old emummc or can i just create a new one? is this the easier to way to get my switch working again?

I can still get into CFW Sysnand and run applet homebrew and get to the Hekate menu so i dont think I'm completely screwed yet.

I have only updated my CFW and system firmware twice since modding it. Chances are i have done something stupid.

 

[impeeza]

you forgot to update your injector payload, that's is all, update your payload and all will work fine.

 

[slyraccoons]

you forgot to update your injector payload, that's is all, update your payload and all will work fine.

thanks for the reply,

when you say update your payload you mean replace the fusee file with the new version from the atmosphere download right?

so I cant delete the fusee file off the root of my sd or copy over the top of it. I put a new fusee file in the bootloader and when I run fusee from tegra I get this error;

failed to parse sdmc:/emummc/emummc.ini!

if I run Hekate first and I get missing LP0 (sleep) Lib update bootloader folder. After that error Hekate gets stuck at the logo Hekate IPL

I’m getting errors in windows saying the card is corrupted when copying atmosphere and Hekate files and files I delete reappear on the card again. Eg system settings.ini there is about 6 other files not copying

Am I able to format this partition of the sd card (the one you can read in windows that’s larger 150gig) safely without disturbing the emmummc partition.

 

[impeeza]

nop, update the file on the method you use to inject the payload, as far I know could be:

• A phone using Rekado.
• A PC using TegraRCM or similar.
• A RCM Dongle (RCM Loader, R4s, etc.).
• A internal Trinket.

All of them have different methods of update the file used to boot the console.
The file could be:

• fuse.bin from atmosphère, which when used boot directly to Atmosphère.
• Hekate_x_x_x.bin used to boot Hekate or Nyx and chainload another payload or boot Atmosphère.
• ArgonNX / ArgonNX-SE, payload.bin from SXOS or similar which try to load a bin file from your SD card, in this case you need to update that one file.

As you can see it depends on YOUR personal configuration so you need to know which one you use and update the correspondent file.

The most common setup is a dongle injector injecting Hekate.

 

[slyraccoons]

nop, update the file on the method you use to inject the payload, as far I know could be:

• A phone using Rekado.
• A PC using TegraRCM or similar.
• A RCM Dongle (RCM Loader, R4s, etc.).
• A internal Trinket.

All of them have different methods of update the file used to boot the console.
The file could be:

• fuse.bin from atmosphère, which when used boot directly to Atmosphère.
• Hekate_x_x_x.bin used to boot Hekate or Nyx and chainload another payload or boot Atmosphère.
• ArgonNX / ArgonNX-SE, payload.bin from SXOS or similar which try to load a bin file from your SD card, in this case you need to update that one file.

As you can see it depends on YOUR personal configuration so you need to know which one you use and update the correspondent file.

The most common setup is a dongle injector injecting Hekate.

cheers for the info.

Didn't think about there are different methods. Ive always used a pc with tegraRCM which before i would run hekate then use hit the payload and use fusee to start. I think the only way now is to run fusee in tegraRCM which is what i have been doing.

So i use the new fusee file that came with atmosphere 1.3.2 in tegraRCM to inject into the switch still getting the;
failed to parse sdmc:/emummc/emummc.ini!

if i instead inject hekate 5.8 through tegraRCM I get the error missing LP0 (sleep) Lib update bootloader folder. After that error Hekate gets stuck at the logo Hekate IPL

 

[impeeza]

In Summary yes, but from helate you can chainload fusee.bin or load directly package3 file. For me is better the later because you get the improvements of hekate bootloader.

 

[PorkyMcChops]

I started writing this yesterday at work and forgot to finish/post it until i was back here today so it ended up being quite a long read overall but here we go..
It does sound like it could possibly be some kind of sd card corruption to me. But without looking deeper into some of the issues around the emummc.ini file and the parsing errors during boot, I can only give you some generic advice thats been repeatedly posted here on the forum many times before that i think could apply to this issue. But hopefully something in my random thoughts here helps you or someone lurking in the future.. Feel free to completely disregard any or all of it.

Hopefully youve backed up your saves and have that data somewhere safe or can try to use a pc to get the data from the sd but if its been corrupted you may run into problems there. (And seems like you are having these problems el-accessing the SD from a PC)

Always use fat32 format not exFat. I personally use exfat with no issues but with everything i read regarding exfat and switch, its probably a terrible idea. (I dont like the file size limitation of fat32 and i keep tons of back ups so im prepared for sd errors should they arise) For reliability, my wife’s switch IS fat32 -it needs to just work every time or it will be my headache. Im not completely sure but i think there is also something with firmware updates and making sure you have the exfat driver present. I believe each firmware update is available with and without the exfat driver(someone please correct me if im wrong) - formatting in fat32 would theoretically, also circumvent this particular issue as it should work with or without the exfat driver.

Its a good sign that you can get any info from the card and emunand partition with emutools. I haven’t used that particular program but im interested in checking it out. *If you’re using windows, Admin rights being an issue may be fixed by starting the program in administrator mode (found in rt click drop menu when selecting any program)

If it was me, I would use a different card and just try to start fresh - Format, make a new emunand, and go from there. That would most likely be the easiest option to just quickly get going again. (It seems like you’ve been messing around with the sd card files/folders and who knows what other problems may have been created.) If you can do that then you still have the possibility of extracting data (themes, games, saves, etc..) from the original sd card and transferring it to the new SD card at any point after its up and running properly.

I can see from one of the pics you uploaded from NXnandmanager it says something about “Device ID: keyset needed”. I have no clue if it’s normal but may be a red flag in tracking down what’s going on with the not-working emunand. I.e. prod keys issues? Boot0 related? Why would any of these stop hekate from booting?

Ok after re reading the posts, i can see that you are having issues booting hekate or anything at all. (I thought you could originally get into syscfw? How? From hekate? Is it not working anymore but WAS originally?) Make a new sd and even re download the files completely for atmosphere and hekate. Look for “hats” pack from sythetix. Google it. I believe its a nice “turn-key” solution with everything you need and i have seen it recommended before for people not fully comfortable piecing it all together.

Start simple. You have auto RCM enabled? So you cant check to see if the switch boots to ofw ok and reads the card from ofw hos..? If not, then provided you have the proper files on the sd card and the proper payload hekate should boot. Start there. Get into hekate. Try to make a new emunand. If you cant even do that id start looking at verifying the sd card reader within the switch is actually working properly. Good luck.