I've tired most of the top ROMs for the past 2+ years and haven't had any success getting encryption to work on anything past Android Nougat. Either boot decryption will work and TWRP fails to decrypt or vice versa or neither will be able to decrypt.
For a while (using LineageOS) you could flash Nougat, encrypt the device, then wipe AppData + System (keeping the encryption), and flash the Oreo ROM and it would work. Although I haven't had luck with that anymore.
What's causing this issue with N5 and successful encryption? Is TWRP fundamentally outdated or flawed? Is there something wrong with N5 hardware that prevents it from working with newer Android versions? And is there a successful way to get encryption working?
NOTE: I have done the Nexus5 system repartition , this was occurring before I performed that, and I've tried with both stock TWRP and partition TWRP to no success.
Everything is pretty simple. TWRP for hammerhead should be updated to support new encryption introduced since Oreo. Many other devices have updated device tree to support new encryption...
Related
I have installed the CyanogenMod 12 nightlys on my OnePlus using TWRP.
After setting my phone up how I wanted it, I encrypted my phone, not thinking it would cause any issues.
I now want to update to the latest nightly but TWRP will not install anything as it cannot mount any of the volumes.
I assume this is because I encrypted it.
There doesn't seem to be a way to decrypt my phone and there's no way to get to anything in TWRP.
So far I've tried reflashing my bootloader but still can't mount the volumes I need to wipe to reinstall the ROM.
How do I wipe them with the volume being encrypted? Where do I go from here? Thanks in advance!
TWRP / Lollipop encryption bug
See Bug #333 on TWRP's github.com site
Hello everyone,
I think I have a big issue on my hands. My OnePlus One has always been encrypted. When I upgraded to lollipop for Cyanogenmod, I had to wipe my device because the encryption from lollipop was different than kitkat. That seemed to go well and lollipop is working fantastically. I encrypted my device again after installing lollipop. Now, when I try to flash a zip with TWRP, it says my password is incorrect and I can't mount the system. I am able to decrypt my device when booting into Android, so I know my password is correct, but TWRP doesn't think it is. When I upgraded and encrypted my device, I was using TWRP version 2.8.0.1. I have since upgraded to the latest version 2.8.5.1 successfully with no change in behavior. What can I do to get TWRP working again? It is pretty much useless when I can't mount the system and install anything.
Please let me know if this thread belongs elsewhere.
Thanks,
Chris
abel408 said:
Hello everyone,
I think I have a big issue on my hands. My OnePlus One has always been encrypted. When I upgraded to lollipop for Cyanogenmod, I had to wipe my device because the encryption from lollipop was different than kitkat. That seemed to go well and lollipop is working fantastically. I encrypted my device again after installing lollipop. Now, when I try to flash a zip with TWRP, it says my password is incorrect and I can't mount the system. I am able to decrypt my device when booting into Android, so I know my password is correct, but TWRP doesn't think it is. When I upgraded and encrypted my device, I was using TWRP version 2.8.0.1. I have since upgraded to the latest version 2.8.5.1 successfully with no change in behavior. What can I do to get TWRP working again? It is pretty much useless when I can't mount the system and install anything.
Click to expand...
Click to collapse
Have you tried flashing back to 2.8.0.1 to see if it still works?
Newer versions of TWRP have encryption problems.
meekrawb said:
Have you tried flashing back to 2.8.0.1 to see if it still works?
Newer versions of TWRP have encryption problems.
Click to expand...
Click to collapse
I just tried 2.8.0.1 with no success. This appears to be a known issue (issue 333 on the TWRP GitHub repo), and people are suggesting to just upgrade nightly versions without backing up first. :S
Hello everybody, I hope to find help here.
My phone is the HTC One A9, Europe Version ("hiaeuhl"). Recovery is TWRP 3.0.2-0.
The background story is that I already managed to install Cyanogenmod after downgrading the original ROM to Version 1.10 and unlocked the bootloader with the HTC Unlock tool. I also managed to decrypt the device.
I'd like to update my system regularly, but unfortunately the last running version is the cm-13.0-20160904-NIGHTLY-hiaeuhl.zip from September 4th.
If I try to install the latest versions of Cyanogenmod (for example from September 9th) I always get the error
hiae.veryfy.trustzone() failed to read current TZ version: -2
Updater process ended with ERROR 7
I already tried to remove the lines that check this in the file updater_script inside the ROM's zip, then I could install the update, but afterwards I was stuck in a boot loop.
The error has nothing to do with the encryption, it apears with and without device encryption, and it has nothing to do which system (original or custom) is installed before flashing. It is also indifferent if I try the update via the system's update function or directly in TWRP. It's the fact that the Cyanogenmod version from September 4th is the last working for me. I definetly chose the right one for hiaeuhl, but it seems the developers have added a feature that makey my device incompatible to this ROM.
If there is anything I can do to update my system again, please let me know.
Have the same issue.
We need to update it, but I don't know how
jira.cyanogenmod.org/browse/NIGHTLIES-3351
Here is how I could solve the issue:
- flashing the latest stock firmware (and let it possibly completely update)
- install TWRP via fastboot
- from TWRP a factory reset
- install new version of the Cyanogenmod from TWRP
It worked for me, now I can use my beloved custom Rom
The Same Problem
I have exactly the same Problem, last working CM-Update was the 3rd September
Did you try my solution? With the older CM Rom versions for the HTC A9 you had to downgrade the stock rom, otherwise the CM wouldn't have started after the installation. Now it seems that the stock rom has to be the latest one (for me the 1.56) that you are able to flash the latest CM versions.
I do not have the latest stock Rom, my os is 1.27.161.6, seems actually cm needs 1.57, i am unlocked and s-off
You should probably find the right version for your phone here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
You should take the one with the right cid for your phone (which you can find with "fastboot getvar all" in the fastboot mode)
Thanks, i will try it and report
The last build i found for my version is 1.27. this is what i have
Hmmm... then I guess you have to wait until the new version appears in the forum. Seems that you have a device with vodafone branding. Since you already set S-off you also have the possibility to change your cid to one of the existing newer firmwares.
Is there a solution without going back to stock?
I'm not an expert, but I don't think so. It seems that the version number of the stock rom is stored somewhere even after changing the system to Cyanogenmod, and this version has to be the latest one. So unfortunately, as far as I know, you'll have to do the flashing procedure again...
thanks Silberhase, now i am on CM 13 again. Thats what i did: wrote Supdercid, searched a ruu-version for my build, found a 1.56.401.70 version, flashed this, then flashed twrp 3.0.2.0 again, factory reset - without factory reset i was not able to install cm, format data, recovery, latest cm update, flash gapps, restore my other data with titanium, done....
I'm glad to hear it worked for you!
Yes, but next Problem or better i actually do not know what problems will raise. After updating today successfully to last cm build phone is encrypted... TWRP requires password for decryption. Problem all over forums. Today i habe no fun to Format data again and restore all.
That's also what I experienced. Other users reported that the current TWRP version 3.0.2.0 can't handle the encryption of the HTC One A9. And every update will encrypt the device again. As a workaround you can do this:
- copy the downloaded update from /sdcard/cmupdater to the external memory card
- boot to the recovery (when asked for password push the cancel button) and install both the update and the gapps again (without wiping anything) from the memory card.
Its a pity, all worked perfectly. Installed last cm.. Which encrypted phone. Restored my backup. All Working. Updated apps, want backup again.... .... Error opening /system/addon.d (not a directory)..error in generating tarlist......Create tarfork()
Process Ended with error 255
I'm trying to help as much as I can even though I have no experience with all this. I never did a backup
Maybe you find the answer here:
http://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462
Maybe it helps to mount "system" in TWRP and then delete /system/addon.d. But it seems that this step has to be repeated before every backup.
Any news to this theme? Is Twrp able to handle A9 again in new Version?
The recent version 3.0.2.0 of TWRP is available for the A9 but can't handle it's encryption. It works anyway if you are willing to use some workarounds.
Hey guys,
has anyone succeeded in upgrading their OPO from nougat to oreo with activated encryption? So far I have tried different roms, but none of them get along with the encryption. Even when I encrypted in the custom rom after a clean flash, they didn't work.
I have tested OmniRom, DU, CandyRom and CarbonRom until now.
Unfortunately, there are no hints in the corresponding threads as to whether the encryption works. I would be happy to receive further information. Thank you!
I tried these last two weeks. In all cases I formatted data first and encrypted after flashing.
Carbon ROM works for me without bugs. It's my daily driver. One downside is battery usage.
AOSP Oreo for OnePlus One worked as well, but with bug 'camera force closing'.
[Android 8.1.0r20][OMS] TugaPower™ 12.0 worked as well but I had Bluetooth issues (wrong Mac address). Not related to encryption I guess.
What was your issue with CarbonRoM?
Good luck.
Peter.Zwegat said:
Hey guys,
has anyone succeeded in upgrading their OPO from nougat to oreo with activated encryption? So far I have tried different roms, but none of them get along with the encryption.
Even when I encrypted in the custom rom after a clean flash, they didn't work.
Click to expand...
Click to collapse
The bold part DOES work, upgrading with activated encryption is not a good way to do it. I.e. first you format data in TWRP and then clean flash.
---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------
hartlijn said:
I tried these last two weeks. In all cases I formatted data first and encrypted after flashing.
[Android 8.1.0r20][OMS] TugaPower™ 12.0 worked as well but I had Bluetooth issues (wrong Mac address). Not related to encryption I guess.
Click to expand...
Click to collapse
I use Tugapower O13 now. However please reveal the mystery Which bloody version of TWRP actually supports Oreo encryption? I have tried three recent versions including the latest official and they all cannot decrypt /data in recovery.
PS. Also what is the best firmware for oreo roms, which one you personally use for carbon rom for instance?
hartlijn said:
I tried these last two weeks. In all cases I formatted data first and encrypted after flashing.
Carbon ROM works for me without bugs. It's my daily driver. One downside is battery usage.
AOSP Oreo for OnePlus One worked as well, but with bug 'camera force closing'.
[Android 8.1.0r20][OMS] TugaPower™ 12.0 worked as well but I had Bluetooth issues (wrong Mac address). Not related to encryption I guess.
What was your issue with CarbonRoM?
Good luck.
Click to expand...
Click to collapse
Good to know because of TugaPower and CarbonROM. With the latter I had a bootloop after a few days without my influence, so I finally switched back to LineageOS 14.1. And AFWall+ didn't work.
1plus said:
The bold part DOES work, upgrading with activated encryption is not a good way to do it. I.e. first you format data in TWRP and then clean flash.
---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------
I use Tugapower O13 now. However please reveal the mystery Which bloody version of TWRP actually supports Oreo encryption? I have tried three recent versions including the latest official and they all cannot decrypt /data in recovery.
PS. Also what is the best firmware for oreo roms, which one you personally use for carbon rom for instance?
Click to expand...
Click to collapse
Why not upgrade from Nougat to Oreo with encryption enabled? Theoretically that should work...
I don't want to use TugaPower because I'm still looking for a custom rom with Slim recents.
1plus said:
...
I use Tugapower O13 now. However please reveal the mystery Which bloody version of TWRP actually supports Oreo encryption? I have tried three recent versions including the latest official and they all cannot decrypt /data in recovery.
PS. Also what is the best firmware for oreo roms, which one you personally use for carbon rom for instance?
Click to expand...
Click to collapse
TWRP does not support decryption. So I always backup and format data
Firmware I flashed before flashing BaconRom is for the baseband 4.0.1.c7.0011.
Peter.Zwegat said:
Why not upgrade from Nougat to Oreo with encryption enabled? Theoretically that should work...
I don't want to use TugaPower because I'm still looking for a custom rom with Slim recents.
Click to expand...
Click to collapse
No, precisely in theory that WONT work. Problem is that sometimes the encryption is changed in the AOSP source itself, so any downstream roms have the same problem.
Daniel (Tugapower builder) in another thread confirmed that no twrp currently works with oreo encryption on oneplus1 after february security patch in AOSP.
I guess our only change is to beg unofficial TWRP builders to patch twrp and build it for oneplus.
Yep, TWRP can't decrypt storage on Oreo. So you can encrypt in Oreo, it works fine, but you can't then access storage in recovery. I find this to my cost in AOSOext, had the camera problem, thought flashing an update might fix it, and found I could not.
So if you need encryption, forget Oreo for now.
While waiting for working TWRP, I've been sideloading rom updates. Thus far this has worked on encrypted Tuga Oreo.
The "famous" february patch is for File Based Encryption that is not supported on Oneplus One (due to missing encryption in ext4 kernel driver).
Oneplus One only encrypt the full data partition (Full Disk Encryption). So in my opinion a rebuild of twrp is needed but also with some other fixs.
Someone has some logs!?!
Thanks
Michele
Can we expect an update for TWRP in near future? That seems to be the biggest problem
BUMP - anyone working on TWRP for Oreo encryption? Without it I can't upgrade from Nougat.
Upgraded to Oreo with working encryption
I had upgraded from lineage 14.1 (encryption enabled) to ASOP Oreo (21/12/2017 (Beta 4) Encryption Enabled) and upgraded to further versions and currently using Resurrection Remix 6.0 (encryption enabled) using TWRP, wiped my system and data partition during each flash, while the internal storage remains untouched.
pp_1 said:
I had upgraded from lineage 14.1 (encryption enabled) to ASOP Oreo (21/12/2017 (Beta 4) Encryption Enabled) and upgraded to further versions and currently using Resurrection Remix 6.0 (encryption enabled) using TWRP, wiped my system and data partition during each flash, while the internal storage remains untouched.
Click to expand...
Click to collapse
You mean you are now using RR6.0 with encryption turn on and the encryption too works in TWRP? As of now I saw "practically all" Oreo rom and all versions or TWRP with encryption turned on will have problem to access data partition within TWRP. Or long question short, you can decrypt data partition in TWRP?
xange said:
You mean you are now using RR6.0 with encryption turn on and the encryption too works in TWRP? As of now I saw "practically all" Oreo rom and all versions or TWRP with encryption turned on will have problem to access data partition within TWRP. Or long question short, you can decrypt data partition in TWRP?
Click to expand...
Click to collapse
Yes using RR6.0 with encryption enabled and can decrypt the data partition in TWRP.
noticed we've had some A12 roms for a little while now and for some reason now instead of flashing them, all of them seem to be sideloaded and using that roms custom recovery to sideload it instead of using something like twrp and normally flashing it. any reason this is the case with A12 roms? and is it possible to downgrade from an A12 rom back to OOS 11/10?
The reason for the sideloading is that there's no working version of TWRP for A12 that can decrypt the data partition, hence lineage created a custom recovery and I believe everyone else has copied it. As for the downgrading, you may be able to sideload a stock file, but I'd use the MSM tool to get back to OOS, although you should keep in mind you will need to unlock the bootloader once again.