Hardware Switch video in docked mode stops after 30 seconds

[Hannahmanaman]

Hey guys. I have a weird issue with my switch. It works great in handheld mode but when I try to play games docked, it shows video/audio for about 30 seconds to 1 minute before it cuts out and stops working. It still charges just fine and the dock has a solid gree light.

It worked fine before I sent it to a third party repair center because it wouldn't turn on. They said they replaced the IC chips and sent it back. I assume something was botched with the m92T36 replacement but have no idea.

I have tried 2 separate official docs and power cables
Used about 5 other HDMI cables
Cycled through the tv output settings 480,720,1080 all else is default.
I am at a loss here. Any ideas would be very much appreciated. Thanks in advance

 

[Draxzelex]

Have you tried using other televisions?

 

[Donnie-Burger]

Hey guys. I have a weird issue with my switch. It works great in handheld mode but when I try to play games docked, it shows video/audio for about 30 seconds to 1 minute before it cuts out and stops working. It still charges just fine and the dock has a solid gree light.

It worked fine before I sent it to a third party repair center because it wouldn't turn on. They said they replaced the IC chips and sent it back. I assume something was botched with the m92T36 replacement but have no idea.

I have tried 2 separate official docs and power cables
Used about 5 other HDMI cables
Cycled through the tv output settings 480,720,1080 all else is default.
I am at a loss here. Any ideas would be very much appreciated. Thanks in advance

Seen this before with a Switch that had dry to no paste left. To me thats a failed repair as it should dock normally.

Can be
m9, p13, bq, usbc or see picture of M6f9 - circled in red (Some motherboard revision have this part under a different part #) - Oh yeah check filters as well. Removing them can actually fix some issues. V1 early boards mostly had these filters.

 

[Hannahmanaman]

Thank you so much! I have an update but it brings more problems unfortunately. I ended up getting referred to another switch repair service that seemed much better. It turns out the previous person botched the M92T36 & said that they melted the usb port while soldering BQ24193.

The new person replaced a damaged usb port, M92T36, left joy con FPC connector, and pi3usb. Sent pictures and seemed to do a great job. The problem now is that It boots fine in both ofw and cfw and I can play around in the system menus all day with no problem, but whenever I boot any game in docked mode, it throws error code Error code 2101-0001. It also plays for about 30 mins or so in handheld mode but eventually ends up throwing out the same error

I have tried the following since getting it back:
used 3 different (fat32 formatted) SD cards in case it was a SD card corruption issue

-Did a system wipe in case something was funky there

- Did a full NAND restore back to somewhere around 8.0 then updated all back to 13.2 since I read it could be something wrong with something written to the NAND.


-They suggested I am using a "killer charger" and it probably messed up their M92T36, however I've only used the official one it came with. They rebottled with if it isn't that, it must be a bad SoC and I can send it in again at no charge, but if it is the SOC then im SOL.

Is there anything else you can think of before I send it back? Do you think it could be overheating or something? It just seems weird that I will play the games but not for very long.

 

[Donnie-Burger]

Thank you so much! I have an update but it brings more problems unfortunately. I ended up getting referred to another switch repair service that seemed much better. It turns out the previous person botched the M92T36 & said that they melted the usb port while soldering BQ24193.

The new person replaced a damaged usb port, M92T36, left joy con FPC connector, and pi3usb. Sent pictures and seemed to do a great job. The problem now is that It boots fine in both ofw and cfw and I can play around in the system menus all day with no problem, but whenever I boot any game in docked mode, it throws error code Error code 2101-0001. It also plays for about 30 mins or so in handheld mode but eventually ends up throwing out the same error

I have tried the following since getting it back:
used 3 different (fat32 formatted) SD cards in case it was a SD card corruption issue

-Did a system wipe in case something was funky there

- Did a full NAND restore back to somewhere around 8.0 then updated all back to 13.2 since I read it could be something wrong with something written to the NAND.


-They suggested I am using a "killer charger" and it probably messed up their M92T36, however I've only used the official one it came with. They rebottled with if it isn't that, it must be a bad SoC and I can send it in again at no charge, but if it is the SOC then im SOL.

Is there anything else you can think of before I send it back? Do you think it could be overheating or something? It just seems weird that I will play the games but not for very long.

Error code 2101-0001 is a faulty M92T36. They don't always work brand new.

 

[Hannahmanaman]

Error code 2101-0001 is a faulty M92T36. They don't always work brand new.

Thanks Donnie! I will stop messing with it and send it back to them Will report back when I get it back.

 

[MaxiTheFox]

im having a similar issue the video/audio glitches fot about 30 seconds then stops think its bc ive dropped it so many times

 

[Donnie-Burger]

Thanks Donnie! I will stop messing with it and send it back to them Will report back when I get it back.

No problem. After over 1,000 switch repairs I had to start writing down in my notes error code / repair fixes.

 

[Hannahmanaman]

Hey Donnie, the repair shop just got my switch back. I sent my charger with it and asked them to test it as well. So far they have only tested the charger but sent the message below. Does that sound right? From what I understand, the switch charger is rated at 5v.

Hi, hello, I have received your console, I just checked your charger, your cc1/cc2 voltage is 5.0v, the normal voltage should be <=3.3v, I tested all my 3 chargers, all the cc1/cc2 are <= 3.3v. so I think you need to buy a new charger.

 

[Donnie-Burger]

Hey Donnie, the repair shop just got my switch back. I sent my charger with it and asked them to test it as well. So far they have only tested the charger but sent the message below. Does that sound right? From what I understand, the switch charger is rated at 5v.

Hi, hello, I have received your console, I just checked your charger, your cc1/cc2 voltage is 5.0v, the normal voltage should be <=3.3v, I tested all my 3 chargers, all the cc1/cc2 are <= 3.3v. so I think you need to buy a new charger.

Its possible. Replace m9, replace charger. No issues then most likely.

 

[Hannahmanaman]

Welp..I think I'm going to throw in the towel on this one... I Got the message below from the repair shop.. it booted and functioned in the system menu all day before I sent it out..


I just opened and checked it, the M92T36 is good, no damaged, the diode value of all the pins are normal, it can charge. But when I press power button, the Soc can boot up, but the working current is wrong, it stuck at about 220mA. So this situation is nothing about the charge issue, we say it is Emmc issue or bricked console.

the first photo is it's working current, it stuck at 220mA, it means Soc can't read data from Emmc, so it can't do next step, the screen is black, can't show logo.
the second photo is charge current, it can charge, but the screen didn't show charging logo.

Followed a few minutes by


o, my God, you do wrong, you didn't power off when it was shipped, it must be damaged by weather, it come from the hot area to our cold area, dew can condense inside the console, but the console is still runing, so it same with dropping it in water!

Then after saying that it was indeed powers off and that the temperature change is not that dramatic and that it is colder here now then when it was sent the 1st time ..

Sorry, I'm busy today, I will check it later, I will check the Emmc, if Emmc is good, we usually need to rebuild it, if Emmc is dead, it is unrepairable

 

[Donnie-Burger]

Welp..I think I'm going to throw in the towel on this one... I Got the message below from the repair shop.. it booted and functioned in the system menu all day before I sent it out..


I just opened and checked it, the M92T36 is good, no damaged, the diode value of all the pins are normal, it can charge. But when I press power button, the Soc can boot up, but the working current is wrong, it stuck at about 220mA. So this situation is nothing about the charge issue, we say it is Emmc issue or bricked console.

the first photo is it's working current, it stuck at 220mA, it means Soc can't read data from Emmc, so it can't do next step, the screen is black, can't show logo.
the second photo is charge current, it can charge, but the screen didn't show charging logo.

Followed a few minutes by


o, my God, you do wrong, you didn't power off when it was shipped, it must be damaged by weather, it come from the hot area to our cold area, dew can condense inside the console, but the console is still runing, so it same with dropping it in water!

Then after saying that it was indeed powers off and that the temperature change is not that dramatic and that it is colder here now then when it was sent the 1st time ..

Sorry, I'm busy today, I will check it later, I will check the Emmc, if Emmc is good, we usually need to rebuild it, if Emmc is dead, it is unrepairable

M9s can be bad with no shorts.

 

[Hannahmanaman]

M9s can be bad with no shorts.

Thanks again. Here is a new update on this one. I was refunded by the repair shop as the switch no longer boots. They blame damage during shipping or water damage from the change in climate. I tried to plug it into my PC to see if it gets recognized by Tegrarcm. It does not and device manager shows "Unknown USB Device (Device Descriptor Request Failed)"

They took the following pictures with explanations. Is my switch a lost cause at this point?

Thank you

1st message
"
just opened and checked it, the M92T36 is good, no damaged, the diode value of all the pins are normal, it can charge. But when I press power button, the Soc can boot up, but the working current is wrong, it stuck at about 220mA. So this situation is nothing about the charge issue, we say it is Emmc issue or "brick" console.

the first photo is it's working current, it stuck at 220mA, it means Soc can't read data from Emmc, so it can't do next step, the screen is black, can't show logo.
the second photo is charge current, it can charge, but the screen didn't show charging logo."

2nd message
"
Hi, I just did more tests for your console, I want to get the Emmc information by Hekate, but I find it can't come in the RCM mode, my RCMloader doesn't work, I connect it with my computer, it also can't be connected. Then I checked the usb signal D+, D- signal, the D+ is normal, the diode value is about 0.740v , but D- is disconnected, we can't get its diode value, that means we can't communicate with Soc by usb signal.

This situation is very rare, there are 2 possibilities, one is the Soc D- signal pot is detached from motherboard, so we can't test the diode value. another is the Soc was damaged, so we can't get the D- value.

Unfortunately, I have no idea for this situation, because it can't connect to the computer, I can't do anything .

the first photo shows it can't connect my computer, the second is the D- signal, the last is the D+ signal."

 

[Donnie-Burger]

Thanks again. Here is a new update on this one. I was refunded by the repair shop as the switch no longer boots. They blame damage during shipping or water damage from the change in climate. I tried to plug it into my PC to see if it gets recognized by Tegrarcm. It does not and device manager shows "Unknown USB Device (Device Descriptor Request Failed)"

They took the following pictures with explanations. Is my switch a lost cause at this point?

Thank you

1st message
"
just opened and checked it, the M92T36 is good, no damaged, the diode value of all the pins are normal, it can charge. But when I press power button, the Soc can boot up, but the working current is wrong, it stuck at about 220mA. So this situation is nothing about the charge issue, we say it is Emmc issue or "brick" console.

the first photo is it's working current, it stuck at 220mA, it means Soc can't read data from Emmc, so it can't do next step, the screen is black, can't show logo.
the second photo is charge current, it can charge, but the screen didn't show charging logo."

2nd message
"
Hi, I just did more tests for your console, I want to get the Emmc information by Hekate, but I find it can't come in the RCM mode, my RCMloader doesn't work, I connect it with my computer, it also can't be connected. Then I checked the usb signal D+, D- signal, the D+ is normal, the diode value is about 0.740v , but D- is disconnected, we can't get its diode value, that means we can't communicate with Soc by usb signal.

This situation is very rare, there are 2 possibilities, one is the Soc D- signal pot is detached from motherboard, so we can't test the diode value. another is the Soc was damaged, so we can't get the D- value.

Unfortunately, I have no idea for this situation, because it can't connect to the computer, I can't do anything .

the first photo shows it can't connect my computer, the second is the D- signal, the last is the D+ signal."

I had a switch in just like this - Had to write nand to a new module like so.

Take off 32gb module then use jig to trigger rcm with usb cable (32gb Module plugged 1st in wouldnt allow this)- Plug 32gb back in then load Hekate. Use Hekate to dump nand and boot 0/1. Write nand to new 32gb. After this switch only worked with rcm on.

Note: Other switches that behaved like this were fixed with a 32gb reflow or reball.

You said you were in game then getting the error. Did they ever replace m9 again after this?

 

[Hannahmanaman]

I had a switch in just like this - Had to write nand to a new module like so.

Take off 32gb module then use jig to trigger rcm with usb cable (32gb Module plugged 1st in wouldnt allow this)- Plug 32gb back in then load Hekate. Use Hekate to dump nand and boot 0/1. Write nand to new 32gb. After this switch only worked with rcm on.

Note: Other switches that behaved like this were fixed with a 32gb reflow or reball.

You said you were in game then getting the error. Did they ever replace m9 again after this?

Thank you. a few more questions.
1. This means that would need to buy a new emmc right?
2.Would I be able to write my back up nand to the new Emmc?

Correct I was getting the error in game, they did not replace the M9 because they did not believe that it was the issue

 

[Donnie-Burger]

Thank you. a few more questions.
1. This means that would need to buy a new emmc right?
2.Would I be able to write my back up nand to the new Emmc?

Correct I was getting the error in game, they did not replace the M9 because they did not believe that it was the issue

I would test to see if rcm triggers with usb cable+jig and no 32gb module plugged in.

 

[Hannahmanaman]

I would test to see if rcm triggers with usb cable+jig and no 32gb module plugged in.

Just gave it a shot. No luck there. Still a blank screen, no RCM detected. PC still chimes but gives USB device descriptor request failed.

 

[Donnie-Burger]

Just gave it a shot. No luck there. Still a blank screen, no RCM detected. PC still chimes but gives USB device descriptor request failed.

Do you hear usb sound with jig + cable + no 32GB? I can take a look if wanted.

 

[Hannahmanaman]

Do you hear usb sound with jig + cable + no 32GB? I can take a look if wanted.

Yes, the USB sounds on the pc with jig+cable + emmc removed and emmc plugged in. How much would you charge to take a look and if it does need a reball, is that something you do? I am just wondering if it is worth putting more money into this thing or if it would be better to find another unpatched console. Much appreciated