As I say if one of it’s primary rails is shorted then sure, otherwise it’s highly unlikely… the chip is a mux, nothing more, it’s not required for boot etc 
I stripped the switch completely down to barebones board (nothing attached)
Installed and ran TegraRcm;
Plugged USB in with eMMC attached - findings= No Rcm detected
Unplugged, removed eMMC and plugged USB back in -
Findings= Rcm detected
The BSOD has disappeared and now it just won’t display ANYTHING
As mentioned before; this is not my Switch and I am trying to fix it for a friend of the families children, who dropped it down a few steps, but could in fact have been a whole flight of steps.
I am wondering whether to start fresh from the top with fresh trouble shooting.
I will replace the fuel gauge though, just got to purchase one and wait on its delivery… might also order a P13USB and BQ at the same time.
Right, this is pretty typical behaviour on a SoC/joint related fault condition (ruling out fuel gauge) unfortunately.
If you disconnect the EMMC, plug it into the PC, try injecting the Hekate payload and let us no the code TegraRCM spits out 0x… in the log so we can check if it’s patched/unpatched
Save your money, it’s virtually impossible for it to be the P13 at fault, and it’s highly unlikely to be the BQ IC - the only reason I suggested the BQ IC above was the fact there was no charge current with the original battery plugged in so it was a very, very loose chance the BQ could be at fault but it’s so slim
@Severence I mean He can try and still use the parts for other Switches
Since the console got dropped, Maybe the PI3USB isnt making contact at every pin anymore.
@Techie_hobby1
How did you get rif of the blue screen?
Have you already tried reflowing both CPU and RAM?
The solder balls on the switch are relativly week.
Maybe give reflowing the Max ICs a chance
@zyrex
I have never reflowed a cpu before - I think I asked some time ago if I need specialist equipment to do this.
Do I need an IC stencil template as well or can this be achieved without one?
I will order a P13USB chip
Does this need a stencil as well or can this be done without one?
The BSOD seemed to disappear when I removed the LCD ribbon cable, and when I was putting it back I noticed a couple of LCD connectors pins were not seated correctly (causing a short). So I swapped out the connector for a new one, but then @Insomniac had noticed that the new connector was installed correctly and had damaged pins ….and since then has no sign of LCD life.
Okay to make clear:
You can try to reflow the CPU and RAM just by appling hot air on it, until the solder under them melted. With the help of flux which is applied on All sides the solder balls under the Chip will eventually reconnect with the solder pads on the Board.
Sometimes this is enough, other times the Chips need a complete reballing, which means taking it off an put New solder balls onto it.
There are couple of Videos on YouTube where thy reflow the CPU to fix a BSOD.
Please not there is a chance to burn the CPU if you arent know what you doing. Best is to practise this on donor Boards or Having experince with other cpus in the past.
PI3USB is Not a BGA Chip and you can solder it the same way you solder the M92.
The fuel gauge is a BGA, but only has 9 balls and the ones you buy should come pre Balled.
Remove the old Fuel Gauge, then Mix the solder pads on the board with lowmelt or leaded solder, then wick it a away. Then apply only a bit flux, heat it up so it’s in Liquid Form, than put the New fuel gauge in place and heat it with little airflow, since you dont want it to blow away.
It will “Flow into place” when the solder balls have melted.
Again, I recommend watching Videos on this topic. For switch repairs, theCoder and Northridge Fix have good Videos on YouTube.
Reflowing both Max ICs (one South of the CPU, the other is on the other side of the board, North of CPU) is Not really dangerous since they dont need that mich heat and time to melt as the CPU does and can be done in a few Minutes.
Btw, have you checked the usb Port under microscope for bent or broken pins (inside)?
As I say, the P13 IC is simply a Mux IC, it’s not required to boot, charge or anything else - it’s only purpose is dock functionality. The only way this IC would fail is if, the I/O was bridged to one another or one of it’s power rails was abruptly shorted to ground (in which case this IC would drag said rail to ground in failure) regardless of whether the IC was damaged on impact (near impossible, the IC is near buletproof) or if the I/O was not making a connection to the board, it simply wouldn’t make a difference, the Switch can boot without this IC present hope that clears up my reasoning for not wasting any time or money on this one 
I would reccommend you do not do this, especially not as your first try, your more likely to cause more damage more than anything else… besides in heavy impact cases it’s likely there is either going to be joint/pad damage to the board, or a ball has came clear loose below the ram or SoC which a reflow can only make worse.
Blindly reflowing things is not the answer… even in desperation…
If you can confirm the patched/Unpatched status I mentioned above you could potentially rule out the EMMC and fuel gauge and a few other things
1 Like
According to my friends information- they bought this switch brand new a few years ago from a well known store…I am guessing therefore it is not patched
My friends provided some extra information - they tried to hold down the vol + & - and power button to try and reset the switch …and seems they have done this multiple times.
If I am able to get this into Rcm mode could I potentially re-install said software to see if that sorts the Nand maybe… or is this not possible.
@Severence - I have had to pop out for a little bit, once I am back I will inject payload Hekate just to be certain it’s not patched etc…
Whilst we are discussing Rcm mode - is there (and this is probably me having wishful thinking) a payload I can inject into this switch to do a Debug and tell me what is bleeding well wrong with it haha
Unforunatelly there is no way to recreate the NAND if it’s damaged and you dont have a Backup, since it’s married to the CPU.
But if it boots into hekate you can Check the Status of the emmc and battery which will therfor Show if there is a Problem.
Patched or unpatched is just a matter of when the switch was bought, if it was in 2017 or 2018 it’s likely unpatched, later consoles are probably patched.
You can Check it buy looking at the serial number on the bottom housing and Look at this Website
https://suchmememanyskill.github.io/guides/switchserials/
1 Like
Yeah it’s possible to use another NAND with atmosphere / cfw, but not with the Stock ROM.
And reballing the original NAND can help in some cases, but in many not, if the partion itself is corrupted or the Chip itself is damaged
@Severence @zyrex
Is this what you meant??? (see below)
No RCM device detected
RCM Device detected
RCM device disconnected
RCM Device detected
Preset “PAYLOAD_FILE” set to : C:\Program Files (x86)\TegraRcmGUI\favorites\hekate_ctcaer_5.0.0.bin
Invoking TegraRcmSmash.exe with args : “C:\Program Files (x86)\TegraRcmGUI\favorites\hekate_ctcaer_5.0.0.bin”
TegraRcmSmash (32bit) 1.2.1-3 by rajkosto
Opened USB device path \?\usb#vid_0955&pid_7321#7&1f3d457c&0&3#{aa0dbd45-3117-f331-5c49-76bf65225042}
RCM Device with id 0002FF060000001440D6416401101062 initialized successfully!
Uploading payload (mezzo size: 92, user size: 126207, total size: 192423, total padded size: 192512)…
Smashing the stack!
Smashed the stack with a 0x001f byte SETUP request!
Payload successfully injected
RCM device disconnected
RCM Device detected
See this video here, at 7:17
After injecting a payload, in the log output following “smashing the stack” you’ll get a hex code
It would seem though the the code spat out in your case - “0x001f byte SETUP request!” is a bit different to what I’ve seen before… bear with me
do I need to assemble the whole switch before I can get this information? or can I just get do this with the barebones board and no eMMC attached
No, all you need is the board with the battery connected and USB connected. leave the EMMC disconnected so it remains in an RCM state
I’ve searched online and some are putting this code down to either a bug with TegraRCMGUI or an issue with the newer version of Hekate 
not had this issue before myself
Maybe try using the previous version of TegraRCMGui (with the APX driver installed if it isn’t already) and using an older version of the Hekate payload, or just use the Biskeydump payload instead and see if that works
@Techie_hobby1 Try downloading newest hekate, it’s 5.8, you still using old 5.0
https://github.com/CTCaer/hekate/releases/download/v5.8.0/hekate_ctcaer_5.8.0_Nyx_1.3.0.zip
I tried still with the new version of Tegra and updated to new version Hekate and got this now
Smashed the stack with a 0x7000 byte SETUP request!
Payload successfully injected
Also have received delivery of P13, USB, BQ and Fuel Gauge ready to swap out one by one
perfect, the switch is unpatched
So now try with everything hooked up (exl the EMMC) , put the files for Hekate on the SD and inject the Hekate payload, see if you get anything on the display and if you do take some photos of the console info section - with the fuel gauge stats etc
1 Like