Hacking My switch does not read the payload

  • Thread starter Thread starter mgjpm37
  • Start date Start date
  • Views Views 11,732
  • Replies Replies 51
When you connected your android did you mean a mobile phone / Handy?
Then you need an OTG USB adapter. A normal USB micro USB to USB C, for example, doesn't work.
With a normal USB adapter the android is a client. Your Switch is a client too, so it doesn't work.
With an OTG Adapter cable, your android device will become a server an can send the payload to the client Switch.
 
When you connected your android did you mean a mobile phone / Handy?
Then you need an OTG USB adapter. A normal USB micro USB to USB C, for example, doesn't work.
With a normal USB adapter the android is a client. Your Switch is a client too, so it doesn't work.
With an OTG Adapter cable, your android device will become a server an can send the payload to the client Switch.

apk was aware of the switch
 
  • Like
Reactions: Calahan
I use my android phone to send payload too, and never got any issues.

it depends on multiple reasons, you should:

-whenever you upgrade CFW, you HAVE TO upgrade payload too, you are probably using oldpayload to boot newer CFW or viceversa;
-both pc and smartphone do the same job, but on pc you can check if ur switch is in RCM mod

go to this guide and download TegraRcmGUI and try again

https://gbatemp.net/threads/tegrarcmgui-simple-gui-for-tegrarcmsmash.503510/
 
  • Like
Reactions: Calahan
apk was aware of the switch
As x65943 mentioned, I also think it would be a good idea to test it with a pc first.
TegraRCMGui would show you, if your Switch is in RCM modus. Then send the same payload, which is on your android.
If that works, it is a problem with the android device or the rikado apk.
It that doesn't work too, you could have a wrong reinx.bin.
I had such problem when my switch was on an older firmware.
I had to use an older version of reinx.bin. reinx.bin version 2.0 didn't work for me.
I then updated the firmware to 6.2 and then the reinx.bin version 2.0 did work too...

Edit:
Seems like I was typing too slow. leon315 wrote the same. One more reason to try it first on a pc.
 
Last edited by Calahan,
As x65943 mentioned, I also think it would be a good idea to test it with a pc first.
TegraRCMGui would show you, if your Switch is in RCM modus. Then send the same payload, which is on your android.
If that works, it is a problem with the android device or the rikado apk.
It that doesn't work too, you could have a wrong reinx.bin.
I had such problem when my switch was on an older firmware.
I had to use an older version of reinx.bin. reinx.bin version 2.0 didn't work for me.
I then updated the firmware to 6.2 and then the reinx.bin version 2.0 did work too...

I will try it when I can use the PC
thankyou
 
  • Like
Reactions: Calahan
It happens. Go into RCM again with your method of choice, and inject again. Sometimes it takes me 4 to 5 times
 
  • Like
Reactions: Kubez
By the way, is there a recommended payload?
I don't know, what you have done so far and on which firmware your switch is, but it seems to me, you never send a payload to your switch before.
So I would recommend, you use a tutorial for the next steps. There are so many in different languages, so find one which you can understand.
First step in every case, I think, would be injecting the hekate payload. You can find it here: https://github.com/CTCaer/hekate/releases
You can try the hekate payload with your android device. I don't know exactly if hekate does work with all older firmwares, but I think so.
Then you should save your boot0 and boot1 files and make a full nand backup, in case anything goes wrong later :)
 
Not all phones support OTG so you probably have a phone that doesn't support OTG. So you can't do it through a phone since it only works with an OTG adapter
 
i boot using latest Atmosphere for autoboot, switch boots goes right into home after Sept splashscreen,
 
Well you need:
  • An android phone
  • PC/notebook
  • dongle
You only need one of list above, and you only need once! I suggest you to use latest HEKATE payload, from there you can backup nand and activate AUTORCM.
 
Well you need:
  • An android phone
  • PC/notebook
  • dongle
You only need one of list above, and you only need once! I suggest you to use latest HEKATE payload, from there you can backup nand and activate AUTORCM.

Can AUTORCM switch between CFW and OFW?
 
Last edited by leon315,
Well you need:
  • An android phone
  • PC/notebook
  • dongle
You only need one of list above, and you only need once! I suggest you to use latest HEKATE payload, from there you can backup nand and activate AUTORCM.

After sending the payload, it will be displayed as "SUBMITURB failed" on the application
 
After sending the payload, it will be displayed as "SUBMITURB failed" on the application
OH MY, listen try to restart do all the steps again:

-delete the payload and try different one;
-try to boot with a different memory card or w/out it;

it's weird if you followed the link i provided, can you take a picture about ur firmware and SUBMITURB??
 

Site & Scene News

Popular threads in this forum