Hacking Question Black Screen when trying to boot, new hardware released ?

  • Thread starter Thread starter Picooz
  • Start date Start date
  • Views Views 68,752
  • Replies Replies 136
unknown-2.png
 
updated video url which removed my BIS KEY information.



I went out to get another spare Nintendo Switch on the same model but lower serial number.
And it still works fine.
I hope this video give you the idea to avoid XAJ7004XXXXXX if you want to exploit your nintendo switch.
 
Last edited by gnilwob,
updated video url which removed my BIS KEY information.



I went out to get another spare Nintendo Switch on the same model but lower serial number.
And it still works fine.
I hope this video give you the idea to avoid XAJ7004XXXXXX if you want to exploit your nintendo switch.


Hi, I hit the exactly same problem with you.
My new Nintendo Switch bought on Jul 12 from Hong Kong and the serial number is XAJ7004395XXXX
Nothing happened after payload injected.
I wonder if you have tried to use NSLoader? I'm struggling if I should buy a new cable...
 
Hi, I hit the exactly same problem with you.
My new Nintendo Switch bought on Jul 12 from Hong Kong and the serial number is XAJ7004395XXXX
Nothing happened after payload injected.
I wonder if you have tried to use NSLoader? I'm struggling if I should buy a new cable...

You have to buy a new Switch !!!
The unit you got is patched and it does not accept payload either from USB, NXLoader, SX Pro dongle, etc...

If you are not sure whether it is your cable, please try to inject biskeydump
Go to https://switchtools.sshnuke.net/ to download tegrarcmsmash and biskeydump
Then open a command prompt, plug in your RCM switch and run this command.

TegraRcmSmash.exe -w biskeydump.bin BOOT:0x0

You will see from the output then your switch received payload but it does not execute the payload.

This is from XAJ700439xxxxx: (Not working, no solution as of now)
2018-07-13_4-48-11.png

This is from XAJ7003xxxxxx: (working)
2018-07-13_5-20-39.png

By the way, welcome to the club :cry:
 
Last edited by gnilwob,
hi guys i got a switch a week or 2 ago ive managed to get my switch into rcm mode its connected as and apx device on pc but tegrarcmgui still says "rcm not connected" does this mean i have a patched unit or am i missing something?
 
hi guys i got a switch a week or 2 ago ive managed to get my switch into rcm mode its connected as and apx device on pc but tegrarcmgui still says "rcm not connected" does this mean i have a patched unit or am i missing something?
Not it just means its not in RCM. Its patched if you send a payload and nothing happens.
 
I'm having the same problem.

I'm using TegraRCM.

NXloader app on android does not recognize my switch

On TegraRCM, I get injection successful, but black screen with no SX OS booting up.

If it helps, mine is a XAW7001XXXXXX device.

Checked everywhere for solutions, nothing works.

Used multiple sd cards, usb wires, usb adapters, usb hubs, different laptops.

Getting desperate here!
 
Last edited by lifetolifeless,
I'm having the same problem.

I'm using TegraRCM.

NXloader app on android does not recognize my switch

On TegraRCM, I get injection successful, but black screen with no SX OS booting up.

If it helps, mine is a XAW7001XXXXXX device.

Checked everywhere for solutions, nothing works.

Used multiple sd cards, usb wires, usb adapters, usb hubs, different laptops.

Getting desperate here!

SD card is out of question, you can remove it and test with SX's payload.bin (it will just complain about boot.dat is not found)
Or you can test it with biskeydump.bin
See my 3 posts above on how to run tegrarcmsmash on command line.
You will see in more detail on the command line and you will know exactly if the payload has been sent to your console or not (and it implies if you console is a patched unit or not).
 
SD card is out of question, you can remove it and test with SX's payload.bin (it will just complain about boot.dat is not found)
Or you can test it with biskeydump.bin
See my 3 posts above on how to run tegrarcmsmash on command line.
You will see in more detail on the command line and you will know exactly if the payload has been sent to your console or not (and it implies if you console is a patched unit or not).


I didn't run the tegrasmash test, but I tried ejecting the card before injecting payload.

Same thing with the black screen.

Could it be a false positive on payload injection success?

I was using tegrasmashGUI btw.
 
Last edited by lifetolifeless,
Ok, managed to run the test:

fail.PNG

(mine is the one highlighted in green)

Have already shared this on the TX's thread.

if it helps here's the details on my set:
  • US Set
  • XAW7001822XXXX
  • HAC-S-UXA-C1
  • Came with 4.10 Installed, updated it to 5.1.0 for sdxc use.
Guess it's back to my trusty ol' 3DS for mah gaemz!

Please follow this post to test it.
Because the command line will provide more information so you know what happen. (look at both pictures)
 
Last edited by lifetolifeless,
Ok, managed to run the test:

View attachment 136187
(mine is the one highlighted in green)

Have already shared this on the TX's thread.

if it helps here's the details on my set:
  • US Set
  • XAW7001822XXXX
  • HAC-S-UXA-C1
  • Came with 4.10 Installed, updated it to 5.1.0 for sdxc use.
Guess it's back to my trusty ol' 3DS for mah gaemz!

Did you share this in the serial number thread? Yes, this is patched.
 
if you can take the back off and see if they changed the motherboard markings should be right next to the usb port, something like
HAC-CPU-10

I would imagine markio units will be
HAC-CPU-20 (assuming there hasn't been other revisions to the pcb prior to the markio

Baught in Australia May 2018, running sx os definetly not mariko
 

Attachments

  • 20180720_135830.jpg
    20180720_135830.jpg
    1.5 MB · Views: 389
  • Like
Reactions: gamesquest1
Small, but will exponentially increase as time passes.
Guess I have to do it asap then.
Is there a way to check if it's a new revision? Specific bundles being more safe than the others or serial codes, or something else. Just how to minimize the risk?
 

Site & Scene News

Popular threads in this forum