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.
Hi guys
I really need some assistance, just because I received a notification for update my honor 8 L09 from B389 to B394.
I'm not sure because the device has the bootloader unlocked and it is rooted now, so i'm really afraid to mess it up!
Should i do the update?
Thanks for the help in advance.
Crake said:
Hi guys
I really need some assistance, just because I received a notification for update my honor 8 L09 from B389 to B394.
I'm not sure because the device has the bootloader unlocked and it is rooted now, so i'm really afraid to mess it up!
Should i do the update?
Thanks for the help in advance.
Click to expand...
Click to collapse
Well I'll tell you how I updated my Honor 8 L09 from B389 to B394 and you decide if you wish to proceed. What you get with update is probably new security patch (you are currently on May I assume? And get updated to August 5th) and some minor changes.
So I updated same way as I did the update before (B381 to B389). I was rooted and bootloader unlocked same way as you currently are now, stock EMUI. First what you must do is a full TWRP backup because there is a high chance your bootloader will relock and you will have to restore data partition on your updated device, or at least that's how I had to do it.
To update you need to extract stock recovery.img from B389 and flash it via fastboot. After that you download full update image via
Settings > Update Device and confirm that you want to update. After that device will reboot and you'll be booted to recovery where update will take place. Once that finishes your device should reboot and if you encounter the same scenario as I did you will find yourself with fully locked bootloader. You won't encounter the "Your device is unlocked and bla bla black screen", you will go straight to the system and your device will be unrooted.
What I did after that is go to the fastboot to confirm that my bootloader is locked and indeed it was. I was unable to flash my TWRP recovery again. So my only solution to rooting and having TWRP again was to unlock the bootloader once again. You know the drill for that... Enter "fastboot oem unlock xxxxxxxx" and confirm the dialog. Get full factory reset, and reenter the fastboot to finally reflash TWRP. So assuming that you made the backup now all that has to be done is restore only DATA partition. And not to forget flash latest SuperSU zip. Of course I recommend you wiping dalvik cache or not restoring the data partition at all and starting from the beginning on your new system just so you have a clean start and no unexpected bugs even if I have none personally.
That's it. Some people reported different scenarios while doing this update. This is only how it went for me and your situation might be different so ALWAYS do backups.
NatusVincere said:
Well I'll tell you how I updated my Honor 8 L09 from B389 to B394 and you decide if you wish to proceed. What you get with update is probably new security patch (you are currently on May I assume? And get updated to August 5th) and some minor changes.
So I updated same way as I did the update before (B381 to B389). I was rooted and bootloader unlocked same way as you currently are now, stock EMUI. First what you must do is a full TWRP backup because there is a high chance your bootloader will relock and you will have to restore data partition on your updated device, or at least that's how I had to do it.
To update you need to extract stock recovery.img from B389 and flash it via fastboot. After that you download full update image via
Settings > Update Device and confirm that you want to update. After that device will reboot and you'll be booted to recovery where update will take place. Once that finishes your device should reboot and if you encounter the same scenario as I did you will find yourself with fully locked bootloader. You won't encounter the "Your device is unlocked and bla bla black screen", you will go straight to the system and your device will be unrooted.
What I did after that is go to the fastboot to confirm that my bootloader is locked and indeed it was. I was unable to flash my TWRP recovery again. So my only solution to rooting and having TWRP again was to unlock the bootloader once again. You know the drill for that... Enter "fastboot oem unlock xxxxxxxx" and confirm the dialog. Get full factory reset, and reenter the fastboot to finally reflash TWRP. So assuming that you made the backup now all that has to be done is restore only DATA partition. And not to forget flash latest SuperSU zip. Of course I recommend you wiping dalvik cache or not restoring the data partition at all and starting from the beginning on your new system just so you have a clean start and no unexpected bugs even if I have none personally.
That's it. Some people reported different scenarios while doing this update. This is only how it went for me and your situation might be different so ALWAYS do backups.
Click to expand...
Click to collapse
First of all thanks very much.
I'm really confident that is too much work for so few improvements.
I guess i will wait for Oreo update and the corresponding Emui version, and at that time i will get my hands busy!
I updated from B392SP02 super-easily via ota without losing root or my bootloader0unlock but beforehand I flashed the modified recovery that doesn't verify update files. (available in one of the threads here) Give that a try.
So I did a stupid move by flashing a lower-version (OOS 9.0.3) over the latest version in hopes it would downgrade.
Of course, this failed, and now I'm always bootlooping to my recovery (TWRP), but it never asks for an encryption password anymore (meaning I can't access my files).
Would flashing the latest version of OOS fix this issue? And if so, how am I supposed to flash it?
alrightthen said:
So I did a stupid move by flashing a lower-version (OOS 9.0.3) over the latest version in hopes it would downgrade.
Of course, this failed, and now I'm always bootlooping to my recovery (TWRP), but it never asks for an encryption password anymore (meaning I can't access my files).
Would flashing the latest version of OOS fix this issue? And if so, how am I supposed to flash it?
Click to expand...
Click to collapse
Use the unbrick tool in the guide section.
alrightthen said:
So I did a stupid move by flashing a lower-version (OOS 9.0.3) over the latest version in hopes it would downgrade.
Of course, this failed, and now I'm always bootlooping to my recovery (TWRP), but it never asks for an encryption password anymore (meaning I can't access my files).
Would flashing the latest version of OOS fix this issue? And if so, how am I supposed to flash it?
Click to expand...
Click to collapse
You have 2 choices. First to fix this now and stay on this version, in twrp, just format data and phone will boot. Second, you could just flash the latest version in fastboot mode to save your data. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 here is link to the fastboot rom thread.