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

  • Thread starter Thread starter Picooz
  • Start date Start date
  • Views Views 69,165
  • Replies Replies 136
This is fascinating, although not too surprising. I guess with the release of SX OS Ninty might have started releasing these new revisions. Very interested to see if they're using the T214 SoC, or if they found another way to prevent the payload from being launched via RCM.

EDIT: Looks like it's an updated/patched version of the T210. I wonder why they chose to ship them with 4.1, though? Seems an odd choice, considering it's still vulnerable to softhax.

Very glad I have two OG units that are both exploitable, one that's completely virgin/legit and one that's not. Maybe when the "New Switch XL Hyper Championship Limited Edition" comes out I'll sell my legit one for some profit.

And to think people gave me a hard time for buying a 2nd Switch. Who's stupid now?
 
Last edited by castdreams,
  • Like
Reactions: NoNAND
All they had to do was update the ROM code and essentially flash any future units with that to fix the fusee exploit. It's not surprising they're appearing now. Also probably why stock levels have dropped off in the last month or so by the looks of things. Reduce production down release updated units ramp production again.
 
Last edited by andijames,
Hi I get a similar problem in rcm that sx pro doesn't recognize my sd card and boot failed with a boot.dat? screen. I have tried many different ways to boot my sx pro in rcm, but all failed. l post it here to see if the same RCM problem.
Bought date: May 28.
Initial version:4.1.0, now have updated to 5.1.0.
Model: 2018 HAC-S-JXE-C3
SN:XAJ7003767xxxx
 

Attachments

  • IMG_2235.JPG
    IMG_2235.JPG
    182.6 KB · Views: 543
  • IMG_2405.JPG
    IMG_2405.JPG
    1.4 MB · Views: 557
  • Like
Reactions: comput3rus3r
Hi I get a similar problem in rcm that sx pro doesn't recognize my sd card and boot failed with a boot.dat? screen. I have tried many different ways to boot my sx pro in rcm, but all failed. l post it here to see if the same RCM problem.
Bought date: May 28.
Initial version:4.1.0, now have updated to 5.1.0.
Model: 2018 HAC-S-JXE-C3
SN:XAJ7003767xxxx

Can you give it another try with a different micro sd card and putting the boot.dat inside? Also, try formatting it again just in case, it seems like the micro sd is the thing that's giving you a hard time, not the sx os itself.
 
  • Like
Reactions: comput3rus3r
Hi I get a similar problem in rcm that sx pro doesn't recognize my sd card and boot failed with a boot.dat? screen. I have tried many different ways to boot my sx pro in rcm, but all failed. l post it here to see if the same RCM problem.
Bought date: May 28.
Initial version:4.1.0, now have updated to 5.1.0.
Model: 2018 HAC-S-JXE-C3
SN:XAJ7003767xxxx
that's a different issue, the payload is booting on your system, its just not reading the boot.dat file from the SD, try reformatting your card with this
https://fat32-format.en.softonic.com/
 
Last edited by gamesquest1,
  • Like
Reactions: cawalls_deep
Can you proof that showing us a short video?
I have one too, runs payload just fine.
The ones that do not were patched through ipatches rather than a new CPU revision so you won't be able to tell unless you try the fusee gelee exploit.

--------------------- MERGED ---------------------------

Not in Japan anymore.

Very strange that RCM is recognized but not the payload.
Did you place the payload on the microsd as well ?

--------------------- MERGED ---------------------------


No.
Because your 4.1 model is receiving payload (so do mine), it doesn't mean that they don't know what they are doing.
It's not strange at all, they still need RCM for legit factory/servicing operations. Nintendo has the private keys required to sign a valid BCT/Bootloader, they don't need to trigger an overflow using the USB stack bug.
 
Factories have different timetables, one factory can have the updated patch and another not right away. Time, date, year, doesn't matter. Source matters.

And if they are shipping with 4.x, then they're not even 'new' units. These have been in retail backchannels/shipping crates for some time.

Not in Japan anymore.

Very strange that RCM is recognized but not the payload.
Did you place the payload on the microsd as well ?

--------------------- MERGED ---------------------------

No.
Because your 4.1 model is receiving payload (so do mine), it doesn't mean that they don't know what they are doing.

They're not going to patch out RCM. That's how they repair your system.
 
XAJ70043979XXX
XAJ400490XXXXX

- if this is to go by, it's from two different factories. Much intresting, so far the XAJ70 is the culprites?

switch
2018 HAC-S-JXE-C3
SN XAJ700392XXXX

tried hekate... and thanks god its working..... so nintendo started patching around and above XAJ7004.....
 
  • Like
Reactions: gnilwob
switch
2018 HAC-S-JXE-C3
SN XAJ700392XXXX

tried hekate... and thanks god its working..... so nintendo started patching around and above XAJ7004.....
Hmm Intresting. I wonder if the 3 and 4 means the month? then the rest is a serial?
 
We just need the latest switch serial number that is still hackable. That can be the cut off for the time being
 
that's a different issue, the payload is booting on your system, its just not reading the boot.dat file from the SD, try reformatting your card with this
https://fat32-format.en.softonic.com/
that's not the problem. I created that thread he posted and nothing works on that switch. I have a second switch and the sd cards work fine to load the payloads. It seems some ipatches just block the payloads access to the micro sd card.
 
Last edited by comput3rus3r,
We just need the latest switch serial number that is still hackable. That can be the cut off for the time being
XAJ7003XXXXXX are probably the last unpached units and XAJ7004XXXXXXX are the patched ones. But it is all still just speculation.

@Picooz
Could you share your serial with us?
 
Guys, I bought a Switch today. It’s a mario odyssey bundle.
2018 HAC-S-JXE-C3
XAJ1001xxx
Version 4.1
I haven’t tried it yet since i don’t have sx pro yet. All the switch in the store that i bought it from has 2018 HAC-S-JXE-C3 and XAJ7003 and XAJ7004. Mine’s the only one that’s different. I wonder if mine is still safe.
 
I haven’t tried it yet since i don’t have sx pro yet. All the switch in the store that i bought it from has 2018 HAC-S-JXE-C3 and XAJ7003 and XAJ7004. Mine’s the only one that’s different. I wonder if mine is still safe.
A HAC-S-JXE-C3 XAJ7003 would be probably the best option. Yours is probably from a different factory/production line than the others. What are the next two digits after the 1001?

I haven’t tried it yet since i don’t have sx pro yet
You don't have to to check your unit. All you need is a piece of wire, a paperclip or a tinfoil and a usb-c to usb-a cable and a pc.
 
A HAC-S-JXE-C3 XAJ7003 would be probably the best option. Yours is probably from a different factory/production line than the others. What are the next two digits after the 1001?


You don't have to to check your unit. All you need is a piece of wire, a paperclip or a tinfoil and a usb-c to usb-a cable and a pc.
I did not get the xaj7 because they said its the culprit. It’s XAJ100172
 
Because those units came with Horizon 4.1, they actually can't be T214 based, right? So it's still T210 just with an updated bootROM?

BTW, whats the difference between a T210 and a T214? New manufacturing process? Higher clocks? Higher mem bandwidth?

It's possible that 4.1 would work on the T214, but not take advantage of any newer features. Like PS4 Pro shipped with 3.70, but needed 4.05 for boost mode.

But it's also possible these are just T210 units. I don't think anyone has seen a T214, it's a special part for Nintendo. In light of recent events they might change it.

And if they are shipping with 4.x, then they're not even 'new' units. These have been in retail backchannels/shipping crates for some time.

The channels will take a while to empty at this time of year, but also they might not change to 5.0.0 on the day that it's released. So they're as new as you could reasonably expect.
 
The channels will take a while to empty at this time of year, but also they might not change to 5.0.0 on the day that it's released. So they're as new as you could reasonably expect.

That's sort of what I mean, they're "new" for retail but they're not "new" as in they were just freshly minted. They've been sitting around in a depot somewhere for a while.
 

Site & Scene News

Popular threads in this forum