Nexus 5X lost lock pattern (fastboot found, adb not found), recovery "no command"
Hello !
So, I've had the same pattern to unlock my screen AND boot my phone for months.
This morning, I can't unlock : I do not remember it, I try to connect the dot "as usual" and then start to think, and now I've got my muscle memory mixed with me trying to figure out what is the pattern! So I try different combination that I think are close.
Then I reboot...
Then... there's this lock on boot time also, I tried a few different combination, and I have only 5 tries left before device WIPE !
- I have installed Android studio, the USB Driver (which I think is the right one)
- I can either boot my phone in normal mode (stuck in the dot patern lock), either in fastboot mode
- From fasboot mode, I can go to recovery, but it says "No command"
- With the SDK tools, I can list my device with "fastboot devices" (and reboot it for example), but I can't have it to appear with "adb devices"
I'll try one or two other time later when I'm tired my patern, to see if i can do it without thinking...
BUT, Can't I remove the lockscreen somehow? I'd preferably backup some files and apps data before wiping it
What do you suggest!?
Thanks in advance
I finally had to wipe / factory reset.
On reboot, he asked me to unlock the phone WITH MY GOOGLE ACCOUNT.
So ... I had to wipe everything, then unlock it. Why, oh why, the boot screen does not have this option!?
Related
I have a 2013 Nexus 7 wifi tablet, bootloader locked, with USB debugging disabled. It decided mid-activity that all it would like to do in life is display the "Google" image on the boot up screen.
I can access the bootloader so I tried doing the standard wipe in recovery mode but that did not work.
Investigated Wugfresh's Nexus Root Toolkit. Drivers (Windows 7) are installed but under Step 4 of the Full Driver Configuration guide it is unable to find the device as an ADB device, even though the device does show up on my Device Manager (but only as bootloader interface, not ADB). Tried to use the unlock feature anyway but on the tablet it just gets stuck on the "unlock bootloader" screen after trying to run the unlock tool (choosing "yes" by pressing the up volume button to scroll to the yes option, followed by the power button to select it).
My questions based on this are simple:
1) Can I unlock this device without having USB debugging enabled? If so, how?
2) Can I restore to factory stock settings without having USB debugging enabled (and not using recovery mode on the device itself, as that does not work)? If so, how?
All of the tools I have seen thus far require that USB debugging be enabled on the device. Since I can't actually boot up the device, there is no way to make this happen. I don't really care about any of the data on the device, I just want it to function again to avoid buying a new one.
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
nhizzat said:
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
Click to expand...
Click to collapse
I believe this also requires that USB Debugging be enabled. I would paste links but the forum prevents me from doing so since I just signed up.
If I am incorrect in thinking that USB Debugging must be enabled for this to work, then please let me know. All I really need is clear instructions on how to hard reset the device without USB debugging enabled. Unlocking just seems to be a prerequisite for that in most of the tutorials I have found so far.
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
skrypj said:
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
Click to expand...
Click to collapse
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Bugnerd said:
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Click to expand...
Click to collapse
Couple of things:
1. You may also have a driver issue, I was playing with this the other day on both my Nexus 5 and Nexus 7. My nexus 5 worked fine, but later that day when i tried my nexus 7 I had troubles with my PC recognizing the N7 in fastboot mode. It would be fine in ADB and would reboot, but then the computer would freak out when it saw the fastboot device. Sometimes it would kinda work, sometimes the N7 would freeze on the bootloader screen or fail to flash during the process. It even locked my PC at one point. I completely uninstalled(per the Step 1 instructions in Wug's) all Android associated drivers(Samsung, LG, Asus, whatever. Kill them all) on the PC and reinstalled and it solved the issues. It sounds like maybe your PC is failing to flash properly like mine was.
2. Not sure if you tried this yet but; go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. I had to do this for both my N5 and N7.
Keep in mind, you will lose EVERYTHING on your N7 if you unroot and flash, including your internal storage.
Yeah, it does not seem to want to do the unroot + flash even with the override of checks. It seems unlocking is really a prerequisite for that tool (according to the text that appears as it proceeds), and unlocking appears to require the USB debugging. If it really can be unlocked without that, then it is not cooperating and just getting stuck on the unlocking screen. I expect it is now a very expensive paperweight.
All of this nonsense just over a year since I bought it, of course.
Try it with another computer, another USB cable...
I'm in the same boat, can't get it to unlock so it's essentially dead now
I've tried original and a G3 usb cord and nothing, front and rear USB ports, just will not unlock, almost to the point of sending it on and paying to get it fixed if possible , will try another computer first
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Az-one786 said:
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Click to expand...
Click to collapse
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
skrypj said:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Click to expand...
Click to collapse
I looked into this a week or so ago and I think I determined that it would also require the USB debugging to be on (at least from the tutorials). Do you have any recommendations of tutorials on this process? Screwing around with this stuff is not really my bag.
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
Click to expand...
Click to collapse
Ok.., Your have no choice by now, you'll need to find a working driver for your PC to get recognize your tablet when on fastboot mode..
I've got this issues before when I want to update my tab using toolkit...
My PC can recognized my tab as adb devices, but when it's reboot to check fastboot status it fail to detect my device is on fastboot mode..
But maybe I'm so lucky that day, Moboginie notification has pop-up and it's has searching and found the driver and fix it itself ...
Then i try again and this time it's has no problem at all till now... I still can access my storage using Moboginie but until now window explorer still fail to recognized my N7...
It's so weird isn't it ...
Try Moborobo
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
Click to expand...
Click to collapse
After the recovery screen with "sick" Andy, did it automatically begin to reboot? If not, you know that it's very tricky with the power+vol up button (sometimes I think it's power+both volume buttons that works) to access that screen in recovery (the one past sick Andy). Sometimes I've tried five or six times. I have twrp so I can't check it out right now.
As far as adb/fastboot drivers set up to run any commands, I thought they were required. I'm not certain about USB debugging. It seems you've tried with your device in fastboot and running Cmd (fastboot oem unlock) from your fast boot directory. Do you get a device code when you enter [fastboot devices] while in that directory? If not, your N7 will not accept fastboot commands.
Sent from my Nexus 7 using Tapatalk
Hi guys,
my wiley fox swift gets stuck in a continual optimising apps cycle. I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted) it worked fine yesterday and today i can't get it to work.
It's always optimising apps, if it's finished then i see the cyanogen logo and it starts optimising again shortly after.
I removed the battery and did wait about 15 minutes before putting it back in, i tried waiting (after 2 hours+ of it optimising i gave up),
i does not get recognised when i connect it to the pc (although i only used it to put stuff on the sd-card before) maybe a driver would fix this but i'm not sure which one.
I'm pretty clueless right now and i would be happy if someone can help me.
Saw the same thing on a friend's device today, used fastboot to factory reset the device. Insert USB in a powered-off device while holding vol+ then using fastboot do a "fastboot -w" to factory reset and recreate the (probably corrupted) data partitions.
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
dajohre said:
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
Click to expand...
Click to collapse
ADB needs debugging to be enabled in developer options
FASTBOOT will only work if the phone is in bootloader mode
I already said in my first post:
dajohre said:
I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted)
Click to expand...
Click to collapse
since i never changed anything in my phone I haven't enabled debugging in developer options, if I could access the bootloader mode I could reset my phone but like i said,
it enters fastboot and not the bootloader from which i could enter recovery mode
under these circumstances, can i do anything?
see here https://wiki.lineageos.org/devices/crackling/
Note they call bootloader mode Download
Ok i can access recovery mode now (it was explained wrong here)
i tried to factory reset but the problem still persits.
in recovery mode i did go to ->Wipe data/factory reset then i had the options (No/No/Yes -- delete all User data/No)
i choose the third option and it did load a short while. after a reboot it still wants to optimise apps.
what's the best option now? i can choose (Apply update\ Wipe data/factory reset\Wipe cache partition\wipe media\reboot to bootloader\View recovery logs)
Fix
Hi,
I had the same issue and wrote the Wileyfox customer support.
They provided me the following instructions to fix the issue:
Download:
* 1 - ZNH0EAS2NH
* 2 - ZNH2KAS7EB
* 3 - TOS111B
Repeat for File X in [1, 2,3] :
* Goto Recovery
* Update your phone using File X
Since this is my first post I am not allowed to post links.
Find the full document including file links here: h t t p s : / / we . tl / B1IpUP6wtB
Already after running the first update my phone booted again.
Only thing I noticed is that the UI feels a little laggy / slower than before.
Regards
Long story short.
My phone dropped in water.
Tried dry with rice, dehumidifier, open, clean contacts, dry . Screen is not working, totally black no responses and neither is the front button.
However, I can start, reboot, enter in fastboot and normal boot. I know it because I connect it to PC through USB and I can see the device connected as MTP device in normal mode and as android device in fastboot.
I cannot comunicate, nor extract info with ADB as USB developer mode was not enable. ADB doesn't see the device.
fastboot do see the device and I can get serial number and all variables with "fastboot getvar all".
I tried to flash a custom recovery from fastboot but It says that bootloader is locked and I cannot unlock it as I have no screen.
I tried to boot external image with fastboot boot image but again I cannot as bootloader is locked
I doesn't seem to autoconnect to my home wifi nor to the phone carrier network inserting a sim card with pin lock removed.
I have now ordered a new phone but I would like to extract info from this phone and acces to the storage.
Does anyone have any idea what else can I do to acces the phone or how to remove the bootloader lock withouth screen ??
Thanks
I have a Nexus 7 (2013) stuck on the Google screen, like so many other people. I need some advice please from those who know more that I.
Power + Vol down brings the 4 options Power Off, Start, Recovery, and Restart bootloader. each leads to stuck screen or blank. I have reseated the flexible cables inside, with no change.
Command: "Fastboot devices" recognises the tablet and gives the serial number 07f3ddc1.
If I use Fastboot oem unlock, the tablet screen changed to "Unlock Bootloader" with options Yes and No. (see screenshot). I selected Yes. Wait forever erasing userdata.
Fastboot -w tried.
A response said the userdata had been successfully erased. (If I try oem unlock again it still responds with erasing userdata, but I presume it is then trying to erase what is no longer there).
Although it says "Erase userdata but not formatting automatically formatting", (see screenshot 2), I have obtained a response which says the formatting has been done, with details (see screenshot 3).
User data loss does not matter, my files were all copied to laptop ( Lenovo at the time. Now using Dell with Windows 10)
My question therefore is: If the reformatting has been done, does this mean that the Operating System is no longer in the memory, and I will have to sideload a new image?
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.