After installing beta 1, and factory resetting, phone hung in loop in setup. Wants me to enter my old pin code, and after i enter it, it takes me back to restoring backup screen. Anyone have any ideas?
Thanks
same problem here
Todesdoktor said:
same problem here
Click to expand...
Click to collapse
i'm find solution and it works for me so u can try to
https://www.reddit.com/r/android_beta/comments/nfsvxj
read my instruction post also undre my post u can see links for ota images for p[hone models u must download ota for your phone and then flsah by my instructions
Same issue here. Running Android 12 Beta and was fine. Then a couple weeks in the phone start crashing/rebooting on some apps. I thought I'd factory reset to clear any erroneous data and try again. Now it boots into Android setup, asks and accepts pin, but won't let me enter gmail and password. Keeps asking to restore data from old phone via cable, then back to enter pin again. Over and over. I can boot into recovery, but don't currently have a Windows machine to troubleshoot; only a macbook air and a chromebook. Haven't figured that side out yet.
I found this promising looking info. It's SUPER simple too! Unfortunately it has not worked for me yet, but I'm optimistic maybe later today I can get it going!
https://www.reddit.com/r/android_beta/comments/nrwzxm
Related
Hello, all. I've had this problem for about a year, but I just kind of put the KF away once I got it replaced instead of fixing it.
Last year, I put my KF into a softbrick, factory reset bootloop. On boot, the KF warns:
Your Kindle has detected a problem and must clear App storage. The recovery process will erase some apps and data from your device.
Click to expand...
Click to collapse
The rest is the generic factory reset info. Press power to proceed. This looks like it goes through the process, restarts, and just boots back up into this message. Thus, bootloop. I've tried looking up others with the same problem, but no one has had the same one I mention. I don't have a custom bootloader or TWRP.
As for what caused this, if i can remember correctly I was having trouble with google apps permissions and changed a folder in /system/ to something else. The fire freaked out and I rebooted it. The above has happened ever since. So the only modification is being rooted. I've tried getting access to adb, but it hasn't listed the device. Maybe I installed the drivers wrong or something, but I didn't mess with it for long because I don't like being in Windows if I can help it.
Any help would be greatly appreciated. Not in too big of a hurry, though, as I have a Nexus 7 currently. ^.^
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Thepooch said:
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Click to expand...
Click to collapse
I knew about fastboot, I should have mentioned. I just don't have the money to spend on one currently. What do you mean by attempt to race it to factory reset and reset it?
Just what I said you have just a little time to race to settings and factory reset it before it fc`s and shuts down some people manage to pull it off.
So I am having this exact problem described here:
https://www.xda-developers.com/google-factory-reset-protection-bug/
After a successful OTA update to 8.1 (Android Beta Program) I do not get the option to enter my email credentials. Lockscreen pattern only.
I tried reflashing 8.1 via fastboot and it was successful, but the problem persists.
I did not forget my screen lock pattern like the user in the article says he did. I am using the same one I have always used. Anybody have any ideas besides RMA?
Unable to flash 8.0 also. Bootloader is the wrong version TMZ11f
I got this all fixed. Posting just in case someone else runs into this.
Using the "flash-all" command, I flashed an 8.0 factory image. Upon reboot the phone said it was corrupt and would not boot past the white Google screen. So I went in and relocked the bootloader. The error message went away and I was able to boot and enter my Gmail account. I have no idea why relocking the bootloader took the corrupt device message away but it did.
Moral to the story here:. DO NOT do a factory reset, or anything else that will trigger a reset if you are using a screen lock pattern at the time on 8.1 beta.
Just to make sure, I completely disabled my lock screen and did a factory reset immediately after installing the 8.1 ota. All is well. Lesson learned.
r0adki111 said:
I have no idea why relocking the bootloader took the corrupt device message away but it did.
Click to expand...
Click to collapse
It might just be me, but I think it pertains to the bootloader being unlocked in general.
Nexus phones showed an unlocked padlock, while other OEMS (Samsung) would plaster a giant WARNING screen similar to what you guys are experiencing.
r0adki111 said:
I got this all fixed. Posting just in case someone else runs into this.
Using the "flash-all" command, I flashed an 8.0 factory image. Upon reboot the phone said it was corrupt and would not boot past the white Google screen. So I went in and relocked the bootloader. The error message went away and I was able to boot and enter my Gmail account. I have no idea why relocking the bootloader took the corrupt device message away but it did.
Moral to the story here:. DO NOT do a factory reset, or anything else that will trigger a reset if you are using a screen lock pattern at the time on 8.1 beta.
Just to make sure, I completely disabled my lock screen and did a factory reset immediately after installing the 8.1 ota. All is well. Lesson learned.
Click to expand...
Click to collapse
I went through the exact same thing. It's because I didn't have updated fastboot. And i believe you have to do a factory reset to go to the preview and back. I also found out I had to unlock critical to flash a new bootloader
Having some serious trouble. I rebooted my phone and it asked for my password once it was done as always but this time it said it was wrong. I'm certain I used the correct password but even tried my other alternatives to be sure and still a no go. This isn't the decryption option password you get when booting but my lockscreen password. I booted into recovery and it asks me for an encryption password that I never set but I know this is a common issue with twrp. Tried to go back into android but wouldn't let me because of the "wrong" password so I used the failsafe and went into recoveries file manager and deleted my lockscreen settings to remove my lockscreen passcode (tried and proven method, done it dozen times before). Got past my lockscreen this time but now it was saying starting android forever. Figured it was something with the passcode being deleted so I just decidd to factory reset from the recovery and take that loss. NOW the problem is upon booting the rom in trying to start the setup, I'm stuck on the "just a sec..." screen that comes up after you click start. What do I do from here? I cant access anything in recovery because the encryption passcode issue so I'm kind of stuck. Also I'm a work right now and we cant connect our phones (or any USB for that matter) to the computers and laptops because theyre government property and on a secured line. Any help PLEASE, Ill be home later and can try more then.
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
loeffler23 said:
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
Click to expand...
Click to collapse
Hey, I got my phone back working after that and rooted again and flashed same rom. NOW another problem, I rebooted my phone and its not accepting my PIN anymore, nor my fingerprint, and I cant reset through TWRP because of encryption. WTF is the issue, how do I fix this or do I have to flash-all again?
Hello.
I create a new post it will be better organized. Well, in the end I have a big problem with the c pixel. I wanted to flash Factory 7.1.2 ryu. I followed all the steps on the Google site. So install adb and Fastboot with their drivers. Then double click on Flash_all.bat. All went well it rebooted and I can use the tablet without any problem. The only thing I didn't do was lock the bootloader because I thought it would wait until tomorrow. So everything works fine I have test some features, then I test the restart and there is a big mistake. I see the message: bootloader is unlocked and os verification is off the device continues booting in 30 second. Then a high-pitched beep and the Google logo appears but never changes. So nothing left and blocked on this logo. And did I do something stupid, did I brick it. I'm lost ?
While trying to connect it in sector there was the animation of the four small rounds then it turns off and goes in bootloop. Is it over? ?? Or can I still fix it?
I'm going back to the message I posted earlier. Here, I undertook alone to look for my mistake to remedy it. So in the recovery I saw "enter in fastboot mode" so I pressed it and I reflashed the rom factory. then everything went well. And instead of continuing like yesterday I immediately locked the bootloader. Then I rebooted and for the moment everything is going well. The only thing I'm afraid to do is restart. But if everything goes wrong I'll just have to flash the rom factory again, I think. So here it is I solved my problem by myself
Edit: the restart works perfectly. My mistake was to restart without locking the bootloader.
Hey! Need a little help. I updated to Android 11 Beta 2. Now my phone is stuck on a boot loop. A li'l different though, phone boots up normally and stays on the lockscreen and alive. Can receive calls. But once I unlock with the pattern it shows ' Phone is starting' works for a good 2 seconds and then ends up on infinite bootloop until I Power down. How do I access my files on PC ? If I can get just few files out of it then maybe I can perform a factory reset . Please HELP!
kkrazzyyguy said:
Hey! Need a little help. I updated to Android 11 Beta 2. Now my phone is stuck on a boot loop. A li'l different though, phone boots up normally and stays on the lockscreen and alive. Can receive calls. But once I unlock with the pattern it shows ' Phone is starting' works for a good 2 seconds and then ends up on infinite bootloop until I Power down. How do I access my files on PC ? If I can get just few files out of it then maybe I can perform a factory reset . Please HELP!
Click to expand...
Click to collapse
some older app is causing the loop you mayneed to factory reset through recovery or flash factory images to ur devices ,( please backup your all data and i will advice you to remove the screen lock if possible as it may cause issues after flashing older or newer images
That's what I am asking. How do I backup?
kkrazzyyguy said:
That's what I am asking. How do I backup?
Click to expand...
Click to collapse
I use this tool in my computer to update my phone.
Make sure to follow and read the instructions.
Since you're phone is in boot loop, put your phone in into bootloader
https://flash.android.com/welcome?continue=/custom
Facing the same trouble, did it help?
Hi, I finally managed to solve this!! Was able to get the phone working with data intact.
So I got exactly the same problem yesterday and was looking around for a solution when I bumped on this thread, the solution suggested to use Android Flash Tool can work only if the bootloader is already unlocked, USB debugging is on and you edit the flash.bat file to remove -w from the command line, which would not work in my case since my bootloader is locked and unlocking through ADB would wipe all data
So the only good solution is to do an OTA UPDATE USING ADB SIDELOAD, I just downloaded the OTA file, connected the phone to computer, booted into recovery and used ADB to sideload the OTA and boom, the phone is its pristine self again, with ALL DATA intact