Howdy all!
Recently I dropped my phone, and I want to get the nandroid on my phone so I can put it on a backup s4 I have. I was trying to do this through adb, but when I put in "adb devices" into cmd, I get the device label, followed by an unauthorized. I can't see anything on my screen, as the LCD is broken, and so is the touch screen. Is there a way I can get it authorized? I'm sure the phone was in debugging mode because I used it to tether 3g to my laptop through pdanet.
Thanks in advance.
jfsanta said:
Howdy all!
Recently I dropped my phone, and I want to get the nandroid on my phone so I can put it on a backup s4 I have. I was trying to do this through adb, but when I put in "adb devices" into cmd, I get the device label, followed by an unauthorized. I can't see anything on my screen, as the LCD is broken, and so is the touch screen. Is there a way I can get it authorized? I'm sure the phone was in debugging mode because I used it to tether 3g to my laptop through pdanet.
Thanks in advance.
Click to expand...
Click to collapse
Can you just do it through your computer's file explorer? Depending on which version of android is installed on your device, computers may need to be verified as a "trusted" device before the system will accept any commands. Without this you may be SOL.
koivth said:
Can you just do it through your computer's file explorer? Depending on which version of android is installed on your device, computers may need to be verified as a "trusted" device before the system will accept any commands. Without this you may be SOL.
Click to expand...
Click to collapse
I would, but for whatever reason, some files just aren't showing up in the explorer. Thanks, though.
Related
Hey guys,
Haven't been here for a while. Okay, so I have a bit of a dilemma and every solution I've found requires something I just can't do. Here's the situation: my screen is broken, it has a lock screen, not in developer's mode, not unlocked.
This means:
I won't be able to transfer my files over, as I have to get past the lock screen
I can only install applications from Play store on my computer, but can't launch them
No use for any method that requires phone to be rooted
Can't even activate any USB options to transfer files some other way
Still need to be able to control it to create backups and such of important SMS messages, get files off
Does anyone have any suggestions at all? I don't want to have to resort to replacing the screen, as that'll end up costing me enough time and money where it's more cost-effective to purchase a new phone; however, I really need what's on my phone as soon as possible. Thanks in advance.
I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.
machoman1337 said:
I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.
Click to expand...
Click to collapse
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.
ikarma said:
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.
Click to expand...
Click to collapse
where did you get the screen for $79???
hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device
michaeliang said:
hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device
Click to expand...
Click to collapse
1. It means that if you have the SDK Manager installed on your computer, somewhere between the last packages at the bottom of the list, you'll see "android drivers" (or something similar). With those drivers, your device will show up in "Device manager"(the Windows' one) as an adb device.
2. But if you don't want to get the SDK Manager and be quicker, you can download only those drivers, directly from the "Google developers" page and install them manually by going to "Device manager", right clicking on the Nexus 4 (it will appear with a yellow triangle on it, maybe), then "Update driver", "...BROWSE computer...", then click again on "Browse", then go to where the drivers have been downloaded and select the entire folder by highlighting it and clicking ok (or something). The folder with the driver would look like this "latest_usb_driver_windows" and inside you'll see another folder called "usb_drivers". That's what you need to select and install.
So that's what you need to do to make your phone appear as an adb device in "Device manager". And, of course, adb let's you do a lot of stuff to your phone through your computer, but probably you already knew that.
Hey guys. My phone slipped out my pocket and the digitizer is broken. My phone is rooted, the boot loader is unlocked, and I have it recognised as an ADB Recovery device. I want to enable USB Debugging so I can use androidscreencast to use my phone over my PC so I can set it up to push notifications to my computer and to my pebble(smart watch).
How can I do this. Most of the threads I have found just flat out don't work or stop because of some sort of restriction due to the phone being still locked.
It looks like you need to run some commands in a terminal emulator on your phone. Which in your case is going to be impossible. Why don't you just use adb pull to pull the data off your sdcard?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
It looks like you need to run some commands in a terminal emulator on your phone. Which in your case is going to be impossible. Why don't you just use adb pull to pull the data off your sdcard?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Don't need any of the stuff - I could just boot in and take it over USB. All I need is to enable USB Debugging to send touch commands in place of my touch screen. Once I have that my pebble can let me use my phone outside of the house and I can send notifications to my PC too.
Bump!
Bump!
Anyone? I can't get a new phone for a while.
The biggest Problem ist the Drivers "FOR ALL"problems
You must have all Drivers for it
ThePraeceps said:
Hey guys. My phone slipped out my pocket and the digitizer is broken. My phone is rooted, the boot loader is unlocked, and I have it recognised as an ADB Recovery device. I want to enable USB Debugging so I can use androidscreencast to use my phone over my PC so I can set it up to push notifications to my computer and to my pebble(smart watch).
How can I do this. Most of the threads I have found just flat out don't work or stop because of some sort of restriction due to the phone being still locked.
Click to expand...
Click to collapse
R-2-D-2 said:
You must have all Drivers for it
Click to expand...
Click to collapse
Drivers are installed for it too, I literally just need to get USB Debugging
I am in exactly the same boat! I just need to enable debugging so i can remote control my Nexus 4. i have adb access from CWM, in case there is any commands i can do from there?
Roguecube said:
I am in exactly the same boat! I just need to enable debugging so i can remote control my Nexus 4. i have adb access from CWM, in case there is any commands i can do from there?
Click to expand...
Click to collapse
Hey man. Ultimately I just got a new screen but I was able to enable usb debugging with these instructions.
Hope it helps!
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
My daughter dropped her HDX 7 and the screen shattered. I was able to secure a new one for her but she had some serious sweat equity into a few games she was playing on the old one. I am trying to get the game files of the old one to move to the new one but the touch screen won't work and as such, will not take her password. (due to the drop).
Is there an easy way to bypass this? I am trying to access the kindle drive from my PC for purposes of copying the files (done a million times) but with the device technically locked, the device does not show in file explorer.
Any suggestions welcome.
Thank You!
Chris
Do you have Safestrap installed?
EncryptedCurse said:
Do you have Safestrap installed?
Click to expand...
Click to collapse
No I don't. The device is purely vanilla right as it came from the factory.
Chriss9, you should try to get adb working. That should allow you to pull data.
lekofraggle said:
Chriss9, you should try to get adb working. That should allow you to pull data.
Click to expand...
Click to collapse
Can you tell me where to get it and maybe some instructions? Thanks so much!!
Chris
Look into the rootkit in the dev section. That should install the drivers for you. Then, search for how to use adb. You may need to download the developer kit from Google as the toolkit is a little limited.
You need to pull the data to your computer then push it to the new Kindle.
ADB pull on locked phone? // Simulate input
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Grtschnk said:
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Click to expand...
Click to collapse
Thanks for the suggestion. I installed ADB on my PC and when I use "ADB DEVICES" my device does not show on the list though it does show in Windows explorer. Am I out of luck here?
Thank you again for your kind support.
Chris
Assuming you have the latest Fire OS 4.5.1 : (If you have the older version installed there may still be a glimpse of hope (see long answer))
Short answer: Sorry, looks grim.
Your ADB is switched off and there is no way I know of to switch it on.
I wanted to make sure it wasn't just a driver issue with your computer so I checked with my Kindle:
ADB set off: Kindle in Windows, but not detected by ADB-program
ADB set on: Kindle in Windows and detected by ADB-program
Long answer (may be frustrating to read because it states all the possibilities the Kindle lacks): On a nonlocked (in terms of bootloader, not screenlock) device there would have been some possibilities. Install a custom recovery that has ADB built in and pull the files or try to enable ADB from within recovery inside the ROM. If the device could act as a USB host a mouse or keyboard could have been hooked up. The Kindle supports Bluetooth input devices but they have to be set up first (from within the device, not possible without touch). If your device has older Fire OS you could try the mentioned steps, however that's beyond my expertise. So I don't know if it is possible/will work. You'd have to check other threads about flashing the device or hope that someone else posts advice in this thread.
I became a Kindle owner quite recently, so I can't guarantee everything I wrote is correct, but I believe as long as noone magically finds a way to unlock the bootloader the more experienced users will agree to my post.
Did you install the driver as well? I recommended the toolkit because comes with the driver and if you are not used to installing adb drivers on Windows, it can be a bear. But, Grtschnk may be right. I always enable it n all my devices. It is the first thing I do.
Just to be really sure about possible driver issue: You (chris) could try to connect an Android phone via ADB (I'm assuming you have one). Enable ADB on it and see if connects. Unfortunately this will only prove more that your Kindle turned into a piece of plastic :/
Grtschnk, unfortunately, that won't prove anything. ADB requires separate drivers for each device. Again, that is why I recommended the rootkit. It sets it up for you and can even test it.
That's why I compared with my Kindle, computer and S2 (CM11). Newly set up computer, no SDK, just Minimal ADB. Never installed special drivers for Kindle or S2. Newest Visual Studio (2013) runs on the machine, but without additional packages there is no Android support.
However if I was in the situation myself I would have also tried the full SDK.
So I have a bit of an issue. Somehow last night, after trying to help my parents with our home theater system, with the device laying on a soft surface, the LCD (not the glass) somehow broke. I am really not sure how this happened, the phone itself didn't fall, it was laying on a bed the entire time. When I went to grab the phone and turn it on, I was pretty surprised. You can see what I mean in the attached file.
Now the problem with this is, while I would normally just walk into the Sprint Store, complain and get a new phone. I am not in the US for another 5 months. In the mean time of trying to figure out what to do, I would like to at the very least, grab any files off my phone, or back up my phones' file structure.
I am able to do a minimal amount of tapping on the phone, only on the upper half of the screen, but I can't see anything, nor does the device respond with any touch data from the bottom half.
I obviously can't access the files if the device is locked, which means I have to bypass the lock screen. I found this guide, but unfrotunately, Method 1 didn't work, and I can't get adb to recognize my phone for Method 2.
I also have tried using CWM (the non-touch version) to backup my data, but I let it sit there for 45 minutes and I couldn't tell if it was finished or not. It didn't appear to actually be doing anything.
Could someone help me navigate around this or provide some assistance in allowing me to just get the files off the phone while I search for a new one?
With that being said, does anyone have some recommendations? I was thinking of getting a Motorola X or Nexus 5.
EDIT: Update:
I have access to terminal via Cerberus shell. I was able to use Method 2 to disable the lock screen (or in this case set it to Swipe). It is still pretty difficult to use the phone but I can at least backup whatever data I still do have on the phone to my laptop.
Would anyone be able to give me some advice as to uninstall applications or XDA xposed modules via shell? Or perform a backup or enable ADB debugging?
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Darnell0216 said:
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Click to expand...
Click to collapse
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
slixzen said:
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
Click to expand...
Click to collapse
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Darnell0216 said:
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Click to expand...
Click to collapse
I have a sony xperia P that I am using right now until the replacement phone I got arrives. Any idea how I could use that? I have had minimal success with the phone so far in trying to get that phone to flash custom recoveries, to root the device (not sure why, but my laptop just doesn't want to seem to do it, even using automated tools).
Is it better to just wait for the replacement phone to arrive and grab what I need from that and push it? Could you link me to any guide or steps that you used with yours?
Thanks for such quick responses by the way!
EDIT:
Flashing TWRP and booting into recovery with command prompt open and running adb devices / fastboot devices does not show any devices available.
Is there a specific menu setting or other option I need to use to be able to run adb?
When you use TWRP, the phone will be recognized by the PC but the driver doesn't install correctly off the bat. Go to Device Manager and look for your phone. You may need to click the View -> Show Hidden Devices option. Update the driver manually by selecting the one provided by your manufacturer. Some have a dedicated ADB driver for specific functions (bootloader, etc).
The adb key is stored in data/misc/adb/adb.keys -You can pull this file from any other android connected to that PC (or just copy it if you have a root explorer) and push it to the broken one if necessary. This will bypass any ADB authorization issues while the phone is fully booted and let you see the screen.
so i'm trying to root my phone, and connected into fastmode...usb debugging is turned on.... but when i
try to run the adb device command ,my 996 is isn't showing up as devices connected in windows or mac....any suggestions?
Try changing the USB connection type?
For some reason, I had to select the option to connect my device for transferring photos instead of the usual file transfer for it to show up. Is there a particular guide you are using?
Perhaps someone with more knowledge could shed more light on the matter.
If you are in fastboot mode it wont show up in adb devices. it will show up in fastboot devices
me2151 said:
If you are in fastboot mode it wont show up in adb devices. it will show up in fastboot devices
Click to expand...
Click to collapse
thanks, i did notice that...but there's an error device not recognized whenever i type in commands to try to root the phone...
laughingcolors said:
so i'm trying to root my phone, and connected into fastmode...usb debugging is turned on.... but when i
try to run the adb device command ,my 996 is isn't showing up as devices connected in windows or mac....any suggestions?
Click to expand...
Click to collapse
laughingcolors said:
thanks, i did notice that...but there's an error device not recognized whenever i type in commands to try to root the phone...
Click to expand...
Click to collapse
That's because you have to manually chose the driver. Do that and it will work
Still_living714 said:
That's because you have to manually chose the driver. Do that and it will work
Click to expand...
Click to collapse
could you explain a bit? i'm trying to do this mostly in terminal on mac if possible...i thought i installed the drivers for the phone....
laughingcolors said:
could you explain a bit? i'm trying to do this mostly in terminal on mac if possible...i thought i installed the drivers for the phone....
Click to expand...
Click to collapse
Go to the 430 mark
If it helped remember to press the thanks button