Related
Recovery: ClockworkMod 5.5.0.2
ROM: MCR Ir4
So, I've had my GN for about 5 days now, and wanted to experiment with the device encryption option. So, I followed the steps, and let the phone do it's thing, and an hour later it was encrypted. Now when the phone boots, it shows the boot animation, then prompts for the passcode, then remounts the unencrypted partitions as expected.
So, I starting having a look at how this impacts the usability, and now I have a bit of a problem. Firstly, as (at least) the whole /data partition is encrypted, it's not possible to access the 'sd card' from recovery, meaning that it's not possible to either create a backup or restore from one (as CWM can't mount the sdcard to do so). On realising this, I decided that I was done experimenting, and wanted to go back to the unencrypted state. How? Well, I can't.
If you go back to the security menu, the area that was used to start encryption is grayed out...it seems to have been a one-way process. At the time it mentionted that the only way to access the device if the encrytion passcode was lost would be to do a Factory Reset, so, this was what I tried next. The device restarted, showed the android with his front open and the cog on display for a few seconds, then restarted again, but took me back to where I was before - the wipe had not occurred.
Next, I tried to do a wipe from CWM - here I at least got a bit more feedback as to what was going on. It seems CWM needs to mount a given partition before it can wipe it, and as it can't do that, it couldn't wipe anything, so that didn't achieve anything either.
So, I'm now in a position where I have an encrypted device that I can't wipe, either through the normal factory reset in the Android UI, or via CWM recovery. I know that the collective smarts of this forum is a power to be reconed with, and as I've now reached the limits of my knowledge of working with this kind of thing, I'm hoping someone will be able to help me out.
My thinking so far: As the suggested method of recovering from an encrypted state is to do a factory reset, it would suggest that there is either
a) a bug in ICS that isn't handling the wipe of an encrypted device correctly
b) an incompatibility with CWM that is conflicting with the OS' ability to execute the wipe (as CWM can't interact with the encrypted partitions)
c) a bug in Paul's MCR ROM (much less likely IMO)
I hope that all makes sense, and that someone has some thoughts on where to go from here - thanks!
Flash stock images through fast boot?
Sent from my Galaxy Nexus using xda premium
I've just been reading up on fastboot since posting (I think I've only ever used it via other people's scripts before), and assuming that it can overcome the problem, I was thinking that maybe it would be able to do the wipe (though obviously I don't want to end up with a £500 paperweight...)
If I were to flash a stock image, how would I go about that? (It's been a long time since I've loaded a rom not via a recovery)
EDIT: Going to try a manual nandroid restore (from a backup made just before encrypting) as described here - http://wiki.cyanogenmod.com/wiki/Fastboot
Ok, flashed a stock image and back to factory state again so now all working (phew) - thankful I was doing this on a Nexus device where fastboot was easily available.
While this has solved the problem, it didn't really identify the cause - I'd be curious to hear of others' experiences with using the encryption in 3.0+.
Please keep questions out of the development section. Thank you
Sent from the MIUI powered 3d
jayharper08 said:
Please keep questions out of the development section. Thank you
Sent from the MIUI powered 3d
Click to expand...
Click to collapse
Apologies - posted here as thought it could have been development related (Possible CWM/MCR bug).
Don Vincenzo said:
Apologies - posted here as thought it could have been development related (Possible CWM/MCR bug).
Click to expand...
Click to collapse
No worries. Dev section is just for strictly developed roms and kernels and such. No biggie
Wish I could help you with the answer though :/
Sent from the MIUI powered 3d
Don Vincenzo said:
Recovery: ClockworkMod 5.5.0.2
ROM: MCR Ir4
So, I've had my GN for about 5 days now, and wanted to experiment with the device encryption option. So, I followed the steps, and let the phone do it's thing, and an hour later it was encrypted. Now when the phone boots, it shows the boot animation, then prompts for the passcode, then remounts the unencrypted partitions as expected.
So, I starting having a look at how this impacts the usability, and now I have a bit of a problem. Firstly, as (at least) the whole /data partition is encrypted, it's not possible to access the 'sd card' from recovery, meaning that it's not possible to either create a backup or restore from one (as CWM can't mount the sdcard to do so). On realising this, I decided that I was done experimenting, and wanted to go back to the unencrypted state. How? Well, I can't.
If you go back to the security menu, the area that was used to start encryption is grayed out...it seems to have been a one-way process. At the time it mentionted that the only way to access the device if the encrytion passcode was lost would be to do a Factory Reset, so, this was what I tried next. The device restarted, showed the android with his front open and the cog on display for a few seconds, then restarted again, but took me back to where I was before - the wipe had not occurred.
Next, I tried to do a wipe from CWM - here I at least got a bit more feedback as to what was going on. It seems CWM needs to mount a given partition before it can wipe it, and as it can't do that, it couldn't wipe anything, so that didn't achieve anything either.
So, I'm now in a position where I have an encrypted device that I can't wipe, either through the normal factory reset in the Android UI, or via CWM recovery. I know that the collective smarts of this forum is a power to be reconed with, and as I've now reached the limits of my knowledge of working with this kind of thing, I'm hoping someone will be able to help me out.
My thinking so far: As the suggested method of recovering from an encrypted state is to do a factory reset, it would suggest that there is either
a) a bug in ICS that isn't handling the wipe of an encrypted device correctly
b) an incompatibility with CWM that is conflicting with the OS' ability to execute the wipe (as CWM can't interact with the encrypted partitions)
c) a bug in Paul's MCR ROM (much less likely IMO)
I hope that all makes sense, and that someone has some thoughts on where to go from here - thanks!
Click to expand...
Click to collapse
just connect via adb in recovery and format it via mkfs.ext4...
and... then what? Once the partition is formatted - it seems it would need to be populated? Or does some subsequent restoration - once the /data partition is accessible - will re-create any files / folder structure in this filesystem?
Hello,
I hope someone will be able to help with this, although it is very much a case of user error! I upgraded my G3 to Marshmallow using the steps detailed here:
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
It all worked perfectly until I decided to encrypt the handset. The encryption process worked as expected, but as I always did on previous Android versions, I used the CryptFS Password app to change the encryption password. The app advised that it was unable to change the password and that I should run the command via shell, which I did and it seemed to work. The problem is, I changed it to an alphanumeric password and my lock screen is just a numeric PIN, so upon reboot it prompts me to enter the password to decrypt but only allows me to enter numbers.
So, I kicked myself for not changing the lockscreen from PIN to password before rebooting, but figured I could just wipe/reflash and start again. However, when I reflash, I still get prompted for the encryption password at boot. So I figured I'd just enter the password wrong 30 times and factory reset the device that way, except that doesn't work either. It says it's going to reset, reboots to recovery (TWRP 2.8.7.0) and says it has reset, but then boots back to the encryption screen again (which now advises that I am -5 of 30 attempts!!).
Flashing CM13 or 12 works fine. I have settled on CM12 at the moment because it seems to be a bit more stable, but I'd ideally like to get back to stock Marshmallow. Is this possible?
I have tried wiping all partitions and data from within TWRP, and formatting partitions, all to no avail.
Is there any way I can reinstall stock Marshmallow?
Trying flashing marshmellow KDZ and it should reset everything
Let me know how things go
TTib said:
Hello,
I hope someone will be able to help with this, although it is very much a case of user error! I upgraded my G3 to Marshmallow using the steps detailed here:
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
It all worked perfectly until I decided to encrypt the handset. The encryption process worked as expected, but as I always did on previous Android versions, I used the CryptFS Password app to change the encryption password. The app advised that it was unable to change the password and that I should run the command via shell, which I did and it seemed to work. The problem is, I changed it to an alphanumeric password and my lock screen is just a numeric PIN, so upon reboot it prompts me to enter the password to decrypt but only allows me to enter numbers.
So, I kicked myself for not changing the lockscreen from PIN to password before rebooting, but figured I could just wipe/reflash and start again. However, when I reflash, I still get prompted for the encryption password at boot. So I figured I'd just enter the password wrong 30 times and factory reset the device that way, except that doesn't work either. It says it's going to reset, reboots to recovery (TWRP 2.8.7.0) and says it has reset, but then boots back to the encryption screen again (which now advises that I am -5 of 30 attempts!!).
Flashing CM13 or 12 works fine. I have settled on CM12 at the moment because it seems to be a bit more stable, but I'd ideally like to get back to stock Marshmallow. Is this possible?
I have tried wiping all partitions and data from within TWRP, and formatting partitions, all to no avail.
Is there any way I can reinstall stock Marshmallow?
Click to expand...
Click to collapse
try booting into twrp, go into command terminal, manually format data partition using command line, then reflash cm12 and wipe cache and dalvik (you may not need to reflash it but why not if you are going back to mm)
if your partitions are the same as mine this is the command you want to run.
mke2fs -T ext4 /dev/block/mmcblk0p44
make sure you don't format the wrong partition check that your variant has the same partition (grab an app called diskinfo and click on data partition then alter the last parameter to w/e ur data partition is)
mmcblk0p44 is the paramater you want to change if yours isn't identical. this should reset encryption as data is the partition that gets encrypted.
after all of this use a guide to install marshmallow (kdz or something)
(when i encrypted my data partition twrp could no longer mount the partition to format it, but if you use command land format it formats the partition without mounting it.)
i'm assuming this is your issue as well.
KronicSkillz said:
try booting into twrp, go into command terminal, manually format data partition using command line, then reflash cm12 and wipe cache and dalvik (you may not need to reflash it but why not if you are going back to mm)
if your partitions are the same as mine this is the command you want to run.
mke2fs -T ext4 /dev/block/mmcblk0p44
make sure you don't format the wrong partition check that your variant has the same partition (grab an app called diskinfo and click on data partition then alter the last parameter to w/e ur data partition is)
mmcblk0p44 is the paramater you want to change if yours isn't identical. this should reset encryption as data is the partition that gets encrypted.
after all of this use a guide to install marshmallow (kdz or something)
(when i encrypted my data partition twrp could no longer mount the partition to format it, but if you use command land format it formats the partition without mounting it.)
i'm assuming this is your issue as well.
Click to expand...
Click to collapse
Hi, thanks for the advice, I gave it a try last night. My /data partition was named /dev/block/mmcblk0p43 according to DiskInfo, so I made sure the partition was unmounted in TWRP and formatted it via the terminal following your instructions and then reflashed the MM zip from the original link and... still encrypted.
I haven't tried flashing the kdz yet, as I use Linux and I don't believe there is a way to flash kdz files using *nix. I'll have to wait until the weekend and I'll try and do it via a VM.
I don't understand how this encrypted partition is still even there. I have CM12 installed and working, it's showing the full amount of disk space available, I've done multiple wipes, formats and resets, yet the minute I put MM on it, the phone thinks it's encrypted again.
I do actually know the encryption key, is there any way I can unlock the phone via ADB or something similar?
Not sure if it's relevant, but my phone model is D855. I don't think I mentioned that before.
Thanks for the help, I really appreciate it!
TTib said:
Hi, thanks for the advice, I gave it a try last night. My /data partition was named /dev/block/mmcblk0p43 according to DiskInfo, so I made sure the partition was unmounted in TWRP and formatted it via the terminal following your instructions and then reflashed the MM zip from the original link and... still encrypted.
I haven't tried flashing the kdz yet, as I use Linux and I don't believe there is a way to flash kdz files using *nix. I'll have to wait until the weekend and I'll try and do it via a VM.
I don't understand how this encrypted partition is still even there. I have CM12 installed and working, it's showing the full amount of disk space available, I've done multiple wipes, formats and resets, yet the minute I put MM on it, the phone thinks it's encrypted again.
I do actually know the encryption key, is there any way I can unlock the phone via ADB or something similar?
Not sure if it's relevant, but my phone model is D855. I don't think I mentioned that before.
Thanks for the help, I really appreciate it!
Click to expand...
Click to collapse
very strange when i did that it got rid of my encrypted partition... i'm not sure what else to say except maybe see if someone will lend you a windows pc to do kdz flash.
KronicSkillz said:
very strange when i did that it got rid of my encrypted partition... i'm not sure what else to say except maybe see if someone will lend you a windows pc to do kdz flash.
Click to expand...
Click to collapse
I flashed the kdz via LGUP and... now the phone won't boot to anything except TWRP. Have tried restoring two previous nandroid backups, installing CM12 and MM, all install without reporting errors. LGUP detects it as an unknown device, so can't flash kdz again. Might have bricked this one. :crying:
Phew. Okay, solved! I followed the following guide to flash an old version of the stock firmware: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html.
Then, I upgraded, rooted, flash TWRP and finally installed MM again and it seems to be back to normal ("Android is starting" screen as we speak. Fingers crossed!). Thanks to everyone who helped me out with this one!
Hello,
I am a happy owner of OnePlus 3 and at the beginning when I got this Smartphone and run it, I had to set-up a Pin which was also used for Encryption,
due to the decision that I wanted to change it, I have tried numerous things to do this, either via System -> Security, System -> Lock Screen or TWRP Recovery.
Then I have stumbled upon a wiping feature in TWRP. (TWRP Menu -> Wipe) where there was a couple of options like Advanced Wipe, Format Data and Swipe to Factory Reset. So I have
decided to see what Format Data does which showed me the following statement before I continued with it "Format Data will wipe all of your apps, backups, pictures, videos, media and
removes encryption on internal storage". Well when it said it removes the encryption I have proceeded because at this point where all of the methods failed I wanted to remove and
re-encrypt my OnePlus 3 again in order to change my encrypting pin. Ok, cool this worked perfectly except that now I can't restore my original rom or encrypt my OnePlus 3 again ....
Then I have flashed CyanogenMod 13 Nightly from August (The latest one on the CyanogenMod website) and when I went into System -> Security there was Encrypt button instead of saying
Encrypted at the top of the menu then I have played around with setting up a new Pin/Password and when I went throug all the process at the end the following happens within a few
seconds: a green dissasembled android shows then screen turns black and returns to lock screen. I checked if OnePlus 3 is encrypted and is not. This is not the normal as usually
encrypting takes some time.
Also, I have tried to restore my original rom which came with my smartphone and was encrypted, when I restored it, OnePlus 3 stucks on the first screen showing OnePlus logo on the
middle of the screen and text "Powered by Android" on the bottom of the screen.
I presume that CyanogenMod 13 encryption is broken or that I shouldn't have format Data ?
Is there any way that I can encrypt my smartphone again ?
P.S I know that OnePlus 3 encryption is handled by Hardware.
You can try downloading the official OxygenOS ROM, flashing it and trying to encrypt again. Last I tried doing it on Sultan's CM13, it didn't work, so it might be a CM problem.
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
abhibnl said:
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
Click to expand...
Click to collapse
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
formating data with TWRP -28 will decrypt your phone, it's madethis way so it can work on beta 9 and f2fs ...
that said i had encrypted device before on CM
so if you're not using beta 9 and your data partition is not f2fs, you can have an ecrypted device, the easiest way is to sideload official rom 3.2.8 (make sure you're on stock recovery and start adb sideload from there) , after the sideload the phone will be encrypted, if you're staying at MM, fastboot TWRP .22 or 23 or just the official in case .28 decrypts the phone.
Gliop022 said:
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
Click to expand...
Click to collapse
Well man i want you be on as much safe side as possible. When you perform factory data reset on stock recovery, it will wipe and reformat your internal memory as well. TWRP only wipes data partition, and you need to format whole internal memory manually. But stock is recommended for full compatibility.
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Gliop022 said:
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Click to expand...
Click to collapse
Hello Gliop022,
Do you know if flashing OxygenOs stock from TWRP 3.1.0 encrypts the phone or do I have to be on stock recovery?
Then once the phone is encrypted, are you able to flash an OOS based ROM (e.g. FreedomOs) and keep the encryption?
Hello guys,
I just installed TWRP onto my HTC 10. I unlocked the bootloader and flashed the recovery with TWRP. I backed up the default system and then wiped the Dalvik /ART Cache, the system partition, data partion and internal storage. As I now wanted to install LineageOS my device doesn't show up in the windows explorer. I tried rebooting the phone into recovery mode but it didn't work. So basically I can't accses my phone from my pc.
Can you give me some advice?
################ SOLVED ###################
I booted into TWRP. I chose "wipe" and then selected "format data". The description of "format data" already says "will remove the encryption of your phone". So I formated my phone, insalled LineageOS and GApps and the system is running, no password needed.
################ SOLVED ###################
_JonRyan said:
Hello guys,
I just installed TWRP onto my HTC 10. I unlocked the bootloader and flashed the recovery with TWRP. I backed up the default system and then wiped the Dalvik /ART Cache, the system partition, data partion and internal storage. As I now wanted to install LineageOS my device doesn't show up in the windows explorer. I tried rebooting the phone into recovery mode but it didn't work. So basically I can't accses my phone from my pc.
Can you give me some advice?
Click to expand...
Click to collapse
So basically you wiped everything you could without knowing what you were actually wiping, and what wiping that stuff would actually do to your phone?
When you wipe the system partition you won't have an OS unless you flash a ROM directly after.
Place a ROM onto your extSD and put that into your phone. Boot to recovery and flash the ROM.
I'm aware of what a wipe does, but I wasn't prepared for this case. I flashed a couple Samsung Devices and after flashing them I still had access to the phone via my pc as long I was in recovery mode. But it seems to me, that I found the problem. The device is, as far as I know, encryped by default and a signal loss after wiping/flashing the device is common.
https://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
However, I managed to install LineageOS and GApps, and the system boots. But after the boot is completed I am facing a screen where I have to enter a password to unlock Android. And I dont know which password I have to enter.
Do you know how to continue?
Thanks for your help, I really apprechiate it.
_JonRyan said:
I'm aware of what a wipe does, but I wasn't prepared for this case. I flashed a couple Samsung Devices and after flashing them I still had access to the phone via my pc as long I was in recovery mode. But it seems to me, that I found the problem. The device is, as far as I know, encryped by default and a signal loss after wiping/flashing the device is common.
https://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
However, I managed to install LineageOS and GApps, and the system boots. But after the boot is completed I am facing a screen where I have to enter a password to unlock Android. And I dont know which password I have to enter.
Do you know how to continue?
Thanks for your help, I really apprechiate it.
Click to expand...
Click to collapse
Obviously you didn't exactly know, because if you did you would have known that wiping /system would leave you with no OS.
Not slagging you here. I did the exact same thing when I had just got my 2nd gen Nexus 7 and switched to TWRP from CWM for the first time.
For your password issue:
twrp > advanced > file manager > data > system ~ delete the locksettings.db files and reboot
Thank you for your reply!
Unfortunatley, the folder "data" doesn't contain any subfolder or file. Do you still know how to unlock my device?
################ SOLVED ###################
I booted into TWRP. I chose "wipe" and then selected "format data". The description of "format data" already says "will remove the encryption of your phone". So I formated my phone, insalled LineageOS and GApps and the system is running, no password needed.
################ SOLVED ###################
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Simone98RC said:
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Click to expand...
Click to collapse
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
nikexv2 said:
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
Click to expand...
Click to collapse
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Xceeder said:
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Click to expand...
Click to collapse
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Come on, do not vent on XDA, do not make useless quarrels ?
@nikexv2 sorry, but technically speaking, I don't know the reason of problematic encryption on custom roms.
Just enable encryption with official firmware and there's no other compatibility issue.
Encryption still remains when you full wipe device via recovery.
Have a good day.
nikexv2 said:
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Click to expand...
Click to collapse
It works like this - you ask for help and if someone gives you good advice or helps you out in any way then a quick thumbs up is appreciated , it's just courtesy but anyway I hope you get your phone sorted out ...
nikexv2 said:
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
Click to expand...
Click to collapse
Not sure what's wrong with your set up but I came from OOS OB19 to DU, wiped userdata to switch data to ext4, flashed DU + beans gapps (recommended for DU) then booted up, encrypted my phone via Settings > Security and set ask pin on booting device, same pin has worked on all ROMs, even tried some OOS based ones like Freedom OS CE, now on Omni + open gapps, I'm using blu spark latest recovery.