Hacking Cannot boot SX OS at all with dongle or payload

kromara · Dec 1, 2018

I just purchased and received my SX Pro dongle with the jig and such. I've ensured that the dongle and Switch are charged and that the jig is fully inserted. I used TegraRCM to confirm that I have gotten into RCM when attempting payload. My issue is that when I try to either boot into SX OS through payload or if I use the dongle, I get no response at all. My Switch stays at a black screen until I try to boot it normally, thus getting the official boot screen.

EDIT: When attempting to boot with the SX Pro dongle, it flashes blue and green once and then goes dark.
EDIT2: Firmware 5.1 and Serial XAW1000xxxxxxx (Launch-day Switch)

flatty69 · Dec 1, 2018

what firmware are you on

EmulateLife · Dec 1, 2018

Are you sure you have a hackable Switch by the serial number? You didn't say so it's fair for me to ask.

Edit: nevermind, you got into rcm so it's hackable.

kromara · Dec 1, 2018

I'm currently on firmware 5.1 and I got a launch day Switch. Serial XAW1000xxxxxxx

HellaJvke · Dec 1, 2018

you gotta hold the power button and + volume button until it gets setup then activate it with the license or with wifi

double check your sd card files / try a different firmware of sxos

or you could have a faulty sx device /license
where did you buy it from online? could contact the shipper

kiaghi7 · Dec 1, 2018

If you've already had it loaded in the CFW before then you may simply have to do a hardware reset... particularly if you've done a SD card change or taken it out to add/remove things and put it back in...
press and hold the power button for 10-20 seconds, long seconds, don't rush.
Then plug in the dongle and the controller rail jumper
Then press and hold both the power and volume + buttons at the same time.

kromara · Dec 1, 2018

I've never attempted any kind of CFW on this Switch (or any Switch for that matter). Additionally, I've tried two different SD cards. One is a SanDisk 200GB and the other one I can't recall the manufacturer, but it's a 4GB. I formatted the 200GB on my Switch and it setup an necessary files. From there I added the boot(can't recall the file extension) file to the root (also inside the "Nintendo" folder just to see if that was the issue). The 4GB one I setup as FAT32 and added the boot file. Everything resulted in the same black screen with no SX OS menus at all.

@HellaJvke I can't even get to the option for licenses at all. Just black screen. In the morning I will try a different version of SX OS though.

WiiuGold · Dec 1, 2018

kromara said:
I've never attempted any kind of CFW on this Switch (or any Switch for that matter). Additionally, I've tried two different SD cards. One is a SanDisk 200GB and the other one I can't recall the manufacturer, but it's a 4GB. I formatted the 200GB on my Switch and it setup an necessary files. From there I added the boot(can't recall the file extension) file to the root (also inside the "Nintendo" folder just to see if that was the issue). The 4GB one I setup as FAT32 and added the boot file. Everything resulted in the same black screen with no SX OS menus at all.

@HellaJvke I can't even get to the option for licenses at all. Just black screen. In the morning I will try a different version of SX OS though.

Did u put the boot.dat on the root on ur sdcard
Try a different version like 1.9

kromara · Dec 1, 2018

WiiuGold said:
Did u put the boot.dat on the root on ur sdcard

Yes. Not to be rude, but that is what I said in the message that you quoted.

WiiuGold · Dec 1, 2018

kromara said:
Yes. Not to be rude, but that is what I said in the message that you quoted.

Try different versions

MasterJ360 · Dec 1, 2018

Sound more like the dongle doesn't have power at all. But you claim that you did charge it if everything else fails you'll just have to refund or get it replaced

Scubahood · Dec 1, 2018

MasterJ360 said:
Sound more like the dongle doesn't have power at all. But you claim that you did charge it if everything else fails you'll just have to refund or get it replaced

He's getting the blue flashing light so he must have power

kromara · Dec 1, 2018

I'm not home today and won't be home until late tonight. When I'm home, I'll try a few different other versions of the boot.dat file. Both attempts to access SX OS (inject via PC and through the dongle) were done with the same boot.dat file, so I'm assuming that must be the culprit. The only other thing I could think would be something off about my individual Switch console, but that seems unlikely.

MasterJ360 · Dec 1, 2018

Scubahood said:
He's getting the blue flashing light so he must have power

But even blue flashing light doesn't mean its working properly. The light needs to be only green whether you charge it or using it to boot into sxos. For the sake of process of elimination I kinda wish new users stop using RCM when trying other things for the first time since countless of thread are RCM users who generally end up with more issues booting a simple payload. I'd say stop auto rcm and just boot the payload the normal way if you havent already. The sxos has it own auto rcm option when you actually get into the boot menu

kromara · Dec 2, 2018

MasterJ360 said:
But even blue flashing light doesn't mean its working properly. The light needs to be only green whether you charge it or using it to boot into sxos. For the sake of process of elimination I kinda wish new users stop using RCM when trying other things for the first time since countless of thread are RCM users who generally end up with more issues booting a simple payload. I'd say stop auto rcm and just boot the payload the normal way if you havent already. The sxos has it own auto rcm option when you actually get into the boot menu

I'm pretty sure that I'm not going through any Auto RCM procedures. The only reason I went for RCM in the first place was to attempt to boot into SX OS via PC. I installed the jig and placed the boot.dat file on the root and booted into RCM. The payload says that it injected successfully, but the screen always remain black. At this point, I'm finally home from a long day away from home, so I'm going to try a different version of the SX OS and I'll update here with results.

Scitzo · Dec 2, 2018

kromara said:
I'm pretty sure that I'm not going through any Auto RCM procedures. The only reason I went for RCM in the first place was to attempt to boot into SX OS via PC. I installed the jig and placed the boot.dat file on the root and booted into RCM. The payload says that it injected successfully, but the screen always remain black. At this point, I'm finally home from a long day away from home, so I'm going to try a different version of the SX OS and I'll update here with results.

I apologize immensely if youve already covered this, but i dont feel like reading all of this, because im lazy tonight.

That aside, have you tried booting the payload with a phone injection method, instead of the sx pro? This would be step #1 in my troubleshoot if i had a irksome pro device. This would at least tell you if its a switch issue, or a sx pro issue. If you can boot payload successfuly (for any cfw) with an alternate payload -source- , then you know its your pro giving you the fit.

Self edit: i see you mentioned "booting with pc". Does that mean you tried the payload injection from the pc usb port? If so, have you tried alternate payloads such as hekate?

theguyver · Dec 2, 2018

i had that issue when my switch gave me that back error screen twice. All i got was the blue led when I turned it on afterwards. First time it happend I ended up deleting and redownloading and the boot.dat file and it worked. Second time was worse. It ended up being my memory card was corrupted. Tried another card and it worked. Ended up formatting card. But luckily my saves were backed up with checkpoint. Also, im not sure if other have this issue, but my dongle only works one way. If I connect it the other way I get the blue light. I ended up putting the sticker on the working side.

Hacking Cannot boot SX OS at all with dongle or payload

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Member

Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Active Member

Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum