I noticed that the current TWRP version for Pixel (sailfish) now supports data decryption in Oreo. It would be nice to not have to remember to turn off your password before using TWRP. Not to mention having to re-setup all your apps that use fingerprint security after your done with TWRP.
I imagine if it were easy, @invisiblek would have done it. But it would be sweet to have.
Here is a discussion about Pixel 2 that is probably relevant and explains why it is unlikely.
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Related
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).
Hello, despite searching i couldn't find my answer. Is TWRP able to decrypt the h870 encrypted data partition (through pin, pattern, etc..)? Very important for me & i got a good deal on it that expire soon. Hope you can tell me, thanks!
goja said:
Hello, despite searching i couldn't find my answer. Is TWRP able to decrypt the h870 encrypted data partition (through pin, pattern, etc..)? Very important for me & i got a good deal on it that expire soon. Hope you can tell me, thanks!
Click to expand...
Click to collapse
Unpredictable. I would keep data decrypted if you like to play with custom roms and TWRP. If you do stock based only (Nougat, Oreo), then encryption will work fine with Magisk rooting. To backup data using TWRP though, OFFICIAL TWRP for H870 can decrypt data fine but UNOFFICIAL TWRP won't (needed to flash newest custom roms). Some people use both TWRP versions (official one at twrp.me to backup rom, and unofficial 3.2.3 to flash latest custom roms)
I see.. And what's the lastest lineage/resurection rom that's compatible with offical twrp, how far does it goes..?
PS: "then encryption will work fine with Magisk rooting" what?! we're talking about twrp decryption, what's with magisk..?
goja said:
I see.. And what's the lastest lineage/resurection rom that's compatible with offical twrp, how far does it goes..?
PS: "then encryption will work fine with Magisk rooting" what?! we're talking about twrp decryption, what's with magisk..?
Click to expand...
Click to collapse
You're correct. Not related. Just poor choice of words.
Found a Pie GSI that seems to be working great. It can be found at https://forum.xda-developers.com/pr...9-0-0-android-p-pixel-features-kirin-t3833879
Looks like source is located here https://github.com/Huawei-Kirin-Project if someone smarter than me would like to continue the other person's work.
How I installed.
1. Started directly from OpenKirin Lineage with TWRP and Magisk patched kernel.
2. Wiped System, Data and Caches.
3. Flash the img to System Image with TWRP.
4. Flash OpenGapps Nano.
5. Flash Magisk again even though the kernel was already patched.
6. Wipe Caches and reboot to system.
You need to enable Developer Options and choose a Webview implementation. None is chosen automatically. That's why some apps would just close initially. This fixed my Gmail and Amazon app issues.
Issues:
WiFi Hotspot not working.
What I've found so far:
Magisk is working.
Amazon apps force close.
AMI Music won't install. Says it's not available on this device. Could probably restore it from a backup if Titanium worked.
I haven't looked for any solutions yet.
Sent from my BND-L34 using Tapatalk
Edit:
Titanium Backup works after flashing Magisk. I originally didn't flash it because my kernel was already patched and I didn't expect the rom to actually work. When it booted, su was working for everything but Titanium so I assumed flashing Magisk wasn't needed in my case.
AMI Music works after restoring from a backup.
Amazon Alexa and Shopping still close. Amazon Music works.
Can an admin fix my subject line please .
Sent from my BND-L34 using Tapatalk
I've been using this a DD for three days with no issues. It actually runs better than the OpenKirin Lineage build I was running. The developer was supposedly part of the OpenKirin team who quit.
Sent from my BND-L34 using Tapatalk
Hi all,
I'm jumping from LOS 14.1 to 16.1, I have the last unofficial TWRP 3.2.3 installed from the nearby thread, used to work well before encryption, now I can't decrypt the data partition, thus no backups, zip flash, OTA...
Any ideas? Thanks.
[Update]: it seems LineageOS 16 installs its own bootloader on some models that allows the encryption while being compatible with OTA. However, on Z1 it keeps TWRP and thus the incompatibility with the encryption. Any way to install with its bootloader on Z1?
I used Magisk to do an OTA update to Oxygen OS 12, but it feels like my root is gone because TWRP disappeared, the bootloader was locked after the update, and I had to unlock it. But when I do root check, it still says I'm rooted. Most of my Root access requiring apps don't work properly either like battery limiter and Adaway. But I check root status in Momo, and it says the environment is abnormal. Upon restart it doesn't pop up with TWRP as recovery; it goes to default OP recovery. Also, the warning at startup where it says the warning about the bootloader being unlocked is also gone, even after reunlocking my bootloader after the OTA update.
Also, slightly unrelated, but my fingerprint sensor has also stopped functioning completely. I couldn't use it to unlock my phone so I removed all fingerprint data and I tried adding it back and it wouldn't even detect my finger when I tried to add it back.
What is a true test to check if I need to wipe and reroot and install TWRP again?
How did TWRP just disappear?
Did I do the OTA wrong?
Why would my phone allow me to grant root access to root checker if I wasn't still rooted?
Would a simple fix be just reinstalling Magisk?
edit: So it seems that Adaway works, but battery limiter does not(I assume doing a fresh install of the APK might help). And my fingerprint sensor also does not work.
I am indeed rooted, but I am still wondering why TWRP just disappeared? And why does my fingerprint sensor not work at all?
I have the Oneplus 8 Pro American version.
Take a step back and read this.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
A12 is not in a good state anyway and most people use OOS11 or a custom rom.
IDK if battery limiter is a12 compatible but that does not matter.
You should NOT use TWRP with A12 and you should NOT do an OTA with magisk to a12.
What i would do now:
1. Read the thread i posted above carefully.
2. Backup all you data to a pc.
3. Backup persist image.
4. Use MSM Tool ro rollback to a clean state of OOS11.(https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/)
5. Flash latest A12 as local upgrade within the system updater twice (to ensure its on both slots)
6. Extract boot img with payload dumper and patch it via magisk.
7. Unlock bootloader
8. fastboot BOOT patched_boot_image.img
9. Start magisk and install
Enjoy rooted A12.
Or better simply stay on A11 its better anyway.