Hacking Question RCM Switch blank on successful payload injection

Madotsuki

Member
OP
Newcomer
Joined
Jan 4, 2016
Messages
23
Trophies
0
Age
32
XP
140
Country
United States
Preliminary info
Switch Serial: XAW10059
Firmware: 6.0.1
SD Card: Fat32 formatted 128GB

SD Root:
unknown.png



So my Switch just doesn't respond when payloads are injected. When I inject pretty much any payload to it, I get a "success" result, but the screen of my Switch is absolutely blank, without even any backlight. It definitely is still in RCM, but is has zero change. I've tried reinstalling drivers, restarting my PC, using different payloads, etc. I've also tried asking in a few discords and haven't reached a solution yet (though I'll try a different USB-C cord and try a USB 3.0 port on my computer later, as a suggestion from a helpful Discord member). Here are some CMD logs from using Smash to inject ReiNX.bin instead of the GUI:

Code:
C:\Users\Administrator\Downloads\TegraRcmGUI_v2.4_portable\TegraRcmGUI_v2.4_portable>tegrarcmsmash -r C:\Users\Administrator\Downloads\TegraRcmGUI_v2.4_portable\TegraRcmGUI_v2.4_portable\favorites\ReiNX.bin
TegraRcmSmash (32bit) 1.2.0-2 by rajkosto
Opened USB device path (omitted)
RCM Device with id (omitted) initialized successfully!
Uploading payload (mezzo size: 92, user size: 71506, total size: 137722, total padded size: 139264)...
Switched to high buffer
Smashing the stack!
Smashed the stack with a 0x0057 byte SETUP request!

And here's me trying to inject biskeydumb.bin:

Code:
C:\Users\Administrator\Downloads\TegraRcmGUI_v2.4_portable\TegraRcmGUI_v2.4_portable>tegrarcmsmash -r C:\Users\Administrator\Downloads\biskeydumpv7\biskeydump.bin
TegraRcmSmash (32bit) 1.2.0-2 by rajkosto
Opened USB device path (omitted)
RCM Device with id (omitted) initialized successfully!
Uploading payload (mezzo size: 92, user size: 98600, total size: 164816, total padded size: 167936)...
Smashing the stack!
Smashed the stack with a 0x0057 byte SETUP request!
Though it was taking a while and I had to leave for work so I powered down my Switch resulting in a "failed" message after the above. But it didn't seem like it was doing anything on my screen, if it was supposed to. To get the obvious out of the way - yes, the Switch screen DOES work outside of RCM. Yes, my computer detects when it's connected in RCM versus when it's not in RCM, so it can differentiate between the two. And I tried a hard power down by holding the power button for about 30 seconds before attempting again, it still didn't work. I was told that the "0x0057" byte was a somewhat curious value that's not normal to have.

I tried searching far and wide for this issue and it seems my Switch is the special snowflake that's experiencing this. The closest I've found to this issue is someone that was able to resolve it with a hard powercycle and someone that had a corrupted SD card (mine is fine), and people with Switches that are new enough to have patched bootloaders (my serial tests just fine, so unless the seller of this Switch swapped the serial sticker or something I don't see this being an issue). So anyone have any suggestions? Sorry if this is a bit lengthy - I wanted to give as much information as I could.

Edit - Tested with a new USB cable, utilizing a USB 3.0 port, still no dice.

Code:
C:\Users\Administrator\Downloads\TegraRcmGUI_v2.4_portable\TegraRcmGUI_v2.4_portable>TegraRcmSmash.exe -w C:\Users\Administrator\Downloads\biskeydumpv7\biskeydump.bin BOOT:0x0
TegraRcmSmash (32bit) 1.2.0-2 by rajkosto
Opened USB device path (Omitted)
RCM Device with id (Omitted)  initialized successfully!
Uploading payload (mezzo size: 92, user size: 98600, total size: 164816, total p
added size: 167936)...
Smashing the stack!
Smashed the stack with a 0x0057 byte SETUP request!
Win32 error 31 during post-smash read op
The error occurred when I removed my device after about 30 minutes of waiting. Also confirmed via Switch OS that my serial number is XAW10059. There was no switcharoo with serial stickers on the seller's part.


Final edit - Got it to work. I just used a different PC. Not sure what the problem was with my initial PC but it works just fine now. I guess the takeway from this is that if anyone else has this problem, use a different device...
 
Last edited by Madotsuki,

slicer2k

Active Member
Newcomer
Joined
Aug 9, 2017
Messages
40
Trophies
0
Age
43
XP
175
Country
Brazil
Dude did you get to fix that? My NSW is giving me the exactly 0x0057 byte after i have inserted it in a faulty usb PC port, the port now seems to be working(at same point) but i get no screen after injection!
 

olegstar

New Member
Newbie
Joined
Jul 1, 2019
Messages
1
Trophies
0
Age
43
XP
50
Country
United Kingdom
Hi. Just wanted to say I had exact same problem as Madotsuki with 0x0057 and after switching to another PC I got 0x7000 and instead of a black screen my switch lit up with hekate :)

If it matters the first pc runs windows 7 ultimate and the second windows 10 pro.

Good Luck everyone!
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    cearp @ cearp: and Psi - I had a cd player / radio that played mp3 cds once, very cool