Hacking Payload not working

radicalwookie · May 25, 2021

Hey guys,

i recently went to homebrew channel and updated m atmosphere and hekate files with the app AIO SWITCH UPDATER. I had my payload set in a way that allows S

Before restarting I accidentally updated Switch to 12.0.2. I tried injecting hekate payload and it only goes to blank screen. Tegra explorer injects successfully but none of my payloads do

Not update.bin, reboot.bin, payload.bin or any else.

Am I doing something wrong? I currently cant access sd card filea as I dont have a card reader so I hope this can be fixed without putting bew hekate and atmos and deleting old files.

Hayato213 · May 25, 2021

You might have to manually replace your Atmosphere file from the github and tried again, SciresM doesn't recommend replacing Atmosphere file while cfw is running.

radicalwookie · May 25, 2021

Hayato213 said:
You might have to manually replace your Atmosphere file from the github and tried again, SciresM doesn't recommend replacing Atmosphere file while cfw is running.

Damn the luck.
I dont have card reader to be able to replace atmosphere files

((

BaamAlex · May 25, 2021

radicalwookie said:
I dont have card reader to be able to replace atmosphere files

Use hekates usb feature.

radicalwookie · May 25, 2021

BaamAlex said:
Use hekates usb feature.

I cant get in hekate payload, thats the problem.
Hekate boot should boot regardless of atmosphere files right?

the only thing that gets booted successfully is tegraexplorer.bin

Homlet · May 25, 2021

radicalwookie said:
Damn the luck.
I dont have card reader to be able to replace atmosphere files ((

the hekate payload should inject properly. You may have autoboot on, in which case you need to hold vol+ (or vol-, not sure which one) when injecting the payload. From hekate, you can connect your console to your PC via usb with the USB Mass Storage feature and update your atmosphere. You shouldn't abort the update process of aio-switch-updater, the payload it's running after extracting the archives is a necessary step and not a simple reboot

radicalwookie · May 25, 2021

Homlet said:
the hekate payload should inject properly. You may have autoboot on, in which case you need to hold vol+ (or vol-, not sure which one) when injecting the payload. From hekate, you can connect your console to your PC via usb with the USB Mass Storage feature and update your atmosphere. You shouldn't abort the update process of aio-switch-updater, the payload it's running after extracting the archives is a necessary step and not a simple reboot

Ah you are the dev of AIO!
Yeah I aborted stupidly because I didnt want to restart just yet (also i thought its just a simple reboot to rcm).

i was holding volume button while injecting but it didnt work either. No matter what I try, hekate wont boot. Meanwhile Tegraexplorer works perfectly fine but if I select any payload within tegraexplorer and press launch it again goes to dark blank screen.

What on earth is wrong

Hayato213 · May 25, 2021

radicalwookie said:
Ah you are the dev of AIO!
Yeah I aborted stupidly because I didnt want to restart just yet (also i thought its just a simple reboot to rcm).

i was holding volume button while injecting but it didnt work either. No matter what I try, hekate wont boot. Meanwhile Tegraexplorer works perfectly fine but if I select any payload within tegraexplorer and press launch it again goes to dark blank screen.

What on earth is wrong

Did you abort when it was flashing firmware files or was it flashing CFW files?

radicalwookie · May 25, 2021

Hayato213 said:
Did you abort when it was flashing firmware files or was it flashing CFW files?

It was just updating CFW files.

Hayato213 · May 25, 2021

radicalwookie said:
It was just updating CFW files.

Replacing the files should fix your problem, I was using the AIO updater on Sunday and it didn't update correctly for me either, see post #113 in the thread below about SciresM not recommending updating while Atmosphere is running.

https://gbatemp.net/threads/atmosphere-updater-an-atmosphere-updater-for-your-switch.548450/page-6

Homlet · May 25, 2021

radicalwookie said:
It was just updating CFW files.

Indeed, replacing the files will fix your problem. It's odd you can't boot into hekate though. Does it even show a splash screen?

Hayato213 said:
Replacing the files should fix your problem, I was using the AIO updater on Sunday and it didn't update correctly for me either, see post #113 in the thread below about SciresM not recommending updating while Atmosphere is running.

https://gbatemp.net/threads/atmosphere-updater-an-atmosphere-updater-for-your-switch.548450/page-6

SciresM did say it's ok, and it's definitely not expected behavior that it didn't update correctly. It might be a sysmodules issue though, but if it's not I'd appreciate if you could open a github issue, say so in my thread or send me a PM

Hayato213 · May 25, 2021

Homlet said:
Indeed, replacing the files will fix your problem. It's odd you can't boot into hekate though. Does it even show a splash screen?

SciresM did say it's ok, and it's definitely not expected behavior that it didn't update correctly. It might be a sysmodules issue though, but if it's not I'd appreciate if you could open a github issue, say so in my thread or send me a PM

I'm not against your work, the post I linked SciresM request Atmosphere updater to be removed from homebrew shop as the concern if replacing custom firmware files by the updater didn't do its job correctly you would encounter the situation where it won't boot, that what happened to me on Sunday where my unit wouldn't boot using files that all in one updater downloaded, I have to manually replace all of the Atmosphere files.

Homlet · May 25, 2021

Hayato213 said:
I'm not against your work, the post I linked SciresM request Atmosphere updater to be removed from homebrew shop as the concern if replacing custom firmware files by the updater didn't do its job correctly you would encounter the situation where it won't boot, that what happened to me on Sunday where my unit wouldn't boot using files that all in one updater downloaded, I have to manually replace all of the Atmosphere files.

I didn't mean to sound rude. I just want my app to work for everyone, and it works for me (otherwise I wouldn't release it) but I'm interested in fixing and/or understanding why it doesn't work for others. SciresM gave me a greenlight on 4channel to update via RCM, and he said it's fine on Discord too so if there is a problem, it's either user error (oftentimes sysmodules) or something with my code

@radicalwookie Are you sure you're injecting the latest hekate payload?

radicalwookie · May 25, 2021

Homlet said:
I didn't mean to sound rude. I just want my app to work for everyone, and it works for me (otherwise I wouldn't release it) but I'm interested in fixing and/or understanding why it doesn't work for others. SciresM gave me a greenlight on 4channel to update via RCM, and he said it's fine on Discord too so if there is a problem, it's either user error (oftentimes sysmodules) or something with my code

@radicalwookie Are you sure you're injecting the latest hekate payload?

I am 100% sure. Im using latest hekate payload from official github. Theres no splashscreen nothing just black screen. I really find that odd.

I have to find out what i did to enable sx dongle booting and see if thats the issue.

--------------------- MERGED ---------------------------

Homlet said:
I didn't mean to sound rude. I just want my app to work for everyone, and it works for me (otherwise I wouldn't release it) but I'm interested in fixing and/or understanding why it doesn't work for others. SciresM gave me a greenlight on 4channel to update via RCM, and he said it's fine on Discord too so if there is a problem, it's either user error (oftentimes sysmodules) or something with my code

@radicalwookie Are you sure you're injecting the latest hekate payload?

This is the tutorial I followed to enable sx dongle to rcm boot into hekate

Using the SX Pro or Gear Dongle to boot Atmosphere without the possibility to load SX OS

Utilizing the SX Gear boot.dat (which is just a chainloader), you can force the dongle to boot Hekate directly. As with the SX OS boot.dat, it will not launch Atmosphere directly and just blackscreen if you try to, and you'll also have to use Hekate to achieve getting into Atmosphere.

Follow all the steps above to set up Hekate

Get the SX Gear boot.dat, put that on the root of your microSD, overwriting any existing boot.dat

If you use the dongle to boot your console now, it will bring you into Hekate, where you can navigate to Launch > Payloads and choose fusee-primary.bin to launch Atmosphere

Homlet · May 25, 2021

radicalwookie said:
I am 100% sure. Im using latest hekate payload from official github. Theres no splashscreen nothing just black screen. I really find that odd.

I have to find out what i did to enable sx dongle booting and see if thats the issue.

--------------------- MERGED ---------------------------

This is the tutorial I followed to enable sx dongle to rcm boot into hekate

Can't you try uploading it directly from your computer instead? It's starting to look like your problem is the injection, not so much the files that are or aren't on your sd card

radicalwookie · May 25, 2021

Homlet said:
Can't you try uploading it directly from your computer instead? It's starting to look like your problem is the injection, not so much the files that are or aren't on your sd card

I did inject from pc because dongle didnt work (i thought batteries died for good).
I used TegraRCMgui abd latest hekate payload file

radicalwookie · May 26, 2021

I Finally got card reader!

which files should I delete on sdcard? Atmosphere folder and boot.dat?

Homlet · May 26, 2021

radicalwookie said:
I Finally got card reader!

which files should I delete on sdcard? Atmosphere folder and boot.dat?

why do you even have a boot.dat? To be thourough, you can delete atmosphere, sept and bootler and get a new atmophere and hekate

radicalwookie · May 26, 2021

Homlet said:
why do you even have a boot.dat? To be thourough, you can delete atmosphere, sept and bootler and get a new atmophere and hekate

I told you boot.dat is for sx dongle to work so that i can boot while away from pc

Draxzelex · Jun 25, 2021

radicalwookie said:
I Finally got card reader!

which files should I delete on sdcard? Atmosphere folder and boot.dat?

Make sure the SD card is formatted to FAT32 as well.

Hacking Payload not working

Well-Known Member

Newcomer

Well-Known Member

UDE GA NARU ZE!

Well-Known Member

Well-Known Member

Well-Known Member

Newcomer

Well-Known Member

Newcomer

Well-Known Member

Newcomer

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum