So the background to this is… got a Switch that had water damage so wasn’t turning on, I can’t recall what the voltage and amps was before I opened it. There was a bit of corrosion but not a huge amount. Cleaned the boards/connecters with IPA, nice and clean, tested the chips and caps and no continuity issues. Put it all back together and tested it, still not turning on, power reading was 5v 46amps.
Pulled it apart and cleaned it a few more times but same result. Then I saw one of Steves videos where he had the 8 switches, liquid damage and and similar power readings. He tested the CPU and was getting continuity issues. I tested the same and I seem to have the exact same issues, that is if I have black probe on the USB port and red on the caps, if I put red probe on USB port and black on caps then no continuity issue, is this normal?
Now I have seen somewhere that sometimes these caps under the CPU can test as shorted but are not really and therefore do a diode test which I did and it comes back as around 0.04.
What is also confusing me is that sometimes my PC is recognising the Switch, it will come up as unknown APX device, used ZADiag to install the driver and then used TegraRCMGUI to be able to install a payload and it did it successfully! Is this possible if the CPU is shorted?
Can you highlight in an image the cap you were measuring as shorted and also provide the resistance to ground also
This is rarely a memory issue and the Switch doesn’t have a “Rom” but it does have an EMMC with internal nand, in order for you to identify if this is the issue easily the console would have to be unpatched.
So I get no continuity issue on the SYS Rail. If I measure resistance, I’m getting just 1 on both sides measuring at 200 Ohms, I get 0.952 if I change it to 2k Ohms.
Also, it was recognised by PC today and I did a Payload injection and this is the output
RCM Device detected
Invoking TegraRcmSmash.exe with args : “C:\Users\Downloads\Switch\hekate_ctcaer_5.7.2.bin”
TegraRcmSmash (32bit) 1.2.1-3 by rajkosto
Opened USB device path \?\usb#vid_0955&pid_7321#8&1e054ac&0&3#{2157a238-de1e-4121-b9be-ceb2d5ca4a45}
RCM Device with id C083FE09000000180873306401101062 initialized successfully!
Uploading payload (mezzo size: 92, user size: 106917, total size: 173133, total padded size: 176128)…
Smashing the stack!
Smashed the stack with a 0x7000 byte SETUP request!
Payload successfully injected
I think your meter is playing silly buggers with you, I think somebody else had this same issue as you and it turned out it was because the meter was truly terrible and was displaying a “1” to indicate it’s limit (maybe it’s an “L”)… such bad design.
Can you take the readings on blue, red, yellow and purple again with your meter in the 20K position?
Good news, your switch is unpatched , you should be seeing something on the display following
icbw but I think there was a version of Hekate which wouldn’t boot into text only mode without the files on the SD… not sure if the newer versions are like this as I haven’t used it in a while so might be worth trying a payload such as Biskeydump
You might also want to try disconnecting the EMMCModule (be sure to disconnect battery/power prior to removing this)
don’t worry about fast charging for now, we just want to verify if payloads will run and display first
, you should be seeing something on the display following
