I have an unlocked bootloader and custom rooted rom. I was going to re-flash it since my battery life has not been great. I booted to recovery but am unable to decrypt /data with my boot up password. It does work after boot, however.
Only thing recently I did was change kernel with EX kernel manager. I am assuming this is what caused the issue. I changed back to stock kernel but still not able to decrypt.
I plan on wiping my phone and setting it up again with backups I made but would like to know how to prevent this in the future if possible.
Thanks
Just flash new recovery
#pnexusj# said:
Just flash new recovery
Click to expand...
Click to collapse
Yea, just saw that. Thanks!
Related
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Azlun said:
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
cam30era said:
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
Click to expand...
Click to collapse
" Dees_Troy to allow TWRP to decrypt the data partition involves modifying the same init binary " is NOT what I want according developer's
https://plus.google.com/+DeesTroy Pixel update 4 picture.
What I want is need the full device decryption permanently, on Anroid running time, not only on TWRP.
so, I think that is maybe more than TWRP can do, I guess a special boot.img or a kernel patch zip is need to reach what I need.
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
blueyes said:
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
Click to expand...
Click to collapse
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Mike02z said:
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Click to expand...
Click to collapse
Don't you need to format user data with fast boot to decrypt?
Sent from my Google Pixel XL using XDA Labs
hi, I unlocked and rooted my nexus with 5x stock rom 7.1.1
I try to disable the encryption of files by formatting the data partition, but if you check in the SECURITY settings, the phone is always encrypted.
What am I doing wrong? Thank you.
Decrypt Question
Are you flashing SuperSu to patch kernel to remove forced encryp or flashing a custom kernel to remove it? If not, the stock kernel will re-encrypt upon boot.
I think that is normal, mine also shows encrypted currently with a stock kernel. Only time I need to decrypt is in TWRP, and instead of a password, I'm using a pattern.
TypNguy said:
I think that is normal, mine also shows encrypted currently with a stock kernel. Only time I need to decrypt is in TWRP, and instead of a password, I'm using a pattern.
Click to expand...
Click to collapse
That's probably not the kind of decryption he was looking for.
The correct answer has been given
thanks for the answers, but I still have the same problem.
I rooted, I installed the latest TWRP recovery, as well installed nexus ...
Then I formatato the DATA partition.
Start the well nexus (latest version) and under the heading Safety, the phone is still encrypted!
The kernel of pure nexus is stock?
Someone please explain this to me. Idk if it's because I've been out of the rooted/custom rim game for so long or if I've gotten dumber in my old age. Also this is the first ohone I've ever had to even think about it with.
So I:
Boot into TWRP
wipe /data
Boot back into os
Profit?
Or boot back into TWRP
Flash dm-whatever the hell it's called
Boot into os
Profit?
Also, is any if this necessary at all just to flash a different rom? Being encrypted has no bearing on my life, so I don't care if I am or not.
EDIT: I'm currently going back thru old posts so I'll delete if I find my answer before there's a reply.
If you've installed TWRP you can just flash a custom ROM unless the ROM says something about "dm-verity required [disabled/enabled]". Disabled, means no encryption. Enabled is encrypted.
Any time you flash a different ROM you need to Factory Reset. Otherwise CustomROM 1.2 to 1.3 is usually safe to dirty flash (no data wipe).
Ok. Just making sure I wasn't screwing up by flashing like I normally would:
Wipe
Rom
Gapps
Root
Reboot
Verity if it says to in the OP of the rom thread.
How does this dm-verity business work? Whenever I try to flash a later OOS version without a "format" when it boots I always get the encryption failed message. Will flashing the dm-verity .zip fix that?
This phone is a real pain in the backside to flash with. TWRP backups usually fail, encryption issues and all that stuff. On my last phone it was flash and forget. What happened?
TangledAbstact said:
How does this dm-verity business work? Whenever I try to flash a later OOS version without a "format" when it boots I always get the encryption failed message. Will flashing the dm-verity .zip fix that?
This phone is a real pain in the backside to flash with. TWRP backups usually fail, encryption issues and all that stuff. On my last phone it was flash and forget. What happened?
Click to expand...
Click to collapse
You only need to flash no-dm-verity if you want to run an unencrypted rom. All OOS ROMs are encrypted so of course you're going to get encryption failed. Omni has encryption and so does Liquid Remix now, so you don't need the verity file at all, unless you want to stay unencrypted on a ROM that supports it. Since you have been decrypted by flashing the verity file, if you want to go back to OOS, you will now need to format data (at the bottom right in wipe menu) in TWRP after flashing OOS. This will wipe all user data. DO NOT flash no-dm-verity again! If you think this phone's complicated, don't buy an Essential or any device with A/B partitions, it's a nightmare.
Edit: Actually I'm not sure if you can run OOS unencrypted or not (never tried), but if you want to restore factory encryption an flash back to stock, you have to restore the stock recovery. This guide by The Doctor will help you: https://forum.xda-developers.com/oneplus-5t/how-to/how-to-revert-to-oos-oreo-8-1-t3730952/page4
If you just want to run a custom ROM encrypted, formatting data in TWRP should work.
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
stellarroar said:
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Click to expand...
Click to collapse
Siljorfag said:
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Click to expand...
Click to collapse
Stock image is the stock OOS rom right?
lyrebird said:
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
Click to expand...
Click to collapse
The twrp password is known only to god because I've tried every pin/password I have ever used on all roms I've tried so far but none of them work. Which is why I can't flash any rom as my storage is encrypted. Most of the times I have a pattern lock set but that can't be mapped to a password can it?
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
stellarroar said:
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
Click to expand...
Click to collapse
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
blas4me said:
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
Click to expand...
Click to collapse
Formatting everything did the trick. I thought sideloading OOS would implicitly do that but I was wrong. Thanks a lot man! Now is there any way I can keep my device unencrypted going ahead? I don't want Twrp to ask me for a password when I'm booting it.
every time i flash custom rom its just going to bootloop. i think its because of encrytion.
when i restore twrp stck backup. the touch is not working properly. it requires two touches simultanously to touch any thing.
how to disable encryption? plz help
You can disable decryption by formatting the data partition in TWRP. Of course you will delete all data in the process. And I kind of doubt that encryption is causing your problems.
Are you sure that you are flashing the right ROM for your bootloader? Which Android version did you have on your phone before, and which version are you trying to flash?
zeeshanbage said:
every time i flash custom rom its just going to bootloop. i think its because of encrytion.
when i restore twrp stck backup. the touch is not working properly. it requires two touches simultanously to touch any thing.
how to disable encryption? plz help
Click to expand...
Click to collapse
what ROM?, what procedure (RSDlite, manual, etc?)are you using to flash ROM - and what bootloaders?
i wiped everything including internal storage. flashed rom successfully. but after reboot again bootloop happen. so went into twrp then again its asking password to decrypt.
now i flashed stock firmware using adb. i wasted whole day just to get root access and still didn't got one
I just put a few guides at the top of MZP Guides etc - start there and we'll see how it goes. RSDlite-ing a phone can cure a lot of ills.