Related
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 all, i have a problem whan i install lineage os, i don't have any system on my oneplus one and i want install lineage but when the installation has finished, my phone restart and freeze on logo one plus one android powered.
if you have a solution ;D
good night
LucasJahier said:
Hi all, i have a problem whan i install lineage os, i don't have any system on my oneplus one and i want install lineage but when the installation has finished, my phone restart and freeze on logo one plus one android powered.
if you have a solution ;D
good night
Click to expand...
Click to collapse
Which firmware were you on? Which recovery you used?
Did you tried previous lineage os nightly's?
I don't know what firmware i m and i have try with the latest nighly release. And i use the latest version of twrp
LucasJahier said:
I don't know what firmware i m and i have try with the latest nighly release. And i use the latest version of twrp
Click to expand...
Click to collapse
Go to setting > about phone and see Baseband version.
If you're coming from CM13.1 make sure to wipe everything except internal storage.
Download the ROM again if possible (the version you have downloaded may be corrupted) from the Lineage os official site and gapps(micro or pico).
Flash the ROM first and then gapps.
Reboot your device.
If you want the Root access download the Su add-on from the Lineage website also.
Hope it will work.
Let us know.
Thanks.
Re
Re,
Sorry... but i don't have any os in my oneplus one... he is empty exept zip the lastest version of official website and zip of gapps.
Thank you
I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted
retalger said:
I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted
Click to expand...
Click to collapse
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.
SOLVED
OGdroidster said:
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.
Click to expand...
Click to collapse
Oh! Thank you so much for the help.
retalger said:
Oh! Thank you so much for the help.
Click to expand...
Click to collapse
Sure your welcome
Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.
drkdeath5000 said:
Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.
Click to expand...
Click to collapse
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.
thunder2132 said:
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.
Click to expand...
Click to collapse
I tried this last weekend but was getting constant force closes from System UI so i gave up and went back to the MokeeOS build.
Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.
polyzen said:
Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.
Click to expand...
Click to collapse
Nice! I'm glad you got it working.
what do you mean with reflashed factory image 4.1.2?
I was on Resurrection Remix for the Razr M and now flashed LOS from this thread because of connectivity problems and I hoped it is a problem of RR. But unfortunately I still just have Edge connection, no 3G or 4G. Does anyone know how to fix that? There were no problems under 4.1.
Edit: I went back to 4.1.2 and wanted to start from zero but now on 4.1.2 there's only Edge connection as well :/
Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys
Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!
if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:（Translation is not easy to use）
celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip
So I tried to install a custom rom on GT-N8010.
Used Odin to flash ClockworkMod and TWRP.
I wiped cache and system.
Then I Intalled LineageOS 16.0 + Gaps: Some error while installing, so the instalation was aborted.
LineageOS 15.0/ResurectionRemix/SlimRom+GApps the instalation went fine. But on every one of these Roms the tablet is stuck in the bootscreen of the rom.
Between them I wiped cache and system.
Does someone have an idea what wnet wrong?
You need to read roms instructions .
Clockwork MOD No and use correct TWRP versions .
Thank you for the answer. But can you tell me/or send me a link, where I can read up on how to fix the tablet?
I could set up my windows machine in the sleep, but android, if they where asking me I would still use windows phone.
https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-16-0-t4182187
TWRP versions .
JJEgan said:
https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-16-0-t4182187
TWRP versions .
Click to expand...
Click to collapse
I used the correct TWRP Version and installed Lineage OS 16.0 and Gapps Pico, I wanted to boot the tablet and I saw the Lineage Logo and after a while it sent me straight back to TWRP.
I'm a bit baffelded.