yashsingh1/xdaforums huggingface dataset:
[HTC One A9] megatomic:
Would you mind making the firmware.zip file you used available to download also? I am still seeing the failure to mount /carrier error.

Tried to install LOS and Gapps, stuck at the animated LOS boot screen again. Grrr.

OK, I fixed the missing partition by flashing stock HTC recovery and booting to an RUU zip file, this repaired the partitions. I flashed the special TWRP version and wiped data and had no error messages this time. I'm flashing Gapps now and hoping for the best.

SUCCESS!! Thanks to everyone for helping me with this mess. Now I have 2 more questions:

1. Does anyone have a flashable version of the Snap camera for the A9? The version of Gapps I installed overwrote the Snap camera with Google Camera and the Google Camera force closes immediately as it opens.

2. If there is no way to flash the Snap camera separately what is the preferred third party camera app? I've tried Open Camera and it's pretty basic and Bacon Camera and it's laggy and kind of buggy so far. Thanks for any help with this small dilemma.

Nevermind about camera apps, I started from scratch and installed the mini Gapps package. Snap camera survived the flash and it's much better than the ones I tried off of the Play Store. Now my phone is a smaller version of my OnePlus One with the addition of a fingerprint scanner. I'm happy.
[HTC One A9] Sympl3x:
Sorry for the late response on the firmware. Glad you got it worked out. One thing I noticed, is TWRP was unable to decrypt my data partition after successfully installing. I was able to fix it by turning on a boot PIN rebooting, then turning off both lock screen and boot PIN. Then after booting to TWRP it took the previous boot PIN I setup. Weird, but not really sure how all that works. If someone can explain the Lineage encryption and if there is a better way to get TWRP working with it that would be great.
[HTC One A9] Ultramanoid:
Sorry if I misunderstand you, but do you actually mean you got TWRP to decrypt with Lineage ?

If so, you would be the first, not even the developer making TWRP for the A9 got it working yet, you should report it to him in the TWRP for the A9 thread.
[HTC One A9] Fudgehog:
My firmware issue is fixed. It is now compressed without the extra folder. You forgot to use the RUU TO COMPLETE FIRMWARE UPDATE. This is a very important step. You will get bootloops if you do not let the RUU completely overwrite your system to a stock sense ROM. It needs to be done. Then reinstall TWRP or if you use my firmware package with it, then you're good to go. Wipe everything, THEN install Lineage.

Ultramandroid, TWRP decrypts after installing lineage as long as a format data is performed. Newest TWRP. On the 5-9 build works perfectly. The 5-30 build was more restrictive I found and would not let me receive calls and was a general PITA with using TWRP.

I've also had no mounting storage, data, or carrier issues using the newest official TWRP. I did the M firmware, ran the HTC RUU, did a format data and complete wipe, installed lineage. Did another format data to remove encryption and all mounting issues, then installed gapps and everything else. And remember guys, sometimes recoveries work better with a simple setenforce 0 in terminal.

RUU zips do nothing to change firmware. Once you flash desired firmware you need to use RUU.exe to match what firmware you flashed. It's all really simple really, then just my steps above.
[HTC One A9] Ultramanoid:
Well, I'll be...

After all the endless tries by CaptainThrowback and the boot patcher coming and going and whatnot, you'd think him or someone else would announce this major change in the TWRP thread ( or here ) ... If somebody did, I've missed it completely. Thanks.
[HTC One A9] megatomic:
Is Google Duo crashing for other people? I am on LOS from 06062017 with mini Gapps (Snap camera intact) with no mods or other files flashed to the phone aside from the load of apps installed from the Google Play Store.
[HTC One A9] Sympl3x:
I'm having an issue receiving calls when using LTE with AT&T. One the stock HTC ROM I was able to get HD Voice calls with VoLTE. I noticed today I can make calls, but do not get any incoming calls unless I change my preferred network to 3G. If it is set to LTE, then my number just rings and rings until it kicks over to my Google Voice voicemail box. From what I have been reading VoLTE does not work with Lineage. Does anyone know of a way to disable it on the carrier side so I can keep using my LTE for data?
[HTC One A9] megatomic:
I'm on AT&T also, calls are fine here. I'm currently on a Microcell (4G), I'll test the LTE calling after work.

My big issue is camera. Snap camera works great all on its own but most apps that access the camera are crashing. FB Messenger, Google Duo, and MSQRD so far all crash immediately.
[HTC One A9] Fudgehog:
I had this exact same problem on a completely fresh wipe, installed it twice with clean wipes. I went back to the 5-9 build for this very issue. See my former posts.

---------- Post added at 02:17 AM ---------- Previous post was at 02:13 AM ----------

No problem, although it's been like that since before we had CM or Lineage, formatting data removes encryption on internal storage and allows TWRP to act in full capacity. Not that you missed it, but I thought it was almost common knowledge.

I have my fixed and updated my firmware here:

Stock 1.57.617.60 - https://www.mediafire.com/file/jc3jp4afacb01rv/1.57.617.60.zip

1.57.617.60 with TWRP - https://www.mediafire.com/file/0l420t9d4604afs/1.57.617.60+-+with+TWRP.zip
[HTC One A9] Ultramanoid:
No, that's not what I was talking about. I'm talking about keeping the device encrypted, and being able to decrypt it from TWRP, which in fact, then, is not possible yet.

As of now, we still have to choose between using TWRP with no encryption, or using encryption without TWRP having access to data, which cripples its functionality. CaptainThrowback has been able to make it work in stock but not with Lineage.

Glad I'm not going senile yet...

Encryption is enforced by Lineage which is why we still need to use the boot patcher to disable it and dm-verity.
[HTC One A9] Sympl3x:
Bummer, OK. Can I dirty flash from 6-6 back to 5-9? Or will I have to re-wipe and reload everything? On that note, will every new Lineage OS update re-encrypt data thus requiring a format data each time we update?
[HTC One A9] Fudgehog:
I couldn't answer that second part. I would advise a clean wipe and restore apps and contacts from Google, but that's just me. It seems for now every other update is broken one way or another, but that's nightlies for you.

But at least with the 5-30 build, not doing a format data, it did encrypt on first boot, yes. That also could have been my negligence for not formatting data as well.
[HTC One A9] Ultramanoid:
Use the boot patcher available for this purpose; keeping the device decrypted and with dm-verity off. TWRP does not work with encryption on the A9 as yet, using Lineage.

Remember to flash the boot patcher after flashing Lineage every time.

Again, there's a boot patcher available. Please read properly through this thread and TWRP's thread before volunteering information that is not correct.

TWRP for the A9 with Lineage does NOT support encryption. Once the device is decrypted formatting data, it can be kept that way and dm-verity off, and use TWRP fully, by flashing the boot patcher.
[HTC One A9] Fudgehog:
"Information that is not correct" ??. I'm not CNN. And sure the tool may work but it also hasn't been updated since December 2015. I don't want or need any of my data encrypted, but would like it decrypted for the sake of a backup. And dirty flashes most of the time are not a good idea. But yeah thanks for jumping the gun. ?

And the tool has never worked for me personally, with any ROM, so while Captain Throwback is awesome, you won't see me advising to use it.

Anyone is welcome to sue me for bricking their device. ? I live at the corner of you did it to yourself and not my fault street. Yes OP's are knowledgeable, but they don't have time or patience to answer piddly questions, most of the time.

As a police officer, I know civil liability all too well, and this is not now, and not ever going to be a case of it.

"I believe HIAEWHL is Europe based, if I'm correct", "Do some more research on it" exactly what I said.

For sure I'll file that as a complaint, make sure it's in my report too. Yeah 12 hour shifts and keeping the peace, I don't have time to argue with someone who knows it all. Get a moderator to edit it I could care less. Maybe I'll open a PO box so you can lodge complaints in it that I'll never care to look it. Like I said everyone is open to sue me, just glad there is someone like you to differentiate the "alt-right" facts. You have a good one.
[HTC One A9] Ultramanoid:
Number one, there has been no need to update it, works perfectly fine for everyone except you. It was made by osmosis and CT himself points to it as the only way to keep an A9 device decrypted with dm-verity off for Lineage at present, which is how everyone does it unless encryption is a stronger priority.

Number two, speaking plainly instead of politely as I did at first, stop giving advice to other people based on false information or your opinions without knowledge of a particular issue, you've done this before in this thread, as for instance when speaking of the Sprint A9 as a European model, when Sprint is a US carrier and the radio is not compatible with neither hiaeul nor hiaeuhl models.

You're going to get someone's device bricked if you keep doing this.

There's a reason why there are threads for TWRP for the A9 and RUU for the A9, each with knowledgeable OPs that know what they are doing and that's where users should be pointed to.

Edit : Might as well correct yet another false statement so people searching the thread can find the right answers; being S-Off is NOT required to upgrade or downgrade firmware or needed at all to run Lineage on the A9.
[HTC One A9] bjo81:
Argh. adb sideload got stuck at 33%, and as I tried to flash again, TWRP reboots and the phone gets stuck at the HTC screen. With the build form 30.5. I had this issue also, and I could only flash without TWRP crashing after wiping system. But after wiping system, Google Play Services were unable to sign in until I wiped also data.

Any clues excepct wiping now all again? :/

Edit:

Wiped system, flashed image and gapps again and all works again :)
[HTC One A9] Xtaner:
Only for: HTC One A9 (GSM International) - hiaeuhl

Status report from me to the following build:

lineage-14.1-20170613-nightly-hiaeuhl-signed.zip

Carrier: German Telekom

SU addon enabled

Recovery: twrp-3.1.1-0-hiae.img	2017-05-17

Phone

htc_hiaeuhl PVT S-ON
LK-1.0.0.0000
RADIO-1.1.U00036.1@60204
OpenDSP-7.8.2.00197-8952-1228
OS-1.62.161.2

Bugs I've spotted in the build:

- Music Player alway displaying album covers on lock screen (if you enable and disable this bug stop till you close the app)

- Decryption of /data with TWRP 3.1.1.0 still not working

Fixed:

- Carrier is not detected automatically (you've to selected manually after every reboot and every time you've switch from flight mod back to normal) --> FIXED

- Email notification is not working --> FIXED Select PUSH mode

- LiveDisplay does work sometimes and sometimes not (kind of strange) --> FIXED

- No translation for the new GPS menu --> FIXED

- Notification LED is not working for apps that are active if screen is locked (sms/mms is working) --> FIXED

- Personal encryption password is not working (if you enter one, lineage does not detect any carrier)--> Haven't tested it with this build. Because I'm not able to do a full backup (/data decryption not working), I'm not willing to wipe the phone for the test --> FIXED

- WLAN only working in 5 GHZ mode, no 2.4 GHZ mode --> FIXED

Note:

Camera works fine, no crashes if apps access the camera.

No reboots or other wired stuff.

Great build!
[HTC One A9] bjo81:
Hm, no issues here with 2,4GHz Wifi, both work fine.

But btw, can you use VoLTE with Lineage and Telekom?
[HTC One A9] Ultramanoid:
No issues with 2.4 WiFi here either.

How is TWRP decrypting for you ? It doesn't support encryption in Lineage. See points 5 and 6 of the FAQ in the TWRP thread, that functionality is not possible, according to the developer who makes TWRP for the A9.

Edit : Will double check in the other thread about this.
[HTC One A9] Captain_Throwback:
That FAQ hasn't been updated in a while. And I never said it's not possible - in fact, I don't know why it wasn't working. I'll have to load the latest Lineage and see if it decrypts for me. I haven't tested that in months and last tests were on CM13.

EDIT: Just tested the lastest nightly, and decryption in TWRP isn't working for me. So I'm not sure how it's working for anyone else. I'd have to see a recovery log from TWRP where it's working.
[HTC One A9] Mbuuqw:
I'm on the latest version of HTC's ROM for the One A9 (Can't remember the version number, I just know it's on Nougat)

I tried flashing LOS onto the phone and I'd always just end up in the bootloader, with the phone going into a bootloop due to a missing OS when I try to reboot to system. I think this correlates with me just installing TWRP, rebooting to the bootloader and booting into recovery. I haven't tried installing TWRP, rebooting to system and then rebooting to recovery yet.

Edit: TWRP install just destroyed all data, including OS. Great. I tried rebooting to system and it pulled up the whole install TWRP app and put me into a bootloop after I swiped to install the app. Waiting in download mode so I can install LOS on this.

Edit 2: Flashed RUU, set everything up, installed TWRP, rebooted system with no success and now I'm stuck on the HTC splash.
[HTC One A9] Ultramanoid:
Thank you. I have two A9, it doesn't work in either.

From wrong statements posted in this thread lately, I fear some are now confusing formatting-data-and-removing-encryption from TWRP with actually-decrypting from TWRP.
[HTC One A9] :
Hi there,

i am back to Los since the 05/30 build. Wifi works fine :) the reboots i had in the past changed, now there are no reboots when i go outside. I had only 2 reboots overnight since 05/30 (One with 05/30 and one with 06/06, until now no reboot with 06/13).

Only wanted to tell this :)
[HTC One A9] Xtaner:
I'm very sorry. You're right, there is no 2.4 WLAN problem.

I was confused because in my WLAN I'm using most of the time only 5 GHZ mode.

Sorry about that.

Lets get to TWRP.

This is what TWRP is reporting if I try to decyrpt /data

Updating partition details...
...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block device '/dev/block/dm-0'
Updating partition details...
...done
Unable to mount storage
E: Cannot decrypt adopted storage because /data will not mount
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)

After the "Data successfully decrypted" report, TWRP switch to main screen, so you can't see the errors that displayed after the "Data successfully decrypted" report, if you didn't look in to the log file.

So it seems to be the right way, but still buggy. Maybe some one else could interpret the log output.

Just for the notes, I've enabled the boot password. So maybe thats the reason for the wired report from TWRP.

But thats only speculation from me. I don't know enough about the decryption process.

I'm sorry for this too.

I've corrected my original post.

What you mean VoLTE?

My carrier is "Deutsche Telekom" D1 network, I've a normal contract and LTE is standard for the contract.

The phone use LTE automatically.

Let me know if you got there some issues, maybe i can help.
[HTC One A9] Ultramanoid:
Lineage doesn't run on Nougat ( 2.x ) firmware yet, to use it you'd have to downgrade to 1.5x firmware, or wait until hTC releases Nougat kernel source.
[HTC One A9] Mbuuqw:
I've tried many times on 1.5x firmware, says that something is outdated. I'll probably revert to RUU and be patient.
[HTC One A9] loner.:
It doesn't look like HTC is going to release the source code. (Maybe they lost it)
[HTC One A9] Captain_Throwback:
Did you ask them for it?
[HTC One A9] loner.:
Yes
[HTC One A9] Captain_Throwback:
And they actually said they won't post it? Because they'd be in violation of GPL if they don't...
[HTC One A9] loner.:
I never said that.

I received no reply which speaks for itself in a way.
[HTC One A9] Captain_Throwback:
https://twitter.com/Cpt_Throwback/status/875910164020436993

I just tweeted at them so we'll see what they say.
[HTC One A9] buicongsang:
please help me,i can't start phone[IMG="phone"]http://imageshack.com/a/img922/1923/uXBOrJ.jpg[/IMG] [IMG="thông tin"]http://imageshack.com/a/img922/6269/BhH490.jpg[/IMG]
[HTC One A9] Dragonkind:
I've found some issues from 0621's rom:

- Fingerprint button can't be set as home button, no related options.

- Default dpi isn't the same as stock rom, LOS 14.1 is higher. (smaller texts and icons)

- HDR capture works with bug, it would take 2 pics but not combine them.

- Third-part camera isn't supported as before.

- Media volume seems to be too low with lower levels?
[HTC One A9] Ultramanoid:
From what you write looks like you only used hTC's version of Android or an old version of CM.

This has never been possible with CM or Lineage for the A9.

Edit : It is possible to use the fingerprint reader in other devices with Lineage, the most recent one that comes to mind is the Moto G5 plus, which even supports gestures, but these kinds of settings differ with differences in hardware, so not a universal feature in all Lineage builds.

This was a change that happened months ago. hTC uses 480, CM / Lineage changed it to 420. You can fiddle with interface settings or change the value editing yourself the build.prop file.

Edit : In build.prop it's at ro.sf.lcd_density; personally I dislike both values ( hTC too big, Lineage a bit too small ) and set it to 440 which is the closest to the actual screen dpi of this device.

Third party cameras I use work fine, including barcode scanner ones. Some have complained social media applications are hit or miss. Guess it depends on what you use. Lineage includes Snap though, which is the one they support.

Some complained about this in the past, claimed it could be solved by erasing a system file. Search the thread for details.
[HTC One A9] Sympl3x:
So has anyone with AT&T with HD voice enabled on the stock HTC ROM been able to get calls in Lineage with LTE? On the 5/30 and 6/13 (current one I'm on) I have to disable LTE to receive any calls. I know people have claimed they can get calls on ATT LTE but were you using HD voice before? I feel like it's an ATT issue with my SIM but have no idea. Getting tired of using 3G as the service is much worse in some areas for me. With the LTE issues and other general weirdness I've been having on Lineage i may just have to go back to stock HTC for a bit.
[HTC One A9] DeadlyByNite:
Is anyone else having problems receiving calls on the past few builds? I'm using AT&T, converted to Dev Edition, and I can't receive any calls since the 5/9 build. I believe that it works sometimes as long as I'm not using an LTE network connection. From what I have read a few pages back, it seems that others are having the same issue, but I thought it would have been fixed by now.

Edit: I don't think that I was using HD voice before, unless it was enabled by default.
[HTC One A9] Sympl3x:
When making calls before, did they sound any different with other ATT users? Most often iPhone users. You can tell if it was HD voice because it would sound much better/different like a skype call.
[HTC One A9] DeadlyByNite:
No, I don't believe that I have ever used the HD voice feature. I don't really remember even seeing it in the settings anywhere. I don't know if it is even available in my area.
[HTC One A9] megatomic:
It wasn't hit or miss with social media apps. Every single one I tried had the same response, app crashed. Snapchat, Facebook Messenger, Prisma, and Instagram. I can't remember if I tried Duo or maybe I gave up before then.

I tried with the Snap camera, Bacon camera, Manual Camera, and a few others I can't remember the names of right now. I'm hoping that when and if HTC released the kernel code as per the GPL that the maintainers of our ROM will be able to fix nuisance issues like this.
[HTC One A9] Ultramanoid:
I already posted about camera applications ( I don't use social media ones ), but just tested all again with yesterday's build; Open Camera, Camera from simplemobile and FreeDCam, as well as Barcode Scanner, all work for me, all open source. Images and video, although surely image quality is worse than it was on CM 13.

I don't have or use Snap but I assume it works because otherwise 1 ) every single user would be complaining that it doesn't work, and 2 ) we wouldn't have official builds. Intervigil already stopped building once, Lineage does not put out builds when a major feature is broken.

I just hope he still has an A9 by the time hTC decide to comply with their legal duty... Clearly they're not in a hurry.
[HTC One A9] loner.:
I am guessing they ignored your tweet.
[HTC One A9] Captain_Throwback:
I'll remind them in a week.
[HTC One A9] megatomic:
All by themselves the camera apps worked fine for me. It's just when third party apps try to access the camera hardware that they crash. And I'm like you, I hope HTC gives the community the kernel source code while I'm still using this device.
[HTC One A9] Xtaner:
Could it be possbile that the problems with the camera only show up in the US version aka HTC One A9 (GSM US) hiaeul ?

Because like Ultramanoid I've got not problem with the camera and all third party apps can access camera without crashing.
[HTC One A9] megatomic:
Oh man I really hope not. Is the actual camera hardware the same in the US phones vs. International phones?
[HTC One A9] Dragonkind:
Sure they're the same. Mine is A9w with HTC621's firmware, also face the 3rd-part social apps camera issue...

Hope HTC released the latest kernel source ASAP+1
[HTC One A9] :
With my banking app (Photo Tan) the camera is working, with whatsapp it is working, too. I use the Lite Facebook app and video calls don't work there (App is crashing).

Then there was a reboot when i was outside with 21/6, with 13/6 there were no reboot at all. Can't provide a log because i can't predict the reboots, there are days/weeks without one.

So since 30/5 there were three reboots, two over night (30/5 and 6/6) and one when i walked outside (21/6). Can't really tell why because the phone was in my pocket when the reboots appear, i should say that the reboots now are no longer a problem for me because they appear really rarely.

I have to say that for my daily use the system is perfect, i hope that htc releases the sources for nougat in the next few days/weeks, maybe that fixes some bugs (like reboots) and maybe it bring some new bugs (Hopefully not :) )
[HTC One A9] Captain_Throwback:
[MENTION=5142831]loner.[/MENTION]

https://twitter.com/htcdev/status/878720861888446464
[HTC One A9] :
Hey guys. Haven't been in this thread in a while, let alone on XDA. Just letting you guys know that I probably won't be building for this device anymore because I no longer have a use for the builds although I'm not ruling it out.

I bought an Aukey quick charge 3.0 charger and my A9 didn't like it. So much in fact that it decided to melt the charging port. I'm not sure if it was because of the charger or because of HTC's code, but regardless, it's almost inoperable.
[HTC One A9] Ultramanoid:
Thank you for your builds. Surely saved many when Lineage builds were on hold.

The A9 is now included in the list of official nightlies ( in case you haven't read the last few pages ) so there's a build coming out every week.

Hope you can fix your device and use it again.
[HTC One A9] megatomic:
Yes!
[HTC One A9] :
Heh. Didn't know it was official now. Haven't been keeping up with Lineage well enough either it would seem.

But I had fun and I'm glad I helped for a while there.

And I'm not sure what to do with my device. I may fix it.

Anyway, Cheers guys! Hope to see you all around on XDA.