Hi,
I own an HTC Panache, never rooted it or anything. Yesterday I factory reset my phone, battery must have died while trying to sync all my apps. Now the phone won't turn on or charge (no indicator light for charging). I tried to load into recovery, doesn't work either. When I plug it into my computer it get's recognized in device manager as "other device" even though I believe I have the drivers installed, and it won't try to mount the sd-card. Finally "adb devices" will return nothing in cmd.
Do you think it's a dead battery problem, and could I recover from this?
Thanks,
Corey
corey.t.m said:
Hi,
I own an HTC Panache, never rooted it or anything. Yesterday I factory reset my phone, battery must have died while trying to sync all my apps. Now the phone won't turn on or charge (no indicator light for charging). I tried to load into recovery, doesn't work either. When I plug it into my computer it get's recognized in device manager as "other device" even though I believe I have the drivers installed, and it won't try to mount the sd-card. Finally "adb devices" will return nothing in cmd.
Do you think it's a dead battery problem, and could I recover from this?
Thanks,
Corey
Click to expand...
Click to collapse
I just wanted to add that my computer is recognizing the device as "QHSUSB_DLOAD"
I found this link that makes it possible to undo this for the HTC Sensation, has anyone tried this on a panache/mytouch4g
http://forum.xda-developers.com/showthread.php?t=1522351
what do u mean by "adb devices" will not return anything?
just so its clearer for others....
u didnt root but installed adb drivers properly? (or just opened cmd & typed adb devices?)
here is a link you can try to make sure u have adb installed correctly & try to downgrade to stock with temp root...or just might as well go all the way
Related
So I am installing the Nexus 7 in my car as the head unit, but am now stuck with this issue.
I unlocked, and rooted the device, and used the fastboot oem off-mode-charge 0 command and it worked.
Anytime the Nexus 7 receives power it turns on.
However the device battery died completely and now when I plug it in to charge, the screen stays black, buttons do nothing, and eventually it boots up, but immediatley powers off as the battery is at 0 % and has the red ! mark.
I can't even use the fastboot command to reverse it since the device can't stay on.
What the heck can I do?
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Username invalid said:
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Click to expand...
Click to collapse
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
@Username invalid
Yes, but will the command be executed before the device dies again?
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
When you're in bootloader, you don't need debugging enabled since the fastboot protocol comes into play, not ADB (which requires debugging to be enabled). Root is also unnecessary. At least that's what I have learnt in the past 5 months I have had this.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
sgt. meow said:
@Username invalid
Yes, but will the command be executed before the device dies again?
Click to expand...
Click to collapse
There is not enough time for me to set debugging on before the device dies. It stays on for maybe 5 seconds at the home screen then powers off.
Is there a way I could charge the battery a little bit bypassing the Nexus?
Can I splice in the pos and neg of the usb charger to the pos and neg of the battery?
I'd highly discourage the battery direct charging bit.
Username invalid said:
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
Click to expand...
Click to collapse
I'm not sure at all.
I used the R3 Nexus 7 Superboot to push the original command. I had downloaded fastboot from somewhere else, and put it in the Superboot folder to get it to push the command.
By the way sorry for taking so long to reply in between. Since I am a new user, I have to wait the 5 minutes in between posts.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Username invalid said:
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Click to expand...
Click to collapse
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Jeremi1023 said:
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Click to expand...
Click to collapse
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I will do that and let you know what I see.
Just gotta wait for the thing to turn on. It's very random right now.
Okay, I was able to get into bootloader, and I I did "fastboot devices" and nothing came up.
Also checked device manager and no Android or anything like it in there.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Jeremi1023 said:
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Click to expand...
Click to collapse
http://d-h.st/kDu
Username invalid said:
http://d-h.st/kDu
Click to expand...
Click to collapse
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Jeremi1023 said:
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Click to expand...
Click to collapse
Uninstall your current one first.
Username invalid said:
Uninstall your current one first.
Click to expand...
Click to collapse
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Jeremi1023 said:
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Click to expand...
Click to collapse
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Username invalid said:
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Click to expand...
Click to collapse
Yeah I have a desktop I could try it on.
I've never plugged the Nexus in to the desktop, so it should be a complete clean install of drivers.
If Windows recognizes the nexus on the desktop, what should I do?
Do I need to uninstall anything it may install on its own?
I figure I will end up installing the drivers you previously provided.
SOLVED!
Hello All.. I have searching for hours not making much progress. Last night my LG G2 ran out of battery and I plugged it into the car charger and it soft bricked. I've been pretty busy lately so I'm on an old ROM Optimus DE 2.2. I don't have the ROM saved and I've been trying to ADB sideload the ROM back onto my phone but in the command prompt it says device not found. I tried installing some generic drivers and that didn't work. I tried the LGUnitedMobileDriver and that isn't working either.
I'm not sure what to do next. I have ADB on my computer and ADB sideload on my TWRP recovery, so I would like to push the ROM on my phone so I can flash it without having to wipe my phone. What drivers do I need; right now my phone shows up under other devices in device manager. Or am I sideloading wrong? Any help please lol..
I was caught off guard because of the random soft brick. If I would have been working on my phone I would have had the proper backups made. Thanks for any help, it is much needed I need my phone back ASAP!! Thanks again.
SOLVED
Finally figured it out. I had to updated my device (LG G2) with the ADB drivers not the LG drivers.
I went into Device Manager, right clicked my phone, clicked update driver software, clicked browse my computer, clicked let me pick from a list of drivers, then selected ADB drivers, then selected HTC Dream Composite ADB Interface. I believe the drivers I last installed were Snoop05's adb-setup-1.4.2.
Then I did a backup in TWRP, then I sideloaded the ROM. Next I had to wipe everything but internal memory and the use Nandroid Manager to restore my data from the backup... Took my whole day but at least I have a phone again.
The car charger soft bricked it ?
So you have TWRP, the drivers you can get from the LG site too. Just search for your model and go to software update section. This is for D802, i dont know if the drivers are the same: http://www.lg.com/uk/support-mobile/lg-D802
Hmm..i dont know how to use the sideload..
Another way can be with USB flash drive and OTG cable, i used my usb flash drive with OTG cable to flash ROMs from TWRP
Last option is lg flash tool and then reroot
Thanks for your help guys.. I appreciate it! Looks like I just needed to update my phone with the ADB drivers in Windows 8 Device Manager. I'm back up and running.
But yea so weird.. I haven't flashed anything on this phone in months so I guess something was corrupted when it died. I think it was trying to boot with too low of a charge and the battery died mid boot which corrupted something.
Although you've solved it let me recommend you another way.
Use : "adb push romname.zip /sdcard/romname.zip"
instead of "adb sideload romname.zip"
Hello Guys,
I am really clueless about what to do...
Heres my Problem:
"Accidentally" wiped everything on my phone including the Stock Rom ( was stuck in Bootloop...)
I have access to Bootloader and TWRP Recovery(v2.8.7.0) but whatever I try my phone isnt showing in the device manager. Actually there isnt even this "plugged-something-in" sound when I plug in the phone to my PC. (Win10)
Already tried to install UniversalADBDrivers/NakedDrivers/GoogleDrivers....
Device Manager just isnt reacting when I plug in my phone.
Can someone help?
*Push*
BTW: It is charging ....
Ilthiaros said:
*Push*
BTW: It is charging ....
Click to expand...
Click to collapse
Boot into recovery and using adb.exe, type "adb devices". Does it see anything?
Had the same
Hi!
I've made the exact same with my Nexus 4 two month ago.
I wanted to update my ROM, a DirtyUnicorn v9.6 to the v9.7, i've also got the bootloop, and my w10 didn't recognise my N4 when plug-in (only as "Android device")
After a lot of googling, i gave up (i didn't have the time to repair it), and gave it to a "repair shop".
The "repairman" explain to me that the firmware was broken, and he need to take a "developpement-kit" (from Google or LG, i'm not sure) to install a new firmware.
It takes 2 weeks for him to identify the problem, try many firmware, and restore the phone to the last stock rom.
It cost me 50€ to repair the phone (is it expensive?).
I hope my little story will help you, and you will not have to pay for the repair :good:
P.S i'm French be nice to my English, please (and that's also why some world are in "..." )
Thx for the replies
... but....
I think IF it would show up as "android device" I could use adb and bring it back to life... problem is... it isnt showing up as anything... neither does my PC is doing that "USB is plugged in Sound".
@fr3quency I tried that alrdy it isnt showing any devices for adb or fastboot commands and yes it could be a driver Problem but as I said before i cant say that because the phone isnt showing up at all ....
Ilthiaros said:
Thx for the replies
... but....
I think IF it would show up as "android device" I could use adb and bring it back to life... problem is... it isnt showing up as anything... neither does my PC is doing that "USB is plugged in Sound".
@fr3quency I tried that alrdy it isnt showing any devices for adb or fastboot commands and yes it could be a driver Problem but as I said before i cant say that because the phone isnt showing up at all ....
Click to expand...
Click to collapse
Send it for jtag reflash, cost me around $20 had almost the same issue except I knew bootloader is dead for sure after bad fastboot flash from official firmware. Or ask if usb port diode could be damaged so it doesn't recognize it, should cost nearly same price and it is possible to be problem instead.
Ilthiaros said:
Thx for the replies
... but....
I think IF it would show up as "android device" I could use adb and bring it back to life... problem is... it isnt showing up as anything... neither does my PC is doing that "USB is plugged in Sound".
@fr3quency I tried that alrdy it isnt showing any devices for adb or fastboot commands and yes it could be a driver Problem but as I said before i cant say that because the phone isnt showing up at all ....
Click to expand...
Click to collapse
I think it's a driver problem. Connect it to some other PC. It happened to be 2 days ago; PC couldn't find my friend's Nexus 5 on neither mtp(OS boot) nor in recovery(Mount > enable mtp) (Universal adb drivers were already installed). And device manager (Windows 10) DID detect the device. It just wouldn't show for some reason. Just find another PC and try. Android drivers like to fk us up. :3
Thank you guys i just repaired it
It was a Hardware Problem. Just replaced the Micro USB Circuit Board and it is working(Damaged it myself during display replacement)
I was just having this same issue, then I plugged in my phone directly to the motherboard, so the slots in the back, and it was recognized!
I know that there is countless posts out there on how to do just this, but for me it is just not working.
I just got this phone via warranty replacement one week ago and all of a sudden the screen is unresponsive. The whole phone works, can open camera, take screen shots, everything. I just can't touch the screen.
Through the last 3 hours or so I've been trying everything and I finally found someone that had a solution, to delete NextSMS from the phone. Apparently that app has caused other screens to stop responding, my only problem is that I can't figure out how to uninstall it if I can't touch the screen. If I get adb running on my computer and on my phone, and type "adb devices", it returns:
"numbers/letters" sideload
But then when I type "adb uninstall com.handcent.nextsms" it returns "waiting for device..." and nothing happens. the phone never receives a command at all. I have enabled usb debugging before on my phone, but I fear that I changed the usb mode to charging only so when I had it plugged into my car it wouldn't try to read the device. The only thing I haven't tried is a factory reset because I have pictures and videos on my phone that would kill me if they got deleted. I never got the chance to back it up and already sent my old phone back. My phone is not rooted and is up to date, I have not done anything to it besides doing the SmartSwitch with the previous device to get all my **** onto this phone. I have tried to boot into safe mode as also suggested, but that hasn't worked either, this led me to believe it wasn't apps and actually a faulty phone but the other post I read about the whole handcent thing also tried booting in safe mode and it didn't work either.
To recap I have tried:
restarting
letting the phone die completely
recharging the phone completely
booting into safe mode
deleting the app via adb
opening bootloader (whenever I choose this option, my phone just reboots normally)
deleting via Play Store on my computer (saw guides for this, and I feel like they updated the website to actually take this feature away...)
should I try to install a custom rom? is there anything ATT can do? I'm reluctant to install a custom rom because I don't want to lose the warranty.
I'm slowly coming to the conclusion that since USB debugging isn't on, there's nothing I can do and all my data is lost... Please someone prove me wrong.
Also forgot to mention, when I plug my phone into my computer, it recognizes it as a Samsung-SM-G298A but show it as an empty device with no storage at all. Which basically proves it's not in usb debugging mode iirc.
sound like a hardware issue to me , sent it back for warranty ?
The other day I was trying to flash my 6p back to stock so I can sell it, and I was flashing everything through cmd, until all of a sudden cmd stopped working towards the end for some reason. Now my phone only boots into fastboot mode and is NOT being detected by my pc. When it's plugged in, the fastboot menu says to connect the data cable. I've tried restarting my computer and reinstalling the drivers, but nothing seems to work. When I go into cmd and type adb devices, nothing shows up when it's plugged in, and device manager doesn't show any changes whether it's plugged in or not.
I've called local cellphone repair shops, but apparently if it's not Samsung or iPhone they can't help
Btw I've searched the forums and haven't found a solution to this problem.
Robertdudeman said:
The other day I was trying to flash my 6p back to stock so I can sell it, and I was flashing everything through cmd, until all of a sudden cmd stopped working towards the end for some reason. Now my phone only boots into fastboot mode and is NOT being detected by my pc. When it's plugged in, the fastboot menu says to connect the data cable. I've tried restarting my computer and reinstalling the drivers, but nothing seems to work. When I go into cmd and type adb devices, nothing shows up when it's plugged in, and device manager doesn't show any changes whether it's plugged in or not.
I've called local cellphone repair shops, but apparently if it's not Samsung or iPhone they can't help
Btw I've searched the forums and haven't found a solution to this problem.
Click to expand...
Click to collapse
Can you enter recovery?
No I can't enter recovery