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.
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.
I was copying a movie onto my H950 when it started to take a long time. I was in a rush so I canceled the file transfer and waited for the computer to finish prompting me about the cancellation. I then unplugged the phone from my computer and noticed that the charging light was still on. I then noticed the phone wouldn't wake up when I pressed the power button. I held the power button and the volume down button to do a hard reset but after the LG start up screen all I got were some random numbers in brackets and "Fastboot mode started" in small text at the upper left hand corner of the screen. The numbers tend to change from time to time.
I have done multiple resets, let the battery die all of the way, recharged all of the way, factory data reset and nothing has changed a thing. When I boot it into download mode it sits there for a minute and by the time the computer sees that it has been plugged in the phone goes back to the black screen with the "Fastboot mode started" text. The computer also only recognizes it as Android Bootloader Interface in the device manager.
It is recognized by the "fastboot devices" command but thats about all I have been able to get out of it. It wouldn't accept flashing a new system image on it either. Please tell me there is still hope. I cant wrap my head around how something so normal could have caused this to happen. It has been rooted for around 6 months and I haven't done anything to the phone sense. I cant even remember what version I was running. I would greatly appreciate any help or advice.
somehow corrupted the laf partition maybe !!
try :
1. fastboot continue
2. fastboot reboot
if it does not work contact LG
i have the same problem with the same variant . tried everything but the kitchen sink .
took it to LG Romania but because its an US device they could not help .
3 days ago I've woken up to my "supernatural" work-out to find out the light on the side of the oculus is RED, which was funky cause it was plugged in all night.
SO, I've looked inside and saw that it's "Updating' I was all happy to get the latest version, but then it just finished, showed the logo blinking as usual and then - NOTHING!
Blank screen, after a couple of seconds - Again started up, Logo, Updating, Logo, Dead. -->> Over and over again and again!!!
I can't connect to it via the phone APP as it keeps restarting and going to update like mentioned, computer doesn't connect as well!
I tried holding down the buttons and factory reset the thing, it goes to Erasing -> Update - > Logo - DEAD! same loop, looks like the "Basic" upgrading is faulty so it can't even factory reset.
Tried to choose 'sideload' option from the "USB update menu" - no good! reboots to loop again.
I can get it to stay stiil if I pop up the 'USB UPDATE MENU' with the buttons and just leave it there, USB Connection to PC shows up 'Oculus ADB Interface' in device manager but I can't get the device to show on "Adb devices" Probaby because it's not on 'developer mode', maybe.
Tried to update drivers and to re'install adb.
PC app shows oculus as connected but I can't do anthying through there...
Contacted support 3 days ago - Nothing! they will look into it... NOTHING! sooooo angry!
EDIT>>
I have managed to pair once from the phone APP but as it "finished' the setup it went straight back into that update boot loop and can't connect again on phone.
Was hoping to manage to get it to developer mode and maybe force an update via adb.
I've been coding for most of my life, playing around with android phones software and such... so i'm not a complete idiot when it comes to these things but this one looks like there is no other choice but just sending it back for repair.
But these guys don't answer or anything... don't even know If I can send it or not, where to etc...
Boot loop:
https://photos.app.goo.gl/zsh8gws7eD8yRR4z6
Tried factory reset:
https://photos.app.goo.gl/h8GC7nurrkQnNsLe6
ANY IDEAS?
come on you guys!!! nothing?!
OK,
Found out I can make the device show in ADB Devices list if I manually load the USB Update menu (volume+power) and then choose sideload option.
However, this won't help much it disconnects from ADB as soon as it finishes loading the logo and restarts the update loop.
I tried to start the sideload as soon as it pops up in the device list, got to 4% serving and then connection was cut off...
If there was a mini update file (couple of KB\MBs) with some settings to make the oculus reset into sideload mode and stop looping i could sideloap a proper version and make it work again maybe.
Please someone help me fix the oculusssss pleaseee!
I same!!!
and oculus support said
"With that in mind, Oculus will not be able to offer warranty replacment/repair for this headset. I can only suggest that you consider purchasing a replacement device from our online store or an authorized retailer. "
fxxxk!!!!!!!!
You're great man. I didn't have such an issue, but I also didn't know the Quest had a menu like this.
Hey @Shlomikalfa - did you ever come back to this and make any progress? With the Quest 2 situation now, and FB logins required, I suspect a LOT more people are going to get interested in this idea.
Just to add, my Quest2 has being working just fine since I got it at launch from Amazon. I was playing beatsaber last night until it ran out of battery and shutdown. I plugged it in to charge and went to bed. This morning, I tried to turn it back on, and it went straight to the USB UPDATE MENU!!
I tried every single option in the USB UPDATE MENU, including factory reset, and it reboots and goes immediately back to the USB UPDATE MENU again. The only option that doesn't take you back to that menu, is POWER OFF! (LOL)
But if I power off, as soon as I power it back on, I got the same menu!
The volume buttons are not stuck at all... since I can use then to navigate the options in the menu.
So I just created a ticket at Oculus support to see what they say!
Good thing is that Amazon.ca gave me until January 31/2021 to return the headset... so if Oculus doesn't sort it out, I'll be returning to amazon for a refund!
Funny thing though. While in this "USB UPDATE MENU", I plugged it in my linux box, and it shows as a fastboot device! I can even run "fastboot reboot" and it indeed does reboot the headset!
I tried "fastboot flashing get_unlock_ability" just to see if it would say 0 or 1... but got an error: "FAILED (remote: 'unknown command')"
Does anyone want me try anything? (as long as the warranty is not voided since I'm waiting support answer! )
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?