I recently upgraded my HTC M8 for an M9, I installed all stock updates bringing it to Android 7.0, flashed TWRP to recovery, encrypted the device and installed Magisk.
My device was encrypted (Asked for password at power on, TWRP requested a password to mount the partition) and had been rebooted a few times, every time asking for the decryption password, until Magisk updated about 10 days ago. I only noticed it a few days later, on a reboot that it didn't ask for a password. I did a full power off just to make sure there was no caching going on and again it no longer asked for the password. Going into TWRP I confirmed that the device is no longer encrypted and can be mounted and read without a decryption password.
Despite the phone now being decrypted, Android still believes it is and the encryption check box is ticked and greyed out (Because you can't turn it off when it's on....well usually anyhow).
Why did it decrypt with Magisk's update? How can I enable encryption again?
It's probably still encrypted, just that the password has been reset. There was a few reports like this when v16.0 dropped, no idea why.
Try reapplying the password at boot in Android security settings.
Didgeridoohan said:
It's probably still encrypted, just that the password has been reset. There was a few reports like this when v16.0 dropped, no idea why.
Try reapplying the password at boot in Android security settings.
Click to expand...
Click to collapse
Yeah that was it. I'm assuming it still was 'encrypted' because it didn't go through the hour long process encrypting the device, but it's kind of pointless having encryption that still gives you access to the contents of the device without any kind of security verification :laugh:
It was still prompting for a PIN as a screen lock (So I didn't think of resetting the PIN), but having an unlocked bootloader means it's trivial to bypass a screen lock for data access.
Anyhow, I set the PIN again and it prompted for enhanced security, I selected that and it's back to asking for a PIN to access the data so that's good
Thanks for your help!
Related
Few month ago found out there was a stock option for encrypting the data. After the process everything worked great. However, I decided to try out a different rom and rebooted to the phone into recovery mode. Come to find out it's also locked out by the encryption. First reaction was awesome, android got this on a lock down on all sides. Here comes the bad news. My normal encryption password does not work with the recovery encryption password. It keeps telling me I got the wrong password. It's seems I can't make any changes anymore.
I was wondering, what do you do in this case? I can use the phone as is for now but what if I want to update or sell my phone, what do I do? I can't even full wipe the phone for fresh new rom.
So I am a developer, making a lockscreen app. Part of the app allows it to set a system lock for double protection. Upon doing this, it set PIN needed for phone to start up. The pin I had set wouldn't work so I entered it in too many times and it wiped my device. The weird thing is, the default password "0" worked in TWRP but NOT to boot Android. Now, after it wiped my device, it boots up to the Android screen, and tells me to enter my PIN again.. It still doesn't work, but tells me in -1 attempts my device will be wiped. How can I just get this all to go away and start again? I have root and TWRP installed. Is there anything I can do?
I can't even boot into Android because it asks for the PIN, even though it already wiped it. I can't use my phone at all.
Flash factory images?
Sent from my Nexus 6 using Tapatalk
Will this mess up TWRP?
DRatJr said:
Will this mess up TWRP?
Click to expand...
Click to collapse
does it matter? it takes 10-15 seconds to flash twrp, or reflash. but anyways i have a feeling that itll ask again, i hope not.
Yea. I would fastboot erase and reflash everything. If bootloader is locked you are hosed.
DRatJr said:
So I am a developer, making a lockscreen app. Part of the app allows it to set a system lock for double protection. Upon doing this, it set PIN needed for phone to start up. The pin I had set wouldn't work so I entered it in too many times and it wiped my device. The weird thing is, the default password "0" worked in TWRP but NOT to boot Android. Now, after it wiped my device, it boots up to the Android screen, and tells me to enter my PIN again.. It still doesn't work, but tells me in -1 attempts my device will be wiped. How can I just get this all to go away and start again? I have root and TWRP installed. Is there anything I can do?
I can't even boot into Android because it asks for the PIN, even though it already wiped it. I can't use my phone at all.
Click to expand...
Click to collapse
Contact the previous owner for his unlocking gesture or code/pin and Gmail account, then factory reset and login with his account and when done delete this accoubt in /settings/accounts/. Then data factory reset again and it should be fixed imo. Or send your phone to the prev. owner so he can do it himself. Look here too http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504.
I've had this phone since it came out haha. I haven't stolen it or anything. The problem came because I was solely testing on Samsung devices. Here, I set a backup PASSWORD in case you couldn't unlock your phone. My app was a device admin so it had the ability to set phone lock and lock the phone. What happened was when I tested it on my Nexus, between making the password and setting the password there is the option of "require at boot", which mysteriously, my app automatically selected. Now the issue comes in when I rebooted my phone and Google did NOT let me put a PASSWORD it, but required a PIN. This was an impossible scenario because the android lock screen was set with a PASSWORD, not a PIN.
The even weirder thing was that my app automatically sets the backup android pin to "0" if no backup password is set. When I tried 0 at boot it wouldn't work. BUT when I tried it in TWRP 0 was the only thing that decrypted the phone. I am still not sure why this whole thing happened (Google not letting me put a PASSWORD instead of a PIN if the device is encrypted. My app automatically selecting require PIN at boot, and the backup "0" working in TWRP when it wouldn't work to boot Android).
So @gee2012 I know it may seem like another thread where someone stole a Nexus and wanted to break in to use it. But I assure you I am the only one to ever own this phone. This was just a weird scenario that hopefully won't happen again.
But for the sake of the question:
Flashing factory images worked! Thanks @HolyAngel
DRatJr said:
I've had this phone since it came out haha. I haven't stolen it or anything. The problem came because I was solely testing on Samsung devices. Here, I set a backup PASSWORD in case you couldn't unlock your phone. My app was a device admin so it had the ability to set phone lock and lock the phone. What happened was when I tested it on my Nexus, between making the password and setting the password there is the option of "require at boot", which mysteriously, my app automatically selected. Now the issue comes in when I rebooted my phone and Google did NOT let me put a PASSWORD it, but required a PIN. This was an impossible scenario because the android lock screen was set with a PASSWORD, not a PIN.
The even weirder thing was that my app automatically sets the backup android pin to "0" if no backup password is set. When I tried 0 at boot it wouldn't work. BUT when I tried it in TWRP 0 was the only thing that decrypted the phone. I am still not sure why this whole thing happened (Google not letting me put a PASSWORD instead of a PIN if the device is encrypted. My app automatically selecting require PIN at boot, and the backup "0" working in TWRP when it wouldn't work to boot Android).
So @gee2012 I know it may seem like another thread where someone stole a Nexus and wanted to break in to use it. But I assure you I am the only one to ever own this phone. This was just a weird scenario that hopefully won't happen again.
But for the sake of the question:
Flashing factory images worked! Thanks @HolyAngel
Click to expand...
Click to collapse
Who talked about stolen devices mate, I surely didn`t! I thought that you bought a used Nexus 6 mate, and the previous owner didn`t delete his account :silly:
gee2012 said:
Who talked about stolen devices mate, I surely didn`t! I thought that you bought a used Nexus 6 mate, and the previous owner didn`t delete his account :silly:
Click to expand...
Click to collapse
Oh sorry :/ haha. Wasn't sure if it seemed that way. But nah this has been my baby since unboxing lol
I can no longer seem to be able to install custom roms,ive tried the resurrection remix rom and the cm13 rom but both are asking for a password after it installs and reboot(like when you encrypt the phone) so i cant access anything and my google password does nothing nor have i set another password
All i can do is the three finger recovery and reflash a full stock rom which does work.
I have checked the OEM unlock in developer options as well and full wiped before installing roms.
There shouldnt be any anti theft on the phone because afaik i have disabled all the anti theft options so there should be no reason why it asks for a password.
Does anyone have any idea why this is happening?
Does anyone know if doing a full factory reset through twrp instead of through the phone could be the reason why?
Good to see someone else is also having this ****ing stupid problem. I've been struggling with a way to fix this as well. I'm on the EVA-109 with a single SIM and its been giving me this problem no matter what I do. I read through one of posts on the CM 13 thread which stated you need to use Surdu's tweaked TWRP in order to not have the password booting problem. It'd be nice to get an official response from Surdu on this as he hasn't mentioned the need to use his version of TWRP.
Although, despite trying this I'm still having the password problem at boot but it might be worth a try if you do it. I'll pass you the link - Do let me know how it goes, though I wouldn't place all my faith in this. https://forum.xda-developers.com/p9/development/twrp-t3493979
Dear All,
I have a friend with Huawei P9 Plus with this Firmware VIE-L29C636B103, i don't know what is in his mind on that time but unfortunately after restarting the phone he forgot his PIN to unlocked the phone and the fingerprint was not working. As far as i know, the only solution is by Factory Reset the phone, but he did not want to loose his data. Is there any way to solve this problem?
Thank You
mardiatmo said:
Dear All,
I have a friend with Huawei P9 Plus with this Firmware VIE-L29C636B103, i don't know what is in his mind on that time but unfortunately after restarting the phone he forgot his PIN to unlocked the phone and the fingerprint was not working. As far as i know, the only solution is by Factory Reset the phone, but he did not want to loose his data. Is there any way to solve this problem?
Thank You
Click to expand...
Click to collapse
has his phone root and is there a custom recovery?
Fed2x said:
has his phone root and is there a custom recovery?
Click to expand...
Click to collapse
No still original without custom recovery. Can i use TWRP to backup first the data ?
The problem is that you not unlock and then root yet. You basically can't use TWRP. If unlock bootloader, the phone will be immediately wipe data.
mardiatmo said:
No still original without custom recovery. Can i use TWRP to backup first the data ?
Click to expand...
Click to collapse
mardiatmo said:
No still original without custom recovery. Can i use TWRP to backup first the data ?
Click to expand...
Click to collapse
He or you could've used it to delete ". key" -files through adb. But that is only useful to have access to the data. You can't set new fingerprints or delete any of them because he must know his forgotten password for it. So it would only be a temporary solution.
Unlocking the bootloader never erased my data. It couldn't cause of some failure appeared at let's say 30%. But I'm not certain that the failure appears also on his phone. Which leads to my suggested solution:
He should try to remember the password and include any typos(yes, typos. My pin was 85320 but it also happened that i typed two times the false pin. The outcome was 85350. Huawei's layout was kinda bull**** and vulnerable for that type of failures. At least to me.) As I know it must be a PIN, not a password. If that fails get rid of the data and make a factory reset.
Thank you all,
Today i connect the P9 Plus Phone USB to HiSuite in Windows 10, i just leave this around 5 minutes and suddenly it connected to HiSuite automatically. Now i'm still backing up the data pictures, etc. Still wondering why in windows 10 it can connected automatically than in windows 7 After backup finished i'm gonna factory reset the phone.
My mistake on comments on unlocking bootloader will erase date since I mixed up the process. Now I remembered that after unlock, if you proceed further to root the phone, the phone will have to erase the data immediately. No option for you to choose not to erase data during rooting process if not mistaken. That's why I dare not to root again the phone.
Fed2x said:
He or you could've used it to delete ". key" -files through adb. But that is only useful to have access to the data. You can't set new fingerprints or delete any of them because he must know his forgotten password for it. So it would only be a temporary solution.
Unlocking the bootloader never erased my data. It couldn't cause of some failure appeared at let's say 30%. But I'm not certain that the failure appears also on his phone. Which leads to my suggested solution:
He should try to remember the password and include any typos(yes, typos. My pin was 85320 but it also happened that i typed two times the false pin. The outcome was 85350. Huawei's layout was kinda bull**** and vulnerable for that type of failures. At least to me.) As I know it must be a PIN, not a password. If that fails get rid of the data and make a factory reset.
Click to expand...
Click to collapse
How to use adb ???
Hello all,
I'm in a bit of a predicament. I have an old OnePlus 3t that I have not used for years. The device contains extremely important business information that I need to recover. However, I cannot for the life of my remember my lock screen pattern to boot the device. I tried to remember the password and have now triggered the messaging of "This device will be wiped after 8 more tries."
I haven't updated the phone in years, so it would be on an old version of Android. Is there any toolset that could remove this lockscreen and allow the device to boot?
async-mesh said:
Hello all,
I'm in a bit of a predicament. I have an old OnePlus 3t that I have not used for years. The device contains extremely important business information that I need to recover. However, I cannot for the life of my remember my lock screen pattern to boot the device. I tried to remember the password and have now triggered the messaging of "This device will be wiped after 8 more tries."
I haven't updated the phone in years, so it would be on an old version of Android. Is there any toolset that could remove this lockscreen and allow the device to boot?
Click to expand...
Click to collapse
If you:
1. Have unlocked the bootloader, AND
2. Do NOT have an on-boot password set (a lock screen password is ok)
then it is possible to remove the lock screen password.
So, do you meet this requirement? If you do, then do you have TWRP installed?
Screenshot showing on-boot password request:
Sent from my OnePlus3T using XDA Labs
BillGoss said:
If you:
1. Have unlocked the bootloader, AND
2. Do NOT have an on-boot password set (a lock screen password is ok)
then it is possible to remove the lock screen password.
So, do you meet this requirement? If you do, then do you have TWRP installed?
Screenshot showing on-boot password request:
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I thought my bootloader was unlocked, but I cannot completely remember. When I boot the phone with volume down and power, I see a OnePlus branded screen that is also asking me to swipe the password pattern. I assume this means the bootloader is not unlocked, right? If I try to enter the password on this screen, will it use up the twies that trigger the wiping of my phone?
async-mesh said:
I thought my bootloader was unlocked, but I cannot completely remember. When I boot the phone with volume down and power, I see a OnePlus branded screen that is also asking me to swipe the password pattern. I assume this means the bootloader is not unlocked, right? If I try to enter the password on this screen, will it use up the twies that trigger the wiping of my phone?
Click to expand...
Click to collapse
Power+Vol down takes you to recovery. The fact that it's asking you for a password tells you that the phone is encrypted and has an on-boot password.
So, unfortunately you're not going to be able to recover the data on your phone.
Sent from my OnePlus3T using XDA Labs
async-mesh said:
I thought my bootloader was unlocked, but I cannot completely remember.
Click to expand...
Click to collapse
If your bootloader is unlocked, you will always see the unlocked bootloader warning screen when you power on or reboot (before it goes to any other screens.
If you do not see that bootloader unlocked warning screen, the bootloader is locked.
redpoint73 said:
If your bootloader is unlocked, you will always see the unlocked bootloader warning screen when you power on or reboot (before it goes to any other screens.
If you do not see that bootloader unlocked warning screen, the bootloader is locked.
Click to expand...
Click to collapse
It is definitely locked then..
Is there any known exploit that might be available for the device? It is older and has not been updated in years... Even if there were a way to keep trying patterns without triggering the device wipe, that would be hugely beneficial.
async-mesh said:
It is definitely locked then..
Is there any known exploit that might be available for the device? It is older and has not been updated in years...
Click to expand...
Click to collapse
The security features and encryption are very secure. You won't be able to exploit these, to extract your data. They do this on purpose, otherwise it would defeat the whole purpose of data security in the first place.
If the data was important to you; you should have been backing it up. Many easy and free options available to back up your data. I'm always surprised how many folks don't take advantage of any of those backup options. Then they come scrambling over to xda once a disaster has struck, asking for ways to retrieve their data. By that time, it's too late. Don't wait until after the car has crashed, to put your seatbelt on!
If your device is rooted and had twrp, I got a file to flash and it cleans the pattern or password, it safe my life, many times. So let me know. To upload the file.