So before I get into this know you need to have a custom recovery.
Hey guys, so I don't know if there is a thread about this or not but I think this might be helpful in certain occasions. So recently I found out about googles 72 hour lock down when you reset your password. Which means if you own a nexus phone and you try to flash a new rom you must sign in with your last google account. BUT they don't let you because of their 72 hour security so you have to wait 3 days to finally use your phone again unless you have a back up. So this happened to me last night, couldn't sign in with the new password, so I put my sim back in my nexus 6 and decided I could wait. I slept on it and this morning decided to figure out a way how. So it was actually an easy fix. I installed chroma rom with no gapps knowing I could get into the system, then rebooted and went back to recovery and flashed gapps recommended in the chroma thread. After I got a few force closes but nothing I couldn't tap out of and I signed into the device by going to settings-accounts. (BTW I got to settings by dropping down status bar and clicking the gear icon as the launcher was not working.) From there I went to developer mode and checked the box OEM unlocking. Went back to recovery cleaned wiped my phone and installed rom and gapps. Since I checked on the OEM unlock I didn't have to use an email to get into the phone. Now I have everything working like normal! so i hope this helps at least someone in the future! [emoji1]
Sent from my Nexus 6P using Tapatalk
Related
I have a Nexus 6P and last night I tried rooting it with Nexus Root Kit by Wugfresh.
Everything went well. I was rooted.. I installed all my back ups and what not. This morning I was gonna install the dbrand skind I received a while bad so I turned the phone off. After skin installation when I tried booting the phone, it boots to the "Encrypt/decrypt Pattern" part and the pattern input area is not there.. it is blank.. Not the whole page, just the 3x3 dots for pattern input.
I have the stock rom, latest build
help.. please.. someone
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
Just so everyone's aware, I got this boot loop too today with the following scenario:
Completely stock 6p, upto date with latest MM, never been rooted, flashed, whatever.
Signed up for beta N programme today
Immediately got the N OTA update
Installed it - it rebooted post install but back into MM not N.
Rebooted - it got stuck on the Google logo for 30 minutes
Rebooted - permanent boot loop
I can get into the recovery menu and bootloader, and have tried sideloading the latest 7 OTA but still have the bootloop. Reset/cache clearing all tried.
Annoyingly my bootloader is locked - I've never tried doing anything other than installing standard OTA updates from Google so was unaware that unlocking it might save my bacon until it was too late.
I guess it's a phone call to Google tomorrow....
Update - sideloading this installed OK but I still have the boot loop:
6.0.1 (MTC20F) Link 5a1e93e9974908a0683a4ac8a732b81023f4b01182fd3ead3f091f54300de5ce
So all is not lost. I have an unlocked bootloader, but everything else the same as you. Doesn't really matter as I'm unable to flash anything....even updated my android SDK.
Anyway, I too signed up for Android beta program this morning, and instantly got the N update. Boom bootloop. Non stop. Most I could get it was 20 minutes after a factory reset.
What has worked for me (since 12pm today) was a factory reset and upon signing in to setup. I didn't. I set it up like it was brand new and didn't take ANY restore of apps or data from Google. I added my Gmail after and it's up and running with no reboots for 8 hours now.
It really sucks. The only thing I was able to salvage were my ringtones and notification sounds. It's like starting with a brand new phone ( froyo days without titanium backup). Google has a list of all your apps in the store but reinstalling all of them and logging in is a real pia. Been at it all day. But I do have a functioning stable Android 7.
Hey guys,
So I went to do a factory reset on my phone on Saturday just gone (and several more times on the Sunday), since apps started randomly not working properly. Anyway, I figured since I'm doing a reset I might as well re-attempt installing RenICE since the last time I tried, the support for gs8+ was still very early.
So I reset the phone and go to flash TWRP (tried 3.14 and 3.2x), using Odin.
I have developer options enabled and USB debugging, but there was no OEM unlock button.
So I tried the following tricks:
- disable all auto-updates (not the one inside Google Play)
- disable automatic time set
- set time to 7 days before the current date
Apparently doing this and resetting enables OEM unlock, however the time just reset to a variance between the current date (when wifi or network was enabled) and 24 hours prior the fac reset (with sim removed and wifi turned off)
I have my gmail account put into the device. I also tried wiping the cache, which succeeded but still did not affect the current known date and no OEM unlock.
I did some digging and this can happen when the BL is already unlocked... so I put it into recovery mode and it says "OEM LOCK: 1" or something to the effect that it is still in fact locked.
I even tried re-flashing an XSA rom and that didn't change anything either.
Anyway, I've just found a potential solution to this problem and I just want to share it with the community in case anyone is facing the same problem.
It now seems very obvious, but I literally just tried it again as I was writing this post asking for help and now OEM unlock is enabled.
Solution: disable updates in Google Play Store then reset with wifi off and sim removed. (not sure about the combination here, the only thing I did different was Google Play. So it could be needing all three at once, might just be that last update setting needed switching off. Who knows, not gonna risk it again coz I want RenICE today haha)
If anyone is having this issue, or there are some hackers around with some spare time. Give it a whirl and lemme know how you go.
Some sys info:
Model: SM-G955F
Android: 8
Baseband: G955FXXU4CRI1
Kernel: 4.4.111-14315050-QB19732162
Build#: R16NW.G955FXXU4CRI1
Knox: 3.0
TIMA: 3.3.0
One question. You say turn off auto update play store then reset with wifi off and sim removed. My question is reset what? The wifi or auto update play store. A bit confused
Quick Steps to get OEM after flash a stock firmware
Nice to see your message, but I facing that trouble on the night and I notice this
Flashing stock firmware and doing the setup normally, I can't pass the 7 days going back then I do this; going to stock recovery and I do format data and cache and wiping cache, then do the setup normally and you can pass the 7 days going back to get OEM
santiago013 said:
Nice to see your message, but I facing that trouble on the night and I notice this
Flashing stock firmware and doing the setup normally, I can't pass the 7 days going back then I do this; going to stock recovery and I do format data and cache and wiping cache, then do the setup normally and you can pass the 7 days going back to get OEM
Click to expand...
Click to collapse
I also tried that and it didn't work for me... forgot to mention
Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.
kazim.asghar said:
Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.
Click to expand...
Click to collapse
Same issue with me as well. Can anyone help..
kazim.asghar said:
Hi, Today I was using my phone and in mid day I realised my phone is not accepting my pin code but finger print is working fine.
I tried many time but pin didnt work and I used my pin code unlock few hours ago. Long story short I have reset my phone from recovery and setup my phone again.
BUT when I try to put a pin lock or password or any other security, my phone gives me error that is "Screen lock was already changed. Try again with the new screen lock." Screenshot attached
Any solution to this?
My phone is G975F on Android Q beta 2 DBT (VAU).
I have done factory reset , installed new firmware but it is not working.
Click to expand...
Click to collapse
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..
mykenyc said:
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..
Click to expand...
Click to collapse
I intalled beta 2. Everything was working fine. But when I restarted my phone, it stopped accepting my 4 digit pin. Then i hard reset the phone and factory reset. But after that it not accepting any new Pin or Pattern to register.
What should I do know as there is no screen lock on my phone
mykenyc said:
Was this right after installing the beta 2? When you installed Beta 1 did you leave the system as it was or did you factory reset it? if so can you quantify how many times you unlocked your phone before went south? Was you stuck after rebooting from realizing your pin is not working? Meaning, after the issue and you restarted the phone was you able to enter your pin and proceed, then afterward it stopped?
[edit] The reason why I ask about the factory reset is in one of the other Beta threads people was having a lot of issues and after a factory reset it became near flawless. As of right now I''m monitoring my phone to see if this will happen to me, however after Beta 1 I did a factory reset, so I'm not sure it's a symptom of lingering files. I usally after applying an update to a beta ROM, I factory reset and out of all the times I did it, Android Q was the most buggy and was the only Beta i reverted, but the phone was a Pxiel..
Click to expand...
Click to collapse
I did a clean install fresh firmware for beta 1, clear cache for beta 2.
I am not sure how many unlocks but i took few days after beta 2. My phone was waorking fine in morning as I unlock my phone in car using pin. But in after noon when I used the pin it showed me wrong pin. Every thing related to security wont work. Cant register finger print or face. But if you do same in secure folder everything will work fine.
Okay if it happens to me I will try to track down how it happened.
You did something and screwed up. A lot of people are using beta 2 already and have not encountered this issue, myself in it. I have done a lot of restarts and I have changed my pin successfully.
NickosD said:
You did something and screwed up. A lot of people are using beta 2 already and have not encountered this issue, myself in it. I have done a lot of restarts and I have changed my pin successfully.
Click to expand...
Click to collapse
What about other people who are affected by it? Read comments in Android 10 beta thread on page after 135. You will find people reporting this issue.
I didnt do anything with my phone just updating with beta.
I'm another that's been affected, had to do a factory reset via bootloader.
Currently stuck on Beta 2, Smart switch won't downgrade.
No security options available and an extremely buggy phone.
A new update has been pushed out. I just received it on my phone. Will be performing a factory reset once the update is installed and will setup the phone from scratch.
ashwinrajsr said:
A new update has been pushed out. I just received it on my phone. Will be performing a factory reset once the update is installed and will setup the phone from scratch.
Click to expand...
Click to collapse
Update me if it has fixed the security issue.
i installed *emergency update* , no wipe,no reset ,things go back to normal
Everything is cool as the phone has not been blocked. Otherwise there is no way to upload the update.
I wonder why they can't release the patch to upload it via ODIN, that would solve the problem.
Wait what !?!?, the same thing happened to me
Even worse - i rolled back to P, where i was able to add a pin but it would always forget it. I ended up going to a samsung center where they changed the board (in warranty), they said my unique device key was corrupted - likely due to internal storage error
So it is a beta problem then
Please provide feedback in the samsung members app. Those that cant, send feedback in the official thread at samsung forums.
Beta 2 is Terrible, having all kinds of Problems with it. Beta 1 was Much Better. Hope another Update comes out soon or will just go back to PIE. G975U S10+
I do have the same problem on my Zenfone 6z. After I relocked my bootloader I couldn't set up a pin. Asus still haven't rolled out an update.