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?
Related
Hi all,
I'm running OOS 4.5.15, unlocked bootloader, still encrypted, xdvs23's TWRP 3.1.1 (build 62 - so quite old) with the latest Magisk. I'm finally ready to upgrade to Oreo and having read some of the threads / guides etc. I think I'm happy to do a full-wipe to upgrade to Oreo and I'm considering going to LineageOS rather than the stock OOS.
As I'm on an old TWRP build that won't work with Oreo, and won't allow me to restore backups I think I need to upgrade to twrp-noapp-3.2.1-0-20180309-codeworkx-cheeseburger.img which will allow me to make a full backup that I could restore later. Once I've got this backup, and a TitaniumBackup I can copy everything off my /sdcard drive to my PC.
I need to lock the bootloader (which will wipe the entire phone) and I can then allow the stock OOS 4.5.15 to upgrade to the latest build of Oreo (5.0.4). I can then unlock the bootloader, re-flash codeworkx TWRP and generally follow the instructions at https://forum.xda-developers.com/oneplus-5/development/rom-lineageos-15-1-oreo-oneplus-5-t3727228 also installing the latest version of Magisk and then restore from TitaniumBackup the apps I actually still want.
Questions:
1) Can my initial twrp backup happen whilst I still have a lock screen pattern / finger print or does this cause issues if I choose to restore later?
2) I see that there are some ~60MB firmware files from https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/firmware/ (e.g. firmware_OP5_O2_Open_8_oneplus5.zip) do I need to do anything with these if I'm having OOS upgrade to the latest 5.0.4 (That is Oreo 8.0 but LineageOS is 8.1)? I've not seen any real info on the different firmwares (rather than the OOS changelog).
3) If I want to restore the initial TWRP backup of OOS4.5.15, could I do this after installing LineageOS or is there something else that needs to be done first (as I can't just install Oreo without re-locking the bootloader etc).
4) Is my upgrade process correct, or have I missed something?
Many thanks!
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.
So I'm running the 03/25/2019 Lineage OS microG build for my OP5, it is Android Pie and I have the latest codeworkxx TWRP 03/11/2019 and PIE firmware.
When flashing the rom (clean install) I decided to go unencrypted this time so I used the following force encryption disable zip found bellow after I clean flashed/installed the rom...
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
...followed by flashing magisk right after. Everything worked, LOS PIE is installed and unencrypted/rooted perfectly.
Problem I am having is that now when I try and install the weekly builds through the Android OS updater, it does it's thing, reboots to recovery, installs the update, magisks then re-installs through the survival addon.d script but then the phone just gets stuck into a bootloop. While reading the install messages in TWRP it does mention that magisk is removing dm-verity for what it's worth.
Does this have something to do with magisk or the LOS ROM having an "encrypted kernel" by default and how I am installing an encrypted kernel/update over an unencrypted phone? Or is this some issue with magisk?
Does this mean if I want to flash weekly updates while keeping unencrypted status I will have to dirty flash them by downloading the zip, manually placing it in my storage, booting to recovery, flashing, then flashing the encryption disable zip again and finally Magisk instead of of just pressing a button in the Android OS updater?
Luckily I restored successfully from a backup but I'm wondering is I screwed myself over here setting up my rom without encryption. Never had this issue updating with the weekly builds when my phone was encrypted.
What do you guys think?
Alright well I managed to update my ROM without bootlooping, just like I thought instead of being able to use the built in OS update manager that does everything for you I have to manually download/transfer file to my phone, flash rom update, flash force encryption disable zip and then magisk again.
While this is an alright workaround for now, is there anyway to regain the stock updating functionality built into the rom while remaining unencrypted and having it NOT bootloop my phone each time? What if I want to use addonSU instead of Magisk, I don't think the disable encryption zip works unless you flash Magisk right after unless I have to update the rom, flash the disable zip, flash magisk, remove magisk and then use addonSU.
G935FD
So I’m getting this in my Samsung S7 edge exynos with latest stock rom 8.0
¤Magisk 18.1 and magisk manager 7.1.1¤
Format /data,
restore stock boot.img to install magisk zip
install remove encryption,
install Magisk 18.1,
Reboot system.
After reboot to twrp, /data is again encrypted.
(But the data remains unencrypted when rooted with SuperSu)
☆Please tell me how do I keep my data in twrp unencrypted while keeping magisk installed☆
《Any help is greatly appreciated》
You can flash the modded twrp with encryption support so you don't need to remove encryption of your device.
the latest one I'm using is the one on my signature.
If you wan't to keep device unecryped anyways use this video for as a guide, this is the first guide I used before using xda forums: https://www.youtube.com/watch?v=JwLja68KmKM
Hi, I'm on LineageOS 14.1 Optimized by JDCTeam.
However I'm not able to install the latest Magisk.
Is it just not possible anymore because you need fastboot to install a patched boot.img?
I tried flashing through the regular way as a .zip file (just renaming the magisk apk into .zip) in TWRP 3.2.x.x. Also tried flashing the patched boot.img file from the rom through TWRP.
But whenever I flash it and reboot, everything force closes.
Any help on that?
Latest TWRP, latest LineageOS version (18.1), latest Magisk here. I have no issues with flashing Magisk in TWRP. In fact, I have lately had to dirty flash LineageOS then Magisk in TWRP, as a standard update in LineageOS via its updater causes a bootloop.
Fortunately this isn't my main device so....
In your case, I would update to the latest LineageOS as the version you have is really old. Updating may help.
Strephon Alkhalikoi said:
Latest TWRP, latest LineageOS version (18.1), latest Magisk here. I have no issues with flashing Magisk in TWRP. In fact, I have lately had to dirty flash LineageOS then Magisk in TWRP, as a standard update in LineageOS via its updater causes a bootloop.
Fortunately this isn't my main device so....
In your case, I would update to the latest LineageOS as the version you have is really old. Updating may help.
Click to expand...
Click to collapse
Thanks for the reply, but I want to stay on Android 7 Nougat, so maybe it's in fact not possible anymore. But maybe somebody else has an idea.
crysen said:
Thanks for the reply, but I want to stay on Android 7 Nougat, so maybe it's in fact not possible anymore. But maybe somebody else has an idea.
Click to expand...
Click to collapse
Check my S4 Unified Collection & Guides. You will find everything you need.