I came from MIUI 9 official. I unlocked bootloader, flashed TWRP 3.2.1 vasishath, flashed Magisk and it said: "encrypted data detected, keep forceencryp"t. Then I did full wipes, then I installed AEX rom, gapps, and my device appears as encrypted. If i boot to recovery also is encrypted and asks me toenter pin. Encrypted by default? Is this MIUI, TWRP or AEX feature?
How can I decrypt? I want to decrypt to avoid future problems with dirty flashing and some other things, In addition, encryption slows down the system theoretically.
You need to FORMAT Data (not wipe) to remove encryption, Magisk will then prevent your rom from encrypting again on boot.
If your rom has a survival script for magisk, there is no need to reflash it on updating the rom.
If it doesn't then you will need to reflash it on update to prevent your rom from encrypting it on boot.
Me too....
Related
Hey guys, I unlocked the bootloader, flashed twrp and root. Then I proceeded to do a fastboot format userdata. But after the boot the encryption was still there. Now I am running PureNexus latest build along with ElementalX kernel. I would like to remove encryption when I will be flashing another rom, How do I do that? Do I simply need to do a fastboot format userdata? Will I lose Twrp and root if I do that?
If you format user data and then boot with the stock kernel it will just re encrypt the device.
Only way to stop this to format usersata and then BEFORE booting the device flashing a kernel or custom rom with force encrypt disabled.
Keep in mind the installation instructions that come with your custom ROM or kernel though. Some require you to be on stock before flashing.
I would generally consider dirty flashing a different ROM over purenexus a bad idea, so you best revert to stock, format user data to disable encryption, do a factory reset then install the new custom rom.
You will lose everything though and have to start from scratch. You may get away with using titanium backup for backup and restoring apps if you know what you are doing.
If the ROM has a kernel with force encrypt disabled then you just flash the whole ROM through fastboot and boot it. What ROM are going to try?
Someone told me on reddit to just simply format data using twrp and that it will remove the encryption and wipe my whole internal storage. Is that correct?
I believe it does just that.
Hello all,
Seeing MHC19J being the latest update to 6.0.1, I'm tempted to flash factory images like I've done for previous monthly updates (system, vendor, cache, bootloader, radio). Giving all the discussion on MHC19J & twrp v3 related to data encryption, I just want a few clarifications before I go ahead and get myself into trouble.
Here's my current setup:
-Data/Storage Decrypted (formatted userdata using twrp v2.x after unlocking bootloader when I first got 5X)
-MMB29Q - Feb 1 2016 security patch level
-Stock Rooted with Systemless v2.67 beta
-Xposed installed
Here's clarifications I'm looking for:
- will flashing MHC19J automatically RE-encrypt data/storage?
- if so, is there any way to De-crypt it without wiping data/storage? This is important to me because I'd rather keep my phone decrypted for superior performance gains and I don't really have time to reinstall my apps and restore data via Titanium backup at the moment.
If there's no way to decrypt again without completely wiping data, I think I'd rather go with V version or stay on Feb update for now.
mickey4mice said:
Hello all,
Seeing MHC19J being the latest update to 6.0.1, I'm tempted to flash factory images like I've done for previous monthly updates (system, vendor, cache, bootloader, radio). Giving all the discussion on MHC19J & twrp v3 related to data encryption, I just want a few clarifications before I go ahead and get myself into trouble.
Here's my current setup:
-Data/Storage Decrypted (formatted userdata using twrp v2.x after unlocking bootloader when I first got 5X)
-MMB29Q - Feb 1 2016 security patch level
-Stock Rooted with Systemless v2.67 beta
-Xposed installed
Here's clarifications I'm looking for:
- will flashing MHC19J automatically RE-encrypt data/storage?
- if so, is there any way to De-crypt it without wiping data/storage? This is important to me because I'd rather keep my phone decrypted for superior performance gains and I don't really have time to reinstall my apps and restore data via Titanium backup at the moment.
If there's no way to decrypt again without completely wiping data, I think I'd rather go with V version or stay on Feb update for now.
Click to expand...
Click to collapse
Flashing any factory image will encrypt your phone as soon as you boot into the rom. Make sure that after flashing factory images, you boot straight into TWRP and flash Super. I flashed every partition as the bootloader and radio are newer. I maintained my decrypt status on TWRP 3.0 after upgrading to MHC19J. Basically, do what you have done every month to maintain decrypt status and you will be fine.
Just do not boot into your system until you have flashed SuperSU.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Flashing any factory image will encrypt your phone as soon as you boot into the rom. Make sure that after flashing factory images, you boot straight into TWRP and flash Super. I flashed every partition as the bootloader and radio are newer. I maintained my decrypt status on TWRP 3.0 after upgrading to MHC19J. Basically, do what you have done every month to maintain decrypt status and you will be fine.
Just do not boot into your system until you have flashed SuperSU.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks. Did you use officially released TWRP v3 or the test version posted today?
Did you have to flash Su from OTG or the data partition was okay?
mickey4mice said:
Thanks. Did you use officially released TWRP v3 or the test version posted today?
Did twrp(the version you used to flash J) ask for password for data/storage upon reboot from bootloader after flashing?
Click to expand...
Click to collapse
I always follow the above post without an issue. I flash the boot.ing also as supersu will patch the kernel when flashed. I used TWRP 3.0.0 and did not have a password prompt and retained unencrypted status. Biggest key is not to boot into the ROM. If you do... It's already too late. Data is encrypted at first boot
mickey4mice said:
Thanks. Did you use officially released TWRP v3 or the test version posted today?
Did you have to flash Su from OTG or the data partition was okay?
Click to expand...
Click to collapse
I used the official TWRP 3.0 from awhile ago. Being that I was decrypted already, official TWRP 3.0 has no issues finding internal storage when moving to MHC19J. No OTG necessary.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Flashing any factory image will encrypt your phone as soon as you boot into the rom. Make sure that after flashing factory images, you boot straight into TWRP and flash Super. I flashed every partition as the bootloader and radio are newer. I maintained my decrypt status on TWRP 3.0 after upgrading to MHC19J. Basically, do what you have done every month to maintain decrypt status and you will be fine.
Just do not boot into your system until you have flashed SuperSU.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks. Is it enough to just flash SuperSU before boot into rom? I read something like
> You need a custom kernel that doesn’t enforce encryption on boot up. So install custom kernel via TWRP. Erase data partition. Boot up.
> via: www<dot>reddit<dot>com/r/nexus5x/comments/3zctaw/need_help_decrypting/cylsdle
That is, do I need to flash a "custom kernel" besides that flashing SuperSU before boot into rom?
KANGOD said:
That is, do I need to flash a "custom kernel" besides that flashing SuperSU before boot into rom?
Click to expand...
Click to collapse
Nope. You can flash SuperSU 2.6x only or flash a custom kernel that has disabled "force encrypt." SuperSU also patches the stock boot.img and turns off "force encrypt." Doing either will keep you decrypted.
Sent from my Nexus 5X using Tapatalk
SuperSu 2.68
I have flashed the new 19J ROM (radio, new boot loader, system, cache & vendor partitions) I left the userdata partition as is, it was decrypted.
I have installed the latest SuperSu 2.68 Beta zip immediately through TWRP (3.0.0-1), Than I have rebooted the system.
After the first boot up, the system is ENCRYPTED! There is no option to decrypt the system in TWRP. It can see all partitions just fine.
Where did I mess it up? How can I decrypt the system without to format the data partition?
I always install monthly updates on the same way, I never had any issues..
thank you
----------------------------------
Update 1:
when I boot into Recovery and I push the "Mount" option I can see the following note
" Data successfully decrypted, new block device '/dev/block/dm-0'
Updating partition details.,..
... done
Successfully decrypted with default password"
When I reboot the system it still shows: The device is encrypted.
Something wrong with the latest SuperSu?
---------------------
Update 2:
I did the exact same thing with my wife's 5X. Her phone is still decrypted after the exact same manual installation. I'm confused. ...
I encrypted my phone under security settings menu. It finished encryption process just fine, rebooted, asked for my pattern and then just got stuck on boot animation. I let it sit on boot animation for at least 45 minutes yet no success.
Here is the TWRP recovery log. https://pastebin.com/3BLnGdVw
I noticed some I/O errors show up regarding some apps but it's hard to see why they would be causing errors.
I'm using the latest RR ROM by Eliminater with TWRP 3.1.0-x by blu_spark v26. Also OB16 rom+fw.
Cache and data partitions use F2FS, system is EXT4.
Edit: Kind of fixed it by reflashing everything and flashing SuperSU instead of Magisk that was included with RR by Eliminater. Had no luck installing Magisk in any way. Still feels like something is wrong so further testing is needed, I'll edit when I find something out.
karliyo said:
I encrypted my phone under security settings menu. It finished encryption process just fine, rebooted, asked for my pattern and then just got stuck on boot animation. I let it sit on boot animation for at least 45 minutes yet no success.
Here is the TWRP recovery log. https://pastebin.com/3BLnGdVw
I noticed some I/O errors show up regarding some apps but it's hard to see why they would be causing errors.
I'm using the latest RR ROM by Eliminater with TWRP 3.1.0-x by blu_spark v26. Also OB16 rom+fw.
Cache and data partitions use F2FS, system is EXT4.
Edit: Kind of fixed it by reflashing everything and flashing SuperSU instead of Magisk that was included with RR by Eliminater. Had no luck installing Magisk in any way. Still feels like something is wrong so further testing is needed, I'll edit when I find something out.
Click to expand...
Click to collapse
Yep dont do that stuff, done it once and my phone magically didn't boot..
karliyo said:
I encrypted my phone under security settings menu. It finished encryption process just fine, rebooted, asked for my pattern and then just got stuck on boot animation. I let it sit on boot animation for at least 45 minutes yet no success.
Here is the TWRP recovery log. https://pastebin.com/3BLnGdVw
I noticed some I/O errors show up regarding some apps but it's hard to see why they would be causing errors.
I'm using the latest RR ROM by Eliminater with TWRP 3.1.0-x by blu_spark v26. Also OB16 rom+fw.
Cache and data partitions use F2FS, system is EXT4.
Edit: Kind of fixed it by reflashing everything and flashing SuperSU instead of Magisk that was included with RR by Eliminater. Had no luck installing Magisk in any way. Still feels like something is wrong so further testing is needed, I'll edit when I find something out.
Click to expand...
Click to collapse
The real trouble is the mine: I've done encryption with a custom rom (Dirty Unicorns v11.3) and I achieved your same result: bootloop.
You've to keep OxygenOS encryption, is much simple:
1) Reflash the firmware with a factory reset without Magisk (because it prevents forced encryption);
2) After first startup, reboot in bootloader and flash again TWRP;
3) Go in TWRP for a full wipe, then flash your desider rom.
4) Et voilà, encryption still remains (because it's upper to /data, /system and /cache);
5) Now you can install Magisk, because encryption is already enabled.
I would add that 3rd-party encryption get you in troubles when you switch back to OOS (99% sure that recovery can't decrypt).
Stay with stock encryption, or remove it via fastboot format userdata.
Hi all
Before I flash a test (unencrypted) 8.1 firmware, I would like to check:
Currently I run encrypted 8.0 OOS 5.0.4 and codeworkx latest TWRP.
If I backup with TWRP (first remove security) and then factory reset (and format /data)
If I next flash decrypted ROM, can I straightforward revert back to OOS 5.0.4 with same TWRP?
Someone who did so, please raise a hand.
Thanks for letting me know.
Encryption happens on boot, so if you back up was encrypted and you don't flash no verity after restore. Then it will re- encrypt
PCWright86 said:
Encryption happens on boot, so if you back up was encrypted and you don't flash no verity after restore. Then it will re- encrypt
Click to expand...
Click to collapse
I am not sure I follow why data re- encrypt is needed upon boot for restored encrypted data.
Or do you mean decrypt and re-encrypt? I thought crypt was file based.
I was rather wondering if the restored 8.0 OOS backup has the keys and code and setup to read encrypted data files. Especially when coming from 8.1 which may have different parameters. I guess it does but wanted to know someone who had restored encrypted OOS TWRP 8.0 data after running decrypted 8.1 ROM. Have you?
But then again, I do not understand well and therefore ask.
Because: if I don't like the firmware with decrypted data, I want to revert back to original encrypted OOS including its data. Since it takes much time to get the hundreds of apps configured.
The boot image of the backup will encrypt the phone again. In short, yes you can restore and be encrypted on ,OOS again
PCWright86 said:
The boot image of the backup will encrypt the phone again. In short, yes you can restore and be encrypted on ,OOS again
Click to expand...
Click to collapse
Thanks for explaining. I feel more confident now about what to expect!
Hello,
Previously I'm on Xiaomi.eu Stable 11.0.5 based on Android 9, did backup on system and other partition except data partition.
I updated to Xiaomi.eu Stable 11.01 based on Android 10. Flashing done without problem. After first boot, PIN code I used doesn't work to unlock the phone. (yes, i forgot to disable phone lock before updating)
Then I boot to twrp, it's prompt for decryption PIN, after decryption. I try to restore system partition, but it lead to bootloop.
I boot to TWRP again, but now it doesn't prompt for decryption PIN and my data partition still encrypted.
Is there any possiblity to decrypt it on TWRP so I can backup it to OTG drive before I clean Install it?
Or there are any other method to decrypt the files cause I can still access the files as MTP devices.
Thank you very much for your help
@underd0g, try to flash the ROM, of which data you want to restore, dirty before. This may make encrypt key availiable.
rp158 said:
@underd0g, try to flash the ROM, of which data you want to restore, dirty before. This may make encrypt key availiable.
Click to expand...
Click to collapse
Do you mean that I need to reflash the ROM previously I used?
Okay let me try it. Thank you for your answer.
edit: reflashing ROM fixed the problem
I´Hello I have the same problem,
Unfortunate flashing via OTG does not solve the problem.
Also I am not able to flash a stock rom via the mi flash tool
Hello, i don´t know wy but after several formats and installations it worked and I´m running now on 20-3-19
Thanks all