My Nexus 5 has water damage and at first wouldn't turn on at all. After taking it apart and cleaning it up, it will be picked up by the PC but no screen. I figured I can just backup my files through the computer, but it shows it as empty in windows. I am guessing it's because of the gesture unlock? I tried to do the gesture even though the screen didn't turn on in hopes that it would still take it, but I don't think the digitizer is working because the computer never showed it as unlocked. Maybe I messed up since I can't see what I am doing on the screen, but I am pretty sure it's just not taking my gesture input. I am trying to get the files backed up (mostly care about pictures, but having access to the downloads and music would be nice).
I got it to boot into the bootloader ( I think) because device manager reads it as "Android bootloader interface" now. Can I turn on adb with fastboot? I was goolging it and read that I can backup my files with adb shell? When I run 'adb devices" it shows nothing. When I run "fastboot devices" it shows the device. Thanks in advance!
Related
Hi, I got Motorola Moto G, original system, no root. I just encrypted my phone, process most probably finished without problems - I stopped watching the phone on around 90%. Then it restarted, boot animation, "enter your password to decrypt the phone", I type it in, green robo shows for 1 second and then black screen (backlighted) :/ After couple hours nothing changes.
If I type wrong password, phone ofc doesn't accept it. Computer sees device, but I can't access it. When I turn off the phone by pressing POWER for long time, it just resets and goes back to asking for passwod again.
Please help me recover my data...
EDIT
before entering password PC says phone is off, after typing it, PC says it doesn't have drivers (it worked normally before encryption).
I can enter fast boot, but IDK what next. Recovery mode just ends with "NO COMMAND"
I see that probably all users who got this problem have Motorola Moto G too. Mostly people who use CM and tried to encrypt phone too.
I downloaded Android SDK, fastboot.exe tool sees my phone in this state. Not sure if it can be used to do something useful....
adb.exe doesn't see device
bump :crying:
So, I left the phone in black screen step over night. Battery ran out. I tried turning it on/off, entering fast boot mode, but nothing happened, then connected to USB. LED turned on for a while, screen too, showing battery with 0%. But now nothing again. Just black or off, not sure. Can't do literally anything, I tried pressing different keys for minutes and changing USB slot.
EDIT
nevermind, fixed battery problem, Moto G with no power needs normal charger or much longer time on USB
phantom_gopher said:
Cut...
before entering password PC says phone is off, after typing it, PC says it doesn't have drivers (it worked normally before encryption).
I can enter fast boot, but IDK what next. Recovery mode just ends with "NO COMMAND"
Click to expand...
Click to collapse
Dunno if this can help (and sorry for the grammar but i'm not english and i really suck at it), but for me it's normal to see "no command" on the recovery, to see the recovery commands you just need to:
(Token from Customer Help Motorola):
1. Go in fastboot mode.
2. Select the voice "Recovery".
3. Now the phone'll show motorola's logo and then the android bot with the exclamation mark.
So now, you have to press VOL UP for 10-15 seconds. while pressing it, press and release the POWER button.
U should now see the voices in the recovery.
phantom_gopher said:
So, I left the phone in black screen step over night. Battery ran out. I tried turning it on/off, entering fast boot mode, but nothing happened, then connected to USB. LED turned on for a while, screen too, showing battery with 0%. But now nothing again. Just black or off, not sure. Can't do literally anything, I tried pressing different keys for minutes and changing USB slot.
EDIT
nevermind, fixed battery problem, Moto G with no power needs normal charger or much longer time on USB
Click to expand...
Click to collapse
If you can get the phone to be recognised try reflash firmware
Sent from my Moto G using XDA Free mobile app
Thanks for replies. Menu in recovery mode lets me wipe all data, so that's last thing I want to do, but I guess I will have too soon :/
About flashing firmware - from what I've read, encrypted data on phone is protected by password and some kind of encryption key/file. Reflhasing would cause permanent lose of that key and thus whole encrypted data.
The only solution I guess is copying that key on PC. Copying encrypted data if possible, and decrypting on PC using some tool, as Android is open source, so it shouldn't be a problem to extract it's decryption mechanism and run it on PC.
OR copying key to PC, reflashing phone, copying back key and praying this time system will start.
Well what's more important I working phone or a few apps??
If you need to get data off the phone maybe using a otg cable and using the file manager in recovery to copy it all over to the USB otg but as far as that I think your gunna have yo count your losses and learn not to encrypt your phone lol....
Sent from my Moto G using XDA Free mobile app
ME TOO!!!
phantom_gopher said:
Hi, I got Motorola Moto G, original system, no root. I just encrypted my phone, process most probably finished without problems - I stopped watching the phone on around 90%. Then it restarted, boot animation, "enter your password to decrypt the phone", I type it in, green robo shows for 1 second and then black screen (backlighted) :/ After couple hours nothing changes.
If I type wrong password, phone ofc doesn't accept it. Computer sees device, but I can't access it. When I turn off the phone by pressing POWER for long time, it just resets and goes back to asking for passwod again.
Please help me recover my data...
EDIT
before entering password PC says phone is off, after typing it, PC says it doesn't have drivers (it worked normally before encryption).
I can enter fast boot, but IDK what next. Recovery mode just ends with "NO COMMAND"
Click to expand...
Click to collapse
Same happened to me...couldn't even do a factory reset. I had to get a new phone. I was so mad!!! Now I have a Sony Xperia phone. I just bought it outright so I wouldn't be stuck in a plan.
Hey guys,
just replaced my screen by myself and it isn't working. It boots and the screen lights up for a few seconds but thats it. So it seems like I ****ed up somewhere. :/
Now I've got some questions for you guys.
1. What could cause this error? Since it's already not working I don't mind taking it apart some more and trying to fix it.
2. Do you think if I send it to the support from OnePlus they will take a look at it?
3. The whole reason I did this was to get my data back. Is there any way to access the data on the phone without the touchscreen? I encrypted it using CynogenMod. USB-Debugging is enabled.
Thank you so much guys, I'd really appreciate some help. This **** is really tearing me down since it was a lot of work.
I did this on my own phone but Idk about OPO. If you use the power+voldown method to boot into recovery (yes ik nothing on screen) then connect a usb and see what happens
If you power it on, wait 5 mins then call it and if the phone rings you should be able to rule out the display and speakers and storage, obvs if the display is still not on at this point it is probably the display.
you can also adb from recovery and or fastboot so you should be able to see it in there if it is still working (make sure you change the phone for a decent amount of hours before you do any of these) If the display is dead its likely its been on for the last day and dead
Sorry for the late answer, really appreciate your help!
So if I connect the phone to the PC (tried it in recovery and in normal mode) windows detects the phone under "Devices" but sadly if I type in "adb devices" in cmd it doesn't detect the device.
But still, windows is detecting the phone so it seems to still function. I booted into recovery and I could use the touscreen and the lower buttons. I couldn't see anything but it was vibrating whenever I was using the touscreen. So it seems like only the display part is broken.
Can't call the phone since it's fully encrypted so I need to type in a password before booting anything (recovery, normal mode, ...)
I'll try to contact the vendor of the display and see what he has to say.
If anyone got any more tips I'd appreciate them. I'm a pretty big noob so I even appreciate "common sense" tips.
I know this may be a "common sense" thing to say, but double check your connections. Sometimes the connectors aren't made properly and a pin could be covered so you can try connecting and disconnecting several times to see if it clears up.
Since the touch screen was registering and vibrating, then it could be the backlight that's broken. Try holding a flashlight at an angle and see if you can make out anything on screen. If it's the backlight, then you can probably back up your data in case your phone does end up breaking.
reconnected everything multiple times and also tried the flashlight trick. sadly with both no luck
but something good:
adb recognizes my phone in "recovery"
bad news: no commands work, most likely because the phone is encrypted. if I enter a command nothing happens, it looks like its loading forever.
any ideas?
Hey!
I also had the same problem after I replaced OPO's screen about one year ago. The replacement screen was from ebay.
I could see the Cyanogen logo but after a few seconds the screen became black. Booting into recovery mode worked well.
On the video also ROM boots well but the screen stays black.
https://www.youtube.com/watch?v=VcWDCJIkPKQ
Eventually, the screen was defective and I returned it and bought new one.
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
Hi all,
My wife owns a Mi 10 Lite 5G. This morning she was taken some photos to our children and suddenly the phone, apparently, shut down.
She left some time connected to the charger and tried to boot it again, but the only thing she got was a black screen that from time to time blinks and show the 5G logo for less than a second.
If I connect the mobile to the computer it cannot be connected to adb neither PCSuite. If I restart it to recovery or bootloader, it works as expected. The bootloader is locked, so I cannot access to a recovery with a shell, AFAIK.
If I launch the default Xiaomi recovery, the phone is only showed as "sideload" when I run "adb devices".
I'm not very worried about the phone because it is on warranty, but my wife is very upset about some photos that she was taken when the phone shut down, so most of them were not backup by Google Photos nor Xiaomi Cloud
Do you think that the photos can be recovered somehow without unlocking the bootloader?
Do you know if "sideloading" a ROM would erase the data storage (and then wipe the photos)?
Help and suggestions will be very appreciated.
Thank you in advance
After some more research, the mobile is able to boot up, but the screen blinks too fast that it is impossible to unlock the screen using the fingerprint or the unlock pattern.
I'm able to see, while blinking, the notification drawer, and if I connect the mobile to the PC, I'm able to see the new notification about being connected, but if I want to enter settings from the notification bar or open the USB connection mode menu tapping in the notification, I'm redirected to the pattern unlock screen and it is totally impossible to draw the pattern while blinking.
It feels like while the screen is off, the touchscreen and fingerprint reader don't work, so it is impossible to unlock the device right now.
Sadly I didn't activate the debug, so I'm not able to enter in the mobile using "adb" :-(
Any idea?
Lk2 said:
After some more research, the mobile is able to boot up, but the screen blinks too fast that it is impossible to unlock the screen using the fingerprint or the unlock pattern.
I'm able to see, while blinking, the notification drawer, and if I connect the mobile to the PC, I'm able to see the new notification about being connected, but if I want to enter settings from the notification bar or open the USB connection mode menu tapping in the notification, I'm redirected to the pattern unlock screen and it is totally impossible to draw the pattern while blinking.
It feels like while the screen is off, the touchscreen and fingerprint reader don't work, so it is impossible to unlock the device right now.
Sadly I didn't activate the debug, so I'm not able to enter in the mobile using "adb" :-(
Any idea?
Click to expand...
Click to collapse
Not sure what could've happened and Im not to literate on the topic, but are u still able to boot into FASTBOOT MODE?
nocturnosteve said:
Not sure what could've happened and Im not to literate on the topic, but are u still able to boot into FASTBOOT MODE?
Click to expand...
Click to collapse
I have the same problem, I can enter fastboot mode but my pc does not recognize the device
I have the same problem, I can enter fastboot mode but my pc does not recognize the device
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Hi, provided that you have already
- enabled adb debugging;
- installed adb.
Now you have to
1. enter fastboot mode;
2. in adb type
Code:
fastboot erase recovery
then, reinstall recovery if you want to.
s.0105._j said:
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Click to expand...
Click to collapse
How about rebooting to system using volume buttons?