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

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by Picooz, Jul 10, 2018.

  1. SirNapkin1334

    SirNapkin1334 Renound Aritst

    Member
    6
    Aug 20, 2017
    United States
    Crap Mountain
  2. gnilwob

    gnilwob GBAtemp Regular

    Member
    5
    Mar 16, 2008
    Hong Kong
    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, Jul 12, 2018
  3. Terry1124

    Terry1124 Newbie

    Newcomer
    1
    Jul 13, 2018
    Hong Kong
    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...
     
  4. gnilwob

    gnilwob GBAtemp Regular

    Member
    5
    Mar 16, 2008
    Hong Kong
    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.

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

    By the way, welcome to the club :cry:
     
    Last edited by gnilwob, Jul 13, 2018
  5. LoGy88

    LoGy88 Newbie

    Newcomer
    1
    Jul 12, 2018
    United Kingdom
    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?
     
  6. Draxzelex

    Draxzelex GBAtemp Legend

    Member
    19
    Aug 6, 2017
    United States
    New York City
    Not it just means its not in RCM. Its patched if you send a payload and nothing happens.
     
  7. lifetolifeless

    lifetolifeless Member

    Newcomer
    2
    May 8, 2007
    United States
    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, Jul 17, 2018
  8. gnilwob

    gnilwob GBAtemp Regular

    Member
    5
    Mar 16, 2008
    Hong Kong
    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).
     
  9. lifetolifeless

    lifetolifeless Member

    Newcomer
    2
    May 8, 2007
    United States

    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, Jul 17, 2018
  10. gnilwob

    gnilwob GBAtemp Regular

    Member
    5
    Mar 16, 2008
    Hong Kong
    Please follow this post to test it.
    https://gbatemp.net/threads/black-s...-hardware-released.510858/page-7#post-8140618

    Because the command line will provide more information so you know what happen. (look at both pictures)
     
  11. lifetolifeless

    lifetolifeless Member

    Newcomer
    2
    May 8, 2007
    United States
    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!

     
    Last edited by lifetolifeless, Jul 18, 2018
  12. V-Temp

    V-Temp GBAtemp Maniac

    Member
    8
    Jul 20, 2017
    United States
    Did you share this in the serial number thread? Yes, this is patched.
     
  13. CrAzYLiFe

    CrAzYLiFe Advanced Member

    Newcomer
    4
    Aug 4, 2007
    Australia
    Australia
    Baught in Australia May 2018, running sx os definetly not mariko
     

    Attached Files:

    gamesquest1 likes this.
  14. ReDEyeDz

    ReDEyeDz GBAtemp Regular

    Member
    2
    Dec 10, 2015
    Serbia, Republic of
    So what's the chance of getting a new revision? I'm scared of buying a new switch.
     
  15. subcon959

    subcon959 teh retro

    Member
    13
    Dec 24, 2008
    Small, but will exponentially increase as time passes.
     
  16. ReDEyeDz

    ReDEyeDz GBAtemp Regular

    Member
    2
    Dec 10, 2015
    Serbia, Republic of
    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?
     
  17. subcon959

    subcon959 teh retro

    Member
    13
    Dec 24, 2008
    Yeah there's a serial number thread somewhere.
     
Quick Reply
Draft saved Draft deleted
Loading...