Has anyone else had this happen to them? Phone stopped responding, so I tried to force a reboot; it wouldn't recognize my pattern anymore, so I booted into TWRP and deleted locksettings.db, whereupon system hung up on "Android is Starting". So, went back to TWRP to attempt to wipe data, and phone would not let me set up; just stayed on "Just a sec" progress bar.
I'm at the point where I'm about to install a factory image and start fresh. Ideas?
Mine told me that the pattern wasn't correct, so my first move was to boot to twrp. Since that took my pattern, I knew that it wasn't incorrect, so I just booted straight without altering anything. It ended up accepting my pattern that time. I've had it happen a few times that it didn't recognize my pattern, then after a reboot, it was fine.
lightningdude said:
Mine told me that the pattern wasn't correct, so my first move was to boot to twrp. Since that took my pattern, I knew that it wasn't incorrect, so I just booted straight without altering anything. It ended up accepting my pattern that time. I've had it happen a few times that it didn't recognize my pattern, then after a reboot, it was fine.
Click to expand...
Click to collapse
I unfortunately didn't get it that easy...had to do a factory reset.
Oddly, this happened right after I got locked out of my Facebook account...
Related
I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?
kyuuku said:
I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?
Click to expand...
Click to collapse
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.
dottat said:
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.
Click to expand...
Click to collapse
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.
kyuuku said:
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.
Click to expand...
Click to collapse
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.
dottat said:
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.
Click to expand...
Click to collapse
Ahh that's too bad. It was what I expected though.
Thank you anyway for the help!
I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
BluGuy said:
I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
Click to expand...
Click to collapse
You need to re-enable the pin from lockscreen options
Sent from my A0001 using Tapatalk
cloudx720 said:
You need to re-enable the pin from lockscreen options
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I think you misunderstood. The lockscreen still ask for a pin. When the phone has encryption turned on, when you either restart or turn the phone on you will receive a prompt on a grey screen to enter you pin. At this point Android hasn't fully booted yet. It then checks the pin and then boots Android. My phone is no longer brining me to this grey screen, it flashes grey but seems to just skip that screen. It is just fully loading android all the way.
BluGuy said:
I have had my phone encrypted for a while now. The other day I decided to install the Google Screenwise app since I take part in the panel. During the setup process it said I had to enter my pin because it "affected" encryption. Well I entered it and went about my business.
Now for the weird part. I needed to restart my phone later on and as it booted up, where it would ask me for my pin before it would boot Android, it now flashes a grey screen really fast and continues booting to the lockscreen where I can enter my pin. When I check under settings it says that my phone is still encrypted, and yet never ask me for my pin during boot up.
Anyone know what's going on here? Am I going to have to do a factory reset to get encryption working correctly again?
I am on Cyanogen OS 12.1 build YOG4PAS3JL.
Click to expand...
Click to collapse
If you set up pin code again will ask if you want pin to boot.
You have two option
One is pin to boot
Other pin after boot
I do not use screenwise for related issues
But i am familiar with encryption
Encryption will exist unless do factory reset
geowolf1000 said:
If you set up pin code again will ask if you want pin to boot.
You have two option
One is pin to boot
Other pin after boot
I do not use screenwise for related issues
But i am familiar with encryption
Encryption will exist unless do factory reset
Click to expand...
Click to collapse
I didn't even know it had the other option in it to ask for the pin during boot up. I would have thought if there was an option for that it would be in the Security menu with encryption rather than the lockscreen menu. Thanks.
Last week I encrypted my phone, and the process went as designed. I've been using it now for a week, and anytime I completely power off the phone, and want to turn on, it goes through two phases:
the first takes about 30 seconds, reaching a screen where I must enter my passcode/pin, and then secondly, the phone takes about another minute, or so, and gets to the boot screen, where I must (again) enter my pin and then I am in the system. Ok.
This afternoon, after turning off the phone completely, and later turning on the phone, it went straight to the boot/login screen. The first step is gone. I've re-checked this 3 times now, and step one no longer appears.
When I check settings/security, it shows as 'encrypted".
If I boot into recovery, and use the encryption password, it says:
failed to decrypt, password failed!
I am running Sultana's CM 13.0 from Feb.
Any thoughts are appreciated.
Yea format the data, it will wipe storage too but will let you use the phone next time.
Transmitted via BACON
JeffDC said:
Last week I encrypted my phone, and the process went as designed. I've been using it now for a week, and anytime I completely power off the phone, and want to turn on, it goes through two phases:
the first takes about 30 seconds, reaching a screen where I must enter my passcode/pin, and then secondly, the phone takes about another minute, or so, and gets to the boot screen, where I must (again) enter my pin and then I am in the system. Ok.
This afternoon, after turning off the phone completely, and later turning on the phone, it went straight to the boot/login screen. The first step is gone. I've re-checked this 3 times now, and step one no longer appears.
When I check settings/security, it shows as 'encrypted".
If I boot into recovery, and use the encryption password, it says:
failed to decrypt, password failed!
I am running Sultana's CM 13.0 from Feb.
Any thoughts are appreciated.
Click to expand...
Click to collapse
Change pin from lockscreen
And check pin to boot
Twrp does not decrypt without this choice
Your phone will have again two phases again
geowolf1000 said:
Change pin from lockscreen
And check pin to boot
Twrp does not decrypt without this choice
Your phone will have again two phases again
Click to expand...
Click to collapse
Thanks folks. I formatted data and restored before reading this. If it happens again Ill try your idea.
Ok Masters, so I am having the same issue that this guy here:
https://forum.xda-developers.com/ga...mand-error-samsung-galaxy-j7-prime-s-t3929850
I can install any rom. However, the pin to register either face or fingerprint, does not work. So I cannot even get to the fingerprint screen because it returns me to enter pin, and when I re-enter it, it says is wrong. I guess it has something to do, the fingerprint so far, had just worked on Cerberus AOSP rom, but neither on one UI nor 8.1 based roms work. on 8.1 I get setting had stopped.
So, flash stock over odin was already tried and it gets stuck there. Already flashed no verity, no luck, flashed, bbos, godness, venom, no luck.
Any other advice? Seems that somehow I messed up with the encryption and that is making not registering the pin or pattern.
I managed to pass the screen with Magisk, but as soon as system boots and I try to set fingerprint, it says settings stopped. I am really frustrated now.
Thanks,
This was already solved. If anyone is interested in getting more details he they are:
The no command was because someway somehow, the system partition was "busy " or non-writteable, at least that was the message that I was able to read. I don't know how it got to that state, but my solution was the following:
- Select system partition in twrp and tapped on repair file system. I got an error immediately that twrp could not read system block. I changed file system to ext2 and rebooted twrp.
- once again I clicked on repair file system. No errors this time. Rebooted twrp. Changed file system to ext4. Rebooted twrp. Repaired file system again and rebooted twrp once again. Downloaded an aosp 8.1 rom and setted screen lock after the set up, it worked. Then, installed apollo v1. Screen got frozen for a second when setting pin, but it let me pass to set my fingerprints.
Then I knew that it was already working. Installed a One Ui rom to try and it worked again my screen lock with finger print.
Hopefully this helps someone as I found no solution whatsoever in any part of forums or internet, this was pure trial an error over 4 days.
this morning, my gps wasn’t working and i did a reboot, since then my phone won’t start anymore. originally: bootloader unlocked, twrp installed, magisk as well.
after typing in the security pin, it was stuck. i assumed there was some problem with that, so i went into twrp and deleted those lock settings files, reboot, now i’m at "phone is starting" after each reboot now and i can access settings and basic stuff, but no home or anything, and tapping on system update tells me that the app is not responding ("settings keeps stopping"). booting into twrp asks for a pin which does NOT work anymore (neither my original one, nor 0000 or default_password).
i used magisk uninstaller (sideloaded), and reflashed what i assumed was an OTA-zip from the oneplus website, so i’ve got stock recovery installed now (bootloader still open), but otherwise not much changed - after booting i can basically only access settings (from the quick settings bar), nothing else works.
i ASSUME it has got something to do with not being able to decrypt data anymore. i also assumed i can just reflash the 2gb-zip from oneplus and that would include a fresh system/boot img and deleting those lock files from twrp would remove decryption, but i guess i was wrong.
other that formatting data now .. any recommandations/suggestions? any help would be greatly appreciated. :/
could be stock launcher is frozen or disabled?
it did this to me, even if I had another launcher.
virtyx said:
could be stock launcher is frozen or disabled?
Click to expand...
Click to collapse
thanks for your guess - but, no, not disabled, i can see it in the list of apps. the only app "disabled" was the oneplus gallery, switched that back on, no effect ..
frank93 said:
thanks for your guess - but, no, not disabled, i can see it in the list of apps. the only app "disabled" was the oneplus gallery, switched that back on, no effect ..
Click to expand...
Click to collapse
wipe cache in recovery
virtyx said:
wipe cache in recovery
Click to expand...
Click to collapse
tried that, didn’t work. and even after a "factory reset", starting from the "hello!"-page from scratch, everything stopped on the next page ("just a sec ..") - so i guess there was something seriously wrong with my data partition. not sure why though.
after formatting data (and crying during those few seconds) it "worked" again, now, and fortunately i had some kind of app backup at least, but ..
yeahwell.
frank93 said:
tried that, didn’t work. and even after a "factory reset", starting from the "hello!"-page from scratch, everything stopped on the next page ("just a sec ..") - so i guess there was something seriously wrong with my data partition. not sure why though.
after formatting data (and crying during those few seconds) it "worked" again, now, and fortunately i had some kind of app backup at least, but ..
yeahwell.
Click to expand...
Click to collapse
very strange
maybe the restricted. XML file was stuck
no point trying since you formatted
four hours later, fresh setup - it’s starting to happen again, sudden "hangs" and "phone is starting .." out of nowhere, then "system ui is not responding", force reboot, .. working right now, but there’s something really fishy and i’m starting to assume it’s a hardware thing.
I'm having the same issue after rebooting to fix gps/mobile data issues. Any other solutions?