Unfortunately my OnePlus is no longer able to function and would like some assistance/suggestion from the community.
OnePlus has TWRP installed
- installed Paranoid Android rom = no issues
- enabled encryption
Now here is where the issue occurs.
When I start the phone I am able to see the PA bootup screen, it prompts me to enter the password. Once the password is entered "bugdroid" appears on the screen for a quick flash and then disappears. The screen continue to stay blank/black with no further progress, I have left the phone in this state for at least 20mins but it still doesn't proceed further. It should also be noted the the soft keys STAYS lit once the password has been entered for decryption.
I am still able to boot into recovery, enter my password to decrypt and use the standard TWRP functions. It should be noted that unfortunately I haven't done a backup on the phone at all {something that I totally regret right now), plus there is no rom left on the phone for me to attempt a install.
Any help is appreciated
note: the phone as able to complete its bootup process when I initially activated encryption but has failed ever since the first reboot
There are multiple threads discussing this in the very section you posted this thread in. Have a look, you'll find what you need.
Transmitted via Bacon
Related
Hi all,
I'm running CM11 on a Moto G. Due to work requirements I encrypted my phone via the security settings. It all went as expected, until I got to the screen where I have to enter my password to decrypt storage...
Once I enter the correct password, it loads a screen with an android on (I think it was similar to the one from the encryption screen) very briefly, then goes blank. I presume it turns off as it doesn't do anything else for quite a while. If I reboot and try enter an incorrect code, it prompts for the right code, so I'm definitely entering the correct pin.
My questions is - is there any way around this (without wiping the phone)? Any idea what's gone wrong?
I can still access recovery, but obviously it's rather limited as it's all encrypted. Is there any way I can connect via PC to get my files and decrypt them as I know the password?
I have Samsung Galaxy S III GT-I9300 with 4.3 stock ROM, rooted with CF-AutoRoot/SuperSU and Recovery replaced by ClockWork Recovery Mod. I used face unlock password together with unlock pattern backup. Now I wanted to encrypt my device. I go trough every step, setting password, charging battery over 80% and plugging in charger. When I finally click Encrypt device, the green Android mascot flashes for second, then screen goes black for minute or two, then phone boots up but no encryption process is performed and the phone is unencrypted.
I tried:
1. Disabling SuperSU
2. Disabling Orbot startup
3. Disabling SIM card PIN request
4. Doing encryption in both portrait and landscape mode
5. Unplugging charger right before clicking Encrypt
I have installed: Flashed Stock ROM with Odin, did a factory reset from stock Recovery, set up my phone, then rooted phone using CF-AutoRoot, Installed SA Manager 2.0, then Xposed Framework and Phone ID changer plugin, then flashed ClockWork Mod Recovery with Odin. At one point I wiped Cache partition from ClockWorkMod Recovery and when exiting choose Repair Root. Then I installed Orbot, Orweb, SecureChat and four other applications to manipulate NFC cards.
What is causing my phone to not encrypt upon reboot? I don't want to reset and reflash everything because my phone already have lot of information that I don't want to lose.
Edit: After trying various methods, I found that disabling SuperSU from paalications menu allowed me to encrypt the phone. This thread delivered http://forum.xda-developers.com/showthread.php?t=2485126&page=4 Tomorrow I will repeat the process again and will tell if Safe Mode is really required for success or only disabling SuperSU
Also the fools saying that Encryption is irreversible process are fools. They are copying each other's wrong blog posts. I clearly see a Decrypt device button and I will try to use it tomorrow!
It all comes down to this: If phone does not encrypt (reboots and then boots few minutes later, but no encryption) then do the following:
To successfully encrypt:
1. Disable SuperSU from applications menu
2. Restart phone in Safe Mode (tap Application key repeatedly while phone restarts)
3. Follow encryption procedure as normal (setting screen lock password, charger, etc.)
4. When encryption is complete, enable SuperSU in Applications menu.
To successfully decrypt:
1. Disable SuperSU
2. Reboot (Safe Mode not required)
3. Decrypt as usual
4. Enable SuperSU again afterwards
This information probably need to be included in some FAQ. This could save other people a lot of time and frustration trying to figure out what is wrong.
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.