I did the infamous update to Android 12 yesterday and this morning tinkering with the new settings I accidentally blocked myself out of my phone.
Before testing yourself I want to give a warning to not you bother to try this setting on, just in case the same thing happens to any of you: it was a setting called "Quickly unlock screen without password" or something like that, it was in Settings > Privacy & Security > Lock screen Password. If anyone that still has the Android 12 update installed would be so kind to share some screenshots of those steps I could tell right away which option was the one I activated, since I can't even access my phone anymore...
Don't know why, but it seems that with this option the system just tries to fill the password but it always fails and it just keeps vibrating forever and can't do anything at all. The only time it stops is after rebooting into the SIM unlock prompt, but after unlocking the SIM it starts vibrating again and can't even input my password.
After this now I'm trying to recover all my stuff from my phone before doing a factory reset, which seem inevitable at this point. I have tried to access mass storage from Recovery Menu but it doesn't seem to be recognized by my PC. I have seen that OnePlus devices have different recovery menus, this one has a menu with four options (Format data, Reboot device, Power off and Advanced) and at the bottom it says "Ver 1.2", which tapping on it twice gives a message telling to go into Download Mode, but it doesn't seem to do anything aside from rebooting.
Also tried to go into Fastboot from the recovery menu (Advanced > Reboot into Fastboot mode) but it just shuts down instantly after the Fastboot logo shows up.
So, please, could anyone give some advice here? I'm pretty much lost at this point and I don't want to factory reset right away just yet. Any help will be appreciated.
are you able to fix your phone?
Related
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.
hi sorry for tge urgent request its just I need my phone for alarms to remind me when to take my various meds.
My screen is stuck in bootloader unlocked scren and i cannot switch it off. No access to settings
Somehow i managed to get it into twrp screen but I dont know how I did it, and i didnt know which option to choose after swiping, so screen went back to 'bootloader unlocked scren'
I got back in again to twrp screen but dunno how, and chose reboot, but screen just went totally black, but still on if you know what I mean.
I cannot seem to get it back into twrp screen
I an very tech naiive and routed my phone to get rid of bloatware by watching some very comprehensive indian guys videos.
I cannot understand all the jargon.
I also downloaded 'unlocked bootloader warning fix' but it got stuck at cmd screen, kept saying 'waiting for device' and I didnt even know whether to plug the phone into the laptop or not.
Plus my battery runs out quick.
Dunno how i managed to get it back to TWRP, dont even understand TWRP, what option would I choose on TWRP to get me back into my phone as I rely on it heavily.
I use the alarms and reminders as I have bad adhd, and really need them, a paper diary doesnt cut it, I also need reminding when to take my meds, but without my phone i cant.
So, if anyone can help me get back into twrp then into my phone by teling me what to press I will be greatful. I dont have access to the settings as it is stuck on bootloader unlocked screen.
thanks in advance and remember your talking to a tech dummy who came here cos her screen is locked, lol and thanks for reading and your kind help in advance.
two people also asked on here http://forum.xda-developers.com/moto-e/help/moto-e-stuck-bootloader-unlock-warning-t3169916 but no answers.
Mebbe a few of us need help here, much apppreciated.
It depends on what you flashed on your phone recently
It can happen due to broken kernels or ROMs for not your version of phone
Get a ROM like cyanogenmod or something like that for your device put it in your external sdcard
Press volume down and power button until the screen is off and then keep pressing it for 20 seconds
Leave it the fastboot mode will start
Use your volume down button to go to 'recovery mode'
Volume up to choose it
Go to wipe
Go to advanced wipe
Select system, cache, dalvik cache, data.
Swipe to wipe
After the wipe is complete go to install
And choose the file you just downloaded in your external sdcard
Swipe to flash it.
This should work
OR
Try flashing back your stock firmware via fastboot mode
http://forum.xda-developers.com/showthread.php?t=2759495
This thread may help you.
Sent from my Moto E using Tapatalk
Hey folks, few days ago i got kind of broken Zuk Z1 phone. After fixing issue with battery i tried to reset it and these is where things got weird.
Before i go into problem itself, im new to flashing/reinstalling OS and i have never done it before. But being a developer im not stranger to command line and compiling (windows and linux) and im willing to use nuclear methods.
Phone boots up normally and it works fine (except home/fingerprint button - im planing to replace it after i fix OS issues). But i cant reset it and i cant flash/reinstall it. Going into settings and selecting reset to factory settings, reboots the phone and it just gets stuck at boot logo (the first screen you ever see - dont mistake it for OS logo). It does not constantly reboot, it just shows that screen and that is it. Enabling developer mode, choosing reboot and selecting recovery mode does the same thing. Powering it off and holding volume up,down and power does the same thing. Holding power and volume down gets me into menu but i cant reset phone from there, not even clear cache like on some tutorial i found online. My options in that menu are these:
Board test
Current test
SD Update
Restore QCN
Save Parameter
Reboot
Some info that might be useful (some are from CPU-Z):
Model Z1 (Ham)
Bootloader K9#CM_8A1690F
Cyanogen OS 12.1-YOG4PAP25I
Android 5.1.1
Kernel 3.4.0-cyanogenmod
SElinux status Enforcing
OEM Unlocking in developers mode enabled
I dont think that the phone is rooter, and i dont know how to check or if i can do it without working recovery mode. I also tried to connect it to PC using ADB but no luck there (I didnt even find working driver). Also there is no SD card slot so i guess SD Update option from that menu is useless (or is it something else?)
I could use it the way it is, but i really dont want to. so help is welcome since i have been trying to fix it for past few days.
Oh and if you need more information or anything just tell me where to look and for what (i dont mind installing additional app)
My wifes Pixel 6 was recently updated to Android 13. From what I can gather the update was not sucessful - The process got stuck on the 'G' screen with the scrolling bar undernath for several hours before my wife gave up and forced the phone to reboot. She has since managed to perform a factory reset from recovery mode but the phone constantly reboots during the android setup screens. I'm now in posession of her phone to try and fix the issue mysef, however recovery and rescue modes both display the 'no command' screen.
I have tried to reflash a stock rom using ADB but this does not work as 'OEM unlocking' is not enabled, nor can it be enabled as the OS refuses to load all the way before a random reboot occurs.
I'm really hoping someone can tell me how to get around the device lock so I can flash this thing!
Thanks
Whether it can enter REC？
cyclo111 said:
My wifes Pixel 6 was recently updated to Android 13. From what I can gather the update was not sucessful - The process got stuck on the 'G' screen with the scrolling bar undernath for several hours before my wife gave up and forced the phone to reboot. She has since managed to perform a factory reset from recovery mode but the phone constantly reboots during the android setup screens. I'm now in posession of her phone to try and fix the issue mysef, however recovery and rescue modes both display the 'no command' screen.
I have tried to reflash a stock rom using ADB but this does not work as 'OEM unlocking' is not enabled, nor can it be enabled as the OS refuses to load all the way before a random reboot occurs.
I'm really hoping someone can tell me how to get around the device lock so I can flash this thing!
Thanks
Click to expand...
Click to collapse
You can try sideloading the full OTA. That doesn't require an unlocked bootloader.