For many of you, my question may look either very familiar or just a piece of cake.
To me neither it is familiar nor easy...
What I have done so far:
Crashed on how to install Android SDK and enabled ADB.
Now my phone is on Recovery mode and ADB has detected it.
I tried the command adb pull, adb backup. Both didn't work as my phone is not rooted and stated "remote object doesn't exist"
What I am after:
Need nooby proof steps to root the phone using adb or any other possible way (which I could decifer)
Then use the command adb pull to get my contacts, possibly pictures.
Some are saying to re-flash. But I am not sure the side effects of re-flashing. I just don't want to lose my data.
To give a bit of background: phone went on soft-bricked in Samsung Service Centre while I was looking for point to charge it as battery was zero charge. Accidently the staff connected my phone to a machine that does software upgrades and disconnected from it.
I am a super noob about the jargon of Android, how things work internally etc. I was just a person who used the phone for messaging, watching lectures, storing music, photos and browing. No games, not much apps.
Related
Hey guys
Last night I broke my SGS's screen. The phone is rooted and I know it still works as can hear it get texts and boot up correctly.
I wanted to just swap the phones out but I have a lot of valuable pictures etc on the phone that I hadn't backed up yet.
Is there any way to access the hard drive from the computer w/o being able to access the phone?
I tried the "Screencast" app but I cant seem to get it to work. I tried doing some searches on here but I'm not exactly sure what to look up.
I have insurance on my phone so I can get a replacement, I'd jsut like to get my pictures and any text messages i may have missed (but mainly the pics)
Any insight you guys have would be much appreciated.
Thanks in advance!
Reboot in recovery mode. That would give you adb access to the phone and you can adb pull your pictures with "adb pull sdcard/DCIM/Camera".
thanks for the reply.
sorry i'm kind of new at this stuff. my friend rooted my phone and did all the dirty work. i have no idea how to use adb or w/e
do i need a linux machine? also, how can i reboot in recovery mode if the screen is completely disabled?
do get via ADB you need to ADB kit or the Android SDK kit, theres a helpful section on how to do ADB but it shouldnt be a problem, i also recall that after ADB is installed you might be able to use Android explorer to go to the phones pciture directory and get them like that?
i'm having a horrible time trying to get this setup lol
i think a problem i'm having is i dont know if USB debugging is enabled on my phone, and since the screen is broken i can't turn it on.
anyone else have any other suggestions?
redstar2k said:
Reboot in recovery mode. That would give you adb access to the phone and you can adb pull your pictures with "adb pull sdcard/DCIM/Camera".
Click to expand...
Click to collapse
it seems i can get it into what i ~think~ is recovery mode (it didnt make the typical noise it makes when booting up, and my bottom row buttons light up if i press the power button then one of the buttons)
not sure what screen im in honestly... but even still, the computer doesnt detect that anything is plugged in and ADB doesnt detect any devices...
maybe with usb cable?
thats what im doing is using USB cable.. problem is i cant mount my usb from my phone as the screen is broken.
i cannot do it blind either i dont believe, i dont think the screen is detecting my fingerpresses at all
Long story short, no gimmicks.
I dropped my Motorola Droid/Milestone/A855/Whatever in a toilet, and it died. I dried the guy out in rice, and all is well, it turns back on, and all that jazz. Sadly, the screen is dead. Remember that.
So I go to Gmail to get contacts from there (synced, right?) t put in my backup phone (yes, I'm a baller) and find that my contacts are severely out of date. Turns out when I got a replacement phone from Verizon (due to the former's ghosting or 'self-touching' (LOLWOWOMG)), the default setting was to not have my contacts synced to my Gmail anymore. Bummer, right? Remember this point as well.
So I need to get my contacts out of my phone, but I can't connect via USB to import due to the fact that I can't use the screen to allow USB debugging.
Nextly, a Verizon person at one of their stores (I have no faith in those people) told me they CANNOT pull anything off the phone with on of their machines, not even contacts.
My question is can you? If so how? Can it be done without a Verizon Employee, because that would be all rainbows and butterflies as I hate most of them. Lastly, I'd ask that you post your ideas in a clear step-by-step format, as I share 99% of my DNA with cavemen. Thanks? And I love you.
Don't know how it works on Droid, but on Milestone if you run the Androidiani Open Recovery then adb will works automatically after start of recovery. So if your buttons are still working, then get to your phone's Recovery, plug in usb and try to run adb on your computer (with command line).
Maybe ClockWorkMod Recovery have the same function, so you can try it if you have a rooted phone.
To pull your contacts from phone using adb open command line and type:
adb shell
$ su (if you've got hash "#" symbol instead of "$" in the beginning of the command line, then you don't need that)
# ls /data/data/com.android.providers.contacts/databases (if you see contacts1.db, contacts2.db etc then write it bellow instead of contacts.db)
# dd if=/data/data/com.android.providers.contacts/databases/contacts.db of=/sdcard/contacts.db
My phone isn't rooted, and USB Debugging is still in the default 'no' setting.
try to, and i know its not easy, to press ur find key, type market, remember the steps to go to download, and try downloading some backup software, they create a file on the sdcard, so u can get them, and export...
I know, is not the easiest thing to do.... but is the only option i can think of, with ur dead screen.
Need someone with tons of knowledge here to help me out
I'm currently dealing with a Nexus 6, unrooted, stock.
The phone was dropped and the screen was destroyed. During the drop something internally must have been damaged as the phone starts the At&t music up and resets immediately and will keep looping until the power dies or I put it into the fastboot screen to shut it up, in which the phone stays on that screen. (or at least theres where im assuming its going)
The thing is, my computer recognizes the phone as an android device and shows the android device bootloader on my device manager on my cpu. Every time I try to get into recovery (or at least how I recall doing it without a screen to assist) the phone just restarts to the at&t music once again...
Is there any hope here for retrieving my data on this thing? I figured I could do something with adb although im not too savvy with it. Just assuming since the computer does recognize the device in some way, it is possible hopefully.
Btw I dont think debugging is on atm.
Any help would be super appreciated. Even willing to donate to anyone that may be able to assist me in this.
If and when Mobiletechvideos gets back up and running, they can more than likely save the entire device and if not at least get your data. But unfortunately because of the high demand for their services, they have gone into a temporary work hold until all current orders are complete. Either way, I would try to get ahold of them and see if they can assist or can point you in the right direction.
If it is unrooted with stock recovery and not booting up to android, there will be no easy way to get your data off.
It is possible, though very unreliable and extremely difficult to unlock the bootloader, flash a custom recovery, create an image of the data partition and scan that on a computer with data recovery software, but that really isn't worth doing.
hi ... how r u .... i have this problem too .... broken screen ... screen totally black ..... stock rom no root no recovery ...... debuging not enabled
http://forum.xda-developers.com/showthread.php?t=2786395&nocache=1
this guy said in his thread i can access the phone via computer but i need to enable debugging which i donno how to do with screen totally black
any suggestions is really appreciated
So I shattered my display and the screen wont turn on but it still vibrates when i get notifications, i was wondering if anyone would know of a way to sort of project the display onto a TV or PC so i can use apps that i installed to backup messages and app data and stuff?
I'm pretty sure if the phone still works you can run it in ADP on your PC and basically click through the phone. Then do whatever you need to do and back it up.
BlueForce64 said:
I'm pretty sure if the phone still works you can run it in ADP on your PC and basically click through the phone. Then do whatever you need to do and back it up.
Click to expand...
Click to collapse
Here's the problem with that:
ADB doesn't work unless you first enable it in developer options. Once you do that, you have to click yes on a confirmation dialog the first time you use it. Both of these processes require a functioning screen.
If you have an unlocked phone with TWRP installed, and you can blindly convince the phone to boot into TWRP (maybe by booting into bootloader and using fastboot reboot-recovery, but I'll have to check and see if that command works when I get home. I think it does.), you'll be able to access the data on your phone by simply plugging it into a computer. If you do not have TWRP installed, and you have no lockscreen set up (no swipe, no password, no pin, no nothing), you might be able to access the data by plugging it into a computer after it boots.
If none of those situations apply, and the data is worth about $100 to you, you might want to look into a screen replacement service. Sometimes you can find little electronics places in malls or shopping centers that will do it, and I'm pretty sure there are businesses that you can mail your phone to and they'll mail it back once the work is completed. A friend of mine even found a service that sent someone to her house to replace her screen then and there.
Thanks, booting into TWRP worked and I was able to get most of the stuff I needed. I completely forgot I could get into it that way.
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Never set Google to back up photos?
Sent from my Nexus 6 using XDA Free mobile app
leetonion said:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Click to expand...
Click to collapse
first off, fastboot only connects to the device in the bootloader mode. ADB NEVER EVER connects to the device when in the bootloader. that sound you are probably hearing isnt "adb" connecting, but just the sound you hear when you connect to the computer.
I know, just didn't word it right. The chime from my computer is just it recognizing the phone, but it coincides with adb losing connection and (I'm assuming) my phone crashing or rebooting somehow...I just need some way to pull files from the sdcard folder and adb doesn't seem to work in my current situation.
If you are lucky and the mobile boot into system then try this http://www.vysor.io/
Sent from my Nexus 6 using Tapatalk
AhmadOkda said:
If you are lucky and the mobile boot into system then try this http://www.vysor.io/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Interesting app ya linked to, but wouldn't he need to be able to install the app on the device before he would be able to see it on his desktop? Just asking because it said available on Google Play.
Sent from my Nexus 6 using XDA Free mobile app
leetonion said:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Click to expand...
Click to collapse
Does your Nexus have root access?
31ken31 said:
Interesting app ya linked to, but wouldn't he need to be able to install the app on the device before he would be able to see it on his desktop? Just asking because it said available on Google Play.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I tested dot on my mobile
You only need usb debugging enabled and it will install itself with no action from my side
Sent from my Nexus 6 using Tapatalk
You can do adb commands in recovery. if you can get into recovery you should be good to go.
Miss read OP. Thought you were trying to boot normal and not boot into recovery.
leetonion said:
I know, just didn't word it right. The chime from my computer is just it recognizing the phone, but it coincides with adb losing connection and (I'm assuming) my phone crashing or rebooting somehow...I just need some way to pull files from the sdcard folder and adb doesn't seem to work in my current situation.
Click to expand...
Click to collapse
To help troubleshoot, try holding down power when you think it has booted to feel for a vibration. If it vibrates you know it booted. From there you may need to enter a password through adb (there are guides, I can't remember of f the top of my head how). Once you are in, you can use this to help navigate your phone http://forum.xda-developers.com/showthread.php?t=2786395. There's a learning curve and high latency but, it works. I have been in a similar situation and I was able to pull it off using this method.
As far as it rebooting or crashing, or whatever else, there's not much I can do to help with that across the internet, good luck to you.
And one last thing, try playing with this. http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html Looks like you can control TWRP through a command prompt, maybe you can get your files.
And one last, last thing. When in the bootloader menu, the options go like this. You cna also get into these optiosn through fastboot but, I figured it couldn't hurt.
START <--- First option you boot into. If you are holding it's possible to go down one extra though, be careful.
RESTART BOOTLOADER
RECOVERY MODE
POWER OFF
FACTORY MODE
BARCODES
BP TOOLS
QCOM
BOOTLOADER LOGS