How to pull data from a dead phone using adb? - LeEco Le Pro3 Questions & Answers

Hello, my le pro3 suddenly died today while using it. Now it's completely unresponsive even after charging for a few hours and it's only detected as adb interface on pc. I tried "adb pull sdcard/dcim" command but it says connection failed. What can i do?

Related

[Q] Both USB Debugging and ability to mount gone

So, last night I decided to install ali ba's CM 7 build. After a few false starts, I ended up with a boot loop. Since then I reverted with fastboot using a LEGEIMG.zip, and I can't mount my microSD card via my phone anymore. USB Debugging is all but gone, I can access it for maybe a minute and then it dies.
To be clear, the icon on my phone indicating that USB Debugging is active, but `adb devices` stops showing it after a minute or so.
When I plug in the phone, Windows tells me "USB Device Not Recognised". I've tried removing and re-installing HTC Sync.
I'm lost for where to go right now, suggestions?
Thanks
ldunn said:
So, last night I decided to install ali ba's CM 7 build. After a few false starts, I ended up with a boot loop. Since then I reverted with fastboot using a LEGEIMG.zip, and I can't mount my microSD card via my phone anymore. USB Debugging is all but gone, I can access it for maybe a minute and then it dies.
To be clear, the icon on my phone indicating that USB Debugging is active, but `adb devices` stops showing it after a minute or so.
When I plug in the phone, Windows tells me "USB Device Not Recognised". I've tried removing and re-installing HTC Sync.
I'm lost for where to go right now, suggestions?
Thanks
Click to expand...
Click to collapse
I had the same problem. I'm not sure how to get ADB back, but I can help you with the MicroSD mount problem. Go into Fastboot on your phone, with it plugged into your computer. In the cmd prompt navigate to the folder where adb devices is and type fastboot oem enableqxdm 0
Let me know if you figure out the adb bit. I'm still trying to fix it.

Won't charge/power on

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

Nexus 6p boots into fastboot, not detected by pc

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

H E L P - bootlooping, COM does not recognize phone

Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p.
this situation is the same when I connect the phone when it is alive.
I have installed adb and fastboot with this software
https://forum.xda-developers.com/showthread.php?t=2588979
with the 1.4.3 version it shows in the end of the process "0 files copied" and then I tried the 1.3 version and it showed that 4 files were copied but it also showed an error.
I have also downloaded ADB from google site but it does not work either.
When I try to open the powershell in a folder where I have downloaded an img and type in a fastboot command the computer doens't recognize any type of command.
So if anyone can help me ill be glad.
Thanks in advance,
Matan.
matan4442 said:
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p. Matan.
Click to expand...
Click to collapse
What is the new device identified as....Qualcomm HS-USB QDLoader 9008? Your phone may be stuck in EDL mode. If that is the case you need to search XDA and attempt solutions for that problem first.
Did you previously have your PC setup properly with the correct USB drivers and it was working OK, or just now trying to get your dead phone to communicate? If the former it may be the EDL issue above. If it was the latter, the communication problem may just be the drivers were never set up in the first place. Have you tried a different cable or port on your PC, or another PC?
With no access to the OS you will be unable unlock the bootloader or access to ADB because those have to be enabled FIRST in the OS, so there's no helping you here until you can actually boot into the OS. Do you have access to Recovery mode? Tried a factory reset? If you don't have recovery, that was a major omission.

Redmi Note 7 not Booting after pushing adb_keys.pub

My Redmi Note 7 recently broke and the screen was not responsive and had no display. But it was still booting at that time. I can feel the vibrations when placing my finger on the fingerprint scanner.
USB Debugging was enabled, but my computer was not authorized.
I tried to generate adb key from my computer so that it would be authorized by my phone.
I entered recovery on my phone and used adb to push the adb_keys.pub into the /data/misc/adb directory.
After that, I rebooted the phone via the command 'adb reboot', but every time, it just reboots to the recovery. I know this by using 'adb get-state'.
I took the logcat and attached them here. Hopefully someone can help me. Thanks!

Categories

Resources