My phone started to lag. I restarted it and when I did this I had to enter the pin to unlock it, I entered it wrong, it seems several times and it makes me wait 30 seconds. I enter the correct pin and it does not recognize it, I keep getting the message to wait 30 seconds. How can I solve that? i guess its a software bug as i try i can't locate it using "find my phone". Should I wait longer to enter the pin? I already tried in safe mode and the same thing happens. I would not like to perform the hard reset. From already thank you very much
If you have USB debugging enabled you can use that by issuing commands via a shell, something like this https://www.google.co.uk/amp/s/www....-security-pattern-lock-adb-110928/amp/?espv=1
Or if you have a custom recovery then it's possible.
Otherwise a hard reset might be your only option.
Some information about your phone would be useful here - ROM installed, recovery, etc.
Peace.
Related
o i woke up this morning and my phone tells me that it has been encrypted? First of all, How and why? I tried to do the factory reset which it was asking me but as soon as i did it, it just restarted and took me back to that screen without doing the reset. Tried to connect it to my pc with Bootloader but it did not find any connected devices and i can not even enable usb debugging mode, because i can not get pass the screen even if i enter the lock screen pin correctly.
I tried to find my device with "adb devices" command but it did not list it.
What else can i do? Please help.
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
veryspecialagent said:
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
Click to expand...
Click to collapse
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
sd_shadow said:
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
veryspecialagent said:
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
Click to expand...
Click to collapse
Window 10?
Yeah. It should remember this phone, since I used this computer to root it when I first got it a year and a half ago.
I used a different cable and got it to pick up the phone (as an unknown device) in Windows but NOT ADB, and the phone to realize it was connected (see last line on phone screen) but they're not talking.
If I boot it all the way up, either regular or recovery (root), it doesn't show at all on my computer.
Like I said, I'd be fine with wiping it, but can't even get to that option.
Install the moto drivers. If that doesn't work then make sure your using a usb2 port and not a usb3 port as its a known issue with moto phones.
I just ordered a new OEM cable.
Also ordered an OTG cable to see if I can force it to startup into a different mode that'll allow me to do something with it.
I'll update this thread once I'm able to test them out.
I got a new cable. My USB ports are not labeled, and my Moto drivers reinstalled.
After rebooting to the recovery screen, I plugged it in and apparently I have fastboot. I checked the bootloader logs and it says:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume down key pressed
USB connected
Windows doesn't pick up anything connected by USB. I can't restart to get root because then adb doesn't pick up the phone either because of the screenlock preventing me from hitting ok to trust my computer.
I'm asking the following because I can't find answers: Can you delete the screen lock file with the only bridge being fastboot, not adb. How can I do a factory reset if rebooting to recovery is our normal way of turnin gon the device with root access? Or would reflashing something work?
command line commands are a perishable skill and it's been a couple years since I did this stuff.
Thanks in advance.
To recap, I either need to be able to get into the directory to delete the pattern lock, or factory reset the phone.
I've tried the pattern lock 79 times, which means I have to wait 300+ seconds between tries. I think an error is causing that though.
Fastboot is my only option at this point as far as using commands goes. Rebooting recovery just reboots it with root permissions, but neither adb or Windows 10 picks it up. Using a brand new factory cord and tried every USB port on my computer, even the USB-C to USB-C. But I can't find anywhere that shows how to get into the directory using fastboot.
In Device Manager, I've been getting an error with Android ADB Interface (The device cannot start; Code 10). I uninstalled, reinstalled various drivers, killed adb.exe, etc., Still happening.
HOWEVER, Motorola ADB Interface is working just fine and goes away when I unplug my phone, returns when I plug it in. Only when it's in recovery/fastboot mode though.
I got into Safe Mode, but computer won't pick it up.
I can't get into Field Test Mode. I did reboot it into something else. I don't know what, but the screen was off and the home button was illuminated. EDL mode? I don't know. Neither my computer or adb read that anything was attached, and i can't figure out how I did it.
I also tried sideloading some pattern lock removers, but apparently you can't do that in fastboot.
Thoughts?
Just to close this out with a solution: I had forgotten that in order to get to the recovery menu, you have to hold the buttons when you reboot recovery. Didn't realize that until I was rooting my Moto e6.
Factory reset complete. No more pattern lock. Though since I've now tried rooting it 4 times with 4 different images and have not succeeded even though I had root before all this, I wish I could have realized the above and possibly gotten in and deleted the gesture.
Lesson learned.
Hold what buttons? I'm afraid I'm in same spot.
onefstfoknv6 said:
Hold what buttons? I'm afraid I'm in same spot.
Click to expand...
Click to collapse
Volume up button and power button
sd_shadow said:
Volume up button and power button
Click to expand...
Click to collapse
Just found this. Timing is everything apparently.
Press and hold the Volume Down and Power buttons simultaneously until the Android Recovery screen appears.
Press the Volume Down button to navigate to Recovery.
With Recovery displayed, press the Power button.
When you see the 'Droid' with 'No Command,' hold Power and tap Volume Up just once and immediately release both buttons.
Scroll to wipe data/factory reset by pressing the Volume Down button
Press the Power button.
Scroll to YES by pressing the Volume Down button.
Press the Power button.
The 'phone will wipe all contents.
Press the Power button.
The 'phone will now reboot to the initial setup screen.
My 5T decided to power off in my pocket this eve. Tried to reboot and now it won't accept my pin. Tried to boot into recovery mode (power & volume down) but only comes up with keyboard, not menu. Tried rebooting using power & volume up to get recovery mode but again comes up with keyboard. Option of forgot password gives factory reset which i want to avoid if possible. Any help please? Thank you
There are multiple ways to bypass a screen lock.
First one is using an adb command, just search on Google "how to bypass android phone with adb" and you'll find it, but for this your phone needs to have USB debugging enabled but it's already locked so it may be useless. This method will work without losing your data.
Other is using a specialised software like "DroidKit" or "DrFone by wondershare", this method will be frustrating because the software may push you to buy a subscription or something but it'll alsol work without losing your data.
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
I assume you didn't have OEM Unlocking enabled before this happened. Without an unlocked bootloader, there is nothing you can do to fix it, because the bootloader will reject any of the necessary commands to reflash the device. If you're still under warranty, seek warranty repair; this is going to require replacing the mainboard, because no one has the necessary tools to perform a low level reflash.
If the bootloader was unlocked, fixing this would be fairly simple because you'd just have to reflash the boot image. But, as I described above, a locked bootloader rejects all the commands that would help in this situation, and there is no way to unlock the bootloader if OEM Unlocking was not enabled.
dch29 said:
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
Click to expand...
Click to collapse
Kind of sounds like a stuck hardware button, either power and volume that's makes the phone think you are holding down buttons during boot to get into bootloader
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Juuuuune said:
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Click to expand...
Click to collapse
Thanks but no change sadly, still completely booked.
Hi all,
I've been researching this phone for a while and I thought I'd take a chance on a functioning phone with a PIN lock. The phone turns on just fine but prompts for the pin when fully booted. I've been away from Android for a few years, but I can't seem to get into recovery mode no matter what I try. Vol down + power just boots to safe mode (pin still needed) and vol up either buzzes 3 times and does nothing or doesn't boot at all. Even tried with headphones plugged in USB port.
I was hoping that once in recovery mode I could wipe device or at least execute some ADB commands, but this is proving to be more difficult than expected. Also plugging into PC while on or off does not seem to appear in device manager, and no device is made in Windows. Are there any options here or should I just try to return to seller?
Thanks
try 'fastboot oem unlock' to factory reset device