My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?
whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean
Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.
Related
Hi everyone,
INTRO:
So the power button on my Nexus S broke. No big deal, I remapped it to the search button and used the volume rocker to wake the device; an option that was embedded in Cyanogenmod9.
Then I upgraded to CM10... since I did that on top of CM9, my volume rocker option was still enabled, but the option is no longer in CM10's GUI.
I had some annoying issue and thought maybe I should wipe my phone; which I did.
Sadly, I realized that my "wake using volume rocker" option was no longer enabled, and there is no GUI to turn it back on.
I then found a .zip package that was supposed to enable the option but, I guess I went too fast, now my phone is stuck on a bootloop.
THE PROBLEM:
Since my power button is broken, I cannot navigate in the fastboot menu to recovery and fix the ROM.
Worst, since the power button is somehow shorted (i.e.: it powers on automatically when I insert the battery) Fastboot is not working properly and my PC never sees my phone, so you can forget about fastboot boot recovery.img
So: boot loop, power button broke, no recovery, no fastboot. =(
I searched quite a bit and found out you could get the Nexus S in download mode and get it to work with ODIN using a USB JIG.
I made myself such a JIG and successfully put the phone in some kind of download mode where my PC sees it, fastboot devices yields nothing *but* ODIN sees the phone!
So a glimmer of hope except for the fact that finding the .tar files for the Nexus S seems impossible...
Thoughts? Suggestion? TIA!
Francis // XC3N
Oh BTW:
-Yes I saw the other posts, but none of them mention the odin files
-Yes, I know fastboot is better; but it's not working and:
-No, I can't see the device on 3 different PCs using 3 different OSes and 3 Different cables when in fastboot mode
I mean by that last line that *nothing* shows in device manager in Win7 or XP and *nothing* shows in lsusb on ubuntu
So unless someone has an idea it looks like Download mode is the only way my PC sees my phone...
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
I think it's something to do with the micro switches giving out after a certain number of uses.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
In short, tap it until it works, once you have control of fastboot plug the usb in and your pc should detect it
Hope this helps, Good Luck
Sent from my U20i using xda app-developers app
Muckyfox said:
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
Click to expand...
Click to collapse
Hey MuckyFox thanks for your reply!
Unfortunately, that would've worked back when the power button was flimsy and still working once in a while... I did try the tapping thing but really nothing works... the button seems entirely dead and shorted. I guess at this point I might've to bring it in for repair... if the power button isn't broken then I'll be able to easily fix everything in recovery or fastboot. Sucks because I feel like I'm so close to getting it to work without spending money XD I just can't find the files for odin even though they really do seem to exist.
Allright so I found some odin files which were said to work with the i9020a
I flashed them... at some point it said "RESET!" and then odin no longer saw the device. The device is now not booting at all. FML
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
My power button started failing over the last couple of days. First when I would set the phone to standby it would ask me if I wanted to switch off the device, then later on it wouldnt respond at all.
Really weird solution - boot into recovery, factory restore, clear dalvik cache, voila, works good as new! (aside from losing all my settings)
Note, I barely managed to get into recovery. The power button fully stopped working halfway through and I had to take the battery out and try it a couple of times.
Oddly, even during this uber-broken phase, the power button would always switch on the device when fully switched off (not just standby) indicating to me that it wasnt just a physical broken connection.
I've mentioned this before, but a full casing for the phone with all the buttons is around $10 on eBay
Sent from my Nexus S using xda app-developers app
XC3N said:
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
Click to expand...
Click to collapse
You need stuff for SOJUA, and just the fact CSC has EUR meaning Europe in it would scare the crap out of me. Possible you just flashed stuff meant for i9020T and not i9020A.
In case anybody comes back here, I'm just gonna drop this in.
Looking for a quick fix here as I can't go to the service centre and get a replacement until at least Tuesday, and I need my phone working before then. I'm hoping someone else has had the same problem and can help me out.
My Moto G froze and became unresponsive (while I was refreshing my Gmail inbox) and it would not accept any input. I held down the power button and the power menu opened, however when I tried to power it off, it wouldn't accept my touch input. So obviously the next course of action was to hold down the power button for 10 seconds to force a reboot. The Motorola logo appeared and the phone vibrated... then it did nothing.
I tried this a few times and still nothing happened. I am able to boot into the bootloader, but apart from that, the phone goes only so far into the boot cycle before the screen goes black and does nothing.
Motorola's website suggests that if the Moto G becomes unresponsive, and the regular 10 second reset doesn't work, you should hold the power button for 120 seconds and keep it plugged in to a charger. This didn't work either. As of right now, my phone is just sitting here on my desk with what I would call a 'black screen of death.' Help would be appreciated.
I cannot boot into recovery, I cannot access anything. The phone is stock, unrooted, and running KitKat 4.4.2 without any modifications whatsoever. It's about 5 months old now, so it's still covered by warranty and I don't want to void it.
Narwhal73 said:
Looking for a quick fix here as I can't go to the service centre and get a replacement until at least Tuesday, and I need my phone working before then. I'm hoping someone else has had the same problem and can help me out.
My Moto G froze and became unresponsive (while I was refreshing my Gmail inbox) and it would not accept any input. I held down the power button and the power menu opened, however when I tried to power it off, it wouldn't accept my touch input. So obviously the next course of action was to hold down the power button for 10 seconds to force a reboot. The Motorola logo appeared and the phone vibrated... then it did nothing.
I tried this a few times and still nothing happened. I am able to boot into the bootloader, but apart from that, the phone goes only so far into the boot cycle before the screen goes black and does nothing.
Motorola's website suggests that if the Moto G becomes unresponsive, and the regular 10 second reset doesn't work, you should hold the power button for 120 seconds and keep it plugged in to a charger. This didn't work either. As of right now, my phone is just sitting here on my desk with what I would call a 'black screen of death.' Help would be appreciated.
I cannot boot into recovery, I cannot access anything. The phone is stock, unrooted, and running KitKat 4.4.2 without any modifications whatsoever. It's about 5 months old now, so it's still covered by warranty and I don't want to void it.
Click to expand...
Click to collapse
Can you boot into bootloader mode and use adb command from a pc? If yes, maybe you can try to flash a stock recovery img file via your pc to phone.
echui2014 said:
Can you boot into bootloader mode and use adb command from a pc? If yes, maybe you can try to flash a stock recovery img file via your pc to phone.
Click to expand...
Click to collapse
Would that require unlocking my boot loader though? I don't want to void my warranty, especially considering I did nothing to the phone and it's currently unresponsive.
I am not sure - but my guess is that bootloader needs to be unlocked to install custom recovery to "recover" & backup userdata before flashing the entire original stock firmware; that's usually the first step we see in all those modding guide in different forums online.
How to get into safe mode
www[dot]youtube[dot]com/watch?v=NSHzoSEx8xY
** I am unable to post outside url yet.**
I suppose you can also contact motorola support to see if they can help you recover your data before getting the phone fixed or replaced under their warranty program.
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.
I did search my terms and didn't come up with anything close to my situation, which is this: I got this phone in 2013, rooted it successfully, but was never able to get TWRP flashed properly, but I was happy with the root, so I sort of ignored the TWRP thing. Now I am getting a replacement phone, LG-V20 VS995 next week, so I decided yesterday to tinker around again with TWRP, as I wanted to put this on the V20.
On the G3 when I flashed(Or so I thought) TWRP and rebooted to recovery, I would get an error message (Very small) in the top left of the screen, then would disappear and I would have to pull the battery to reset and then it would boot fine back to the OS, but not to TWRP.
I made sure I had/have the updated Windows LG drivers, ADB, etc.... and I could see my G3 in Windows properly, the internal device and the microSD, I even pulled up the terminal emulator on the G3 while attached to the PC and ran an ID command I think, successfully. I pulled up a CLI in Windows in my ADB directory and my G3 device showed up as well. Then I tried flashing TWRP, first using Flashify; I started with an older version, like 2.8.6, but it didn't seem to work, so I started going towards the newer versions, but still, Flashify kept saying they failed to flash. So I tried the official TWRP app, and it seemed to be doing the same thing. So I went back to review what I had already done, then disconnected my phone from the PC, rebooted normally and tried again with the TWRP app. I think I was successful with one of the newer versions, 3.1.x so I did the reboot after it said it was successful, but I got that boot error message again, then blank screen and red/blue flashing lights; removed battery and replaced, powered on for normal boot and back in the phone OS again. I checked some YT videos on flashing TWRP on VS985 and it appeared I was doing everything correctly, but then I saw this one video that stated to use the Vol+ and Pwr button (I guess I thought when I selected "boot to recovery" the phone was going to do that automatically), then once you see the LG logo, release the Pwr button, then continue to press the Pwr button all while still holding the Vol+ button down, and then you would go into Recovery mode.
His next words sort of came as a shock - you had to select the option to reset your phone to factory defaults, and THEN, and IF you were successful flashing TWRP, it would take you to TWRP. I thought about this and and decided to do another TWRP flash, and if successful, would try this method. I did and I was able to get into the stock recovery menu, and I did see the option to "Reset phone to factory defaults", but decided just to cancel and went back to the phone OS, and that worked. Later on, I decided to try the "Reset" option on another phone boot, but I've now run into a different issue/error. When I boot the phone, I immediately get the error message (The boot certification verify error), and no matter how many times I remove the battery or for how long, each time the phone boots, I get this error message. The only thing I have been able to do is get into the Hardware Key Control Mode using Vol+Vol-Pwr and just continuing to press them. No matter what option I choose, either Cancel, Mode On, or Mode Off, the phone immediately reboots to the error message; it's like it's stuck in the Recovery boot mode somehow. I'm not sweating it too badly, as I've got a V20 coming next week and I have a work cell I can use for important things, but has anyone run into this type of thing? The way it is now, I cannot view the phone on my PC and cannot seem to get past this boot certification verify error.
EDIT: I am now able to consistently boot into the System Recovery by way of Vol+Pwr button held down until the SR menu shows. HOWEVER, no matter what choice I select, phone reboots and I get the "Boot certification verify" error................ oh well, at least I got an email that my V20 is coming this Thursday.
EDIT: I must be somewhat dyslexic, as the method to get to the SR menu is VOL- (Not Vol+) and Pwr button held down until SR menu entry. Sorry about that
EDIT: I've also seen the "fix" where you remove the back cover, battery, and then remove the top plastic cover over the battery/power/volume, then also remove the metal shield. This is the point where it gets confusing; the author(s) want you to "ground" 2 of the contacts, but it's not clear which ones they are referring to, even with the screenshot, and I'm not electrical engineer, so not exactly sure what they mean by grounding. As I'm getting a replacement tomorrow, I decided not to even explore this technique, although I did dissassemble the phone down to removing the metal plate, so I could try and see if I could figure out what they were talking about (I couldn't). Gotta say, I've had my G3 for over 7 years and for the most part, really loved it; it came in handy during home power outages when the Internet (Cable) went out.
I've been using HTC U11 Plus as my main phone since the day it came out. I absolutely love this phone. In my opinion it's the best phone I've ever had. I never felt the need to get a new phone. I've been gaming, working, etc. and I never had any issue with it.
Two days ago all of a sudden while using my phone it got stuck. None of the button were working and the screen also had response so I pressed and hold the Power button and Volume Down button to boot into recovery mode. So i could clear cache and reboot again but my phone doesn't seem to reboot. It just turns off when I select reboot now. I even tried "Wipe data/factory reset from the Recovery menu options" and then delete all user data option and then Reboot system now to restart your phone. Still no luck. As soon as I press on reboot system my phone just turns off and doesn't reboot or turn on at all.
Even when I put my phone on charging there is not light to indicate that my phone is charging at all.
PLEASE HELP!!!!
Same problem here... Screen flashed white, phone rebooted to encryption screen to enter pin, then powered off... Hasn't been back on since (thins happened in October 2021).
I'm interested in a possible way to get the data off the phone, even if some parts swapping is involved.
PS. I changed the battery thinking it was that, but the phone still isn't coming on or showing the red battery charging light.
I guess it is time for you both to use ADB. When installed properly you should be able to see your phone in device manager on Windows systems. That in itself would be a good starting point. Or just fire up ADB and check if ADB detects your phone. If you are unfamiliar with ADB, Google it.
In ADB use: *.\adb devices* (without the *) If it works properly you should get a return with a device number. You could then flash a boot image or system image or both and see if your phone start's up again.
Hello,
same Issue here.
Solution is to heat up the Phone above 50°C and hold the temperature while it run and copy Data.
I have spend 40h+ to Backup Data and heat up the Phone.
Seems for me to the same problem like the RROD at Xbox360.
Lead-Free solder at the BGA-Chips.