Database Users

Moto G4+ Bricked ---Help ASAP!!

My phone is Moto G4+ -
Indian Version
Android 7.0 (June Security Update installed)
32GB ROM / 3GB RAM
Black Variant
Bought online on amazon.in
My 1 year warranty expired on 18 July 2017.
I update to the June security update last week. Everything was going fine.
Today when my phone was charging (was around 50%), I opened WhatsApp to check my messages. As I reading my messages the whole screen got an "RED" overlay. And most of the things in the background became black but I was still able to see behind the overlay. Also there was a small "BLUE" circle in the middle above the overlay. I have taken a screenshot of it but can't post it (read further to know why). After taking the screenshot the phone was unresponsive to all inputs, nothing worked. Then it switched off. The following things I have tried till now to start it:-
1. Normal turn on (pressing the power button)
2. Forced turn on (pressing power button for more than 2 minutes while charging)
3. Boot in recovery (power button and volume down for approx 5 seconds)
I tried all the methods while charging and while not charging.
The phone is not giving any response. It dose not even turn the screen on (and I know the screen was off not just the backlight on and blank screen). The only respone is IT VIBRATES EVERY 2-3 minutes (do not know the exact interval) . It has been going on continuously. The LED (near the fingerprint scanner) is not turning on too.
I have never done or tried to root, unlock the bootloader, etc.
All my apps were installed from the Play Store except for "Terrarium Tv" (https://terrariumtv.com/).
I connected the phone to my laptop, it detected it as "Moto G4", I tried to open it but the laptop was not able to mount it. I tried after some time and now the laptop dosen't even detect it.

ADPL said:
My phone is Moto G4+ -
Indian Version
Android 7.0 (June Security Update installed)
32GB ROM / 3GB RAM
Black Variant
Bought online on amazon.in
My 1 year warranty expired on 18 July 2017.
I update to the June security update last week. Everything was going fine.
Today when my phone was charging (was around 50%), I opened WhatsApp to check my messages. As I reading my messages the whole screen got an "RED" overlay. And most of the things in the background became black but I was still able to see behind the overlay. Also there was a small "BLUE" circle in the middle above the overlay. I have taken a screenshot of it but can't post it (read further to know why). After taking the screenshot the phone was unresponsive to all inputs, nothing worked. Then it switched off. The following things I have tried till now to start it:-
1. Normal turn on (pressing the power button)
2. Forced turn on (pressing power button for more than 2 minutes while charging)
3. Boot in recovery (power button and volume down for approx 5 seconds)
I tried all the methods while charging and while not charging.
The phone is not giving any response. It dose not even turn the screen on (and I know the screen was off not just the backlight on and blank screen). The only respone is IT VIBRATES EVERY 2-3 minutes (do not know the exact interval) . It has been going on continuously. The LED (near the fingerprint scanner) is not turning on too.
I have never done or tried to root, unlock the bootloader, etc.
All my apps were installed from the Play Store except for "Terrarium Tv" (https://terrariumtv.com/).
I connected the phone to my laptop, it detected it as "Moto G4", I tried to open it but the laptop was not able to mount it. I tried after some time and now the laptop dosen't even detect it.
Click to expand...
Click to collapse
This maybe is the hardware issue bro .because it should get detected in PC eitherway

ADPL said:
My phone is Moto G4+ -
Indian Version
Android 7.0 (June Security Update installed)
32GB ROM / 3GB RAM
Black Variant
Bought online on amazon.in
My 1 year warranty expired on 18 July 2017.
I update to the June security update last week. Everything was going fine.
Today when my phone was charging (was around 50%), I opened WhatsApp to check my messages. As I reading my messages the whole screen got an "RED" overlay. And most of the things in the background became black but I was still able to see behind the overlay. Also there was a small "BLUE" circle in the middle above the overlay. I have taken a screenshot of it but can't post it (read further to know why). After taking the screenshot the phone was unresponsive to all inputs, nothing worked. Then it switched off. The following things I have tried till now to start it:-
1. Normal turn on (pressing the power button)
2. Forced turn on (pressing power button for more than 2 minutes while charging)
3. Boot in recovery (power button and volume down for approx 5 seconds)
I tried all the methods while charging and while not charging.
The phone is not giving any response. It dose not even turn the screen on (and I know the screen was off not just the backlight on and blank screen). The only respone is IT VIBRATES EVERY 2-3 minutes (do not know the exact interval) . It has been going on continuously. The LED (near the fingerprint scanner) is not turning on too.
I have never done or tried to root, unlock the bootloader, etc.
All my apps were installed from the Play Store except for "Terrarium Tv" (https://terrariumtv.com/).
I connected the phone to my laptop, it detected it as "Moto G4", I tried to open it but the laptop was not able to mount it. I tried after some time and now the laptop dosen't even detect it.
Click to expand...
Click to collapse
Hold down power and volume down for 2-5min if it booting into bootloader if it doesn't boot it may be a hardware issue
Sent from my Moto G4 Plus using Tapatalk

BlackBeats said:
Hold down power and volume down for 2-5min if it booting into bootloader if it doesn't boot it may be a hardware issue
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Gave no response, tried that.

ADPL said:
Gave no response, tried that.
Click to expand...
Click to collapse
Use the old twrp your new twrp might be corrupted
If nothing works then flash the stock rom
Using adb
Sent from my Moto G4 Plus using Tapatalk

BlackBeats said:
Use the old twrp your new twrp might be corrupted
If nothing works then flash the stock rom
Using adb
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Bootloader is not unlocked. Never rooted so TWRP dosent come in the picture.

ADPL said:
Bootloader is not unlocked. Never rooted so TWRP dosent come in the picture.
Click to expand...
Click to collapse
June update (14-8) has killed a lot of Athene. Sorry. A warning to others to stay away from this update. Stick with March Security Update ROM 14-4. If under warranty, send it in ASAP.

HueyT said:
June update (14-8) has killed a lot of Athene. Sorry. A warning to others to stay away from this update. Stick with March Security Update ROM 14-4. If under warranty, send it in ASAP.
Click to expand...
Click to collapse
Warranty ended on 18th July, bricked on 20 July

Does it vibrate? what about the LED @ the bottom?
ADPL said:
Warranty ended on 18th July, bricked on 20 July
Click to expand...
Click to collapse
sorry to hear about your phone! there is a high chance that its a hardware problem.
reason_
1. It should be able to get picked up with your Windows / Mac. as QHUSB_Bulk (if your bootloader was damaged)
2. If display was the problem. Connecting to PC should have detected anyway as adb sideloader or Moto Device / Android device.
PS_ try uninstalling moto drivers and reinstalling from **device manager.

jagpreetsinghmatharu said:
sorry to hear about your phone! there is a high chance that its a hardware problem.
reason_
1. It should be able to get picked up with your Windows / Mac. as QHUSB_Bulk (if your bootloader was damaged)
2. If display was the problem. Connecting to PC should have detected anyway as adb sideloader or Moto Device / Android device.
PS_ try uninstalling moto drivers and reinstalling from **device manager.
Click to expand...
Click to collapse
It was a hardware problem, display and motherboard had been shorted.

shubh01608 said:
This maybe is the hardware issue bro .because it should get detected in PC eitherway
Click to expand...
Click to collapse
But terrariumtv.com Not working now, may be https://terrariumtvz.co is working for me

Dead & unresponsive 6P help.

So a couple weeks ago my Nexus 6P died.
I had just taken it off charge and it froze then just died. Became unresponsive and I can't boot it or boot it into recovery. So I have a paper weight at the moment.
Ever since, there has been a couple instances where I got the phone to boot into the Google logo and it will freeze there. Either that, or it will get into the loading animation and freeze on that. It will not turn off until I turn it off myself.
I've only been able to do this a couple times with it being on charge for an hour, unplugging it and plugging it back in whilst holding the power button. Trying to get into recovery with this method has proven unsuccessful.
When left until there is no charge on the phone, I am able to invoke the red blinking lights on the notification led by holding down the power button in any variation (e.g. vol down + power, vol up + power, etc)
The question is if anyone else has come across this issue before and if there is any fix?
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad.
I can't RMA the device back to Google as I bought the phone whilst I was working in Japan and I bought it from Google Japan and I am know back in the UK.
So they apparently follow local warranty. I've spoken to them about 3 times about this and refuse to budge. Huawei are also no help as I bought the device from overseas, they said they aren't allowed to send any devices from Asia to their UK service centre.
So I'm kinda stuck. Any help would be greatly appreciated.

CookieDude_2332 said:
So a couple weeks ago my Nexus 6P died.
I had just taken it off charge and it froze then just died. Became unresponsive and I can't boot it or boot it into recovery. So I have a paper weight at the moment.
Ever since, there has been a couple instances where I got the phone to boot into the Google logo and it will freeze there. Either that, or it will get into the loading animation and freeze on that. It will not turn off until I turn it off myself.
I've only been able to do this a couple times with it being on charge for an hour, unplugging it and plugging it back in whilst holding the power button. Trying to get into recovery with this method has proven unsuccessful.
When left until there is no charge on the phone, I am able to invoke the red blinking lights on the notification led by holding down the power button in any variation (e.g. vol down + power, vol up + power, etc)
The question is if anyone else has come across this issue before and if there is any fix?
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad.
I can't RMA the device back to Google as I bought the phone whilst I was working in Japan and I bought it from Google Japan and I am know back in the UK.
So they apparently follow local warranty. I've spoken to them about 3 times about this and refuse to budge. Huawei are also no help as I bought the device from overseas, they said they aren't allowed to send any devices from Asia to their UK service centre.
So I'm kinda stuck. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Some more information would be useful like do you have an unlocked bootloader and have debugging enabled?

DEVILOPS 007 said:
Some more information would be useful like do you have an unlocked bootloader and have debugging enabled?
Click to expand...
Click to collapse
Unfortunately I don't have the bootloader unlocked nor have I got debugging enabled (I don't think).
Its pretty much as it was outta the box. Only things I tinkered with was enabling dev options in the settings but that is as much as I've done really. But haven't messed around with any of those settings.
The device is all stock.

CookieDude_2332 said:
Unfortunately I don't have the bootloader unlocked nor have I got debugging enabled (I don't think).
Its pretty much as it was outta the box. Only things I tinkered with was enabling dev options in the settings but that is as much as I've done really. But haven't messed around with any of those settings.
The device is all stock.
Click to expand...
Click to collapse
Did you enable OEM unlocking if you enabled Dev options?

DEVILOPS 007 said:
Did you enable OEM unlocking if you enabled Dev options?
Click to expand...
Click to collapse
I don't think so. Sorry, I'm not super technical.

Not wanting to make a new thread when this seems to be relevant; I appear to be experiencing the same issues as the OP.
I was at work and I noticed that my phone had switched off. I assumed it had ran flat and I hadn't noticed so plugged it in when I got home to no avail. The following day I was playing with the power button; holding it down for a period and pressing thinking it might be a loose connection and eventually it did turn back on but only for a few hours and since then the only response I get is a red LED when pressing the power/volume button whilst on charge.
I have replaced both the battery and the charging port/daughter board but this does not appear to have resolved the issue. Is there something I am missing or is my phone now a very expensive paperweight? If that is the case this will be the second Nexus device I owned which died in similar circumstances not long out of it warranty; I had a Nexus 6 which died after a year which I replaced with the 6P and it may be that the same thing has happened.
Any help, advice or suggestions anyone can give would be much appreciated!
Edit: Answering a question asked previously with regards to more information my bootloader is unlocked however I can't remember if USB debugging was enabled. I have a feeling that it is disabled as a work around for Magisk Hide and passing SafetyNet.

CookieDude_2332 said:
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad..
Click to expand...
Click to collapse
BLOD is a bad motherboard. If you can't access Recovery and are bootloader locked, you're at the end of the road.

Have you tried to keep it plugged in then hold the volume down button and power button at the same time, and hold it hard for a while and see if it goes to the recovery partition.
Otherwise, why don't you bring to a hardware store and talk to someone?
GLHF!:crying:

So I've spoken to Huawei on a whim and found out that my phone is under warranty so I am waiting on a return delivery envelope to go to one of their Service Centres however I would like to at least try to restore back to stock and re-lock the boot loader as I have managed on a few occasions to get the phone to boot to the 'Google' logo before it would then shut down. I have since plugged the phone in to my laptop and "QHSUSB__BULK" appears in Device Manager.
I have Wugfresh's NRT 2.1.9 but this does not pick up fastboot or adb. Is there any other tool I should be aware of or a driver I haven't got installed? Is this something anyone has come across or managed to resolve before?

beejkitsune said:
So I've spoken to Huawei on a whim and found out that my phone is under warranty so I am waiting on a return delivery envelope to go to one of their Service Centres however I would like to at least try to restore back to stock and re-lock the boot loader as I have managed on a few occasions to get the phone to boot to the 'Google' logo before it would then shut down. I have since plugged the phone in to my laptop and "QHSUSB__BULK" appears in Device Manager.
I have Wugfresh's NRT 2.1.9 but this does not pick up fastboot or adb. Is there any other tool I should be aware of or a driver I haven't got installed? Is this something anyone has come across or managed to resolve before?
Click to expand...
Click to collapse
Leave it just the way it is. You're stuck in QC 9008 diagnostic mode. Perfect for sending the phone back. Don't worry about it.

v12xke said:
Leave it just the way it is. You're stuck in QC 9008 diagnostic mode. Perfect for sending the phone back. Don't worry about it.
Click to expand...
Click to collapse
Thanks for the advice. I'm just waiting on them sending me the jiffy bag to send my device out to them.
I'm not holding my breath on them actually fixing or replacing it as I have done a DIY battery replacement a little while ago (though I did replace with an OEM battery) but I figure it's worth a shot and worst case scenario I'll hold out for Oct 4th and hope the Pixel 2 XL rumours are right and it will have a similar screen design to the Galaxy S8+.
I love the look of the Infinity Display but will not have a Samsung.

beejkitsune said:
...I love the look of the Infinity Display but will not have a Samsung.
Click to expand...
Click to collapse
Totally agree.

beejkitsune said:
Thanks for the advice. I'm just waiting on them sending me the jiffy bag to send my device out to them.
I'm not holding my breath on them actually fixing or replacing it as I have done a DIY battery replacement a little while ago (though I did replace with an OEM battery) but I figure it's worth a shot and worst case scenario I'll hold out for Oct 4th and hope the Pixel 2 XL rumours are right and it will have a similar screen design to the Galaxy S8+.
I love the look of the Infinity Display but will not have a Samsung.
Click to expand...
Click to collapse
Final update. Apparently Huawei are struggling with a parts shortage and don't know when parts will be come available so they have offered me a "Limited Edition" Gold Mate 9. I'm not entirely happy about this arrangement as I really loved my 6P but they have had my 6P for about six weeks and I haven't had a fully working phone since August 18th so I'm left with little other choice since I can't afford the P2XL.
Thanks for your help and in general to everyone in the 6P threads who have helped me out of the past 18 months.

Bricked Le Pro 3 727 (Blue Screen of Death)

Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.

Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium

My one did the same, the issue was motherboard. You should send it back to repair.

mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.

Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium

That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.

Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.

shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.

i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?

Bricked Essential phone

Hey guys, I just joined and this is my first post so pardon any stupid questions/statements I made
My Essential phone suddenly switched off while driving and it seems like it self-bricked itself - there is (almost) no life to the phone besides it coming up as "Qualcomm" when plugged into my laptop.
I've tried the following:
Hard-resetting it with the volume down/up + power button many times, for longer than a minute, with no response from the phone, so I can't get to fastboot etc.
Charging it with different 3rd party chargers/cables
Using adb (but can not get debugging mode on)
Charging it for atleast an hour before repeating the above
I've read other forums/topics and I can't seem to find a solution.
Another thing, I've made zero mods to the phone.
Can someone please help me, I'm using an old LG G3 at the moment lol.
Thanks

juliangovender92 said:
Hey guys, I just joined and this is my first post so pardon any stupid questions/statements I made
My Essential phone suddenly switched off while driving and it seems like it self-bricked itself - there is (almost) no life to the phone besides it coming up as "Qualcomm" when plugged into my laptop.
I've tried the following:
Hard-resetting it with the volume down/up + power button many times, for longer than a minute, with no response from the phone, so I can't get to fastboot etc.
Charging it with different 3rd party chargers/cables
Using adb (but can not get debugging mode on)
Charging it for atleast an hour before repeating the above
I've read other forums/topics and I can't seem to find a solution.
Another thing, I've made zero mods to the phone.
Can someone please help me, I'm using an old LG G3 at the moment lol.
Thanks
Click to expand...
Click to collapse
came across this yesterday and remembered this post....try this https://www.youtube.com/watch?v=uEERGDgTw-M

Thanks for this ... Not sure how to proceed though, seems like each Android maker has their own specific solution (LG has their volume up battery out charger in, vs Samsung holding all of their buttons) so not sure what to do ... any suggestions?

juliangovender92 said:
Thanks for this ... Not sure how to proceed though, seems like each Android maker has their own specific solution (LG has their volume up battery out charger in, vs Samsung holding all of their buttons) so not sure what to do ... any suggestions?
Click to expand...
Click to collapse
Were you by chance running the official stock January pie update?
Sent from my [device_name] using XDA-Developers Legacy app

canodroid15 said:
Were you by chance running the official stock January pie update?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Nope - the phone bricked in the last week of december

juliangovender92 said:
Nope - the phone bricked in the last week of december
Click to expand...
Click to collapse
That sucks dude sorry to hear. Did you ever figure it out? My wife has the ph-1 & hers just shutdown on her running latest bone stock build. No root, no mods, it refused to boot for me. After several attempts I gave up for a while. I've been dealing with android for years. I was baffled. So I went back to it & held down power+vol up one last time & the damn thing boots after about 20 seconds. So far its doing fine. This just happened earlier this morning. Before it booted up I tried everything like you & it wouldn't respond. Weird. Definitely keeping an eye on it for now.
Sent from my [device_name] using XDA-Developers Legacy app

canodroid15 said:
That sucks dude sorry to hear. Did you ever figure it out? My wife has the ph-1 & hers just shutdown on her running latest bone stock build. No root, no mods, it refused to boot for me. After several attempts I gave up for a while. I've been dealing with android for years. I was baffled. So I went back to it & held down power+vol up one last time & the damn thing boots after about 20 seconds. So far its doing fine. This just happened earlier this morning. Before it booted up I tried everything like you & it wouldn't respond. Weird. Definitely keeping an eye on it for now.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Unfortunately it still isn't working - I'm trying as I type this out lol ... How long did your wife's stay off for? Yeah really love(d) this phone but no life to it ...

canodroid15 said:
That sucks dude sorry to hear. Did you ever figure it out? My wife has the ph-1 & hers just shutdown on her running latest bone stock build. No root, no mods, it refused to boot for me. After several attempts I gave up for a while. I've been dealing with android for years. I was baffled. So I went back to it & held down power+vol up one last time & the damn thing boots after about 20 seconds. So far its doing fine. This just happened earlier this morning. Before it booted up I tried everything like you & it wouldn't respond. Weird. Definitely keeping an eye on it for now.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What happened when you tried to charge it while it shutdown on you guys?

juliangovender92 said:
Unfortunately it still isn't working - I'm trying as I type this out lol ... How long did your wife's stay off for? Yeah really love(d) this phone but no life to it ...
Click to expand...
Click to collapse
It was a few hours. I tried for like an hour to boot it & gave up. Came back to it right after I made my first post quoting you here. Held the power+vol up x'ed fingers & it vibrated then powered on. Let me know if you get yours to boot. I'm going to look into this after work today. I'll talk to ya later. There's gotta be a way to figure your situation out.
Sent from my [device_name] using XDA-Developers Legacy app

canodroid15 said:
It was a few hours. I tried for like an hour to boot it & gave up. Came back to it right after I made my first post quoting you here. Held the power+vol up x'ed fingers & it vibrated then powered on. Let me know if you get yours to boot. I'm going to look into this after work today. I'll talk to ya later. There's gotta be a way to figure your situation out.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Been trying for the past week ... can't seem to get it booted - I literally just put it into the fridge (zip lock bag to [hopefully] keep the moisture out). I've seen a post where someone tried this and it worked. Thanks man, I would appreciate any help I can get

Did anyone try asking essential support?
They've been very helpful to me.
Also had this happen to me, just left it overnight and then it booted. No probs since.
Zo0

ZooBaAr said:
Did anyone try asking essential support?
They've been very helpful to me.
Also had this happen to me, just left it overnight and then it booted. No probs since.
Zo0
Click to expand...
Click to collapse
Yes I have, they told me to hold power+volume; try different USB cables. clean port etc. but nothing is helping ... really sucks!

juliangovender92 said:
Been trying for the past week ... can't seem to get it booted - I literally just put it into the fridge (zip lock bag to [hopefully] keep the moisture out). I've seen a post where someone tried this and it worked. Thanks man, I would appreciate any help I can get
Click to expand...
Click to collapse
My post from her other day didn't seem to post .
In it I suggested you hold down power + vol down for 15sec (maybe longer) as I think that does a virtual battery pull, but you might need to try some other combos. You should maybe put phone in draw for a week or two, then try .
Also see,
https://forum.xda-developers.com/es...icked-essential-phone-regular-update-t3732566
If the "chilling" trick works you might have a bad solder joint, not good, likely cause intermittent problems if it does fix. Or maybe phone shuts down internally if too cold (

IronRoo said:
My post from her other day didn't seem to post .
In it I suggested you hold down power + vol down for 15sec (maybe longer) as I think that does a virtual battery pull, but you might need to try some other combos. You should maybe put phone in draw for a week or two, then try .
Also see,
https://forum.xda-developers.com/es...icked-essential-phone-regular-update-t3732566
If the "chilling" trick works you might have a bad solder joint, not good, likely cause intermittent problems if it does fix. Or maybe phone shuts down internally if too cold (
Click to expand...
Click to collapse
thanks for the advice ... I tried all combinations for atleast a minute:
power + vol down
power + vol up
power + vol up and down
doesnt seem to have any life. I'm not sure if I mentioned but there's no sign of LED lights when charging - only sign of life is the Qualcomm port on device manager (windows) ... Sadly this country does not have any authorized entities to open up the phone

juliangovender92 said:
thanks for the advice ... I tried all combinations for atleast a minute:
power + vol down
power + vol up
power + vol up and down
doesnt seem to have any life. I'm not sure if I mentioned but there's no sign of LED lights when charging - only sign of life is the Qualcomm port on device manager (windows) ... Sadly this country does not have any authorized entities to open up the phone
Click to expand...
Click to collapse
It sounds like your only choice is to try leaving it for a prolonged period eg a couple of weeks (don't charge it) & cross fingers you get lucky like some of the others have. Though it does sound like it may be bricked (might be worth installing Essential drivers on another PC & seeing if that gives you any thing more than the Qualcomm port)
I'd be in the same situation as you as I'm in Australia these days. It doesn't seem like local repair shops have any special Essential service tools, but if you have no chance of warranty repair local repair shop might still be able to identify some internal failure even if only basic electronic tests and order part (though might be hard/impossible to identify specific component failure without a circuit diagram or working phone to compare to), so long shot.

juliangovender92 said:
thanks for the advice ... I tried all combinations for atleast a minute:
power + vol down
power + vol up
power + vol up and down
doesnt seem to have any life. I'm not sure if I mentioned but there's no sign of LED lights when charging - only sign of life is the Qualcomm port on device manager (windows) ... Sadly this country does not have any authorized entities to open up the phone
Click to expand...
Click to collapse
PS. You probably tried this already but just in case, try boot into recovery, hold down
vol up + vol down
(NOT power)
probably won't work, but just to cover all bases

IronRoo said:
It sounds like your only choice is to try leaving it for a prolonged period eg a couple of weeks (don't charge it) & cross fingers you get lucky like some of the others have. Though it does sound like it may be bricked (might be worth installing Essential drivers on another PC & seeing if that gives you any thing more than the Qualcomm port)
I'd be in the same situation as you as I'm in Australia these days. It doesn't seem like local repair shops have any special Essential service tools, but if you have no chance of warranty repair local repair shop might still be able to identify some internal failure even if only basic electronic tests and order part (though might be hard/impossible to identify specific component failure without a circuit diagram or working phone to compare to), so long shot.
Click to expand...
Click to collapse
Apologies for the late reply ... Phone has been like this for about 3 weeks now ... still no luck; will try the Essential drivers now
Yeah I think I'll end up taking it to a local repair shop; hope for the best and expect the worst I guess

IronRoo said:
PS. You probably tried this already but just in case, try boot into recovery, hold down
vol up + vol down
(NOT power)
probably won't work, but just to cover all bases
Click to expand...
Click to collapse
Haha read this at work and gave me some hope, but sadly nothing.
When my phone is plugged into my laptop, Windows makes that signature connection sound; and when I hold power+vol, it effectively makes the "disconnect" followed by the "connect" sounds again, which is surprising

juliangovender92 said:
Haha read this at work and gave me some hope, but sadly nothing.
When my phone is plugged into my laptop, Windows makes that signature connection sound; and when I hold power+vol, it effectively makes the "disconnect" followed by the "connect" sounds again, which is surprising
Click to expand...
Click to collapse
My phone is also hard bricked not even showing led but detecting on PC . currently I don't have PC but yesterday I read about QPST tool . It has an option to backup and restore . I don't know I sound stupid but is there a way to restore firmware of another essential phone through QPST tool . I've tried every thing else .
Link to QPST tool: https://www.qpstflash.com/

mishal msl said:
My phone is also hard bricked not even showing led but detecting on PC . currently I don't have PC but yesterday I read about QPST tool . It has an option to backup and restore . I don't know I sound stupid but is there a way to restore firmware of another essential phone through QPST tool . I've tried every thing else .
Link to QPST tool: https://www.qpstflash.com/
Click to expand...
Click to collapse
Sorry I can't offer any advice on your issue. However, can you or anyone here vouch for the reputability of the developer of this tool? I am suspicious as their website does not offer much info in that regard...
Sent from my CMR-W09 using Tapatalk

LG V20 unresponsive

Hello guys. So after one year of using the LG V20 H910, it's now completely unresponsive. Today, I plugged it to my amp to listen to some music. At some point, the screen froze, but the music (spotify) kept playing for a while. I left it as is, in case it unfroze by itself. After about 30 seconds, the music stopped too, so I removed the battery. When I put it back in and tried powering on the phone, nothing happened. No boot screen, no vibration, nothing. Connecting it to the charger did nothing too. But the phone became a little warm after letting it 5 minutes plugged in. I was running Alpha Omega Rom 1.1.7 (Android 8.0), with root. Any ideas on how I should proceed? Do you think it's completely unrecoverable? I was really enjoying using it.

Thanos_D said:
Hello guys. So after one year of using the LG V20 H910, it's now completely unresponsive. Today, I plugged it to my amp to listen to some music. At some point, the screen froze, but the music (spotify) kept playing for a while. I left it as is, in case it unfroze by itself. After about 30 seconds, the music stopped too, so I removed the battery. When I put it back in and tried powering on the phone, nothing happened. No boot screen, no vibration, nothing. Connecting it to the charger did nothing too. But the phone became a little warm after letting it 5 minutes plugged in. I was running Alpha Omega Rom 1.1.7 (Android 8.0), with root. Any ideas on how I should proceed? Do you think it's completely unrecoverable? I was really enjoying using it.
Click to expand...
Click to collapse
If it won't power on, then not much you can do, maybe try a new battery to eliminate that from being the cause
Sent from my LG-H910 using XDA Labs

cnjax said:
If it won't power on, then not much you can do, maybe try a new battery to eliminate that from being the cause
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
I tried with an extended one I have, and with the original, with the same results

Thanos_D said:
I tried with an extended one I have, and with the original, with the same results
Click to expand...
Click to collapse
If it gets hot means device is on can you at least try to put it download mode and see if LG up recognises it?

mikekote666 said:
If it gets hot means device is on can you at least try to put it download mode and see if LG up recognizes it?
Click to expand...
Click to collapse
Unfortunately, this can't be done. No matter how I try to plug the phone to the computer (simply plugging it in or pressing the up volume button for download mode or pressing the down vol button plus power button to go in fastboot mode) nothing happens. So I guess RIP

Thanos_D said:
Unfortunately, this can't be done. No matter how I try to plug the phone to the computer (simply plugging it in or pressing the up volume button for download mode or pressing the down vol button plus power button to go in fastboot mode) nothing happens. So I guess RIP
Click to expand...
Click to collapse
You said phone gets hot...What if there's a bad screen connection or some other bad connection causing problems

mikekote666 said:
You said phone gets hot...What if there's a bad screen connection or some other bad connection causing problems
Click to expand...
Click to collapse
It might be, but I cannot test that. If only the screen was dead, when pressing the power button and waiting, at some point it should boot up. If you then try to access the power menu, there is haptic feedback. I have tried this, and cannot confirm that the phone is booting, and that just the screen is showing nothing. Regarding any other bad connections, I think it's unlikely, as it hasn't been dropped for over 6 months now, and the day it died was just like the previous ones. I don't have any knowledge on how to troubleshoot such a complicated system for bad connections.

Thanos_D said:
It might be, but I cannot test that. If only the screen was dead, when pressing the power button and waiting, at some point it should boot up. If you then try to access the power menu, there is haptic feedback. I have tried this, and cannot confirm that the phone is booting, and that just the screen is showing nothing. Regarding any other bad connections, I think it's unlikely, as it hasn't been dropped for over 6 months now, and the day it died was just like the previous ones. I don't have any knowledge on how to troubleshoot such a complicated system for bad connections.
Click to expand...
Click to collapse
Say goodbye to your beloved LG V20 then

mikekote666 said:
Say goodbye to your beloved LG V20 then
Click to expand...
Click to collapse
Yeah, I guess so