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.
Related
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
I think I've read at least 20 guides on different topics trying to get TWRP installed (2.6 is installed now), but now I want the latest 2.8 version in the Android Development section of the forum. IT says to only attempt install if you are on latest bootloader.
My current epad version says 10.6.1.15.3. How can I get it on the latest and greatest before installing new twrp? I can't find that anywhere. Edit: Ok, I did more searching and found a thread (http://forum.xda-developers.com/showthread.php?t=1757077) that says to just download stock from Asus and run fastboot to 'flash system blob'. Can I do this with TWRP installed? If so, do I need to reinstall TWRP? Trying to avoid brick at all costs.
Also, in TWRP, the backup section doesn't show a partition and asks for a password when TWRP first loads (like the partition is encrypted... i dont know password).
tried the flash system blob (stock asus blob). It worked.
Greetings,
I am trying to instal the LineageOS on my XT1039 Peregrine but I am always getting the following error: E1001: Failed to update system image. Updater process ended with ERROR: 7. I am able to install any stock rom on it, without any issue, but when I try to install Lineage, or any other modded rom, it doesn't work at all. (I've only tried Slim and cRdroid, both gave different issues as far as I remember). Doing google searchs mainly I found posts here and on Lineage subreddit which possible fixes which include: Updating the bootloader, which didn't work because it's already on the latest version, told me to downgrade TWRP and try to flash again also didn't work and I have tried editing the updater-script by removing the asserts or editing the block_image_update lines which also didn't work.
I have a XT1069 Titan which I unlocked the bootloader, flashed the twrp recovery and flashed the latest nightly LineageOS build and it worked just fine, but I can't get it to work on my XT1039 Peregrine.
Thank you for your time and apologies if something like this has already been solved before. I couldn't find a [solved] thread that works for me.
All stock roms from here work just fine:
https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
updater-script mods I tried:
https://forum.xda-developers.com/showpost.php?p=68442611&postcount=1344
https://forum.xda-developers.com/showthread.php?t=2522762
tool I used to try to upgrade my bootloader, but I already had the latest version:
https://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793
Edit: Not sure if this is worth mentioning, but before getting the stock roms to work, I think I may have hard or soft bricked my peregrine and somehow managed to fix thanks to a lot of hours on google and xda forums.
Off topic!
This is completely off topic, but let's say I want to sell a phone, if I wipe all partitions from twrp will it wipe everything leaving no trace like when we format a SSD before selling a PC? I belive that a factory reset done from android itself doesn't wipe the whole phone and possibly leave traces, is this correct?
Yesterday, I tried to unlock using lineage16, using twrp3.31 version. . In the first system version of emui9, flashing lineage. Failure, error7 is prompted. . I carried out several system updates, (the latest emui9) installed twrp, flashing lineage16. Still failed.
Finally, I carried out the wrong operation, recovery cleared the data, and now rec and erac can not enter I think I should go to the sale to solve this problem.
My device is a Chinese version, the model is al20 (as far as I know, the hardware is no different from the US version, except for the baseband)
This is my system version, and various parameters. . I hope you can get your help I have unlocked the device protection lock. The only problem is error7. This phone does not have the rom I like in China. . . . I have checked some information, it may be that the rom and the phone model are wrong, or the underlying firmware is wrong (I used the official recovery tool to restore to emui9) Now, I can only guess. . . . The problem with rom, may not be considered by the developers, and it is not known that the Chinese version can be unlocked.
My friend told me to delete the rom model verification, I do n’t know if it is useful (after I am modified, use twrp to flash, error7)
He asked me to delete the first four columns
Don’t know if u r still using this device or not, the official 3.3.1 twrp will get error of unable to mount partitions on too new firmware version such as emui 9.1.337, downgradeing the firmware version may help, and lineage 16 will not work on Chinese's specific device such as al00 and al20, it would only work for some US specific model, in this case you can use other rom like aosip, i just flashed this rom and it is booting normally, but my al20 was sucked in installing magisk, after flashing the patched recovery the device will not boot or boot into the system without magisk......too many time were wasted on this device, and i don't want to play with it anymore..
Hello community!
Hope you are doing awesome, I am trying to install specifically the update from the 18 th of May (latest while doing this post) so when I downloaded it I go to TWRP and this is what I done
1)Place my pin and decrypt the device
2) Perform a format Data > Yes
3) Wipe cache, dalvik, internal
4) Restart to Recovery
5) Install the update all seems to be fine and reboot to system
The Phone boots to Poco screen and then vibrates and then gets me back to TWRP. I manage one time to get it worked and got in the config page from the customer rom a UI unresponsive message and is unable to connect to my Wifi so I have to use the Data 4G to make it work and I rolledback to April version of Arrow OS that seems to be the one working now.
The Miui stock that I am using to install the customer Rom is surya_global_images_V12.0.8.0.QJGMIXM_20210222.0000.00_10.0_global
Could you please provide some hints and tips what I am doing wrong so I can get this updates up to date? Because I love the Arrow OS Rom and I want to keep the firmware updated correclty on my side.
Thank you!
I am very interested, too. Got the same problem. After latest OTA-Update I'm stuck in a recovery bootloop as well.
Sadly even the attempt to flash back an older version or a MIUI Stock rom is failing for me now. Always recovery bootloop, even after a successfull flash without errors (and format data of course) .
Is the stock rom or an older arrow os version working for you, after the 18th May update?
@koelbche I was able to make a stock based on the stock fw shown on my post. then I installed old version of arrow OS April update and it was restarting bootloop.
I had to delete data, factory reset and select de wipe options so super clean flash and manage to boot it up.
I am waiting for any updates from others that manage to install the updates because I was not able to do it.
Flash ArrowOS custom recovery for ota update to work. After update you can flash recovery back to TWRP for root and backup, your choice.
I was able to make it worked in another post.
All I have to do was to update the version of the stock with Oss vendor (I think) and then all worked like a charm!.
Thanks for the replies though