Need immediate help! Screen is broken, need to turn usb debug. on - G2 and Desire Z General

My screen is unfortunately broken. Not the digitizer. And i can use my phone. But i have to do few things with my phone. So i have to use androidscreencast etc. programmes like them. But adb can't find my device. I guess i forgot to turn usb debugging on. I know it's hard but is there anybody can send screenshots for me. I was using "AUDACITY B3 or B4", i really need help this is so important for me. Or if is there any way to see my screen from my computer without adb?
Edit: Guys when i connected while my phone is closed, adb devices command answers as recovery. When i turn my phone on i can't see anymore...
Edit 2: I can connect and see screen while on clockworkmod recovery, but it closes connection when phone turns on...

you could find out what setting under /etc or wherever is for usb debugging, then write a small .sh script to change that, put that into a .zip file, and flash it!
maybe this helps, I only skimmed it: http://forum.xda-developers.com/showthread.php?t=1193915
edit: or you could remote-install (via google play store) one of those "stolen phone" apps, maybe that'll give you access

Related

Emulator problem

I connect my wildfire to my computer using the usb lead and set usb debugging on. Then when I try to select it from eclipse to run my program on I can select it but I can't select ok to actually make it run. It doesn't seem to recognise the phone. Any ideas how to fix this.
You may need to set up udev properly. Look around, you will find it. It should be in Android developer guide for Linux.
Yep found that and have followed it to create a new file for udev so that it can recognise my htc wildfire. The problem is that now it doesn't mount the sd card as it used to when I plug it in. Is there a more general set up I can follow that will fix this?
Would like to know as well
found a link which seems interesting. I will try to worj through it later when I get home but I think it states that I may need another line for normal mode. The catch all rule it shows is the one I have and does not recognise plugging it in normally.
not allowed to post url so will post back if it is any good.
Didn't need anything but the catch all line in the end. Restarting the phone made it all work I had obviously turned something off at some point.

[Q] Controlling Nexus 4 on the PC after breaking screen, possible?

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.key​11. 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.

[Q] Nexus 4 screen cracked, need someone fluent with ADB to help

So that's it, my Nexus 4's front glass is broken to where I can only use half the screen. I want to unlock this thing and use ShareKM (Lets me use my mouse and keyboard from my computer on my phone) and Airdroid too I guess. The reason I need help is I can't type in my PIN to unlock the phone and even if I could, I doubt I'd be able to navigate to either ShareKM or Airdroid to start them up. Is there any adb command or otherwise to forward the pin to my phone through usb and then a command to start up the apps? I just wanna be able to use it and get some stuff off before I send it in to be repaired. Thanks in advance.
Not sure about unlocking the pin through adb, but you could use adb pull to copy the files that you need off the phone.
Maybe try this tool
This will only work if your phone is rooted and I hope you enabled usb debugging and unknown sources, otherwise I don't know what to do...
If you will have passed the lockscreen, you should be able to install ShareKM and Airdroid via ADB (if you have the .apk). But I don't know if it's possible to activate ShareKM without using the touchscreen.
But just to get your data off your phone, simply use
Code:
adb pull /sdcard/
then you have a backup of your music/photos/etc
Use adb while in recovery mode. Twrp supports that. Pull the sdcard like the above post suggests.
Sent from my Xiaomi Mi2s

Need to bypass lockscreen/gain access to adb - Broken screen

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.

Salvage data with dead screen

Hello, My phone had some water inside that probably burned the screen, I can still connect with my Bluetooth headphones to it and listen to music, but the screen is pitch black. I bought a new phone already, but I want to salvage my pictures which are not stored on google photos from the phone. Is there anyway to do this ??
You can use adb pull method....
can you elaborate a bit more on that please ?, or a topic to follow ??
Zoro Nasr said:
can you elaborate a bit more on that please ?, or a topic to follow ??
Click to expand...
Click to collapse
There's a full guide here. In short, you'll need to have ADB drivers installed, which you can easily get here, or from the Android Development Kit if you so desire. Then you'll need to open a command prompt. The command you run is
Code:
adb pull "path/to/file/or/folder/on/phone" "path/to/save/to/on/computer"
Say, for example, you're on Windows and you wanted to save your phone's photos folder to your PC, you could run
Code:
adb pull "/sdcard/DCIM" "C:\Users\[your username]\Documents\PhoneFiles"
You might need to have turned on USB debugging in developer options on your phone first, I'm not sure - although this could be hard with no screen...
Hope this helps, good luck!

Categories

Resources