My x727 fails to encrypt itself. After the reboot it did not start the encryption but got stuck for several hours.
Has anyone managed to encrypt the phone? Thank you.
(On my phone, Magisk v8, TWRP, PHH's Superuser and xposed is installed.)
Now that more people have the phone and more ROM versions (including first custom ROMs) are available: has anyone managed to encrypt the phone?
(Device encryption is very important to me because my employer does not allow me to connect an unecrypted phone to the firm network. Therefore, the phone is currently almost useless to me.)
Thanks!
I suppose x727 data partition it's already factory encrypted because during unlocking tests some users said the device asks for a key.
I have now managed to encrypt the phone with the latest ROM: http://forum.xda-developers.com/le-pro3/how-to/5-9-020s-update-x720-t3506829
are you using airwatch ?
Related
After receiving my beloved 1+2, I rooted it, installed TWRP and flashed Xposed. Then I encrypted the phone. After wanting to update the rom, I realized TWRP doesn't yet support encryption. I reflashed the stock recovery, which I found here. This didn't help either, no encryption supported.
How can you safely remove the encryption? Does anyone have a functioning setup with stock recovery an encrypted device? Or is it possible to flash new firmware throught fastboot leaving it encrypted?
I made my Htc M7 useless trying to remove it's encryption, so i'm really careful one the 1+2...
Does really nobody know how to reverse this prominent feature in android???
A simple factory reset from the settings menu completely removed the encryption
Hello,
I just ordered my first OnePlus and should receive it by the end of the month. Like all my previous (and quite old) phones, I would like to root it for several reasons and I found the native encryption needs to be disabled in order to be able to root the phone. Fair enough.
Since I never had to deal with encryption on my previous phones, I was wondering if you could tell me more about the consequences:
1) once the phone is rooted, can I enable the encryption again without hassles?
2) once rooted and (hopefully) encrypted, how will I have to update my phone? Flash the full OTA everytime (no partial updates allowed on rooted phones if I understood correctly)? Can I do this without disabling/re-enabling the encryption? After the full flash, will the data & cache be wiped or will it be hassle-free?
3) I generally use Titanium Backup to backup my apps (hence the need for root access) and copy the files on a network drive. Am I correct to assume that native encryption of the OP5 will not affect this process (either during backup or when the files are copied to the network drive (encrypted)?
Thanks for your help
GeeM said:
Hello,
I just ordered my first OnePlus and should receive it by the end of the month. Like all my previous (and quite old) phones, I would like to root it for several reasons and I found the native encryption needs to be disabled in order to be able to root the phone. Fair enough.
Since I never had to deal with encryption on my previous phones, I was wondering if you could tell me more about the consequences:
1) once the phone is rooted, can I enable the encryption again without hassles?
2) once rooted and (hopefully) encrypted, how will I have to update my phone? Flash the full OTA everytime (no partial updates allowed on rooted phones if I understood correctly)? Can I do this without disabling/re-enabling the encryption? After the full flash, will the data & cache be wiped or will it be hassle-free?
3) I generally use Titanium Backup to backup my apps (hence the need for root access) and copy the files on a network drive. Am I correct to assume that native encryption of the OP5 will not affect this process (either during backup or when the files are copied to the network drive (encrypted)?
Thanks for your help
Click to expand...
Click to collapse
First of all native encryption will still work when rooted. When you root using supersu or Magisk the encryption will stay. When you get your phone you first must boot to fastboot and unlock the bootloader. Doing so will erase data so do it as soon as you get the phone. Second you will need to flash TWRP. Wipe factory settings and flash Supersu or Magisk 13.3. I prefer Magisk. Once in setup you will need to put a password and fingerprint to get the encryption started. After that your all set. To update the rom just head to downloads.oneplus.net and download the correct rom for Oneplus 5 and flash it over TWRP then flash Magisk/Supersu after. I prefer using [ROM] xXx NoLimits 2.0 [OOS][OP5] ☆ Speed/RAM optimized ☆ because it uses stock oxygen os rom with better performance and battery life. Plus extra features like debloating. But other than that you will not lose encryption when rooting. Only when you want to install custom roms for right now like (LineageOS, RR, AOSP).
Hi all,
So its been a long time since i've been in the rooting game, Last dine i did it was on my Sprint Evo 4G :x
I got ahold of a Le Pro3 LEX727. I was able to unlock the bootloader, flash TWRP (3.1.1-0), Install LineageOS 14.1 (20170707 Nightly) and SuperSU (2.82 Flashed from Zip) and everything is working. The issue is that whenever i boot into Recovery, its asking for an encryption password. This prevents me from mounting my storage (aside form a Flash drive attached via USB OTG) Making Backups,and flashing updates. Does anyone have experience with this? I've searched the forums and cant seem to find a clear answer on how to remove the encryption.
If you can boot into the system normally, then set a PIN and set it to require on boot. Then when you go into recovery that PIN should work to unencrypt. I haven't been able to remove encryption but that's how I got around it.
PurpleCowMan said:
Hi all,
So its been a long time since i've been in the rooting game, Last dine i did it was on my Sprint Evo 4G :x
I got ahold of a Le Pro3 LEX727. I was able to unlock the bootloader, flash TWRP (3.1.1-0), Install LineageOS 14.1 (20170707 Nightly) and SuperSU (2.82 Flashed from Zip) and everything is working. The issue is that whenever i boot into Recovery, its asking for an encryption password. This prevents me from mounting my storage (aside form a Flash drive attached via USB OTG) Making Backups,and flashing updates. Does anyone have experience with this? I've searched the forums and cant seem to find a clear answer on how to remove the encryption.
Click to expand...
Click to collapse
？
PurpleCowMan said:
Hi all,
So its been a long time since i've been in the rooting game, Last dine i did it was on my Sprint Evo 4G :x
I got ahold of a Le Pro3 LEX727. I was able to unlock the bootloader, flash TWRP (3.1.1-0), Install LineageOS 14.1 (20170707 Nightly) and SuperSU (2.82 Flashed from Zip) and everything is working. The issue is that whenever i boot into Recovery, its asking for an encryption password. This prevents me from mounting my storage (aside form a Flash drive attached via USB OTG) Making Backups,and flashing updates. Does anyone have experience with this? I've searched the forums and cant seem to find a clear answer on how to remove the encryption.
Click to expand...
Click to collapse
i fixed my issue by flashing this TWRP
https://drive.google.com/file/d/0B7uXK7jfW17nZGRCWmFmZU9NVWs/view
Days ago, I had the wonderful idea of installing TWRP. I didn't want to install a custom ROM, I simply wanted TWRP + the current android. However, after I installed TWRP, the Android 8.0 was wiped out. I thought I would still keep the Android 8...
I tried to install many older versions (from April, June, July, August) of the stock ROM 8.0 via Odin, but all of them failed (as far as I learned, they failed because they had an older version than the Bootloader I had installed), then I successfully installed a stock ROM build from December.
Now, my phone doesn't pass the SafetyNet Test. It fails on "CTS profile match" (I read on the internet it is due to the unlocked Bootloader).
Interesting thing is: when I browse to "Developer Options -> OEM unlock", it says "Bootloader is already unlocked", even if the option is unset.
Now I have no TWRP (and I don't want to play with it anymore) and I have no root access.
Does anyone know how to "relock" the Bootloader or do anything that will allow me to pass the SafetyNet Test?
I have some questions about device security running with an unlocked bootloader.
I am somewhat experienced and comfortable with flashing custom ROMs, mostly LineageOS,
and flashing back the original stock ROMs for Pixel and Samsung devices.
I have recently experimented with running LineageOS 20 (Android 13) on a Samsung Galaxy
Tab S5e with Magisk (and a few Magisk modules). Within several of the XDA forums, and also at
other web sites, it's recommended with custom ROMs the bootloader not be re-locked since
this can create problems.
I use my S5e for steaming videos, basic web browsing and other things. I don't do banking or
have anything I would consider a huge security risk. My intent is to understand what risks
exist with an unlocked bootloader so I can make more informed decisions what I should/should
not install.
With later versions of Android, including 13, the built in storage is encrypted by default.
If the device is powered off filesystems are at rest in an encrypted state so is it possible
for someone else to gain access to my data if they power on the device or flash
their own recovery and/or custom OS? If someone boots into recovery mode encrypted
filesystems should not be mounted and remain unavailable. I'm wanting to understand where
there are weaknesses that could be exploited to access data.
If the device is powered on and the OS has been screen unlocked the first time after boot
(so encrypted filesystems are mounted and available) is access to my data at increased risk,
assuming USB debugging is disabled?
Can apps be sideloaded in recovery mode that an attacker could use to gain access to data
in other ways even if encrypted filesystems have not been mounted.
Any other security issues to be aware of?
If risks I haven't considered are too great I can also go back to stock ROM, but would consider
ways of mitigating or reducing any risks with a custom ROM and unlocked bootloader.
Please let me know if there is a more appropriate place for this posting.
Thanks,
Rodney
Samsung encryption not supported in TWRP recovery, but I have seen Samsung device running LineageOS on AOSP encryption.
of course on unlocked bootloader attacker can enable adb, inject scripts and gain root access easy. however, still it requires lock screen credentials for decrypting, so your personal data remains secured.
for some devices it's possible to set user-settable root of trust, this would allow to compile LineageOS with avb/dm-verity and re-lock bootloader.
Thanks for the reply, would be great to figure out a way to be able to lock the bootloader with LineageOS.
I do notice the "OEM Unlocking" option does not exist in Developer Settings in LineageOS 20.
lol have fun!
How to properly ENABLE dm-verity and FEC for /system on Motorola X4 with LineageOS 17.1?