Hardware Two switch recognizing the same eMMC??!

tomsek68

Well-Known Member
OP
Newcomer
Joined
May 19, 2018
Messages
46
Trophies
0
Age
22
XP
233
Country
Hungary
I had a LOT of switches to fix recently. I forgot which memory goes in which console... While trying to find the pairs, i've noticed the following things:

eMMC1
  • Unit 1 boots with it
  • Unit 2 shows NINTENDO logo then black screen (Maybe eFuse mismatch?)
eMMC2
  • Unit 2 boots with it
  • Unit 1 black screen, no charging icon
Unit 1 is unpatched
Unit 2 is patched

In my experience a switch won't show the logo unless the console specific data is verified from the eMMC.
How can such a scenario exist?
 
Last edited by tomsek68,

tomsek68

Well-Known Member
OP
Newcomer
Joined
May 19, 2018
Messages
46
Trophies
0
Age
22
XP
233
Country
Hungary
UPADTE: I've found a second unit which shows logo with a different eMMC. Maybe this is normal, and i've overlooked something.

Also: Unit 2 won't boot anymore with its own module. It shows logo with the previously said one.
 
Last edited by tomsek68,

tomsek68

Well-Known Member
OP
Newcomer
Joined
May 19, 2018
Messages
46
Trophies
0
Age
22
XP
233
Country
Hungary
Gosh. Any of the switches I tried to boot with eMMC1 wont boot. Did it burn the eFuses while trying to boot?
 

Testo

Active Member
Newcomer
Joined
Jun 13, 2019
Messages
44
Trophies
0
Age
29
XP
376
Country
Germany
Every eMMC is some kind of married to a console. You will never be able to boot an eMMC outside of the console where it's from
 
  • Like
Reactions: ds34 and FXDX

tomsek68

Well-Known Member
OP
Newcomer
Joined
May 19, 2018
Messages
46
Trophies
0
Age
22
XP
233
Country
Hungary
I know. When i tried to boot the higher version BOOT0/BOOT1 it burned my fuses, so i ended up with the processor containing more burnt eFuses than the eMMC's system boots with.

This is technically the same as if I tried to downgrade a patched unit - no way to boot without fuse check.
 
Last edited by tomsek68,

ZachyCatGames

Well-Known Member
Member
Joined
Jun 19, 2018
Messages
3,398
Trophies
1
Location
Hell
XP
4,209
Country
United States
I had a LOT of switches to fix recently. I forgot which memory goes in which console... While trying to find the pairs, i've noticed the following things:

eMMC1
  • Unit 1 boots with it
  • Unit 2 shows NINTENDO logo then black screen (Maybe eFuse mismatch?)
eMMC2
  • Unit 2 boots with it
  • Unit 1 black screen, no charging icon
Unit 1 is unpatched
Unit 2 is patched

In my experience a switch won't show the logo unless the console specific data is verified from the eMMC.
How can such a scenario exist?
Unit 2 with eMMC1 got upto pkg2 before failing. Which makes sense and is normal since pkg1 (BOOT0) & pkg2 (those bcpkg2 partitions) aren’t encrypted with any console unique keys and do not contain anything console unique that’s important for modern FWs, whereas SYSTEM & everything else is encrypted using console unique keys.
Fuse mismatch is just an immediate black screen upon boot.
 

tomsek68

Well-Known Member
OP
Newcomer
Joined
May 19, 2018
Messages
46
Trophies
0
Age
22
XP
233
Country
Hungary
Try dumping encryption keys and update manually
The bricked switch is patched.

I tried booting an unpatched 8.0.x switch with the 9.2.0 eMMC:
The 9.2.0 eMMC definitely burned the 12th fuse. Verified it with hekate. It booted trough hekate, and I was able to update. This one boots now.

Fuse mismatch is just an immediate black screen upon boot.
I was in a hurry, and did not test Unit 2. My table was a mess, and I mixed it up with another switch.
It shows a black screen with its own eMMC, and Nintendo logo with a 9.2.0 one.
 
Last edited by tomsek68,
  • Like
Reactions: Cyan

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: