Database Info

[Q] Encryption broke my phone

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.

Replaced screen, not booting

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.

Recover photos off pixel with a dead screen

The screen on my pixel has died after the battery drained to 0. I charged the phone for 2 hours but the screen wouldn't turn on. I spoke on the phone with google support and they sent me a return label to exchange the phone. There are some important photos on the phone that were not backed up to google photos before the phone died. I tried doing ADB pull but it says device unauthorised. The screen is completely black and touch appears to not work either. The fingerprint scanner doesn't seem to unlock the phone because it vibrates everytime i press it, maybe because it's asking for my password after I rebooted. Is there any way I can recover the photos?

You could try using a mouse connected with a USB OTG adapter. It will be difficult without being able to see the screen, but if you can manage to authorize your computer for ADB, then you should be able to use adb pull to retrieve the pictures.

restart after unlock

hi my one vision every time when i unlock or lock restart device. any help?

normee66601 said:
hi my one vision every time when i unlock or lock restart device. any help?
Click to expand...
Click to collapse
I tried to use Action Launcer on my One Vision, it started doing EXACTLY that (restart after unlock).
The only way I could solve it was entering in recovery and wiping it clean. Here's how to do it:
1. Turn it off (hold Power Button for a few seconds)
2. Hold Power Button + Volume Down for some seconds
3. When you enter fastboot mode (with the android robot on screen), release the buttons
4. Use Volume Down to choose Recovery Mode and press Power Button to enter it
5. It will show the Android Robot with "No Command" on screen, when you get on this screen, hold the Power Button and press Volume Up then release the buttons, you will get into Recovery Mode screen
6. At Recovery Mode, choose Wipe data/Factory Reset and confirm when asked.
This worked on mine.
(link to procedure: https://www.hardreset.info/devices/motorola/motorola-one-vision/recovery-mode/)
It will wipe your phone clean. If after that it don't work right, you better get your phone to warranty.

Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision

I was wrong... It tried with other launchers, same problema. I've read that some phones with problem in the fingerprint sensor have this behaivor. As soon as you add fingerprint as the unlock option, It may reboot randomly or when you try to unlock.
I've wiped It again and confirmed this behavior on mine. I'm going after warranty on monday.

tys0n said:
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
Click to expand...
Click to collapse
I´ve got the same problem. How did you get it to factory rest?

badadam said:
I´ve got the same problem. How did you get it to factory rest?
Click to expand...
Click to collapse
I made factory reset from recovery.
Sent from motorola one vision.

tys0n said:
I made factory reset from recovery.
Sent from motorola one vision.
Click to expand...
Click to collapse
Thanks, did the same thing. Just had to google my way to finding out how to get into recovery.

tys0n said:
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
Click to expand...
Click to collapse
I've made new tests on my Motorola One Vision... That's the problem. As soon as you set the default USB mode to file transfer, my phone starts to reboot even without plugging in the USB cable...
I've wiped it clean, started with the bare minimum, just logged on Google Play Store. I activated the default USB mode to "File Transfer" on the Dev Options.... With no lock option, it works OK. As soon as you set ANY locking method (pin, pattern, fingerprint) it reboots when you try to unlock the phone...
Seems like the only way to solve it is to keep the default USB mode unchaged.

erick.noleto said:
I've made new tests on my Motorola One Vision... That's the problem. As soon as you set the default USB mode to file transfer, my phone starts to reboot even without plugging in the USB cable...
I've wiped it clean, started with the bare minimum, just logged on Google Play Store. I activated the default USB mode to "File Transfer" on the Dev Options.... With no lock option, it works OK. As soon as you set ANY locking method (pin, pattern, fingerprint) it reboots when you try to unlock the phone...
Seems like the only way to solve it is to keep the default USB mode unchaged.
Click to expand...
Click to collapse
Yes. For now we have to change usb mode from the notification panel each time, untill they got it fixed.
https://forums.lenovo.com/t5/motorola-one-vision/Bootloop-when-Developer-options-are-enabled/td-p/4444229

I disable fingerprint, now works perfect

normee66601 said:
I disable fingerprint, now works perfect
Click to expand...
Click to collapse
You disabled only fingerprint? Are you using any other unlock method, or just swipe? Mine got into bootloop even if I add a pattern.

when device restart swipe down status bar press setings then unlock and remove fingerprint

After you have changed the default USB mode to "transfer" on the Developer Options, you cant do that. If you have any sort of lock in place that's different from "swipe to unlock", your phone will reboot on any try to unlock it, even if you try to get to settings (it will ask to unlock, then when you try, it reboots).
If you get into the "bootloop", the only way to get out of it is to enter recovery and wipe the phone. The only way to avoid the bootloop is to a) don't change default USB mode to "transfer" on Developer Option or b) only have "swipe to unlock" as the lock option.
If you set a) and anything different then b), you get stuck in bootloop.

I was sad because I'd need to make a hard reset on my phone after this bootloop but then I tried to start it connected in my PC through USB and then BAM it worked out, boots without restarting, it worked out for me, it should for yours too!

Just wanted to confirm, for all those falling foul of this little bug, that Riverm4n's previous advice does indeed work. And saves the heartache of a full system reset..
Just wanted to clarify the guidance a little..
So with the phone on, and on the lockscreen, plug into your PC.
Let Windows do it's driver install thing of it's the first time it's been plugged in..
Then type in your unlock code on the phone..
Potentially could still go into the reboot again, just leave it plugged into your PC and the next time the phone comes on typing your unlock code in should see it unlock without rebooting!!
Don't forget to disable the developer settings or change the usb thing back!!!

riverm4n said:
I was sad because I'd need to make a hard reset on my phone after this bootloop but then I tried to start it connected in my PC through USB and then BAM it worked out, boots without restarting, it worked out for me, it should for yours too!
Click to expand...
Click to collapse
tonysonyhtc said:
Just wanted to confirm, for all those falling foul of this little bug, that Riverm4n's previous advice does indeed work. And saves the heartache of a full system reset..
Just wanted to clarify the guidance a little..
So with the phone on, and on the lockscreen, plug into your PC.
Let Windows do it's driver install thing of it's the first time it's been plugged in..
Then type in your unlock code on the phone..
Potentially could still go into the reboot again, just leave it plugged into your PC and the next time the phone comes on typing your unlock code in should see it unlock without rebooting!!
Don't forget to disable the developer settings or change the usb thing back!!!
Click to expand...
Click to collapse
Yeah the problem is because is enable fingerprint and default USB configuration was changed.

Just like to thank OP for this - just received a new Vision - & while setting up I had enabled Developer mode mainly due to problem with PC not seeing phone & 1 tip I read was for 'USB Debugging' to be switched on
- while in that menu I decided to force USB file transfer over 'cos of the annoyance having to select it each time I plugged phone in to transfer some pics/doc etc over
Next time I picked up phone it was in boot-loop & I thought it was broken ... PANIC STATIONS !!!!
Factory reset fixed it
- & since being new phone I didn't lose too much of the stuff I had been reinstalling/replacing (which were mainly apps to replace missing 'functions' I had on old phone such as a 'repeat notification/flash camera LED' if unread)
Did lose some game progress on a couple of games I have/had, which is annoying (wish we had a APK Data backup that didn't need root & which isn't Helium since that seems pretty unstable for me atm but then again it's not been updated for a while) but I think I can live with that
Once again thanks

Well, happened to me. I certainly wanted to avoid factory reset. It's a known bug being reviewed by Motorola/Lenovo. Happens when you change the USB connection default action in developer mode and you have any sort of screen lock.
Here is what I did to avoid factory reset, I had fingerprint lock with code.
1. After boot you get to screen lock. I you try to unlock with the code it reboots.
2. In that code enter screen, use a finger not enrolled. You'll see a message that fingerprint was not recognized.
3. Enter now your code and the device won't reset this time.
4. Go to developer options and rollback the USB default action to "no data transfer".
or
1. Factory reset
or
1. Wait for a ROM update
or
1. Return the device to seller and get another one

Avoiding factory reset!
mauro235 said:
Here is what I did to avoid factory reset, I had fingerprint lock with code.
1. After boot you get to screen lock. I you try to unlock with the code it reboots.
2. In that code enter screen, use a finger not enrolled. You'll see a message that fingerprint was not recognized.
3. Enter now your code and the device won't reset this time.
4. Go to developer options and rollback the USB default action to "no data transfer".
Click to expand...
Click to collapse
Thank you for sharing this, it actually allowed me to fix this without wiping everything! I hope they patch this issue soon. I had just finished setting everything up and I thought I would have to start again.

tys0n said:
Yes. For now we have to change usb mode from the notification panel each time, untill they got it fixed.
https://forums.lenovo.com/t5/motorola-one-vision/Bootloop-when-Developer-options-are-enabled/td-p/4444229
Click to expand...
Click to collapse
I've have the same problem on my Motorola One ACTION XT2013-4.

OnePlus 7 pro broken screen

Dear all,
I recently got water damage on my OP7Pro. Now my screen doesn't work and the phone doesn't respond to touch. So I am left with a black screen that sometimes flickers so I can see the bare minimum.
The phone however does boot into the system and recovery and it vibrates when I slide the notification button up and down. When I plug it in my PC, it only shows the drivers and stuff.
Now I know I cant fix this phone, but I want to recover some important photo's.
Here is the real problem:
Since I have never adjusted the developer settings;
OTG allowance is disabled
USB debugging is disabled
So when using adb, it doesn't recognize my device.
When I boot into recovery I have to fill in a password.
Yet I DO know the password, I just don't know how to enter it.
I'm on the internet for 2 days now without succes.
Does anyone know how I can recover the data?
Any help would be highly appreciated.
Thanks!
Martijn

martijn10022 said:
Dear all,
I recently got water damage on my OP7Pro. Now my screen doesn't work and the phone doesn't respond to touch. So I am left with a black screen that sometimes flickers so I can see the bare minimum.
The phone however does boot into the system and recovery and it vibrates when I slide the notification button up and down. When I plug it in my PC, it only shows the drivers and stuff.
Now I know I cant fix this phone, but I want to recover some important photo's.
Here is the real problem:
Since I have never adjusted the developer settings;
OTG allowance is disabled
USB debugging is disabled
So when using adb, it doesn't recognize my device.
When I boot into recovery I have to fill in a password.
Yet I DO know the password, I just don't know how to enter it.
I'm on the internet for 2 days now without succes.
Does anyone know how I can recover the data?
Any help would be highly appreciated.
Thanks!
Martijn
Click to expand...
Click to collapse
If you never unlocked the bootloader or enabled add, you are stuck.