Google Nexus 5 :: Android 6 - Forgot Unlock Pattern But Bootloader Is Unlocked
Nov 1, 2015
I forgot my unlock pattern and I don't have my device in ADM ... But the bootloader is unlocked, so I think I can install any image I want, right? Could this be a way to get into my device? So any solution to unlock my device without doing a hard reset?
I forgot my lock pattern, and even though I've tried the wrong pattern about 80 times by now, the "forgot pattern" button won't show up.I know my gmail address and password, so that's not a problem, I just have no way to enter it.When I've tried to lock my phone with a password using the android device manager I got a message saying that a lock request has been sent, but right after that it says "We could not lock your device. Please try again."I've also tried turning it off and on again, hoping that it'd be unlocked after I've entered my pin, but it's still locked.While I know that I might end up having to reset it.
I have a rooted nexus 5 running android 6.0 MRA58N. After I updated I couldn't set a lock pattern any more. I can access every area in settings accept the lock screen session. When I try to enter the lock screen session it gives me the "unfortunately, settings has stopped message."
My nexus 5 just turned off and is stuck on the boot animation. I am able to access the bootloader and have already tried to wipe cache and performed factory data reset but the phone is still stuck on the boot animation. I have tried to unlock the bootloader with 1-click-nexus-5-bootloader-unlock as well as CF-Auto-Root-hammerhead-hammerhead-nexus5 tools but after I accept to unlock the bootloader, the phone reboots and gets stuck on the boot animation. The bootloader status remains locked.
well my friend was messing about, and changed my unlock pattern. then forgot it.. i've tried to restart it but i can't? PLEASE HELP. is there any other ways i could restart it? i've read other comments saying that something comes up asking for gmail account information but i haven't come across anything like that.
I'm having a problem with my phone security. I unfortunately forgot the required pattern to unlock my phone and now it's isn't recognising my answer to the security code question. Is there any means to restart the phone or get access to phone menu again ??
I have a complicated situation with deleted files (photos and videos) recovery,
Phone : Nexus 5 Android: M (6.0) BN: (MRA58N) Root/unlock: Unrooted and Unlocked
Some one has deleted all the files in the camera folder in the gallery, i want to restore these deleted files. After hours of digging the internet, i found a lot of applications that doesn't work (almost all of it either require root or require USB Mass storage), and as you know we are only able to connect to the PC using MTP protocol. Rooting the device requires unlocking it which will cause the whole phone to be wiped.
I have two questions:
1) Is there any (REAL) way to recover the deleted files (Images and videos) with the current circumstances (Unrooted, Unlocked, MTP Connection) ?
2) If the answer of question 1 is NO, if i unlocked (and for sure wiped) the phone then rooted it, can i still have the ability to recover these files, i mean how badly the wipping process will affect the internal phone storage?
dkotoric has realised this is due to using the double tap to sleep function on some launchers. Locking your device with that prevents the fingerprint scanner from allowing access for some reason. So today was my first full day with the 6P. It's a truly great device. A whole bunch of times though when I've come to unlock the device I've had to put in my pattern because it won't accept the fingerprint scanner.
The icon at the bottom of the lock screen that should be a fingerprint is just a lock symbol. If I then lock the phone again and reunlock it works as expected. Not sure if this is a software bug or some setting I've got wrong. Can't see a pattern for when it does it though. I've switched 'require pattern on restart' off which has made no difference.
I'm not an Android rooting noob (my rooting goes back to OG Moto Droid in late 2009) and I'm sure it's something ridiculously simple I'm missing but I can't get my bootloader to unlock. I've tried ADB/Fastboot, WUG's Nexus Root Toolkit, and Chevy's Android Job Box. Nothing works.
I got my 6P today, SIM'ed it up, booted up, logged in, enabled USB debugging, installed the drivers, and let it update. When I opened WUG's NRT, I saw that I had an Android build one step later than the NRT. Mine's MD80BL and K is the latest in the NRT. I thought that shouldn't be a problem and selected the "any build" option with the Nexus 6P. I went through the installing drivers process and can access the file structure of the phone through W10.
I then went to the unlock bootloader option, clicked through the prompts until the phone rebooted into the bootloader and clicked the OK button to unlock the bootloader. About two seconds later a window popped up on my desktop telling me my bootloader was unlocked, my data was wiped, and I would have to go through the setup process on the phone. Excellent, except my phone booted right back to my stock homepage. I tried again with the same result.
I then tried it manually using ADB/Fastboot. The "fastboot devices" showed a connected device which I assume is my 6P since I have nothing else Android connected. When I type in "fastboot flashing unlock" I get all the fastboot commands/options as if I typed an unknown command. "Fastboot oem unlock" didn't work either. I went and downloaded the latest SDK and retried everything with the same result.
Just wanted to upgrade my sisters phone which was running an old 5.1 version (custom rom, so the phone was unlocked and rooted already) to an android 6.0.1 custom rom. So I flashed newest twrp and flashed 6.0.1 bootloader and radio.img via fastboot using wugfresh tool and the files from the thread on here. now when trying to get into recovery, I am stuck at the google logo.
Ok, so I just got my awesome new 6P. Here's what I've got so far:
I have the SDK, ADB and Fastboot components installed, drivers listed, and everything like I've been reading here and other forums.
So far I've been able to verify that ADB and Fastboot both seem to see my device OK so I know the drivers are good.
USB debugging mode is enabled in the Developer menu, and the option for 'allow oem unlocking' is enabled as well.
From what I'm seeing this all adds up to 'should work', but it isn't.
I originally tried the 'fastboot oem unlock' command found in older posts, and when that didn't work found (from what I'm able to determine) the latest command of 'fastboot flashing unlock'. Unfortunately, all this gets me is this: [URL] ..... (wont let me just link the image since I just had to make a new account. Been too long since I last logged in apparently ...
I am already unlocked and rooted, but I would like to relock the bootloader assuming that I can unlock it for future updates without losing data. The Nexus 5 had a boot locker app in the App Store which allowed this, but I do not find an option for the 6 P.
Last year I bought the nexus 6 and for the first time (I've had a lot of android phones) in my phone was also disabled force encryption after the bootloader unlock, twrp and root. So I decided to decrypt it because reading on the nexus 6 forum some devs suggested this to increase the phone performances.
I read that now twrp supports encryption and that Google increased the phone performance also with force encryption enabled.
I have a nexus 5 that I was preparing to hand down to my wife. I had transfered everything over to my new phone, and initiated a factory reset. It rebooted to the "erasing" screen, and sat there for about 20 minutes, before switching to the dead android screen (w/ red triangle.) I thought that was odd, did some searching, and tried the recovery mode from the bootloader. That produced the same results. So now I'm stuck.
From the boot loader I can access the following options:
Start -> Erases for ~20 minutes, then dead android Restart Bootloader -> Screen goes blank, phone vibrates, and then back to the bootloader screen Recovery Mode -> Erases for ~20 minutes, then dead android Power off -> turns off the phone
I called Google, and the tech support hadn't heard of anything like this. Because it's almost two years old, he transferred me to LG's tech support, who basically said find a local repair shop, or they could RMA it for an unknown cost.I'm pretty sure the phone is bricked at this point, which is frustrating, because it was running stock android - completely unmodified. I think I might have rooted it once, months ago, but I can't imagine that that would have caused this issue. I had even received and installed Marshmallow OTA, and it was running perfectly.
Anyway, some program I might be able to use on the PC to regain access to my device.
Literally the only information I can provide about the phone at this point in time is as follows: Product_Name - hammerhead Variant - hammerhead D820(H) 32GB HW Version - rev_11 Bootloader Version - HHZ12k Baseband Version - H8974A-18.104.22.168.27 Carrier Info - None Serial Number - 047.... Signing - Production Sercure Boot - Enabled Lock State - Unlocked
I was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not: Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there.