yashsingh1/xdaforums huggingface dataset:
[HTC One A9] Ultramanoid:
For the life of me, I couldn't get it to flash over any other previous build, had to wipe completely and set the device plus applications and preferences from scratch, oh well.

Other than that all running fine now. And for those who need it, a confirmation that the boot patcher to disable encryption is also working just fine.
[HTC One A9] :
Sorry if i understand your post wrong, but i have tricked the signed rom.

It refuses to install/flash when the /data Partition is from an older unsigned version, so i made a backup of /data, wiped it, flashed the signed rom and then recovered the backup of /data (On the HTC One M8 of my wife) it booted well and everything is working since then, i can install the latest signed builds without any problems.
[HTC One A9] Ultramanoid:
Thank you for this. I'll try it with the next build if I have the same problem.

This way you mention used to be necessary and I did it with other devices and older CM versions, before TWRP. CM used to be terribly fussy about /data... Since I started using TWRP I never had this happen again until this build now.
[HTC One A9] mlecho:
can any of you confirm camera video works fine (not choppy)
[HTC One A9] :
Recorded two videos one front and one with the back camera with the standard lineageos camera app. The videos are about half a minute long and looking very good.
[HTC One A9] Ultramanoid:
I still get frozen UI with camera applications sometimes though ( Open Camera and another open source one, I don't have or use the default ), usually must force close and relaunch, then it works.

Images and videos themselves are fine. I've just tried short 1080p videos.
[HTC One A9] bjo81:
Updated from my build to the official from yesterday - System-UI crashes :/
[HTC One A9] Ultramanoid:
Same. It's why I had to wipe clean everything. Try the solution mentioned above about /data, or wipe and install from scratch.
[HTC One A9] scott8281:
I'm on 4/18 unofficial with only minor bugs but I couldn't even get 4/25 official to flash at all. It just fails and gives me an error
[HTC One A9] jjakajonas:
Do I have to do a clean wipe of my CM device before installing this?
[HTC One A9] bjo81:
It seems so. After wiping the rom runs fine.
[HTC One A9] jjakajonas:
Damn.

I had hoped on the migrate thing ?
[HTC One A9] mlecho:
so, i've flashed 1.57.617.60 (system & boot). Booted fine. Then per point 6 above in that link, I did the following

1. boot to recovery to TWRP

2. Advanced-> Terminals-> echo -ne "1.57.617.60\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208

3. reboot to download

4. fastboot getvar version-main

but i still have version-main: 2.18.617.1

my understanding is only one \x00 for 11 digits - i clearly have done this wrong.
[HTC One A9] Fudgehog:
If you have fastboot flashed the firmware correctly mlecho, then I would recommend RUU'ing to 1.57.617.60, to update everything else then do your wipe and what not.

This is a firmware.zip for 1.56.617.20 firmware or close to it. I did fastboot flash of it, then RUU'ed to 1.57.617.60.

Sorry, ignore what I said. But I'm sorry to hear you are still S-ON.

https://www.mediafire.com/file/a4xd6c17idbqj25/MMfirmware.zip
[HTC One A9] mlecho:
i can flash, but hows that different than RUU'ing? I'm on a mac, so it's not just a click for me

what is this file?
[HTC One A9] Fudgehog:
Like I mentioned, that is a firmware.zip to downgrade to I want to say 1.56.617.20 that I found here, on XDA. It is just re-uploaded on my mediafire. In download mode I flashed the firmware.zip and afterwards I ran the 1.57.617.60 RUU and was successful in downgrading from N. I also don't like or know apple products at all, but I would suggest trying this method. RUU basically ensures that everything is installed correctly, otherwise it won't update.
[HTC One A9] :
Maybe you need a second try to change the version-main.

If you have a running rooted System you should try it again from there with a console app. "1.57.617.60\x00" is correct, because at the end are two digits (In the example there is one digit less).
[HTC One A9] mlecho:
still no love...i am rooted. I tried both from terminal and TWRP terminal. I'm sure the firmware is as noted ^. Could my TWRP version be a probelm (3.1.0)? Here's the exact c/v from terminal:

$ su
-ne "1.57.617.60\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208 <
12+0 records in
12+0 records out
12 bytes transferred in 0.003 secs (4000 bytes/sec)
root@htc_hiaeul:/ # exit
shell@htc_hiaeul:/ $ exit
E-MacBook-Pro:HQ$ adb reboot download
E-MacBook-Pro:HQ$ fastboot getvar version-main
version-main: 2.18.617.1
finished. total time: 0.000s
[HTC One A9] Ultramanoid:
Several users seem to have problems with 3.1, try 3.0.2.
[HTC One A9] mlecho:
i can't -just tried again, and i get a loop that spits me back to the boot loader screen every time. It should be as simple as

fastboot flash recovery /path/to/twrp-3.0.2-0-hiae.img

is there a reason i can't flash an old TWRP over a newer version?
[HTC One A9] Ultramanoid:
Not that I know of. If you could boot TWRP 3.1 you could even flash 3.0.2 from there, I've done that often recently myself. Maybe check in the RUU firmware thread, alray ( the OP ) seems to be able to solve every issue people throw at him when it comes to firmware.
[HTC One A9] Fudgehog:
3.0.2 has messed with me, and I remain on 3.1.0. It seems the easiest way to downgrade is how you mentioned, with fastboot flash recovery. I guess I would try copying the recovery straight to your adb folder, and running command prompt as administrator (or Mac equivalent). But like the previous poster said you can also install TWRP from TWRP. Just make sure you reboot to bootloader after install instead of recovery right away.
[HTC One A9] mlecho:
tried flashing 3.0.2 from TWRP...no love.....it's off topic anyway, getting back to the topic, which is flashing lineage from a 2.xx firmware - would it help if i completely rollback to stock and relock bootloader? then do the whole cycle from scratch? or am i just getting desperate now?
[HTC One A9] Fudgehog:
As far as I know, unless you can downgrade you cannot install lineage. It is made to target and install over top of MM and I'm not aware of any build that installs over N, especially due to no kernel source. I would say yes you are desperate, and I have a lot of battery issues on Lineage, it practically dies over night. While I love it for simplicity and performance, the battery overnight is a trade off for me. Even on the new nightly.
[HTC One A9] Ultramanoid:
Lineage is running on 1.5x firmware for now. When hTC releases Nougat kernel source, intervirgil will likely rebase on it and it will run on 2.x, you can always wait. hTC is legally bound to release kernel source, nobody knows when they will though.

No battery issues whatsoever on both my A9 with Lineage, one gets used a lot, the other not so much, both seem fine.
[HTC One A9] Fudgehog:
Yeah it seems to die faster in airplane mode overnight, and when I installed this nightly, it was a clean wipe from the unofficial build.
[HTC One A9] mlecho:
Turns out my /misc partition is not mmcblk0p28 but rather mmcblk0p29...got the version-main changed, still get the bootloader loop after trying to install lineage build. I'm convinced my A9 hates me

ls -al /dev/block/bootdevice/by-name/misc
lrwxrwxrwx root root 2017-04-27 10:18 misc -> /dev/block/mmcblk0p29
-ne "1.57.617.60\x00" | dd of=/dev/block/mmcblk0p29 bs=1 seek=2208 <
12+0 records in
12+0 records out
12 bytes transferred in 0.008 secs (1500 bytes/sec)
root@htc_hiaeul:/ # exit
shell@htc_hiaeul:/ $ exit
$ adb reboot download
$ fastboot getvar version-main
version-main: 1.57.617.60
finished. total time: 0.000s
[HTC One A9] Ultramanoid:
It occurs to me ( totally going out on a limb here ) it might be a bug where somehow the device is constantly looking for a signal ( which consumes an awful lot of battery ), which, being in airplane mode, it won't find of course.

Otherwise it makes no sense that not being used, and not having any sort of connection, it would use any battery at all except the absolute minimum.
[HTC One A9] Fudgehog:
Right I absolutely agree. The CM builds last year were great up until the 12-25 nightly, that's really when it started. I've tried to figure it out myself trust me. I use kernel adiutor and it seems that the cpu frequency on the big core likes to stick to 1344 mHz. It won't let me edit it of course either.
[HTC One A9] :
I have another little Bug, sometimes when i press the power button to get to the lockscreen the display shortly turns black again and then it starts the camera app.
[HTC One A9] jupppo:
Hey guys,

I have a question. I am running a quite old CM13 Version on my hiaeuhl (with TWRP . My firmware is also quite old 1.1x.xxx I think. I would love to try this Lineage built, but I think I have to update firmware. Here is the steps I think I need to take. Can you correct me if I am wrong?

1) Flash RUU 1.57

2) flash recovery Twrp 3.02 via fastboot

3) flash flash lineage

4) flash gapps

5) reboot

right or did I miss something?
[HTC One A9] Ultramanoid:
See if this helps : Settings > Gestures > Jump to Camera

That sounds about right. There is a newer TWRP 3.1.0 available as well. Some people have issues with 3.0.2, some do with 3.1.0, see which one works best for you. ( After Lineage updates to run on 2.x firmware, which is not the case yet, looks like 3.0.2 won't work anymore though. )
[HTC One A9] :
Thank you, hope that helps.

So it's not a bug it's a feature :D
[HTC One A9] Fm4r1n:
i think only flash firmware 1.56.401.70 not ruu, but i not sure
[HTC One A9] jupppo:
problem is I cant flash 1.57, because CID is VODAP001 and here is latest 1.27, where linage refuses to install :(
[HTC One A9] :
Does anybody have a Problem with not working flashlight ? For me it won't activate if i press on the button. (With 25.04.2017 hiaeuhl)
[HTC One A9] Ultramanoid:
Curious. I can turn it on. Turning it off though takes 3 or 4 tries, never works the first few times. For a moment there I thought I'd have to turn off the whole device.
[HTC One A9] Fudgehog:
A small bug with the flashlight on several ROMs, if you are pressing from the status bar, and it takes several tries or doesn't activate, you can edit it and move the flashlight away and back then it works. Mine works with one click on Lineage official nightly. It also seemed that last night my battery barely drained, I might have fixed my issue.

Jupppo, I highly suggest S-OFF'ing (sunshine) if you aren't already, and if the device is hiaeul, converting to US developer edition. Simply change the CID to BS_US001 and flash any developer RUU or ROM. After that, your phone can run on Lineage, and make sure you do not update firmware to Nougat. (PS if you are looking for firmware you can use my 1.56 firmware zip I previously posted on mediafire).

Most likely you will have to update the ROM or firmware in steps (likely 1.55 then 1.56 and so on).
[HTC One A9] :
Thank you for the tip, it worked, now it only needs a few seconds to deactivate but that's not bad :)
[HTC One A9] Fudgehog:
No problem, I try to do good in this life, otherwise it would be unbecoming.
[HTC One A9] jupppo:
Thank you for your detailled answer. I s-off'd the phone with sunshine cid'd to 11111111 and flashed the hiaeuhl 1.56, which worked. unfortunately lineage ist stuck in boot animation. I tried to flah with twrp 3.1 and 3.02, no change!
[HTC One A9] wxo:
Same here. Reboots after entering boot password. Works fine if you don't enable the pre-boot authentication. Anyone else seeing this?
[HTC One A9] Fudgehog:
You might find that lineage will not work with SUPERCID, US unlocked ROMs are meant to work on BS_US001, however I would try using Windroid toolkit to install recovery or push it from download mode. If you flashed the firmware successfully, use the RUU to start fresh then install your recovery.
[HTC One A9] Formedras:
Is it possible to convert the HIAEUL or HIAEUHL packages to HIAEWHL? (I am friggin' sick of being stuck on stock+magisk.)
[HTC One A9] Fudgehog:
Why would you want to do this? HIAE is US unlocked and HIAEUHL is GSM international. HIAEWHL if I'm correct is Sprint based, you'd want to convert to US developer ROM, especially if you want to use Lineage. You also need to find out if you can be converted. I also suggest you do more research.
[HTC One A9] st40611:
Hiaewhl is the Sprint model, and can be converted; however converting still requires us to manually flash radio.img or else we have problems with missing IMEI and random reboots.

But I tried that myself. I converted my S-Off hiaewhl to US Unlocked, 1.5x firmware, and then tried flashing Lineage OS; every build so far tells me it can't find sim card, so I am guessing there's more compatibility issues.
[HTC One A9] Ultramanoid:
The hardware is different. Can't slap firmware not meant for it on the device and expect it to work.

If someone provided intervirgil with a Sprint model, he offered before to make a Lineage version for it. Which is basically why there isn't one now, it all comes down to maintainers having the device in question, otherwise how to make the appropriate software for it ?
[HTC One A9] mrsubway:
I'm not sure about this. I'm unlocked and S-OFF running rooted developer 2.18.617.21 and Twrp 3.1. Do I have to downgrade to flash Lineage? I'm reading you can't flash it from Nougat.
[HTC One A9] Ultramanoid:
Lineage does not run on 2.x firmware yet, won't until Nougat kernel source is released. It has to be 1.5x, but not lower, it won't run on 1.2x or 1.1x either. Downgrade to 1.56 or 1.57.
[HTC One A9] jjakajonas:
I got lineage 14.1 flashed on my phone (eu model) no biggy.

The only problem I have is that it sometimes freeze and then reboot and can't find signal after boot.

But aside that it works for me and consume less power.
[HTC One A9] Fudgehog:
Sounds like a kernel issue. Have you modified it at all, or changed governors?
[HTC One A9] jjakajonas:
Not at all
[HTC One A9] Fudgehog:
The first logical question is, have you performed a completely clean wipe? Second logical question, are your APN's set up correctly? Third, I suggest download Kernel Aduitor and check the scheduler governors because when I installed lineage it had those governors changed to BFQ, I suggest setting them back to CFQ. Lastly, what recovery are you running? Need more information to help with complex issues my friend.
[HTC One A9] jjakajonas:
Sorry..

My bad..

1. I made a complete wipe and even wiped my SD card by mistake.

2. Don't know anything about APN.

3. I will look at the kernel thing and update on this post web done.

4. TWRP 3.1.0

Update:

Can't figure the kernel part out.. Any kind of guide on how to?
[HTC One A9] Ultramanoid:
No insights about the freezing, but some users of German carriers reported previously that the network had to be selected manually after reboot. Might be the same bug in your case, check if you can get signal by searching manually for your carrier.
[HTC One A9] jjakajonas:
I can do it manually.

But it's a pain in the *** to do everytime. But I hope for a fix for it.
[HTC One A9] Fudgehog:
APN settings are CRUCIAL for mobile data, calling, and texting to work. You need to know the correct APN settings for your carrier and enter them and save them in network settings. Simply Google them. Kernel Adiutor is an app to modify kernel settings, this of course requires root access.

For example, I have ATT, when I install Lineage it changes my APN to an older one called ATT Phone, which is deprecated. What it actually needs to use is the NXTGENPHONE APN, which allows everything to work properly for me.

Once you are in Kernel Adiutor (don't forget to use SELinux mode changer to ensure proper changes) set the I/O schedulers to CFQ, I had the same problem until I switched the schedulers, make sure it applies on boot, and test the settings.

https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en

https://www.mediafire.com/?qed82fefw6mlj5p (SELinux Mode Changer)
[HTC One A9] jjakajonas:
Okay.

I have now made the kernel thing..

For the APN part.

I have looked at what I supposed is called access point in the English system (I run my device in Danish) and all looks as it should. There's a list of carriers.

Also if I make a manual search for carrier signal it automatically connects to TDC (the owner company of my carrier called YouSee) and works perfectly on the network.
[HTC One A9] Fudgehog:
So whatever your carrier is called, make sure you have all the correct settings. If it is YouSee follow their APN settings to a T and you should be fine. Make sure you changed your I/O schedulers to CFQ as well and you should be fine. Delete all other APNS you don't need.
[HTC One A9] jjakajonas:
Okay.. So I have now tryed to make the APN after what my carrier tells on there website. No luck. I stil have to make the mannuel search to connect.

But the kernel thing is changed as you said.
[HTC One A9] Fudgehog:
I guess your option is to call the carrier, or set the APN settings to that of the parent company, having little things wrong in the APN will make the whole thing not work properly. Other than those two options, I don't know what to suggest. You might also be able to remove the SIM, with the phone off wait 5-10 minutes, put it back in and turn it on. Otherwise I'm tapped on ideas.
[HTC One A9] jjakajonas:
Otherwise I have to live whit doing the manuel search after each boot.
[HTC One A9] Fudgehog:
Well you can complain about your problems or try to fix them ? lol. I'm confident one of my suggestions would work. Worst case get a new SIM card or make your own apns config file. There are master lists available for download on XDA. I'm sorry to hear your problem, I've given plenty of suggestions. Good luck.
[HTC One A9] jjakajonas:
I will maybe look at it later.

It's like 4.18 am here so I'm not that clear right now.

But maybe I should give that list a look later.
[HTC One A9] ClearD:
New nightly came out last night, looks like lots of changes. I've had issues with the browser and reboots, looks like they addressed the browser, hopefully the reboots also.
[HTC One A9] :
I have problems with reboots, too. Another problem is when i try to use whatsapp web, looks like it can't use the camera if i haven't started the camera app before.
[HTC One A9] Ultramanoid:
Strangely enough ( as I always seem to have the weirdest bugs nobody else has ) or maybe not, I have never had any reboots with the last two builds and I can use the devices heavily for two or three days before I need a restart for some reason, like really cleaning RAM because of Firefox choking the device ( unfortunately common ) or something like that.

I don't use Google software or any of Lineage's included applications ( I make a barebones installation from the nightly, basically I just want the base system and up to date security patches ), so I'd think therein should be the problem. Lineage has been working on many of their applications recently, maybe something is misbehaving with the new stuff.
[HTC One A9] ClearD:
Yeah, it didn't help anything for me. Just updated, still crashing regularly. That sucks. Using Chrome for now
[HTC One A9] :
With the new build i have reboot problems (Like previous version), i think it's only when i am outside, as long as i stay home there are no reboots maybe coincidence.
[HTC One A9] Ultramanoid:
What do you use outside that you don't use inside ? Maybe it can narrow down the possible issues.
[HTC One A9] :
I think it could be that changing a cell cause the reboots, or the searching wlan (When there's no connection) or the mobile internet. In reality i have no idea, because i see it when i am home again, because outside i use my phone very rarely.
[HTC One A9] marcos07r:
I installed Lineage OS on my htc one a9 hiauhl but reboot in bootloader mode I do not know I'm doing wrong to help me
[HTC One A9] Ultramanoid:
Do you have a working recovery, the one from Lineage or if TWRP, what version ?

Also, did you check that it is the hiaeuhl rom you flashed and not the hiaeul one ?

Edit : Actually from the post below I gather you're on 2.x firmware, which won't work. See below.
[HTC One A9] :
Hi, I'm so happy to see that I'm not the only one with this issue.

I purchased my HTC ONE A9 last year and was a happy CM 13 user. Back then I was on firmware 1.xx.xxx.x. When the Nougat RUU came out I updated the firmware to 2.17.401.2 since I have an european phone (modelid: 2PQ910000 and cidnum: HTC__034). When I;

- flash TWRP recovery to 3.1.0

- wipe Data, Cache, Dalwik, Internal Storage

- Install latest nightly lineage-14.1-20170502-nightly-hiaeuhl-signed.zip

- it installs just fine but after the installation it reboots in bootloader mode.

So, marcos07r have you updated your phone to firmware 2.xx.xxx.x lately?

Greets

andmars
[HTC One A9] jjakajonas:
i had reboot problems before but the kernel fix a few post back seems to have fixed the problem for me.
[HTC One A9] Ultramanoid:
Lineage does not run yet on 2.x firmware. You'll have to downgrade to 1.5x to use it.
[HTC One A9] marcos07r:
Yes Android 7 2.17.401.2
[HTC One A9] :
Same as me. So we either have to downgrade to 1.xx.xxx.x or wait until lineage os supports 2.x firmware.
[HTC One A9] Ultramanoid:
1.5x will do, but lower than that ( 1.27, etc ) won't work with the newest Lineage. 1.56 or 1.57 is fine for now, until hTC releases Nougat kernel source.
[HTC One A9] wegigdiptyaa:
Did google camera work on lineage os??
[HTC One A9] Kauser Ahmed:
no 3rd party camera app doesn't currently work on lineage os for htc a9
[HTC One A9] wegigdiptyaa:
Thanks
[HTC One A9] jjakajonas:
And I had a reboot again this night so the kernel thing did not fix it.
[HTC One A9] Ultramanoid:
That's a confusing line...

Third party camera applications work, some better than others. I don't know about the Google one specifically, don't use it myself.

I have default kernel with default settings, never had a reboot on both my A9, so not likely that is the problem.

I don't have Google software or Lineage applications, so I would start by looking into those. These are nightlies after all, breakage expected, and Lineage has been making changes in their applications recently.
[HTC One A9] Kauser Ahmed:
Google Camera doesn't work, htc camera doesnt work, the camera on messenger doesn't work, and the camera on facebook is extremely slow
[HTC One A9] Ultramanoid:
Open Camera, FreeDCam, and the camera from simplemobile ( all of them open source ) work. I use the three of them.

FreeDCam is rather buggy lately, but that's on several devices, not related to the A9 in particular.

A Better Camera and Vignette, both paid applications, also work.

Edit : The question was only about Google's camera, so I guess that's the only answer needed.
[HTC One A9] jjakajonas:
I do expect problems in the OS because it's a nightly software. I did the same whit CM back then.

But if an error is seen by others is it maybe a bug and the only way to find out about that is to report what you discover and see if others is experiencing the same.

If you are the only one then it's maybe just your device.

Are there more (like this reboot thing) then maybe it's a incompatible problem whit other software or maybe a bug.

To develop the OS is there a need to come some feedback on the system so it can be better.
[HTC One A9] Ultramanoid:
Exactly, I agree completely, which is why we should focus on what is different between us, since several of you have the problem, but my A9 devices do not. The kernel is not something different, we all use the same.

I do not use Lineage applications, you all do, so it's logical to think the problem could be ( not saying it is ) there, especially considering the rapid code changes in nightlies. An application you all use and I don't could be causing reboots.

Trying to narrow down the problem.

Anyway, logs are the way to go. Get a logcat and see what was going on at the time of reboot, anything else is guesswork.
[HTC One A9] jjakajonas:
Only software I use other then stuck from lineage is some google apps and magisksu.

I don't know how to get hands on that log for yeah.. That could help alot in instead of what I have done so far.