Oneplus 3 with display issue, or motherboard? - OnePlus 3 Questions & Answers

Hi all!
My father's Oneplus 3 (A3003, 64gb) died a few days ago while he was waiting for his new oneplus 6 (if only it died after migrating... sigh), and i'm trying to troubleshoot it.
The display went dark after a night, no led, nothing. He plugged it to a computer, and a device called HS-USB Qdloader 9008 appeared in the device manager.
I thought it was bricked, so we followed the unbrick stepps (even the full package).
Nothing happened on the display after reboot, black screen after a short vibration, then a few minutes later another vibration, and so on...
I let it alone for a few days then tried again to see what was happening, and went again with the unbrick process. This time it completed successfully and i was able to see something on the display, but very very dim!
It booted to the stock OOS, then it rebooted right after arriving on the OOBE, and it froze while booting after that.
Again i let it alone for a few hours, and tried again, outside in the cold. This time it "worked", with the very very dim display though, i could barely see what was happening on the screen, but i was able to set it up including wifi and play store, and i could do a benchmark using geekbench successfully (score was on par with other OP3).
I went inside and tried again a few hours later, and it froze right after launching the benchmark, rebooted and froze during boot. Then i could do nothing to make it boot again (while it was warm anyway).
tl;dr : It only "works" when it is cold, and the display is barely readable. I'm thinking it could be the motherboard or the display, but would a display issue cause the reboots when getting warm? Seems weird to me!
i attached pictures of the failing OP3 next to my OP3T to highlight the display issue, the "band" visible on the 1st picture is not visible to the bare eye, only on camera and it "moves", no idea why this happens.
EDIT : i was able to unlock it while it was "working", if it is of any importance...

Blubster said:
Hi all!
My father's Oneplus 3 (A3003, 64gb) died a few days ago while he was waiting for his new oneplus 6 (if only it died after migrating... sigh), and i'm trying to troubleshoot it.
The display went dark after a night, no led, nothing. He plugged it to a computer, and a device called HS-USB Qdloader 9008 appeared in the device manager.
I thought it was bricked, so we followed the unbrick stepps (even the full package).
Nothing happened on the display after reboot, black screen after a short vibration, then a few minutes later another vibration, and so on...
I let it alone for a few days then tried again to see what was happening, and went again with the unbrick process. This time it completed successfully and i was able to see something on the display, but very very dim!
It booted to the stock OOS, then it rebooted right after arriving on the OOBE, and it froze while booting after that.
Again i let it alone for a few hours, and tried again, outside in the cold. This time it "worked", with the very very dim display though, i could barely see what was happening on the screen, but i was able to set it up including wifi and play store, and i could do a benchmark using geekbench successfully (score was on par with other OP3).
I went inside and tried again a few hours later, and it froze right after launching the benchmark, rebooted and froze during boot. Then i could do nothing to make it boot again (while it was warm anyway).
tl;dr : It only "works" when it is cold, and the display is barely readable. I'm thinking it could be the motherboard or the display, but would a display issue cause the reboots when getting warm? Seems weird to me!
i attached pictures of the failing OP3 next to my OP3T to highlight the display issue, the "band" visible on the 1st picture is not visible to the bare eye, only on camera and it "moves", no idea why this happens.
EDIT : i was able to unlock it while it was "working", if it is of any importance...
Click to expand...
Click to collapse
Looks like a Display issue. It is possible that it triggers the booting issue, though I am not sure about the "hot & cold" issue. May be a loose connection. Did it suffer a fall in the past? If you are upto it, check some videos on opening the phone and check and clean the connections. It may help.

tnsmani said:
Looks like a Display issue. It is possible that it triggers the booting issue, though I am not sure about the "hot & cold" issue. May be a loose connection. Did it suffer a fall in the past? If you are upto it, check some videos on opening the phone and check and clean the connections. It may help.
Click to expand...
Click to collapse
Thanks for your answer, i just looked at the requirements to open it, and i need a T2 screwdriver, which i do not have yet, the smallest i have is a T3 unfortunately.
I think it did fall a few times, but no issue right after at least. It may have loosen the connections though, you're right...

Blubster said:
Hi all!
My father's Oneplus 3 (A3003, 64gb) died a few days ago while he was waiting for his new oneplus 6 (if only it died after migrating... sigh), and i'm trying to troubleshoot it.
The display went dark after a night, no led, nothing. He plugged it to a computer, and a device called HS-USB Qdloader 9008 appeared in the device manager.
I thought it was bricked, so we followed the unbrick stepps (even the full package).
Nothing happened on the display after reboot, black screen after a short vibration, then a few minutes later another vibration, and so on...
I let it alone for a few days then tried again to see what was happening, and went again with the unbrick process. This time it completed successfully and i was able to see something on the display, but very very dim!
It booted to the stock OOS, then it rebooted right after arriving on the OOBE, and it froze while booting after that.
Again i let it alone for a few hours, and tried again, outside in the cold. This time it "worked", with the very very dim display though, i could barely see what was happening on the screen, but i was able to set it up including wifi and play store, and i could do a benchmark using geekbench successfully (score was on par with other OP3).
I went inside and tried again a few hours later, and it froze right after launching the benchmark, rebooted and froze during boot. Then i could do nothing to make it boot again (while it was warm anyway).
tl;dr : It only "works" when it is cold, and the display is barely readable. I'm thinking it could be the motherboard or the display, but would a display issue cause the reboots when getting warm? Seems weird to me!
i attached pictures of the failing OP3 next to my OP3T to highlight the display issue, the "band" visible on the 1st picture is not visible to the bare eye, only on camera and it "moves", no idea why this happens.
EDIT : i was able to unlock it while it was "working", if it is of any importance...
Click to expand...
Click to collapse
You just need to Flash Latest OOS
this type of issue was happened to me 2 months ago, i successfully recovered display by Hard bricked method
first of all i used Qualcomm hard bricked method to get my 1+3t to working condition (display was as you showed in picture) with Qualcomm Tool's Old builtin firmware
then i I flashed OOS 5.0.4 and its all done with Bright Display. I did not opened the phone.

Hayatzada said:
You just need to Flash Latest OOS
this type of issue was happened to me 2 months ago, i successfully recovered display by Hard bricked method
first of all i used Qualcomm hard bricked method to get my 1+3t to working condition (display was as you showed in picture) with Qualcomm Tool's Old builtin firmware
then i I flashed OOS 5.0.4 and its all done with Bright Display. I did not opened the phone.
Click to expand...
Click to collapse
Thanks ! I sideloaded oos 5.0.8 and now the display is fine !
It still freezes when getting warm every time, if I put it outside in the cold i can do benchmarks without issues, but as soon as I try the same inside it freezes. Since I already unbricked it, it seems hardware related but outside of the motherboard, what could be the reason ? Can the battery be responsable for that ?
The freeze happens very quickly inside, it does not get hot, barely warm at the top of the screen.

as far as my idea is concern you have another 1+3/t, to confirm battery issue swap your motherboard or battery with the other one, it'll confirm the battery. other than battery issue check lose connections/rust and thermal issue, if got any clean connection strips then reconnect. my 1+3t never got hot from any side ever.

Hayatzada said:
as far as my idea is concern you have another 1+3/t, to confirm battery issue swap your motherboard or battery with the other one, it'll confirm the battery. other than battery issue check lose connections/rust and thermal issue, if got any clean connection strips then reconnect. my 1+3t never got hot from any side ever.
Click to expand...
Click to collapse
Yes i'll do that, i just need to find the famous torx t2 to open it.
Thanks for your help!

Blubster said:
Yes i'll do that, i just need to find the famous torx t2 to open it.
Thanks for your help!
Click to expand...
Click to collapse
welcome

Related

[Q] Device reboots after SIM unlock

Hi all,
recently my D855 with v20T (root/xposed) started to sort of randomly reboot. It seems like once the device gets too hot, it's gone.
Happens rarely during general usage, often while playing a game, and especially often when starting the camera.
But it behaves strangely in general: if I do *not* unlock the SIM (and thus can't use the phone), the device runs forever, without a reboot, no matter what the device temperature is. Same for recovery (TWRP), it can stay there for hours and heat up however it likes, no reboot.
Removing the SIM and/or microSD does not make a difference, battery level does not matter.
I pulled a backup of the stock ROM, wiped everything (system, data, cache, dalvik) and flashed Fulmics 5.
Unlocking worked once or twice, the next time I entered my SIM pin, the lock screen showed, then reboot. This behaviour (unlock SIM, reboot) repeats endlessly. If I leave it turned off for 10-15 minutes - or sitting at the SIM unlock screen - it most of the time works fine after unlocking.
Wiped again, flashed robalm's v30F ROM.
Guess what, exactly the same.
On both variants, the phone got rather hot during the "optimizing app x of 190" screen, but never rebooted, only after I unlocked the SIM.
Let it sit overnight on the unlock screen, no reboot at all. Unlocked this morning, added my google account, rebooted - same thing again.
It's starting to drive me crazy, now it froze right in the middle of setting up the google account after another clean flash.
Is the phone prone for repair, or can anyone think of another solution to this weird issue?
Edit: Fun fact: if I manage to do the lock screen swipe before the SIM lock screen comes up, the phone reboots instantly as well.
Edit2: Followed the instructions from this thread to go back to completely stock v20T. Rebooted after optimizing apps before I could even choose a language, ran seemingly fine after this, started bootlooping after the first manual reboot. A full wipe later (volDn+Power) it at least boots. What the hell?
Thank you and best regards,
Sub
I have similar problem. Cant connect issue with exact cause, but it restarts almost every few minutes of use. Camera launch causes restart almost immediately. Phone is unusable. My VolDn button is not working so I'm currently a bit afraid to try anything new... I updated from Fulmics4.1 (i havent got reboot problems since last 1,5week ago) to 5.1 but issue persists even after full wipe. Seriously dont know what to think about it.
At first I thought that reboots are caused by low power (much more frequent with battery under 30%), then maybe big cpu load or high brightness.... now basically everything causes reboots. Im really annoyed this phone been crap since day one...
I havent tried your sim unclocking method as my doesnt have pin security etc. Let me know if you will find out solution.
foxracer89 said:
I have similar problem. Cant connect issue with exact cause, but it restarts almost every few minutes of use. Camera launch causes restart almost immediately. Phone is unusable. My VolDn button is not working so I'm currently a bit afraid to try anything new... I updated from Fulmics4.1 (i havent got reboot problems since last 1,5week ago) to 5.1 but issue persists even after full wipe. Seriously dont know what to think about it.
At first I thought that reboots are caused by low power (much more frequent with battery under 30%), then maybe big cpu load or high brightness.... now basically everything causes reboots. Im really annoyed this phone been crap since day one...
I havent tried your sim unclocking method as my doesnt have pin security etc. Let me know if you will find out solution.
Click to expand...
Click to collapse
Try a new battery
Anik49 said:
Try a new battery
Click to expand...
Click to collapse
Just received the device back from LG, they replaced the mainboard, even got a new IMEI and v30c preinstalled.
It is the same case, with the protective glass on top and a dent on the left plus the 2-3 micro-cracks around the frame.
Not sure if they swapped the battery. The problem showed up again with anywhere between 50 and 15 percent battery left.
Unfortunately I only tested it after leaving the shop, after a long walk to the bus which I caught just in time.
Setup assistant completed -> reboot.
Google setup nearly completed -> reboot.
Removed SIM and MicroSD, started phone, started camera, made a movie -> reboot.
Wiped again (strange enough, v30c only has 61 applications to optimize while v20* has 190+?), tried again, same thing.
Next, after letting the back camera take a movie for 2-3 minutes, I wanted to adjust display brightness to the max.
Result: see screenshot. This also happened with the cable plugged in.
I will return it for repair once more tomorrow...
Anyway, thank you for your answers
Regards,
sub
subworx said:
Just received the device back from LG, they replaced the mainboard, even got a new IMEI and v30c preinstalled.
It is the same case, with the protective glass on top and a dent on the left plus the 2-3 micro-cracks around the frame.
Not sure if they swapped the battery. The problem showed up again with anywhere between 50 and 15 percent battery left.
Unfortunately I only tested it after leaving the shop, after a long walk to the bus which I caught just in time.
Setup assistant completed -> reboot.
Google setup nearly completed -> reboot.
Removed SIM and MicroSD, started phone, started camera, made a movie -> reboot.
Wiped again (strange enough, v30c only has 61 applications to optimize while v20* has 190+?), tried again, same thing.
Next, after letting the back camera take a movie for 2-3 minutes, I wanted to adjust display brightness to the max.
Result: see screenshot. This also happened with the cable plugged in.
I will return it for repair once more tomorrow...
Anyway, thank you for your answers
Regards,
sub
Click to expand...
Click to collapse
It's a common thing if you use camera specially if you take video in 4k mode your phone heat up and you can't use full brightness in stock rom it's a feature try moded thermal config...also try new battery if battery percentage suddenly dropped it seems battery issue because i face the same problem....
Anik49 said:
It's a common thing if you use camera specially if you take video in 4k mode your phone heat up and you can't use full brightness in stock rom it's a feature try moded thermal config...also try new battery if battery percentage suddenly dropped it seems battery issue because i face the same problem....
Click to expand...
Click to collapse
I used to have thermals installed, the 75 dregrees Celsius variant, iirc.
Everything else was at stock, except for one short excursion to CM12 and one to ... some custom ROM.
Think I never actually took 4k videos, and the first 1,5 years the phone got a bit warmer but never really hot. Only recently it started to get really hot especially when using the camera, this also consistently was what could cause the reboot loops for sure. Other candidates were a few games which use more processing power like Alto's Adventure.
The battery drops by 2-3% after a reboot, because of the load the phone has (and the heat it develops during boot).
Anyway, I added the screenshot to the next repair request, and the woman at the counter said they'd look into the battery specifically (it seems to give out too much voltage, she said), but also check everything else once more.
I'll let them repair up to three times, then ask for a replacement, should be legal within 2 years after purchase in Germany.
Also, next time I'll take the 15 minutes (before doing a 1h/direction trip) to factory reset the phone, set it up and start the camera. If it reboots during any of this -> return, repeat.
Regards,
sub
Received my phone back from LG, finally.
Battery's broken - it outputs too much power.
Ordered a new battery and just put it in, so far no reboots during setup.
At least this got me a new mainboard and new IMEI
Regards,
sub
Hahahahahahahahaha
I just wondered why the phone shows 25 GB free everywhere, even without SD.
Turns out, during repair instead of replacing the 16GB/2GB board with an identical one, they installed the 32GB/3GB board
\o/ for LG

Is my 1+3 dead!?

Hi everyone,
I'm experiencing pretty silly situation with my phone.
So the story begins here:
I was surfing the web while listening to music in the bus when suddenly my oneplus3 randomly turned off and I couldn't turn it back on. (I was on something around 15% on battery so it's not a low battery problem) I tried to turn it on several times and after holding the power button for like 10secs it turned on, and after pressing the power button again (because I needed to get past unlocked bootloader screen and dm-verity) I saw a boot screen. The capacitive button leds turned on and after 3 secs it turned off again, so I started worrying... After a while I tried to access the recovery, but no luck at all. It powers it self off after bootscreen. So I started to research. Tried to flash the entire OS, partritions with msmdownload tool. After several unsuccessful flashes (firehosewritedata failed sometimes while writing userimg or system.img or boot.img) I did get the download complete green text message, and after successful flash, the white LED turned on, even the phone was not plugged in USB or charger and turned off. The screen is completely black and the white led just flashes constantly without blinking or anything. I could only turn the led off by pressing the power button for another 10 secs. And after turning the phone off, problem still remains. After oneplus logo phone shuts down...
I can access bootloader.
And after flashing everything should be on stock, because now I only got screen only about bootloader, no dm-verity..
And of course - I still cannot access the recovery.
p.s. I tried to do the power cycle (as the tech support told me) but still no luck at all.
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Mukthar. said:
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Click to expand...
Click to collapse
1GB version
djemm1996 said:
1GB version
Click to expand...
Click to collapse
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
Of course. Everything is done right. I also get that green "download complete" message.
p.s I also opened the phone. water indicators are fine and no major defects what can i see by eye... All connectors are good as well.
Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
And yes, phone was connected right. :good: installed drivers with test mode on Win10 and got Snapdragon device in COM devices. As well the MsmDownload tool shows up my device in port #20
Any ideas?
djemm1996 said:
Any ideas?
Click to expand...
Click to collapse
Follow method 2 from the Hard Brick guide by Naman Bhalla and try two or three times.
Sometimes it takes more than once for restoration.
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
try to flash again, and if it still maybe something short inside.
if you have disassembly your phone, try disconnecting various flex cable like camera, sim slot etc that connect to the mainboard, that doesn't prevent device from powered on, then try to turning it on.
if it still, check your mainboard, if you don't know how, send it back.
AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
djemm1996 said:
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
Click to expand...
Click to collapse
They are doing the same thing like you did.
I already had a session since i thought they are going to do something "special"
You can try the remote session but im afraid that wont help you if you already did it multiple times.
What about battery? Charged?
drmuruga said:
What about battery? Charged?
Click to expand...
Click to collapse
Yes battery is charged of course. It's just doint the same thing. Turns on, after a while when bootscreen comes it just turns off and white notification led appears, after that nothing.
I tried to flash it with tool using method 2 for like 15 times with "download complete" messages, but still no luck at all. Tried to erase partritions with fastboot, flashing just only recovery, modded recovery etc. but I still cannot access the recovery nor system. I just don't get it why the phone does not boot into recovery if I flash it or boot it straight away, It just only turns off and that's it. nothing more. Only black screen and white led lighting all the time (after a while the phone turns warm).
I have read all the MsmDownloadTool thread in "Mega Unbrick thread" and saw that few people have experienced the very same situation as me, so I was wondering if there is any fix for this? It's so strange that I was just surfing the Web and it just turned off by it self with like static image for miliseconds and after that just black screen.
There should be any fix. I guess that it's just a partition error...
Ok, not good news. I had a little remote session before a while. They says it's already a hardware problem.
AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Pfffft you think manufacturers notice when you take apart phones? Hell I took apart my Xperia Z2 because it was having problems and then glued it back together with cyanoacrylate hahahaha (worst thing to do but wtv) and no one noticed though it was seemless and everything looked perfect
Guys, I've got something for you! Not really the same thing as Naman.
p.s. not saying its original hehehehe keep safe
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Actually I was on twrp too! Also I have recently noticed that recovery loading speed was far too long than normal one. I'm talking for something about 5-7 minutes after reboot into twrp. So, who knows what did happen. Just made an RMA request. Will see how it goes.
Anyway, I was on stock 7.1.1 and it's just rooted with custom recovery and that's it! Nothing more! Is that just a factory failure or maybe it's caused by drops i have had? Nothing serious for a 4-5 times for a half year. Of course I have used it even in winter when the snowflakes are coming down from the sky and little rain. Btw, these liquid indicators are white, so all safe. ::laugh:
A
makadama said:
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Click to expand...
Click to collapse

Pixel XL stuck in bootloop.

There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Gnatcatcher said:
There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Click to expand...
Click to collapse
Maybe replace battery?
Hi there! I am not sure if your problem was fixed yet. But my Pixel XL died yesterday and did the same exact thing. It went into an infinire boot-loop, and after trying many times to power off and reboot, some weird artifacts appeared.
I think I messed up the phone, because at first the phone booted and then restarted, but now it just restarts and never ends....
EDIT: After some hours of rebooting, and more artifacts, the Pixel finally booted on android. Battery was at 4% so I guess that helped. It keeps rebooting from time to time, but at least I can copy my photos now haha.

Recover photos and videos from broken Nexus 5X

Hello friends,
I’m new to this forum (or, any forum, really) and in desperate need of help.
Hopefully I'm posting this correctly.
In 2017 (I think) my mom bought a Nexus 5X phone. All was well, until suddenly it broke in 2019 and she had to get a replacement. There were a lot of pictures and videos on there (no SD card was used) that we do not have a back up of. (I know, that’s a big mistake...)
What happened: it just suddenly turned off and didn’t turn on anymore. When I tried to figure out what was happening, the only response the phone gave when I plugged it into my PC was a blinking red led underneath the screen. I figured the issue must’ve been with the battery. After a while, it didn't even do that anymore - not a single response was given.
It took me until 2020 to try to replace the battery with a new one. I think I managed to replace it successfully, carefully using two YouTube tutorials. When I held the original battery in my hand, I could bend it easily, so I expected that would solve the issue. But the phone didn’t give a single response to my efforts.
I also tried heating the phone as instructed in this video (with subs):
Again, without any success.
Since I didn’t want to give up on the stuff that is on that phone (precious memories of my cat who passed away at the end of 2020, for example), I randomly tried tinkering with it again a few days ago.
When I plugged it into my computer again, suddenly the red led started blinking again... And a few moments later, the Android logo lit up. Then the screen turned black again.
I noticed that when the phone was plugged in, my PC made this noise that recognizes something is in fact plugged in. However, it didn’t recognize the device.
After trying multiple times to hold down a few buttons, I first managed to get a screen that said “Firmware update”. It disappeared after a while, and showed a Google logo. I don’t remember exactly, but I think the time after that when I pushed the on/off button, the phone actually turned on and I could use it.
I could see all pictures were still on there. I immediately tried to copy them onto my pc but before I could do that, the phone shut off again and connection with my PC was lost. Battery was charged to about 70%.
I managed to reboot it a few times, but the time it stayed on became shorter and shorter. I wanted to try the debugging method and recover data that way, but it simply didn’t give me the time to do so.
A few days later, I still get the red blinking light and sometimes the android screen or a battery loading screen. Other than that, I can’t turn it on or get into safety mode, or anything like that. It *does* still connect to my PC, but doesn’t recognize the device.
TLDR; Nexus 5X shows blinking red light, doesn’t turn on and if it does, it almost immediately turns off again even after replacing its battery. All I really want is a way to recover the photos and videos that are on the device.
If anyone has any leads or tips that could be of help, they are most welcome.

Moto G5 (XT1675) Broken screen replaced. Works fine only for 3 minutes.

I decided to repair my old Moto G5 who had a broken screen at the upper right corner.
When broken, it worked for few minutes and than the screen started to shrink and blink and and disappear.
Today i replaced the broken screen with the new one. Before proceding to remove the old one , i tested the new one by attaching it to the motherboard and it worked very well, no glitches, touch was good, had it tested for a couple of minutes, than removed the old one and placed the new one. Powered on the phone and it worked great. I was able to factory reset it, connect the wifi, test the screen, etc. but after 5 minutes it started with vertical stripes , disapperared and reappeared, flickering and dead.
I noticed that the motherboard was very hot when i removed the battery to shut it down.
When powered on again, it didn't show the screen, but the startup audio was working...
Thinking it wa an heating issue, i put it in the freezer (in a sealed container) and after 10 minutes, i turned it on... and it worked again, letting me test it for another 5 minutes before starting the issues again.
I disabled everything, no wifi, no bluetooth , no sim or sd. The issue happens also in bootloader mode by pressing power+vol- , works for some minutes, letting me brows the boot menu, but if i wait, the screen does the issues again.
Now i have to options :
1) Understand the issue and fix it
2) find someone in Antartica or Artic regions to use the phone at -25 celsius.
Thank You
A chip in your motherboard is malfunctioning. You gotta get it replaced. after 5 mins the problematic chip gets so hot it glitches your whole system. If you have a heat camera look over your motherboard while it is switched on. The culprit will shine like a christmas ball light. Then it's a matter of buying a replacement and replacing it.
If you don't have this type of camera, go to a repair center ( does not need to be official and tell them to check with their camera for the cooker).

Categories

Resources