Was following https://forum.xda-developers.com/amazon-fire/general/how-to-amazon-fire-7-2019-9th-gen-t4078133 and got to step 5.6, which was adb reboot after using mtk-su temp root. The device immediately powered off but is not able to turn back on, every after holding every combination of power, power + vol up, and power + vol down for at least 30 seconds each. When the device is plugged into my computer, running lsusb does not show any connected device. Any advice would be appreciated.
I also took off the back cover to try and pull the battery but can not determine how to disconnect the necessary parts, any image guide would also be appreicated.
Idreamofanarchy said:
Was following https://forum.xda-developers.com/amazon-fire/general/how-to-amazon-fire-7-2019-9th-gen-t4078133 and got to step 5.6, which was adb reboot after using mtk-su temp root. The device immediately powered off but is not able to turn back on, every after holding every combination of power, power + vol up, and power + vol down for at least 30 seconds each. When the device is plugged into my computer, running lsusb does not show any connected device. Any advice would be appreciated.
I also took off the back cover to try and pull the battery but can not determine how to disconnect the necessary parts, any image guide would also be appreicated.
Click to expand...
Click to collapse
I did the same thing, I disconnected the battery, tried to do the hardware method to bootrom with shorting the pin and that didn't work either. No USB activity whatso ever.
Bradl79 said:
I did the same thing, I disconnected the battery, tried to do the hardware method to bootrom with shorting the pin and that didn't work either. No USB activity whatso ever.
Click to expand...
Click to collapse
Hold down the Volume Down + Power button to get to Bootloader, then reboot device. Might be Volume Down + Up + Power, but Down and Power worked for me
Bradl79 said:
I did the same thing, I disconnected the battery, tried to do the hardware method to bootrom with shorting the pin and that didn't work either. No USB activity whatso ever.
Click to expand...
Click to collapse
Might be a driver problem. Are you using a live disk?
Michajin said:
Might be a driver problem. Are you using a live disk?
Click to expand...
Click to collapse
I had it connected just fine until i rebooted, I have tried all combos to power on and nothing. It wont even come up in for any usb either
---------- Post added at 08:42 PM ---------- Previous post was at 08:32 PM ----------
its a new Fire 7 I got a week ago, can they patch the HW method to get into bootrom? I metered the pin to ground an I get about 6.80 and when I plug in charger it goes to OL
Related
Let me start by saying, Power + Home does not work. Yes, really. I know there are a dozen threads about Touchpads not turning on, and they all have "Hold power and home for 20s" as the reply. Please don't respond with "Hold Power and Home for 20s". I have tried it.
Background
I took my Touchpad with me on a road trip. I did not have an official car charger, but I had one rated at 1 amp. I used this charger with my Touchpad, and it said that it was not powerful enough (as expected). I figured I would let the Touchpad at least get some juice while it was not being used. The battery steadily drained over the next couple of days, to the point where the screen did not come on. I assumed this was because the Touchpad was completely drained.
Once I got to a location with an actual outlet I used the original Touchpad wall adapter and let it charge for a few hours. The screen still did not come on, and there was no response (sound/light/vibration) from any buttons. I let the Touchpad continue to charge over night with the same result.
The Touchpad has alpha 2 on it.
What I have done
I have tried:
Power + Home for 15s
Power + Home for 30s
Power + Home for 1min
Power + Vol Up for 15s
Power + Vol Up for 30s
Power + Vol Up for 1min
Power + Vol Up + Home for 15s
Power + Vol Up + Home for 30s
Power + Vol Up + Home for 1min
All of the above with and without the Touchpad being plugged in to the wall and PC.
Trying WebOS Doctor (does not recognize a device)
Trying novacom directly (does not recognize a device)
Letting the Touchpad charge for > 1 day and repeating all of the above
Letting the Touchpad sit on the Touchstone for > 1 day and repeating all of the above
Verifying that the AC adapter is secured properly and repeating all of the above
Changing the USB cable and repeating all of the above
Changing the AC adapter and repeating all of the above
Results
The only time I have gotten any indication that the Touchpad is actually doing something is when using Power + Vol Up (and Vol Down) with the Touchpad connected to the PC. Vol Up has the Touchpad recognize as Palm. Vol Down has the Touchpad recognize as QHSUB_DLOAD. If I have the Touchpad connected to the PC in one of these states, Power + Home will reset the device (and Windows will not recognize it until I use Power + Vol Up/Down again).
That is the only response I get from the Touchpad. Anything else I have tried results in nothing.
My current plan is to attempt to let the battery completely drain, and then charge it again. I was previously under the impression that my Touchpad was out of power, but the testing with Vol Up/Down has shown me otherwise. My hope is that losing all power will truly "reset" the device.
Does anyone have any advice on anything else I should try? Is there a way to recover the Touchpad via booting it as Palm or QHSUB_DLOAD?
Volume Up + Power while connected to PC, then run WebOS Doctor?
You may have done this, but have you tried pressing home first and then holding it and power together? I couldn't get mine to start by pressing power and then home, but when I held home first and then power it came right on. If you have done that then disregard this, but if not I hope it helps.
Another method
Try power and Volume down. Hold for a minimum of 30 seconds before giving up. It has worked twice for me when all else failed.
FishDoc
That was very thorough. Once my TP died completely. I plugged it in and it didn't do anything. When I held Power + hitting home 15 times, it would give mea low battery indicator.
I plugged it in and left it over night. By the morning it was on 100%.
DJ_SpaRky said:
Volume Up + Power while connected to PC, then run WebOS Doctor?
Click to expand...
Click to collapse
It may not have been clear since it came after the list, but I did try this. WebOS doctor does not recognize the device in any mode. I do not know if this is simply because I lack the necessary drivers when it is in one of the other device modes. On the off chance that I didn't I will try again when I get home.
Dbarker 2 said:
You may have done this, but have you tried pressing home first and then holding it and power together? I couldn't get mine to start by pressing power and then home, but when I held home first and then power it came right on. If you have done that then disregard this, but if not I hope it helps.
Click to expand...
Click to collapse
I do believe I have tried this, but I will try again when I get home.
FishDoc said:
Try power and Volume down. Hold for a minimum of 30 seconds before giving up. It has worked twice for me when all else failed.
FishDoc
Click to expand...
Click to collapse
It is my fault for leaving it out, but I tried this after exhausting the other options.
chrischoi said:
That was very thorough. Once my TP died completely. I plugged it in and it didn't do anything. When I held Power + hitting home 15 times, it would give mea low battery indicator.
I plugged it in and left it over night. By the morning it was on 100%.
Click to expand...
Click to collapse
I really wanted to avoid the slew of "Hold power and press home!" comments and the followups telling me to hold it longer, hold volume, and all of the other normally recommended fixes. I know how to write a bug ticket or two. I'm also the type of guy who posts a followup with what actually fixes the problem (No "nm, fixed it" from me).
It sounds like my current plan of action is going to mimic what you did. I originally thought the Touchpad was getting no power, so I kept trying to charge it. Now I am waiting for it to lose all power, so I can repeat the process after the device (hopefully) resets. I'm not sure how long that will take since I cannot actually use the device to drain the battery.
Thanks for the responses. Some replies are better than no replies.
So i had a similar situation and tried everything you had mentioned and all the suggestions in the thread. Nothing. No power, completely dead. I even left it
overnight on the charger... nothing. For sure i thought I bricked it. Then, I read online that someone tried the following:
Press and hold Power + Volume Up and click the card (menu) button a thousand times.
Wow! It worked! The TP is alive! In actuality, it only took about 30-50 times (not a thousand) of pressing the menu button while holding power + volume up.
I then got the white USB icon in the middle of the screen and then pressed and held the power + menu button to reboot.
What I did find interesting though is the battery was almost discharged even after having it on the supplied charger (not touchstone) overnight.
Anyway, hope this resolves your issue as well.
No go with Home + Power, Power + Vol Down, Power + Tapping Home
suremail said:
No go with Home + Power, Power + Vol Down, Power + clicking Home
Click to expand...
Click to collapse
Just making sure you read it right since you didn't list it above.
Power + volume up + clicking home button repeatedly.
All 3, same time. Just trying to help.
^ worked for me..thanks
Sent from my HTC Inspire 4G using XDA App
Well this is a really strange one...
Touchpad was completely non-responsive, I'd tried everything above about 5 times and it just wasn't showing any signs of life. I have left it charging all day today.
Assuming it was completely dead, I sat it down. 5 minutes later, it inexplicably just started booting up.
Wish I knew what I did, if anything to make it boot.
I am having the same issue but what got me there was trying to restore my Touchpad via WebOs Dr. It would restore to like 60% or 80% and then say we were unable to reset your device. It kept failing and no ROM was on my the device anymore. When I hold Power+Vol Up+ Home I can hear my PC detect it but that is all it does.
When I get home tonight I am going to try some of the things in this thread.
But what if I cannot get it into recovery? I read that it is near impossible to brick a Touchpad. How can I still recover without getting into recovery?
http://forum.xda-developers.com/showthread.php?t=1394061
Phillip Fry said:
I am having the same issue but what got me there was trying to restore my Touchpad via WebOs Dr. It would restore to like 60% or 80% and then say we were unable to reset your device. It kept failing and no ROM was on my the device anymore. When I hold Power+Vol Up+ Home I can hear my PC detect it but that is all it does.
When I get home tonight I am going to try some of the things in this thread.
But what if I cannot get it into recovery? I read that it is near impossible to brick a Touchpad. How can I still recover without getting into recovery?
http://forum.xda-developers.com/showthread.php?t=1394061
Click to expand...
Click to collapse
not near impossible. I actually bricked mine and had to send it back for RMA.
it got to the point where the hp screen will show, and webos doctor will detect it, but it'll fail when trying to reinstall at about the same percentage as you (maybe less).
menting said:
not near impossible. I actually bricked mine and had to send it back for RMA.
it got to the point where the hp screen will show, and webos doctor will detect it, but it'll fail when trying to reinstall at about the same percentage as you (maybe less).
Click to expand...
Click to collapse
Well I installed Android uninstalled it. Then installed it again and forgot mboot then uninstalled it. So I belive I am back to stock but I wanted to upgrade to 3.0.4 then install Alpha 3.5 as I has having problems with the Touchpad rebooting in both Android and WebOS.
So when do I know if it is bricked. And what do I say to customer support to get it fixed? I just bought the Referbed ones off ebay the other day.
Here's an update...
No luck with anything so far. I caved and decided to take the Touchpad apart to disconnect the battery. I did this and still no screen response. The only changes have been it's a bit more difficult to get it into Palm mode (if it does at all), and now it seems that I can get into QHUSB mode just by repeatedly pressing the vol- button (no need to hold anything else). I do not know if the QHUSB thing was like that before disassembly, or if it is a result of me mucking around.
Unless anyone has any great ideas it looks like I will have to hope HP fixes it in order to tell me it is out of warranty for having Android.
If you send it to Hp and If they can't power it on, I'd say they would definitely replace it. Problem is, I doubt they have any more TP's in stock. Not sure how the warranty would work now being that its a discontinued product.
Hopefully after toying with it enough you'll figure it out and get it powered.
Mine is stuck in download mode too. Still no success.
Here's my experience so far.
Black screen.
When connected to PC :
Home + Vol UP - Device Manager shows PALM (with yellow exclamation) - no driver found.
Vol Down (no need to press home or power) - Device Manager shows QHSUSB_DLOAD (with yellow exclamation) - no driver found.
WebOS Doctor fails to detect device (palm ! in device manager)
I tried forcing novacom drivers on the Palm device (both novacom and novacom-bootie) and then running WebOS Doctor, still refuses to enable next button.
Tried connecting with novaterm, cannot find device. (both novacom and bootie driver).
Power + Home for 15 - 20 secs always resets and clears device from device manager.
I installed QHSUSB Drivers.
now when I Vol Down it installs as a com port (Qualcomm HS-USB QDLoader 9008).
I installed QPST_2.7.323 and am able to see the device as Q/QPC-XXX - ESN=*Download* - Phone Number=*Download* - Banner=*Download*.
I tried resetting the device with QPST, fails to complete the command.
I think I need a new boot.hex to flash to the TP, or a way to force it to charge (if that is the problem).
My Touchpad was low on power when I put it away in the car while on a road trip. I plugged it in to the wall the next day when it wouldn't turn on. After charging overnight, it still refused to power on. That's when I started combing the web for possible solutions.
Please stop posting irrational solutions, such as Power + tap home 5,000,000 times as the few times this did work for others, it was merely coincidence, and power + home would have worked also.
Any rational solutions are welcome.
I may just send it in for warranty. Although I bet that at HP, they will just hook it up to a machine with "special" drivers and re-flash it with Web-OS. I wish they would just let me do the repair myself with the appropriate files.
Who knows, maybe it is a hardware issue, but I doubt it.
I'm having the same problems too. What happened on mine is that my webOS was crashing doing random things like watching videos so I figured I'd just reflash the whole thing. I rebooted and went into the webOS recovery and that's when I think I bricked it. All I got was a USB cable symbol and the touchpad was unresponsive. I couldn't make it do anything and I tried all the appropriate button holding combinations and so I let the power run out over night.
Now when I plug it into the wall all I get is a low battery charging symbol. If I hold the home+power button down the screen will turn off after about 20-30 seconds of holding it down. But when I try to boot into recovery by holding the power+volume up buttons, all I get is the same low battery charging symbol. I'll add that I have had it charging for most of the morning so I don't think it is low battery still. And when I unplug it from the wall I get a symbol of two pronged plug that shows for about 5 seconds and then disappears.
Now when I plug it into the computer, I get the low battery charging symbol for a quick second and then it flashes to the message telling me "To reliably charge, use the cable and power adapter that came with your device" in 5 different languages. When I run webOS doctor I get to the screen where you connect your phone to the usb but it doesn't recognize anything and doesn't let me click next. I was able to have my computer recognize the power+volumedown button as the weird Qhusab thing but my computer said it couldn't find any drivers for it. Now I am not able to reproduce that.
I'm not sure what else to try so if anyone has any suggestions, that would be great. Otherwise I'm going to have to try my luck with HP support.
skiinginstead said:
I'm having the same problems too. What happened on mine is that my webOS was crashing doing random things like watching videos so I figured I'd just reflash the whole thing. I rebooted and went into the webOS recovery and that's when I think I bricked it. All I got was a USB cable symbol and the touchpad was unresponsive. I couldn't make it do anything and I tried all the appropriate button holding combinations and so I let the power run out over night.
Now when I plug it into the wall all I get is a low battery charging symbol. If I hold the home+power button down the screen will turn off after about 20-30 seconds of holding it down. But when I try to boot into recovery by holding the power+volume up buttons, all I get is the same low battery charging symbol. I'll add that I have had it charging for most of the morning so I don't think it is low battery still. And when I unplug it from the wall I get a symbol of two pronged plug that shows for about 5 seconds and then disappears.
Now when I plug it into the computer, I get the low battery charging symbol for a quick second and then it flashes to the message telling me "To reliably charge, use the cable and power adapter that came with your device" in 5 different languages. When I run webOS doctor I get to the screen where you connect your phone to the usb but it doesn't recognize anything and doesn't let me click next. I was able to have my computer recognize the power+volumedown button as the weird Qhusab thing but my computer said it couldn't find any drivers for it. Now I am not able to reproduce that.
I'm not sure what else to try so if anyone has any suggestions, that would be great. Otherwise I'm going to have to try my luck with HP support.
Click to expand...
Click to collapse
Having the EXACT same problem....anyone have any solutions to this? WHy is this happening?
It's a long shot, but it might help if you are getting to the USB symbol on the Touchpad .
I spent hours trying to connect with no luck with the Touch pad in that state. I rebooted my PC and it connected to the TP right away. (I was using a Win 7 64 bit PC.)
Hi Guys,
I Hope this helps someone because i was tearing my hair out trying to figure this thing out! My lovely perfectly assembled blemish free HTC one was a paperweight
Thought i would update you about a fault that developed on my HTC one 801n On the three network in the UK.
Let the phone battery die as i forgot to put it on charge.
The phone would not turn back on. It would not accept charge and would not connect to PC.
Steps tried:
USB charger < 2 Hours
Genuine HTC One Wall Charger < 24 Hours
Attempting to load boot loader to enable fast boot.
Attempting connection with pc to use ADB to reboot or enter fast boot.
Holding Both volume keys and power keys for 2 Mins
Shining a bright light whilst attempting to turn on (weird i know but apparently it can fool the sensor - reported in some forums)
No LED came one whilst attempting to charge.
After several hours of tinkering i managed to get the LED charging light to come on using volume Up and holding the power button whilst connecting to USB port of a PC directly and the device got warm. I then after 2 Hours connected it to a wall charger for 24 hours. its still would not boot.
Attempted after leaving it for several hours and the LED flashed red but would still not boot.
Managed to get the Solid red charging light to come back and ADB fast boot could not connect to device.
Ran through all troubleshooting steps with HTC. It looks like the battery went below a minimum accepted voltage and therefore as a safety wont accept charge. Im not the only person to have this issue but I've noticed that its mainly rooted users that had the problem and there is a chance the custom recovery that is allowing the drop if fastboot is enabled. I cant confirm this as I'm not technically minded but the circumstances between mine and other peoples issues are similar.
I have managed to get the device to turn on by doing the following:
1) Connect to PC and leave for half an hour and wait until the flashing red LED turns solid RED
2) Open up a ABD fastboot terminal and type fastboot reboot. It will say waiting for device
3) Press and hold volume down and power button and hold until the device vibrates and let go.
4) It will then turn on.
It Seems that the reboot command gets through just quick enough, although the device does not have enough power, whilst attempting to boot into recovery and will load up as normal. Its now working, but just in case there is a fault, I'm getting it replaced as its only a week old and would rather not wait to a point where i cant get a brand new one and would have to wait for a repair through HTC.
My set up was:
HTC 801n
4.2.2 stock rom
rooted (s-on)
CWM Recovery 6.0.3.1
I really hope this helps someone.
How long did u push the vol up + power button until LED come on?
Sent from my GT-N7100 using XDA Premium 4 mobile app
naimmkassim said:
How long did u push the vol up + power button until LED come on?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Couple of seconds worked for me. it will flash and it will either change to a solid LED by itself or to try and force it hold down the power button.
HTC One problem
How you managed to turn flashing LED to solid LED?
I have same problem but I tried all combinations of volume buttons and power button with charge without charge, with bright light, without bright light and so on and so forth. It is charging for almost 24 hours now and still I can't figure this out.
LED is just flashing and that's it.
I will try your advice with ABD fastboot terminal although I never done this.
But honestly I don't think it will turn on.
Cyber-what said:
How you managed to turn flashing LED to solid LED?
I have same problem but I tried all combinations of volume buttons and power button with charge without charge, with bright light, without bright light and so on and so forth. It is charging for almost 24 hours now and still I can't figure this out.
LED is just flashing and that's it.
I will try your advice with ABD fastboot terminal although I never done this.
But honestly I don't think it will turn on.
Click to expand...
Click to collapse
It took me about 2 days of tinkering to eventually get the light on! took connecting it to a USB3 port and then trying to get the lihgt to turn solid red.
The phone itself said it was in an awake state even though the screen was off and the phone would not respond!
HTC One
Well I have problems with your solution. As expected.
I can't use ADB tool because it wont recognize my device since it's off naturally.
I connect it my HTC One and when I try to run ADB it just pops for second lists I believe all commands and shuts off.
So if I could run ADB it would be good to try but I can't get him to run either.
BTW I am following guide for installing ADB and using it.
Do you have any advice?
---------- Post added at 12:52 PM ---------- Previous post was at 12:45 PM ----------
Well ok I did install Minimal ADB and Fastboot tool and tried your advice but no luck.
I am now depressed. Don't know what else to do.
Cyber-what said:
Well I have problems with your solution. As expected.
I can't use ADB tool because it wont recognize my device since it's off naturally.
I connect it my HTC One and when I try to run ADB it just pops for second lists I believe all commands and shuts off.
So if I could run ADB it would be good to try but I can't get him to run either.
BTW I am following guide for installing ADB and using it.
Do you have any advice?
---------- Post added at 12:52 PM ---------- Previous post was at 12:45 PM ----------
Well ok I did install Minimal ADB and Fastboot tool and tried your advice but no luck.
I am now depressed. Don't know what else to do.
Click to expand...
Click to collapse
Well, my devices paperweight issue may have been different to yours.... did you attempt to put it into the Hboot menu before you tried the fastboot command?
The home and back arrow should flash?
Yes I did try to enter Hboot before I tried fastboot command.
Cyber-what said:
Yes I did try to enter Hboot before I tried fastboot command.
Click to expand...
Click to collapse
I dont really know what elese to suggest tbh. If you keep tinkering with it, it will come back to life. they were only the steps that worked for me. Do you get a command error in the terminal window? or does the command get through?
Well it says nothing. After I enter the command it just says "waiting for device" and thats it. I tried power+volume combinations with this command too and still nothing.
Cyber-what said:
Well it says nothing. After I enter the command it just says "waiting for device" and thats it. I tried power+volume combinations with this command too and still nothing.
Click to expand...
Click to collapse
Thats what mine said, waiting for device, and after holding the power and volume down for around ten seconds is when it sprang backinto life.
Is it getting really hot while charging?
kungfudavie said:
Thats what mine said, waiting for device, and after holding the power and volume down for around ten seconds is when it sprang backinto life.
Is it getting really hot while charging?
Click to expand...
Click to collapse
I tried that combination. I even kept pressing it for longer period of time (2 min) and still nothing. But every time when the phone is connected to the PC after I press those buttons after 30-45 sec my Windows constantly plays sound (every 5 seconds) that my USB device has been disconnected. If you know what I mean. And then flashing LED indicator turns off. Then I have to unplug USB and plug it again in order for LED indicator to start flashing again.
It is not very hot. But you can feel it is warm.
Cyber-what said:
I tried that combination. I even kept pressing it for longer period of time (2 min) and still nothing. But every time when the phone is connected to the PC after I press those buttons after 30-45 sec my Windows constantly plays sound (every 5 seconds) that my USB device has been disconnected. If you know what I mean. And then flashing LED indicator turns off. Then I have to unplug USB and plug it again in order for LED indicator to start flashing again.
It is not very hot. But you can feel it is warm.
Click to expand...
Click to collapse
That shows that windows is detected the usb hardware. Have you tried any other commands? when you plug registered as anything? and disk drive or anything like that?
kungfudavie said:
That shows that windows is detected the usb hardware. Have you tried any other commands? when you plug registered as anything? and disk drive or anything like that?
Click to expand...
Click to collapse
When I plug it in it just plays that sound that USB is connected and that's it. I went to device manager to the USB section of the list and there is no sign of my phone. Also it's not detected in any other way but that Windows sound that USB is plugged in.
Honestly I haven't tried any other command then [fastboot reboot & fastboot recovery].
Cyber-what said:
When I plug it in it just plays that sound that USB is connected and that's it. I went to device manager to the USB section of the list and there is no sign of my phone. Also it's not detected in any other way but that Windows sound that USB is plugged in.
Honestly I haven't tried any other command then [fastboot reboot & fastboot recovery].
Click to expand...
Click to collapse
Do you have USB debugging enabled?
try adb reboot bootloader
If its being detected, the adb may be able to trigger a reset.
kungfudavie said:
Do you have USB debugging enabled?
Click to expand...
Click to collapse
How to enable USB debugging when my phone is dead?
Cyber-what said:
How to enable USB debugging when my phone is dead?
Click to expand...
Click to collapse
Do you have it enabled? as in, was it enabled before your phone died?
kungfudavie said:
Do you have it enabled? as in, was it enabled before your phone died?
Click to expand...
Click to collapse
Yes. It's always on. Because when I plugged it in when it was working I could see USB debugging mode tuned on. By default both my HTC One and Desire X have it on.
I was checking my phone right now because its since last nigh on charger its very hot.
I read on some thread on this forum that some guy left it on charger for whole 4 day until his LED indicator flashed solid red and then he was able to turn it on.
Cyber-what said:
Yes. It's always on. Because when I plugged it in when it was working I could see USB debugging mode tuned on. By default both my HTC One and Desire X have it on.
I was checking my phone right now because its since last nigh on charger its very hot.
I read on some thread on this forum that some guy left it on charger for whole 4 day until his LED indicator flashed solid red and then he was able to turn it on.
Click to expand...
Click to collapse
can you try running abd and typing:
adb devices
That should see if its detecting it
I just did that and it says "List of devices attached" and there is nothing else except that line.
Phone does not power on or charge...i
I was out during the day and when I tried using my phone it wouldnt turn on. I thought maybe the battery was dead. I didnt think much of it. I come home and tried charging it and led light doesnt come on. Now I'm really worried. I've tried most of the tricks including
- Press and hold power for 2 mins
- Press and hold power + vol up for 2 mins
- Press and hold power + vol down for 2 mins
- Hold phone under bright light and press and hold power + vol up for 2 mins
- Hold phone under bright light and press and hold power + vol down for 2 mins
- Connect to computer via USB. Computer does not detect phone device.
- Removed SIM card and repeated steps 1-5
What else can I try? What can I do to check if my phone is completely dead. This phone is only 1.5 years old.
crazyboy867 said:
I was out during the day and when I tried using my phone it wouldnt turn on. I thought maybe the battery was dead. I didnt think much of it. I come home and tried charging it and led light doesnt come on. Now I'm really worried. I've tried most of the tricks including
- Press and hold power for 2 mins
- Press and hold power + vol up for 2 mins
- Press and hold power + vol down for 2 mins
- Hold phone under bright light and press and hold power + vol up for 2 mins
- Hold phone under bright light and press and hold power + vol down for 2 mins
- Connect to computer via USB. Computer does not detect phone device.
- Removed SIM card and repeated steps 1-5
What else can I try? What can I do to check if my phone is completely dead. This phone is only 1.5 years old.
Click to expand...
Click to collapse
Go to your Windows devices manager then connect the phone and check if its detected as QHSUSB_DLOAD or anything else with "qualcomm".
alray said:
Go to your Windows devices manager then connect the phone and check if its detected as QHSUSB_DLOAD or anything else with "qualcomm".
Click to expand...
Click to collapse
Hey Alray! Good to see you here!
Sadly, even I have encountered the same problem as above, and have also tried the recommended solutions/steps, but to no avail. Also, I'm on an iMac. Any steps for this platform?
Without using a charger press and hold down the power and volume down keys for two minutes; release after two minutes, plug a wall (not a usb to computer) charger; the phone will flash a red (orange) light and reboot several times with the battery logo....don't mess with it, eventually it will go solid red (orange) and boot; the moment you get to your icons immediately kill the display. It may flash up a few times, just kill the display and let it fully charge. I about freaked out when I couldn't get mine started after misplacing it for months and finding it and it was as dead as dead can be, but it started after I looked up how to get it to start; hope this helps. Cute signature, almost true though!
alray said:
Go to your Windows devices manager then connect the phone and check if its detected as QHSUSB_DLOAD or anything else with "qualcomm".
Click to expand...
Click to collapse
Hi, I have the same problem and the phone is recognized like this
qcserial 2-1:1.0: Qualcomm USB modem converter detected
what can I do to repair this device?
Thanks!
Walo said:
Hi, I have the same problem and the phone is recognized like this
qcserial 2-1:1.0: Qualcomm USB modem converter detected
what can I do to repair this device?
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=67026330&postcount=10
Sent from my HTC One using XDA Labs
alray said:
http://forum.xda-developers.com/showpost.php?p=67026330&postcount=10
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
OK, so the phone is dead, thnkz
Enviado desde mi XT1095 mediante Tapatalk
Recently i got my Honor 9 lite and in a few weeks i managed to install openkirin Resurrection remix. all was good till i decided that i was having ram issues so i then found out about project treble.
This is where the original problem started I used the ARM A Decendent rom and i flashed it to a bootloop. whenever i tried to go back to stock or RR i'd have the same thing. i've tried many things but eventually i made a batch file to erase and reflash all of the stock software.
now i made some typos and the kernal didn't flash. now im stuck with a brick that wont turn on. im ****ting myself. im very scared and i desperately need help. im a ****ing idiot.
Atleast when i plug it in my computer detects it as "USB Ser"
UPDATE: i installed some kind of driver on my PC. it now shows up as "HUAWEI USB COM 1.0 (COM 7)"
I'm actively looking for board software to fix this issue. if you are able to obtain it. DM me on telegram: @AmethystLegit
Its for a LLD-L31
+ I cant get into fastboot
Ok power the phone off fully so whilst it is plugged in your computer press and hold the power button till USB item is removed from the device manager now press volume up and plug the USB cable into a charger see if it will boot into recovery mode from there, then download the firmware from that area.
Sent from my LLD-L31 using Tapatalk
hacktrix2006 said:
Ok power the phone off fully so whilst it is plugged in your computer press and hold the power button till USB item is removed from the device manager now press volume up and plug the USB cable into a charger see if it will boot into recovery mode from there, then download the firmware from that area.
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
Hmm. i've held the button down but it only restarts. i've had it plugged in for awhile now and windows made a disconnect sound a few times. it hasn't unplugged itself. maybe ill check the device manager once thats happened again. and then ill hold vol up
AmethystLegit said:
Hmm. i've held the button down but it only restarts. i've had it plugged in for awhile now and windows made a disconnect sound a few times. it hasn't unplugged itself. maybe ill check the device manager once thats happened again. and then ill hold vol up
Click to expand...
Click to collapse
It literally just happened. the item is still there. i guess we could run it out of battery
That could be one way or press and hold the power button for 10 seconds whilst disconnected from USB and hold the volume up button then plug the USB in while it's connected to a charger, the only pins needed is the power pins not data pins. volume up trick doesn't work whilst data pins are working I.E connected to PC you must use a phone charger.
Sent from my LLD-L31 using Tapatalk
hacktrix2006 said:
That could be one way or press and hold the power button for 10 seconds whilst disconnected from USB and hold the volume up button then plug the USB in while it's connected to a charger, the only pins needed is the power pins not data pins. volume up trick doesn't work whilst data pins are working I.E connected to PC you must use a phone charger.
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
Assuming the cable that came with the phone is a phone charger and not data. its not working. i dont think i have any of such around. ill try running the battery out.
meanwhile im now actively looking for board firmware to try a different method but i've gotten nowhere
The cable with the phone also has the data pins, else how would you transfer your files, please try using the Charger and Volume method like i suggested.
So here is the situation...I bought my wife and I X4s from Google Fi about a year ago and my wife has recently been complaining about her power button not working (though it still functions via the thumbprint). At first I thought it was her abusing the phone (like the last 3 she has destroyed) but because of her insistence that this time was different and the fact that this is a common failure mode of these phones (example 1; example 2), AND the fact that Google had a 1 day, 1/2 price sale on Pixel 3s, I got her one of those.
So now I have a backup phone that has a broken power button with a workaround. What is the best way to prolong the life of the battery in that phone? Let it power down and leave it idle for a year? Always keep it plugged into a low power USB power source?
PS - any easy way to get chop/chop->flashlight and swivel->camera on onto a Pixel?
Best way is to charge the battery to around 60% and then power off.
Leaving the battery alone for one year with a 1% or a 100% charge would definitely damage it.
That is consistent with other lithium ion battery management (non-cell phone) advise I have found in research and I am going to do it that way. The problem I encountered was that, I can't just power down (broken power button).
That being said, I did find the following using adb/fastboot:
To power down: adb shell reboot -p
This brings the X4 to a powered off state and when plugged in shows a recharge status. However, when you plug it in, it will NOT allow you to do anything without the power button.
To power up: hold volume down and plug into computer. This should bring you to the fastboot menu. On the computer type: fastboot continue That will bring you back in as normal.
Another update. Since it is now my backup phone, I am experimenting. I followed the below instructions to unlock the bootloader and root the phone and it essentially worked perfectly (instructions wise):
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-root-moto-x4-install-twrp-t3806460
Because my power button is broken, I had to modify the instructions. Instead of booting into TWRP after installing (which requires the use of a power button), I just pushed the twrp image again and then installed magisk.
Note that Motorola's unlock site was sort of down when I did it but there is a forum that Moto regularly checks if you run into problems which is here:
https://forums.lenovo.com/t5/MOTORO...-Unlock-Problems/td-p/3222809/highlight/false
And yet another update. After I rooted, I installed Custom Quick Settings and created a Reboot quick setting to replace the functionality lost with the power button. There is also a reboot into recovery option that should allow you to get into twrp.
Also, if your power button is broken, you need use the thumbprint as your unlock because otherwise, you won't be able to wake up the phone. I don't know if this works with the noNavigationBar setting but I don't want to risk it.
sleze said:
To power up: hold volume down and plug into computer. This should bring you to the fastboot menu. On the computer type: fastboot continue That will bring you back in as normal.
Click to expand...
Click to collapse
My phone's button is still not broken, so I did a
fastboot oem off-mode-charge disable
Click to expand...
Click to collapse
and now it powers up when I connect it to a charger.