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 hope that you will help me.
My phone is running Android 6.0 marshmallow I think some of you will wonder why I'm in marshmallow before my phone is running android nougat rooted running on TWRP latest ver. and Magisk 14.0 but it happens that my phone experience a soft brick 2 days ago because I update my magisk 15.0 in magisk manager.
Warning: Don't upgrade your magisk to 15.0
I decided to stick with this ROM because I cannot see any instruction to revert back nougat via OTA.
I want to install TWRP but no luck at all
I try to install the oldest version of TWRP on my m8 which is 3.0.0.2 but once I boot up to recovery TWRP is asking for a password.
I think it is encrypted but I don't even put password or FPS.
Note: I use the TWRP recovery of SRK.
then I try the official TWRP came from twrp.me which is the official repo of TWRP
I use the same version which 3.0.0.2
But again it failed the device did not boot up instead it hang up my phone.
I would like to seek your help regarding on my problem.
what will be the right Version for my M8 running on M8 EMUI 4.0.2 & build number B196
also if you know any Instruction how to update my Android MM to Android really appreciate your help
Cheer!
I've installed a deodexed rom with Magisk but now I can't update past 15.x version of Magisk.
I tried to do it in the Magisk app, and trough TWRP both to version 16.0 and to version beta 16.1, but it always just hangs in the part "Flashing new boot image".
I've waited several hours in that part, but nothing.
I've also tried it with and without TWRP installed.
I think I'm missing some step here.
I always uninstall Magisk via TWRP and the latest official uninstaller prior to flashing an upgraded version. A bit cumbersome to once again configure all the settings in the modules, but it works for me.
Hello
Strange think for me, maybe not for you
I switch from carbon 8 and came back to lineage 16.
I'm not able to achieved installation with latest lineage 16, lineage microG or lineage17. Flashing the new rom works well, but after lineage home screen, the phone reboot to recovery.
With an lineage16 old version from 03/2019,install is ok and phone boot well.
I've suspected an old twrp version, but I'm on 3.3.1.0.
Any idea ?
thank you
it's the same with an old twrp version 3.2.
Ok, solved. You shouldn't install twrp as an app before rebooting to new os version.
I just rooted my samsung s10 G973F / DS via Magisk (not without some bootloop issue and a couple of times I had to flash the stock firmware and then the patched one).
I would try to include havoc custom rom which has great reviews for wanting twrp first.
So that the March 2021 update for Android 11 support is out, but I need a guide, in fact I wonder if I flash the twrp 3.5.2. from odin, do i need to reinstall magisk from recovery twrp or is my root safe?
Thanks to who will answer me!
Giulia
Have the exact same question in mind. Hopefully someone will respond soon