So I have a Nexus 4 with 4.2.2. I dropped it yesterday morning in the dirt this morning, it fell out of my bag maybe 2 feet off the ground.
There is a small scuff on the left upper corner and the lower half of the touchscreen no longer works. Only buttons on the top half of the screen respond. The display is completely intact though, not shattered and displays images just fine. Since the lower half screen is unresponsive, I can't enter my SIM PIN or unlock my phone.
My skill level in this area is pretty low. Enabling LTE is pretty much the most technical thing I've done with this phone.
I do have twrp but it appears I do not have USB debugging enabled. I've been googling this mess and experimenting with adb and fastboot for the last hour but haven't been able to make any progress backing up my phone or enabling USB debugging. I was thinking if I could at least enable USB debugging at least I could use Control Android or something right?
I'm able to connect using adb but I must be using incorrect syntax. I've tried every command I have come across and always get a not found error. Is there some other referance I should be using - I started with developer.android.com/tools/help/adb
~ # ←[6nadb devices
adb devices
/sbin/sh: adb: not found
~ # ←[6n
C: \adt\ sdk\ platform-tools>fastboot devices
0047e1b856555005 fastboot
I will be getting a new phone but my primary concern is there are a handful of text messages from my boss sent me literally minutes before I dropped my phone and he is now unreachable for the next week.
Is there any possibility the digitiser came loose and that's why only half of the screen doesn't work? I need to buy a #5 torx driver anyways but I don't want to open it up if its not a viable solution.
Any other suggestions?
Just boot into TWRP and type 'adb pull /sdcard/' in a console. Recovering text messages I'm not sure how to do, might be doable through a shell.
http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
also maybe useful
http://www.modaco.com/topic/302958-backup-messages-the-adb-way/
Related
Hello everyone
I've got a problem and I need your help. My Legend fell on the ground and now the glass and display are both broken. To access my device with adb, which I previously installed, I used DroidAtScreen. But recently I deactivated USB-Debugging eek, and now I can't enable it. I need to "recreate" every single step from the unlocked screen to Menu->Settings->Applications->Development->USB-Debugging. The first step (Menu->Settings) is easy and abvious, but I need the other ones.
Could some of you take some screenshots and upload them? I.e.:
1. Menu->Settings, then scroll down to bottom **Screenshot**
2. Scroll a little bit up until "Applications" reaches first entry **Screenshot**
3. Press first entry (=Applications) **Screenshot**
4. Press fourth entry (=Development) **Screenshot**
5. Press first entry (=USB-Debugging) *Screenshot**..
I know it may seem complicated, but it would be of tremendous help! My idea is to print out the images and lay them over the Legend to find my way to USB-Debugging
THANK YOU A LOT in advance!
memo9
Good thinking, you actually only need 4 screens, here you go...
Good luck replacing the screen! There's plently of material to work with in accesories section
If the digitiser (top glass) is broken i doubt your presses will be in the right place, I have a desire in front of me that has a crack in the top left corner of the digi and pressing "a" on the keyboard pull notification bar down
Thank you very much for the effort of taking the screenshots, but I couldn't access the settings.
The only question that remains is: Does the phone need to be in "charge only"-mode? Because right now, in fact I can access the SD-Card when mounted, so I may have to switch to charge only?
@bonesy: Thank you for the input, but the touchscreen seems to be working fine as I can turn on the phone and enter the PIN-code to unlock it, as well as call a number after opening the phone-application
ADB should work no matter what the mode...why weren't you able to access it?
I don't know... I followed all the steps, connected the phone to my Mac... all this several times, trying to press on the exact location... but haven't succeeded.
I have adb configured as well as DroidAtScreen running and also tried to access it with DDMS..., but when i use the command "adb devices" none is shown. I can access my SD-Card but can't use adb...
I may try again a few times but can't really think of any other alternative than to replace the screen, although I need to access my phone immediately.
Thanks again for all the fast answers and if anyone has an idea or some sort of walkthrough... I would appreciate it.
ADB wont work unless you are using a custom rom OR its selected already.
Maybe a USB port failure?
What do you mean? I have accessed my phone in this environment several times before, everything should be set up correctly. It may be a USB port failure, altough I have tried to plug it into other USB ports.
The only thing I'm struggling with right now is accessing the Debug-mode in the settings.
memo9 said:
What do you mean? I have accessed my phone in this environment several times before, everything should be set up correctly. It may be a USB port failure, altough I have tried to plug it into other USB ports.
The only thing I'm struggling with right now is accessing the Debug-mode in the settings.
Click to expand...
Click to collapse
Ah i see, i meant the phones usb port... Could be 1 pin failed on it stopping certain things working?
Doesn't seem to be the problem since I can mount the phone and access the SD-card, but thanks anyway.
I'm sorry if this as been asked/answered. I searched but to no avail.
So my phone was plugged in sitting on my lazy boy. I spun to face the T.V. and the short cord was pulled taut and ended up falling to the tile. It resulted in the phone having 4 hairline small cracks.... But destroyed my digitizer I believe, as the touchscreen no longer works.
My question is, how can I perform a backup of my phone as it is through ADB. Which command, if any, would it be to get my phone to start one if I can't access CWM.
Thanks y'all.
Edit: Or, if anyone knows away of how I could control my phone through computer, that'd be great too. I have a lock screen though...
waffleman911 said:
I'm sorry if this as been asked/answered. I searched but to no avail.
So my phone was plugged in sitting on my lazy boy. I spun to face the T.V. and the short cord was pulled taut and ended up falling to the tile. It resulted in the phone having 4 hairline small cracks.... But destroyed my digitizer I believe, as the touchscreen no longer works.
My question is, how can I perform a backup of my phone as it is through ADB. Which command, if any, would it be to get my phone to start one if I can't access CWM.
Thanks y'all.
Edit: Or, if anyone knows away of how I could control my phone through computer, that'd be great too. I have a lock screen though...
Click to expand...
Click to collapse
Is cwm installed? If yes, cwm touch or the normal version (no touch, keys)?
I don't know but if the "normal" cwm is available, the one without touch, simply flash it, perform the backup and adb pull /sdcard/ using your PC
Sent from my Nexus 4 running Android 4.2.2
waffleman911 said:
I'm sorry if this as been asked/answered. I searched but to no avail.
So my phone was plugged in sitting on my lazy boy. I spun to face the T.V. and the short cord was pulled taut and ended up falling to the tile. It resulted in the phone having 4 hairline small cracks.... But destroyed my digitizer I believe, as the touchscreen no longer works.
My question is, how can I perform a backup of my phone as it is through ADB. Which command, if any, would it be to get my phone to start one if I can't access CWM.
Thanks y'all.
Edit: Or, if anyone knows away of how I could control my phone through computer, that'd be great too. I have a lock screen though...
Click to expand...
Click to collapse
Try this toolkit.I hope ur device is recognized in your PC
http://forum.xda-developers.com/showthread.php?t=1995688
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
BrickOfNexus said:
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
Click to expand...
Click to collapse
Hi... There is no available fix for the moment. Check this thread. You are not alone
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page19
BrickOfNexus said:
... Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android....
Click to expand...
Click to collapse
Unfortunately @5.1 is right. The common denominator of the BLOD (many threads on this) is the inability to get into recovery mode by any means. ADB doesn't work unless in recovery. Without ADB you will not be able to pull anything off the phone. At least you are unlocked so you can try some tools and/or manually attempt to fastboot boot or fastboot flash a custom recovery and get ADB working, but chances are almost non-existent. Some ppl have been able to briefly get back into recovery on completely full charge, but it seems to start boot looping again shortly afterwards from recovery. Hopefully you were using Photos and synced recently. If you bought direct from Google, contact them even if out of warranty. If they won't help you or you didn't buy from Google, approach Huawei for an RMA.
I was in your situation and was able to flash the full stock image (flash-all.bat command) even though my device didn't show up on ABD--but maybe I just got lucky. I thought there was no chance it would work but it did. Some people reported getting out of the boot loop using Skipsoft's tool but most likely you will need to RMA the device if it's still under warranty from Huawei. Sorry to hear you have been added to this club. There are a lot of lemon 6Ps that die because of hardware issues (according to Google) and they clearly don't care because they never recalled the affected devices. I was hoping it was just the early generation phones but if yours is 5 months old that means the problem is persisting. None of these things might still be running in a couple years which is ridiculous for a premium phone. Makes you think twice about buying another phone from Google since they threw 6p owners under the bus rather than offering 6P owners a credit or something for their defective 6Ps. Good luck. At this point I think people need to create a class action suit against Google. That's the only way people got repairs or compensation from Apple the numerous times they pulled stuff like this with defective products. Why should Google get away with selling what they themselves admit is a defective phone?
Refer to this thread: https://forum.xda-developers.com/showthread.php?p=75551897
So Im waiting on a replacement screen (it started as crazy graphics all over screen, not completely blank, but responds to input), and its taking forever. I knew I had ADB debug enabled, so wondered if I can control the phone via PC.
Behold there are few ways this can be done.
Long story short......in adb, my phones shows as ADB DEVICES : UNAUTHROIZED
Is there anyway I can authorize the adb request between computer/phone?
Its a stock OnePlus 5.....so no custom recovery and not rooted :-/
You could guestimate the area or the enter button of the dialog, and use a mouse connected via USB otg to click it
matrx10503 said:
Refer to this thread: https://forum.xda-developers.com/showthread.php?p=75551897
So Im waiting on a replacement screen (it started as crazy graphics all over screen, not completely blank, but responds to input), and its taking forever. I knew I had ADB debug enabled, so wondered if I can control the phone via PC.
Behold there are few ways this can be done.
Long story short......in adb, my phones shows as ADB DEVICES : UNAUTHROIZED
Is there anyway I can authorize the adb request between computer/phone?
Its a stock OnePlus 5.....so no custom recovery and not rooted :-/
Click to expand...
Click to collapse
Best way would be to use a displaylink adapter do you can see the screen.
If you can make it through the menus you'd need to install the app which can be done from a PC, just push it to the device, then advanced, then turn on usb, then allow the app. Then the screen will be shown on a monitor.
Either that or change the screen.
I got it working......I had to boot up an old laptop hard drive I had that was Auth'd. It let me do what I needed.
Hehy there,
unfortunately the screen on my mi9t stopped displaying. Really weird. While I was using it, the screen started flashing, just to turn black and never wake up again. No fall or water involved. The phone still seems to work fine, and even touch seems to work, but no display.
I opened up the phone to see if the connector got loose, but everything is well in place.
Now my problem ist, that I can not access the phone anymore. All my files and things are still on there but unreachable.
Here are the facts:
- no display
- bootloader is locked
- usb debugging is enabled, but my pc is not authorized
- I can blindly get into fastboot and to the lockscreen
- I am not able to blindly unlock the device
Easiest option would obvoulsy be to exchange the display, but unfortunately I can not get on here (South Africa) and shipping would take a month.
My favourite aproach so far was to mirror the screen via Vizor, but unfortunately it needs to install the according app on the device, which it can not while the device is locked.
Does someone here know how to recover the data?
Thanks
and a happy new year to everyone!
cartonneexpress said:
Hehy there,
unfortunately the screen on my mi9t stopped displaying. Really weird. While I was using it, the screen started flashing, just to turn black and never wake up again. No fall or water involved. The phone still seems to work fine, and even touch seems to work, but no display.
I opened up the phone to see if the connector got loose, but everything is well in place.
Now my problem ist, that I can not access the phone anymore. All my files and things are still on there but unreachable.
Here are the facts:
- no display
- bootloader is locked
- usb debugging is enabled, but my pc is not authorized
- I can blindly get into fastboot and to the lockscreen
- I am not able to blindly unlock the device
Easiest option would obvoulsy be to exchange the display, but unfortunately I can not get on here (South Africa) and shipping would take a month.
My favourite aproach so far was to mirror the screen via Vizor, but unfortunately it needs to install the according app on the device, which it can not while the device is locked.
Does someone here know how to recover the data?
Thanks
and a happy new year to everyone!
Click to expand...
Click to collapse
When I experimented, I was able to unlock my two SIM cards and Android by adb (replace xxxx by your PINs)
However, phone was rooted and shell was given the root grant:
adb wait-for-device devices
adb shell
su
input text xxxx
input keyevent 66
input text xxxx
input keyevent 66
input touchscreen swipe 930 880 930 380
input text xxxx
exit
exit
try fastboot apk
Mirror screen to pc with vyzor. You have usb debugging turned on, so it's worth a try.
If touch doesn't work, use usb otg adapter to plug keyboard or mouse
There's no other option.
zgfg said:
...
Click to expand...
Click to collapse
Thank your for the idea! Unfortunately it does not work in the unrooted phone. I suspect that's only because I can't the adb connection to my pv authorized.
I tried this on an unrooted lineage os 17, which I have on my old Mix2, and there it works like a charm.
yaro666 said:
try fastboot apk
Mirror screen to pc with vyzor. You have usb debugging turned on, so it's worth a try.
If touch doesn't work, use usb otg adapter to plug keyboard or mouse
There's no other option.
Click to expand...
Click to collapse
Thanks for the advice. I think i tried everything to get the apk installed, but I can not do anything through adb since even though debugging is activated, the connection to my pc is not authorized.
I guess I have to wait for the replacement screen.
cartonneexpress said:
I guess I have to wait for the replacement screen.
Click to expand...
Click to collapse
Any water exposure? Ever?
May not be the screen; a mobo failure is just as likely even more so especially if they use no lead solder paste.
Maybe a loose or bad connector/cable if you get real lucky... and find it.