I haven't used my nexus in a couple months, turned it on today and there's a PIN lock.
I don't remember ever setting this up, I tried my usual PINs and none work.
I keep trying but I never get a forgot password log in with google option. I always get 5 wrong entries, wait 30 secs.
I'm at 35 incorrect PINs so far.
-I've also tried going to device manager but my device is always unavailable so I can't send a lock screen to it.
-I can't do a factory reset because my recovery is broken and I can't get into it to erase my data.
-I can't flash a new recovery because my computer isn't a trusted device to access it and I can't allow it because I can't log in.
I'm not sure what else to do.
I have a secondary user on it but I can't turn on the developer options for it because it's not the primary account.
Any ideas what I can do?
If you can get your driver issues figured out, so that the Fast Boot driver works, you can just reflash images from the Bootloader. You do not need to get into Recovery, or get passed the pin lock to reflash. To make it easy, you can use something like Wug's NRT and use the "Bricked Device" option to flash images from the bootloader screen.
Related
So I have a busted screen, and due to work email and such, I'd like to wipe the phone before sending it back. I have attempted to navigate the factory reset with the buttons with no success. Any suggestions? The phone is factory unlocked.
Help is much appreciated!
ReMMy1100 said:
So I have a busted screen, and due to work email and such, I'd like to wipe the phone before sending it back. I have attempted to navigate the factory reset with the buttons with no success. Any suggestions? The phone is factory unlocked.
Help is much appreciated!
Click to expand...
Click to collapse
You have a few options.
Get the screen fixed.
Buy an mhl cable and show the screen on a TV, do what you like from there.
Not 100% but try adb commands through a PC and see if there is one to wipe the phone.
Again not 100% but you could use USB OTG to communicate and type in the code within the dialer to wipe the phone.
Flash an ruu, this should nuke the devices memory AFAIK.
There are probably more ways but they're what I would try first.
Or change your password on your work email, if you use a client like good, you can remove it from the device and the password will stop people entering it anyway, not to mention that its sandboxed.
If you have a password (pattern or pin) and you're rooted then you can easily remove them from TWRP recovery by deleting one file, however would the people who get the broken phone go to those lengths?
Hope this helps.
Ok, Ill admit I didnt research things fully, and went on my merry way flashing things mercilessly in hopes to find something I really liked.
I ended up flashing a 7.0 rom and it wanted me to add a fingerprint, which meant I added a pattern. This put that damn pattern everyway, except fastboot/bootloader
I wanted to remove it, a user suggested a delete userdata and rebuild - I did that, only I deleted everything, all partitions.
Now, the code representation of my pattern doesnt work and recovery doesnt do much, doesnt mount anything.
Where, Im currently at / things Ive tried to get going again:
adb sideload: seems to work, says it serving the file, but nothing happens ( thought it was immediately supposed to start installing? ) Cant seem to find the file in sdcard or sideload. I suspect its because things are not being mounted.
fastboot works as Ive tried reinstalling TWRP in efforts to remove the damn password. That seemed to have installed, but the password persists and my old one ( the pattern above ) does not work.
Please tell me how to correct this password madness and get a working phone again.
same here +1
Ok so I flashed: cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J6-oneplus3-recovery.img from https://download.cyanogenmod.org?device=oneplus3
and did a factory reset and Im up and running again.
You can turn off PIN on boot/ boot into TWRP but it's enabled by default and it's not obvious how to do it. You have to turn off the pattern (set your security type to None), then re-enable a pattern. At that point it will ask you if you want a pattern on boot or not.
This device had a messed up screen for a few months (the fade-out/black screen issue), and I now have been able to apply a temporary fix (paper wedge behind the mobo) so I can get to the screen again. I have found that I've actually forgotten the recovery PIN and the pattern lock I setup on the device.
I know I had enabled ADB at some point previously, but at this time it does not show up when I connect it to my computer (Linux system). I need to recover the data on it, if at all possible. Can anyone offer some insight on ways to get around this?
Thanks in advance
My father in law died last weekend and we don't know the pincode of his stock Nexus 5X. We can access his Google account and we know the pincode of his sim card. I hope someone can help us out to get access to his phone. Things we've tried:
- The vingerprint reader was setup but we've tried a lot of possible pins. We've tried his vinger yesterday but because of the attempts the pin is also required now.
- With a pattern lock you'll get a possibility to unlock through the Google account password after some attempts but his phone was secured with a vingerprint and/or pincode. Only the delay between attempts get increased, currently 16 minutes between them.
- The lock option from https://www.google.com/android/devicemanager, but because there is already a pin lock it doesn't work. The pin doesn't change.
- I've tried to access the phone through ADB, booted into the recovery but "adb devices" doesn't see the phone. When I choose to "install update through adb" I see the devices with "adb devices" but I can't use "adb shell", only sideloading works.
- Installing a custom recovery could work but the bootloader is locked, when I unlock it a full wipe will be performed so we still can't access the data.
- From the Play store in the browser on my Mac I've installed the androidlost.com app on the phone, but the app needs to be opened once before it can be used.
- A rubber ducky could help us out, but I don't have one and the time between attempts get increased and increased... it would take weeks, months or years to unlock.
What other possibilities do I have?
First sorry for your lost!
Second, i don´t know for sure, but maybe get the phone to the store where you bought it and explain the situation, maybe they will give a correct advice or like you said the phone is registed in google ( device manager) maybe if you contact them they will help you with that ( the problem is they probably will take a long time to reply or don´t reply at all) or wait for a more expert user than me here in xda,
again, sorry for your lost and hope you solve this problem,
cheers
If the phone was rooted with a recovery installed, YES, you could delete the passcode files and get into it, without root/recovery, you cannot get into it without the password, that is the point of encryption and passwords and all that jazz.... Yes there is probably a way for some high level hacker to do it but good luck finding that.... If you just want to be able to USE the phone, do a factory reset from recovery....
So hello there!
I'm having the following issue and I'm kinda out of ideas.
I was running a (KingRoot) rooted fireOS 4.6.6.1 (420) if I'm not mistaken.
So this is what happened:
Phone was running just fine, but I wanted to get rid of the facebook background services which kept running without the actual app installed. Also a friend proposed to run the 'fstrim' command. So reading through xda I found an app called 3C Toolbox (http://www.3c71.com/android/?q=node/916) which seemed to be safe to use. Installed it and still didn't change a thing except for the three 'fstrim' actions to perform. After that I restarted my phone.
Powered off just fine, but at the start only the 'Amazon' logo comes up and vanishes into a black screen with the backlight still on. Even after waiting several hours nothing changes.
So what did I attempt to get it wirking again?
At first I tried to simply restart it. --> Nothing changed.
Tried to get into recovery and clean the cache. --> Nothing changed except the 'Amazon' being on for a bit longer
Get into ADB and try pull/uninstall... --> Guess due to the locked bootloader I'm not allowed to issue any command other than 'adb sideload [packagename]' for system updates. As for ADB itself I can only get it to recognize on the PC when I get into recovery and choose the 'apply update from ADB' option.
Get into fastboot according to this tutorial (https://forum.xda-developers.com/showthread.php?t=1668159) --> doesn't work.
Get into 'Safe Mode' with this tutorial (https://forum.xda-developers.com/fire-phone/help/how-to-fire-phone-to-boot-safe-mode-t2828240) --> doesn't work either.
So does anybody has another idea I could give a try or should I just abondon all my data and flash a new clean image?
Also I'm not sure if updating from ADB will erase all personal data too. Guess so, but maybe I can get a clearification in here too.