Hacking OLED V6 Chip Black screen

[hespartan61]

Hello guys! Yesterday I was playing my NS Oled modded (1 month ago) with Instict nx v6 on Tabletop mode when my switch randomly turned off and didn't turn back on, it didn't even show any errors. Then I tried to turn it on and nothing, the chip only flashes red twice, then purple twice and finally white several times. My NS does not start OFW mode or hekate, the only thing I always see is a black screen. I have already measured the points in diode mode, obtaining the following:
A:0.735V
B:2.059V
C:0.740V
D:0.765V
IDK what is happening

Does anyone know what I should do?

 

[Hassal]

Your problem is most likely D0 especially if it ran for a month without issues.

 

[zamastyle]

Check yout RST/B connections. When installed properly it should read within roughly .080 volts of all the rest of the points. It is reading way too high.

 

[hespartan61]

Well, I desoldered, changed and cleaned the D0 and RST cables and it didn't work, the console remains the same with the black screen
Also i reflowed the eMMC
And i still have 2.059V on B point while the sthetix v6 installation video shows 2.9V on B

 

[Hassal]

What error are you getting when you lift the chip? No sign of life? Something on the board may have shorted.

 

[hespartan61]

What error are you getting when you lift the chip? No sign of life? Something on the board may have shorted.

The chip only flashes red twice, then purple twice and finally white several times.
I disconnected the two flex cables and rst cable from the chip to start in OFW but nothing happened, just the same black screen
But if i connect my oled to PC, tegra RCM recognizes my switch as RCM mode

 

[Hayato213]

The chip only flashes red twice, then purple twice and finally white several times.
I disconnected the two flex cables and rst cable from the chip to start in OFW but nothing happened, just the same black screen
But if i connect my oled to PC, tegra RCM recognizes my switch as RCM mode

Perhaps this might help you.

 

[Hassal]

For that to have any meaning the console must boot normally when lifting the modchip otherwise error signals will not help much if the console is dead.

 

[Phantomas77]

Well, I desoldered, changed and cleaned the D0 and RST cables and it didn't work, the console remains the same with the black screen
Also i reflowed the eMMC
And i still have 2.059V on B point while the sthetix v6 installation video shows 2.9V on B

Did you desolder as well the flex/MOSFET from SoC and without the chip you're still getting black screen?

 

[hespartan61]

Did you desolder as well the flex/MOSFET from SoC and without the chip you're still getting black screen?

I didnt try to desolder the SOC flex, I just tried disconnecting them from the chip.
I saw a post where they mentioned that the chip could be connected to the PC via USB serial and that through commands the chip would diagnose the connections and I tried it.
The chip printed this:
[2023-11-23 17:55:36.568]# RECV ASCII> > d # Diagnosing... [2023-11-23 17:55:37.315]# RECV ASCII> # Diagnose report: Device type: Lite adc: 1069 (flag 3000) adc: 1065 (flag 0) adc: 1068 (flag 0) adc: 1065 (flag 0) adc: 1065 (flag 0) adc: 1065 (flag 0) adc: 1069 (flag 0) adc: 1065 (flag 0) adc: 1069 (flag 0) adc: 1058 (flag 0) adc: 1065 (flag 0) adc: 1068 (flag 0) adc: 1065 (flag 0) adc: 1067 (flag 0) adc: 1068 (flag 0) adc: 1064 (flag 0) adc: 1068 (flag 0) adc: 1069 (flag 0) adc: 1068 (flag 0) adc: 1066 (flag 0) adc: 1069 (flag 0) adc: 1065 (flag 0) adc: 1064 (flag 0) [2023-11-23 17:55:37.642]# RECV ASCII> adc: 1066 (flag 0) adc: 1065 (flag 0) adc: 1066 (flag 0) adc: 1064 (flag 0) adc: 1066 (flag 0) adc: 1068 (flag 0) adc: 1067 (flag 0) adc: 1069 (flag 0) adc: 1063 (flag 0) adc: 1064 (flag 2000) [2023-11-23 17:55:41.773]# RECV ASCII> mmc init failed: BAD00111 (ERR_MMC_SEND_CID_FAILED) flash_payload() complete; actual blocks written: 0 # Status: BAD00111 (ERR_MMC_SEND_CID_FAILED) Glitching started [2023-11-23 17:55:41.946]# RECV ASCII> glitch info: [845, 120, 0] {no comms} 04 03 [2023-11-23 17:55:42.119]# RECV ASCII> glitch info: [845, 120, 1] {no comms} 04 03 [2023-11-23 17:55:42.289]# RECV ASCII> glitch info: [845, 120, 2] {no comms} 04 03 [2023-11-23 17:55:42.459]# RECV ASCII> glitch info: [845, 120, 3] {no comms} 04 03 [2023-11-23 17:55:42.632]# RECV ASCII> glitch info: [845, 120, 0] {no comms} 04 03 [2023-11-23 17:55:42.801]# RECV ASCII> glitch info: [845, 120, 1] {no comms} 04 03 [2023-11-23 17:55:42.970]# RECV ASCII> glitch info: [845, 120, 2] {no comms} 04 03 [2023-11-23 17:55:43.143]# RECV ASCII> glitch info: [845, 120, 3] {no comms} 04 03 Done. Glitcher fatal: no MMC CLK observed # Diagnose status: BAD00108 (ERR_GLITCH_NO_EMMC_COMM)

So does it mean that my EMMC is damaged or corrupted?

 

[juanvlc]

NO_EMMC_COMM
Recheck all your points

 

[Hassal]

I didnt try to desolder the SOC flex, I just tried disconnecting them from the chip.
I saw a post where they mentioned that the chip could be connected to the PC via USB serial and that through commands the chip would diagnose the connections and I tried it.
The chip printed this:
[2023-11-23 17:55:36.568]# RECV ASCII> > d # Diagnosing... [2023-11-23 17:55:37.315]# RECV ASCII> # Diagnose report: Device type: Lite adc: 1069 (flag 3000) adc: 1065 (flag 0) adc: 1068 (flag 0) adc: 1065 (flag 0) adc: 1065 (flag 0) adc: 1065 (flag 0) adc: 1069 (flag 0) adc: 1065 (flag 0) adc: 1069 (flag 0) adc: 1058 (flag 0) adc: 1065 (flag 0) adc: 1068 (flag 0) adc: 1065 (flag 0) adc: 1067 (flag 0) adc: 1068 (flag 0) adc: 1064 (flag 0) adc: 1068 (flag 0) adc: 1069 (flag 0) adc: 1068 (flag 0) adc: 1066 (flag 0) adc: 1069 (flag 0) adc: 1065 (flag 0) adc: 1064 (flag 0) [2023-11-23 17:55:37.642]# RECV ASCII> adc: 1066 (flag 0) adc: 1065 (flag 0) adc: 1066 (flag 0) adc: 1064 (flag 0) adc: 1066 (flag 0) adc: 1068 (flag 0) adc: 1067 (flag 0) adc: 1069 (flag 0) adc: 1063 (flag 0) adc: 1064 (flag 2000) [2023-11-23 17:55:41.773]# RECV ASCII> mmc init failed: BAD00111 (ERR_MMC_SEND_CID_FAILED) flash_payload() complete; actual blocks written: 0 # Status: BAD00111 (ERR_MMC_SEND_CID_FAILED) Glitching started [2023-11-23 17:55:41.946]# RECV ASCII> glitch info: [845, 120, 0] {no comms} 04 03 [2023-11-23 17:55:42.119]# RECV ASCII> glitch info: [845, 120, 1] {no comms} 04 03 [2023-11-23 17:55:42.289]# RECV ASCII> glitch info: [845, 120, 2] {no comms} 04 03 [2023-11-23 17:55:42.459]# RECV ASCII> glitch info: [845, 120, 3] {no comms} 04 03 [2023-11-23 17:55:42.632]# RECV ASCII> glitch info: [845, 120, 0] {no comms} 04 03 [2023-11-23 17:55:42.801]# RECV ASCII> glitch info: [845, 120, 1] {no comms} 04 03 [2023-11-23 17:55:42.970]# RECV ASCII> glitch info: [845, 120, 2] {no comms} 04 03 [2023-11-23 17:55:43.143]# RECV ASCII> glitch info: [845, 120, 3] {no comms} 04 03 Done. Glitcher fatal: no MMC CLK observed # Diagnose status: BAD00108 (ERR_GLITCH_NO_EMMC_COMM)

So does it mean that my EMMC is damaged or corrupted?

Well your diagnose says your CLK is broken. I guess that's the reason why your console isn't responding, you have to reball the eMMC or just reflow until the chip is seated properly.

 

[hespartan61]

Well your diagnose says your CLK is broken. I guess that's the reason why your console isn't responding, you have to reball the eMMC or just reflow until the chip is seated properly.

It worked! My OLED is alive again. I reflowed the emmc again but this time at 160-400°C while slightly moving the chip with the tweezers and putting a little pressure on it.

Thank you all for taking the time to respond and help me .

 

[eddz]

I'm having similar issues with my Instinct-NX v6 (black new) in an OLED NS.
When you reflowed the eMMC, what do you mean 160-400C? Did you start at 160C and build up the temp? How long did you do it for?

My debug info is shows:

glitch info: [845, 120, 3] {no comms} 04 00
Done.
Glitcher fatal: no MMC CLK observed


The D (CLK) point and C (DAT0) points are reading within spec using the multimeter (both around 0.600v). However, when I turn the switch on I get OL for D point. When switch is off I get 0.608v again.

My screen isn't turning on at all. Is it supposed to boot to OFW if I don't have the chip connected to the two flex cables (and RST disconnected too)

 

[zamastyle]

I'm having similar issues with my Instinct-NX v6 (black new) in an OLED NS.
When you reflowed the eMMC, what do you mean 160-400C? Did you start at 160C and build up the temp? How long did you do it for?

My debug info is shows:

glitch info: [845, 120, 3] {no comms} 04 00
Done.
Glitcher fatal: no MMC CLK observed


The D (CLK) point and C (DAT0) points are reading within spec using the multimeter (both around 0.600v). However, when I turn the switch on I get OL for D point. When switch is off I get 0.608v again.

My screen isn't turning on at all. Is it supposed to boot to OFW if I don't have the chip connected to the two flex cables (and RST disconnected too)

If all the soldering is done properly with no shorts or bridges, then removing the flex pcbs from the chip should let it boot normally. If it doesnt, then you either have a soldering short or a damaged component

 

[Hassal]

I'm having similar issues with my Instinct-NX v6 (black new) in an OLED NS.
When you reflowed the eMMC, what do you mean 160-400C? Did you start at 160C and build up the temp? How long did you do it for?

My debug info is shows:

glitch info: [845, 120, 3] {no comms} 04 00
Done.
Glitcher fatal: no MMC CLK observed


The D (CLK) point and C (DAT0) points are reading within spec using the multimeter (both around 0.600v). However, when I turn the switch on I get OL for D point. When switch is off I get 0.608v again.

My screen isn't turning on at all. Is it supposed to boot to OFW if I don't have the chip connected to the two flex cables (and RST disconnected too)

Did you reflow the eMMC? If not you must have broken your via CLK. The CLK is a straight path connecting eMMC to SoC.

 

[eddz]

Did you reflow the eMMC? If not you must have broken your via CLK. The CLK is a straight path connecting eMMC to SoC.

I didn't reflow the eMMC. I didn't think it was necessary anymore. When installing the small orange dat0 connector I slightly tinned the point and slid it under the eMMC and anchored it. Tested it and was a little over 0.400v from memory. I'll test it again when I pull apart the NS today.

 

[hespartan61]

I'm having similar issues with my Instinct-NX v6 (black new) in an OLED NS.
When you reflowed the eMMC, what do you mean 160-400C? Did you start at 160C and build up the temp? How long did you do it for?

My debug info is shows:

glitch info: [845, 120, 3] {no comms} 04 00
Done.
Glitcher fatal: no MMC CLK observed


The D (CLK) point and C (DAT0) points are reading within spec using the multimeter (both around 0.600v). However, when I turn the switch on I get OL for D point. When switch is off I get 0.608v again.

My screen isn't turning on at all. Is it supposed to boot to OFW if I don't have the chip connected to the two flex cables (and RST disconnected too)

I reflowed my emmc with my heat gun raising the temperature every 1 min and used the following temperatures:
>160°C 1 minute
>250°C 1 minute
>360°C 1 minute
>400°C 1 minute

When my OLED was alive again. I noticed that the space in the emmc was almost full and I don't have anything installed on it, days later it died again with a black screen. Probably my nand was corrupt, but there is no problem since I have a copy of the emmc and if it doesn't work I plan to follow the guide of sthetix "DO A SYSTEM RESTORE: UNLOCK THE NSW"

 

[eddz]

I reflowed my emmc with my heat gun raising the temperature every 1 min and used the following temperatures:
>160°C 1 minute
>250°C 1 minute
>360°C 1 minute
>400°C 1 minute

When my OLED was alive again. I noticed that the space in the emmc was almost full and I don't have anything installed on it, days later it died again with a black screen. Probably my nand was corrupt, but there is no problem since I have a copy of the emmc and if it doesn't work I plan to follow the guide of sthetix "DO A SYSTEM RESTORE: UNLOCK THE NSW"

Thanks for that. I've reflowed the eMMC using your tips (among many other things that I will explain in more depth in the main Instinct-NX thread - https://gbatemp.net/threads/instinct-nx-chip.628676/page-20) and the switch is working again!! Phew! Thanks for your help.

 

[hespartan61]

Thanks for that. I've reflowed the eMMC using your tips (among many other things that I will explain in more depth in the main Instinct-NX thread - https://gbatemp.net/threads/instinct-nx-chip.628676/page-20) and the switch is working again!! Phew! Thanks for your help.

I suggest you make a copy of your emmc and prod.keys using hekate and lockpick in case it fails again in the future.

Post automatically merged: Dec 6, 2023