My screen died and would like to know if there is a way to get my data off the device before I have to send it back.
The device is not rooted.
I can put it into bootload mode using my old cappy dongle.
I tried bootloader mode and connected it my PC and ran ADB devices but nothing shows.
Any suggestions?
I would suggest booting normally and copying what you can through your PC's file explorer. If you enabled debugging, you should be able to pull the files through ADB.
Related
so, stupid question time.
i've used ADB in the past and its worked great so not sure whats going on this time around.
I get the following errors when trying to start adb:
"daemon still not runningerror: cannot connect to daemon"
I have installed moto drivers for droid 3 (32bit), im on win7 32bit. I have my phone on dev mode, and charge only. I have run CMD with admin rights. and still ADB wont turn on.
I have also tried using the new one click method:
http://rootzwiki.com/showthread.php?t=3714&p=75934
anyone have some direction? I did kill adb from my running processes (all instances) and tried all over, no go, same error.
help?
Did you put the phone is PC Mode as opposed to USB Mass Storage?
its supposed to be done in Charing only mode, the issue isn't on my phone setup, it got to do with my darn computer, I can even do an adb devices command... may have to remove the sdk completely and start over.
Put in charge only, use one click method
Sent from my DROID3 using xda premium
did you change directory in cmd to the folder that adb is in?
...I had to change to the folder like this cd\program files (x86)\android\android-sdk\platform-tools
The one-click root method is bundled with adb.exe. Except for the driver and a USB cable, it contains everything needed to root.
First of all, i have tried to solve this problem for hours and so far i don't have found anything that could help me.
So my screen is broken, completetely black, and i would like to save some files from my galaxy S(files are NOT on external SD card). Connecting phone to computer doesnt help because i should turn mass media mode on, and thats kind of hard when the touch screen is not working. Kies recognizes my phone(tries to connect), but can't connect because i should turn some other mode on? I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
tuotanin said:
First of all, i have tried to solve this problem for hours and so far i don't have found anything that could help me.
So my screen is broken, completetely black, and i would like to save some files from my galaxy S(files are NOT on external SD card). Connecting phone to computer doesnt help because i should turn mass media mode on, and thats kind of hard when the touch screen is not working. Kies recognizes my phone(tries to connect), but can't connect because i should turn some other mode on? I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
Click to expand...
Click to collapse
Hi,
I have a solution for you
No need to turn on mass storage.
What you need:
USB cable
Working pc
Android SDK http://developer.android.com/sdk/index.html
USB Driver http://developer.android.com/sdk/win-usb.html
1. Download and install this tool: http://de.codeplex.com/releases/view/107423
2. Boot your phone into recovery (worked for me) ( volume up+home+power)
3. Connect your usb cable
4. Start Droid Explorer and search for your sd card
cixty said:
Hi,
I have a solution for you
No need to turn on mass storage.
What you need:
USB cable
Working pc
Android SDK
USB Driver
1. Download and install this tool:
2. Boot your phone into recovery (worked for me) ( volume up+home+power)
3. Connect your usb cable
4. Start Droid Explorer and search for your sd card
Click to expand...
Click to collapse
Thank you for your answer. I think i can't get my phone into recevory mode. At least Droid explorer doesn't find it. When i try to boot it into recovery, my computer makes that "connected sound" several times, so i think the phone really is broken... Also, when the phone is connected to computer with usb cable, and i put the battery into the phone, i can hear that connected sound immediately, so i guess the phone automatically boots on? Well i keep trying but i think it is not possible to boot this phone into recovery mode
tuotanin said:
I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
Click to expand...
Click to collapse
What you need therefore is a (rooted) phone and USB debugging must be enabled - at least I never tried withouit thos options turned on. Since you don't need to do sthg with su I think technically you can go without root as well, but did never run it without so not sure on that. Hope you had USB debugging active before your screen broke...
Install the adb tools on your pc if you haven't already. (google is your friend )
What you want to do now is connect your phone to the PC, open up a terminal session (within windows e.g. execute -> cmd ) and then fire up those commands:
Code:
adb
lot of stuff, ignore - if it doesn't work: google installing drivers and the adb tools
Code:
adb devices
here your phone should be listed if it is in debugging mode.
then just
Code:
adb pull [pathToYourHolidaypics] [pathToSaveOnHarddisk]
so for example:
Code:
adb pull /sdcard/DCIM Holidaypics
and you photos should be rescued. Good luck!
2 Be said:
What you need therefore is a (rooted) phone and USB debugging must be enabled - at least I never tried withouit thos options turned on. Since you don't need to do sthg with su I think technically you can go without root as well, but did never run it without so not sure on that. Hope you had USB debugging active before your screen broke...
Install the adb tools on your pc if you haven't already. (google is your friend )
What you want to do now is connect your phone to the PC, open up a terminal session (within windows e.g. execute -> cmd ) and then fire up those commands:
Code:
adb
lot of stuff, ignore - if it doesn't work: google installing drivers and the adb tools
Code:
adb devices
here your phone should be listed if it is in debugging mode.
then just
Code:
adb pull [pathToYourHolidaypics] [pathToSaveOnHarddisk]
so for example:
Code:
adb pull /sdcard/DCIM Holidaypics
and you photos should be rescued. Good luck!
Click to expand...
Click to collapse
Thank you for your answer. Unfortunately, this method doesn't find my phone either.. I think that USB debugging mode was on but can't say for sure. Maybe my Samsung is just completely broken. I guess we are out of ways to recover files . Thank you for your help and of course feel free to post anything if anybody have any idea.
tuotanin said:
Thank you for your answer. Unfortunately, this method doesn't find my phone either.. I think that USB debugging mode was on but can't say for sure. Maybe my Samsung is just completely broken. I guess we are out of ways to recover files . Thank you for your help and of course feel free to post anything if anybody have any idea.
Click to expand...
Click to collapse
if usb debugging off, mtp still working so pc must detect ur fone unless its already not working.if pc recognised ur fone when plugged in, use any partition backup app in pc to backup da entire partition
n i m sorry if its doesnt help u
Sent from my GT-I9000 using xda premium
compacity said:
if usb debugging off, mtp still working so pc must detect ur fone unless its already not working.if pc recognised ur fone when plugged in, use any partition backup app in pc to backup da entire partition
n i m sorry if its doesnt help u
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
It should be in USB storage mode. I dont know what mode is on atm. Even Kies doenst recognize phone
Hello, looking for a bit of help with a problem. I broke the screen on my Nexus 6 a few days ago, and I'm trying to get access to the phone again. The screen is completely black, no image whatsoever, but the phone is still working fine (apparently, even the digitizer--the phone started ringing, so on a whim I swiped to answer the call and it worked fine). It was completely stock without root and with USB debugging disabled (I'm kicking myself for that, it was turned on until a week or so ago). It is locked with a PIN. I managed to use Wug's Nexus Root Toolkit to boot into TWRP, then used ADB to back up all the files on the device. Unfortunately, I'm waiting on a Nexus 5x to be delivered and won't get it for another few days, so I'm looking to access the text messages on the device. I've been trying to use this tool to access my phone from my computer, but the problem is that USB debugging is disabled. I tried following these instructions to enable USB debugging from recovery using ADB, but it doesn't seem to be working. First I received errors saying that the files were read-only when attempting to write to build.prop, but using this StackOverflow question and answer I remounted it and the commands seemed to work. However, after rebooting the phone it doesn't show up in ADB Devices. It does appear to have rebooted fully--I'm hearing notifications periodically again--but I'm guessing the method to enable USB debugging failed. Does anybody have any other suggestions for how I can get USB debugging enabled?
I just used adb pull to get the build.prop and default.prop, it looks like the build.prop had the changes I made in there, but the default.prop didn't. I made the changes manually and pushed my edited default.prop over, but it's still not showing in adb.
hello
dropped my N6 on to a marble floor, the screen is black and touch is not responding. the phone seems to be working otherwise. usb debugging is off, the phone is fully stock (stock recovery, bootloader is locked, encryption is the marshmellow default, phone is not rooted). There is no lockscreen pin or pattern, just the standard slide to unlock. photos are not auto-backed up online, so I need access to the phone itself.
when I plug the phone into my computer, I cannot file explore it because I need to enable a prompt on the phone to MTP instead of charge only. as USB debug if off I cannot use ADP PULL / SDCARD.
I have two ideas:
1) use Wug's nexus root toolkit and do something there like put TWRP on, and then use TWRP to avoid the USB debug being off. I'm not sure on the details of this though! Any guide on the steps here? the power and volume hardware keys work, so in theory I can get into recovery with the right steps.
2) get a micro-usb hub, and plug in a wired mouse as well as connect to my computer, then blindly click about hoping that I enable MTP or USB debugging. I can then either copy files off in windows explorer or use Vysor to control the phone over ADB and email files etc as needed. Would this work? I don't have a hub so would need to spend £5-10 buying one
Many thanks in advance for any help!
Option 1 won't work because the bootloader is locked. You'll have to try option 2.
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
vulcanrvn said:
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
Click to expand...
Click to collapse
Go Here and download the Fastboot drivers. follow the directions on the razor dev portal. I had the same issue and this fixed it for me. https://developer.razer.com/razer-p...94.1708481542.1586624574-305520188.1586475530
If your adb-server is not started with root/admin rights, your phone will never prompt you for authorization unless you choose a different USB Mode (MTP, PTP, etc.) than Charge Only. I suspect this is done to prevent certain malicious actions being performed without the user being aware.
If you start your adb-server with root/admin rights (by typing "sudo adb start-server", make sure you've killed your existing daemons before doing so), you can use ADB while in Charge Only mode, provided you've subsequently authorized the PC to do so. However, unlike normal adb server, the fingerprint may occasionally change and you may need to redo the authorization again.