Dropped my pixel and now the screen doesn't turn on, i am assuming it is responding to touch since i can guess where the numbers are and enter my passcode and i don't feel the vibrations on the finger print sensor over and over. Only thing i care about are the pictures on the phone. Is there any adb commands to put the phone into file transfer mode? i have tried for hours guessing where it is on the screen but just can't get it, or is there any affordable software that will get the files for me? Phone is not rooted and bootloader locked
Idk about a command to put it into transfer mode, but you could always "adb pull" them, they should be under the DCIM folder if they were photos you had taken.
davehasninjas said:
Idk about a command to put it into transfer mode, but you could always "adb pull" them, they should be under the DCIM folder if they were photos you had taken.
Click to expand...
Click to collapse
I have been trying the pull command all night, i can't seem to find where the dcim folder is. Even tried to pull the entire phone. I am adb dumb. I did manage to pull the contents of the bin dir. but thats it.
I use adb pull /storage/emulated/0/Dcim/ and it comes back as not a file or directory
pensfan76 said:
I have been trying the pull command all night, i can't seem to find where the dcim folder is. Even tried to pull the entire phone. I am adb dumb. I did manage to pull the contents of the bin dir. but thats it.
I use adb pull /storage/emulated/0/Dcim/ and it comes back as not a file or directory
Click to expand...
Click to collapse
Hmm... What about adb pull /sdcard/DCIM/
@davehasninjas is right. Remember that it's case-sensitive.
Without invoking root, and in charge-only mode, I can adb shell and connect to my phone. Under /sdcard/DCIM, I have 2 folders: Pictures and Google Photos (which shows up as "Google/ Photos" because of the space).
post-mortem said:
@davehasninjas is right. Remember that it's case-sensitive.
Without invoking root, and in charge-only mode, I can adb shell and connect to my phone. Under /sdcard/DCIM, I have 2 folders: Pictures and Google Photos (which shows up as "Google/ Photos" because of the space).
Click to expand...
Click to collapse
Amazing how well things work when you do them correctly, wasn't even paying attention to the case. Thank you, everything worked.
since i am not rooted is that why i couldn't just grab the entire contents of /sdcard? i kept getting required key missing
Related
Hello,
I managed to drop my phone and bust the screen soon after I bought it (luckily I have insurance). I hadn't had a chance to root it or anything, but I have some pictures on the phone I really want to get out of it. I thought the phone would have put them on the SD card but when I looked on the card, I don't see them, so I must assume they are stored on the phone itself. Since I can't do anything with the phone screen, is there any way to get the pictures off of it?
Thanks for any help!
spdivr said:
Hello,
I managed to drop my phone and bust the screen soon after I bought it (luckily I have insurance). I hadn't had a chance to root it or anything, but I have some pictures on the phone I really want to get out of it. I thought the phone would have put them on the SD card but when I looked on the card, I don't see them, so I must assume they are stored on the phone itself. Since I can't do anything with the phone screen, is there any way to get the pictures off of it?
Thanks for any help!
Click to expand...
Click to collapse
If ADB works you can adb shell/adb pull the files.
Look up Droid Explorer - I believe this automatically installs adb for Windows users and has a nice frontend for file transfers. I've never messed with ADB in Windows as I'm a Linux user so I can't help you any more.
Entropy512 said:
If ADB works you can adb shell/adb pull the files.
Look up Droid Explorer - I believe this automatically installs adb for Windows users and has a nice frontend for file transfers. I've never messed with ADB in Windows as I'm a Linux user so I can't help you any more.
Click to expand...
Click to collapse
That worked, thanks!
I had not rooted the phone, but luckily I had set the phone to USB debugging before I dropped it. So even though I couldn't see anything on the screen, I ran Super One Click and it rooted, then Droid Explorer found it and I was able to pull off my photos.
As many of you may know, there's currently no native way to screenshot an Android Wear device, and at this point it's pretty cumbersome to need to get to a computer to run ADB just to get a screenshot.
I've managed to at least remove the need for a computer, as long as your phone (or whatever your watch is paired with) is rooted (your watch does NOT need to be rooted), through a simple script I threw together, wearcap. It properly loop-back connects to your device and then connects to the watch over ADB. I'm sure this can be made into an actual app, but I don't care enough or have the time to do it. All you need to do is run it as root with whatever terminal app you desire. Wearcap assumes you've done all the necessary USB debugging settings, which can be found below. Screenshots are saved in /sdcard/Pictures/Screenshots/ on your device and then removed from the watch.
Everything else is pretty self-explanatory, just push the script onto your device, give it executable permissions and be on your way. As noted in the script itself, make sure your screen is on during the connection process, my Moto 360 would typically fail to connect if it was off.
For a reminder of how to setup USB debugging for the devices: http://www.androidpolice.com/2014/0...nlock-the-bootloader-and-root-the-lg-g-watch/
And here is the Google+ thread: https://plus.google.com/u/0/113601948978986762347/posts/6dD6xBrvpjs
"This paste has been removed"
Spere said:
"This paste has been removed"
Click to expand...
Click to collapse
Sorry about that, it's been attached as a text file now.
an apk will be wonderful
I can wrap it into app tomorrow if CEnnis91 is OK with it, I'm thinking to add change of the density as well through adb.
I dropped my OnePlus One yesterday, saddest day of my life. The screen is on, but it will not register touches.
I need to get my TitaniumBackup off of it to restore on a different phone. I cannot see the Internal Storage through Windows Explorer to copy it to my computer. I don't know if it is because the screen is PIN locked (and I can't get in because it won't register touches) or because USB debugging is on. Regardless, I can't copy it using Windows Explorer.
I do have access to the phone using ADB. So I should be able to pull the TitaniumBackup folder to my PC. My problem is I don't know the exact path to input to pull from on the phone.
Will someone tell me the path to use to pull the folder (and if you are real familiar with ADB the entire command would be helpful too).
Thanks in advance.
Code:
adb pull /sdcard/TitaniumBackup c:\tibu\
Transmitted via Bacon
Respect Milo said:
I dropped my OnePlus One yesterday, saddest day of my life. The screen is on, but it will not register touches.
I need to get my TitaniumBackup off of it to restore on a different phone. I cannot see the Internal Storage through Windows Explorer to copy it to my computer. I don't know if it is because the screen is PIN locked (and I can't get in because it won't register touches) or because USB debugging is on. Regardless, I can't copy it using Windows Explorer.
I do have access to the phone using ADB. So I should be able to pull the TitaniumBackup folder to my PC. My problem is I don't know the exact path to input to pull from on the phone.
Will someone tell me the path to use to pull the folder (and if you are real familiar with ADB the entire command would be helpful too).
Thanks in advance.
Click to expand...
Click to collapse
If you need to pull anything else or access your phone you can still input touches with adb shell.
You can connect Keyboard / Mouse whatever input device using the USB OTG function.
USB OTG to attach mouse. Run TiBu and back yo ship. Boot into recovery and use the mouse to grab a nandroid. Reboot and plug into the USB with your computer. Pull your data.
I just did this last month with my wife's OPO. $200 later she had a brand new phone fresh from OnePlus. No yellow tint. Great touch screen response.
I just restored the nandroid and she was back in business.
Coug76 said:
USB OTG to attach mouse. Run TiBu and back yo ship. Boot into recovery and use the mouse to grab a nandroid. Reboot and plug into the USB with your computer. Pull your data.
I just did this last month with my wife's OPO. $200 later she had a brand new phone fresh from OnePlus. No yellow tint. Great touch screen response.
I just restored the nandroid and she was back in business.
Click to expand...
Click to collapse
Thanks for the info. Didn't know you could restore nandroid from a different device onto another one. I'll file it for later.
adb pull and adb push fail when filename contains punctuation characters like */\":?
Hello, I've encountered a major error with adb push and adb pull. It makes trying to backup my phone's data (the internal 'sdcard' drive) to my Windows computer an absolute nightmare. Apparently adb can't handle punctuation characters such as */\":?|<> if they're in a filename. If one of these files is encountered while doing an adb pull or adb push, the operation fails entirely and gives no information about what has been backed up or is yet to be backed up.
As you might imagine this issue makes backing up the phone data (like the 'sdcard') almost impossible. Imagine being gigabytes into a transfer and then having it just stop with no opportunity to resolve the issue, resume the transfer or an indication of what's left to backup.
The only resolution I've found is to attempt to search out and eliminate these characters from file names before starting the transfer. Needless to say it's a very poor solution and often results in many, many failures.
Does anyone have a way to resolve this error / failure when doing an adb pull or push WITHOUT searching / removing these characters from filenames first?
cognitivedissonance said:
adb pull and adb push fail when filename contains punctuation characters like */\":?
Hello, I've encountered a major error with adb push and adb pull. It makes trying to backup my phone's data (the internal 'sdcard' drive) to my Windows computer an absolute nightmare. Apparently adb can't handle punctuation characters such as */\":?|<> if they're in a filename. If one of these files is encountered while doing an adb pull or adb push, the operation fails entirely and gives no information about what has been backed up or is yet to be backed up.
As you might imagine this issue makes backing up the phone data (like the 'sdcard') almost impossible. Imagine being gigabytes into a transfer and then having it just stop with no opportunity to resolve the issue, resume the transfer or an indication of what's left to backup.
The only resolution I've found is to attempt to search out and eliminate these characters from file names before starting the transfer. Needless to say it's a very poor solution and often results in many, many failures.
Does anyone have a way to resolve this error / failure when doing an adb pull or push WITHOUT searching / removing these characters from filenames first?
Click to expand...
Click to collapse
did u find any solution
Hello, I just broke the screen of my OnePlus8t Verizon network unlocked phone. The computer I previously linked 8t with also has a broken screen. ... Rains it ..... My Phoe has some important information in docs and screenshots I need to get. I just turned off ADB debugging thinking "Oh I don't need that just yet" the very morning I broke the LCD. Good news, I can still answer it. I already have adb.exe except in ADB shell it shows as unauthorized. I need those files like yesterday. I have an otg/ADB flash drive, but I still can not connect to retrieve files. I can see my phone when I directly connect to comp without the flash drive, however, I can not access it. I have tried to put the phone into recovery, but I have no way to enter the pin as I have tried to guess where it is. How can I receive the data I need from my phone?
Thank You.
P.S. I have little knowledge and only learn what I need to know for whatever project, in other words, I can not code and I barely speak dos.
Is the touch screen still working then?
If it's showing "unauthorized" you can try to plug it into your desktop and then hit the "authorize" button on the popup that you can't see.
Here is where ok is on a different phone. It's somewhere near there on yours.
Renate said:
Is the touch screen still working then?
If it's showing "unauthorized" you can try to plug it into your desktop and then hit the "authorize" button on the popup that you can't see.
Here is where ok is on a different phone. It's somewhere near there on yours.
Click to expand...
Click to collapse
I have tried that. The finger print unlock screen only works ⅔ of the time. I have no way of knowing if it's unlocked. I keep my touch sounds silent. I keep trying to find where it might be. I have tried to slide as if answering a call. Is there a way to force the USB settings for media transfer? Maybe through Google? If any platform knows it's my phone is Google. I can go to the play store and push apps onto it. Unfortunately the two adb drivers I have installed on my Android didnt work.
Oh, actually, you've got it easier! The OnePlus 8t supports HDMI over USB Type C.
https://forum.xda-developers.com/t/does-one-plus-8t-have-video-out-through-usb-c.4465629/
Buy an adapter and hook up an HDMI monitor/TV.
Or just use a new monitor on the computer that is already authorized.
Is there any other way. Right now it is not with in the budget to afford any extras even with the price tag of $20. I am hoping there is a way within an adb shell to force turn on the adb debugging. I have developer options enabled. I would just rewrite the documents, except some of those items I need include the text messaging history. If I can't force the adb, can I remotely back up the phone? Is there a trustworthy app for that? I do have quick settings installed and if my memory is correct, I believe I have sideline installed even.