yashsingh1/xdaforums huggingface dataset:
[HTC One A9] Xtaner:
Status report from me to the following build:

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

Carrier: German Telekom

SU addon enabled

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:

- WLAN only working in 5 GHZ mode, no 2.4 GHZ mode.

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

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

- Decryption of /data with TWRP 3.1.1.0 still not working

[- 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:

- 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
[HTC One A9] Ultramanoid:
Should be reported in the TWRP for the A9 thread, not here. But I wouldn't hold my breath for a fix, at least until Nougat kernel source is released, maybe even then.

Edit : You don't mention WiFi, is this because it has been already reported or because it works for you ?

Edit 2 : WLAN and wireless changes in latest commits by intervigil, reverting some previous changes. Hopefully WiFi will be working in the next build.

https://review.lineageos.org/#/c/174701/

https://review.lineageos.org/174702/
[HTC One A9] Xtaner:
You've been right. Forgot about the not working 2.4 GHZ WLAN, thx.
[HTC One A9] jjakajonas:
Okay..

Passable fix for the "no auto find network" thing.

I had a SIM card pin on my SIM card.

I tried to deactivate it on my device but that resulted in my device got really messed up (could see my SIM card and all apps stopped working literally all my 130 apps stopped working) so I re-flashed my 05-09 lineage, gapps and magisk (still no pin on the SIM card at this point)

After first boot my device had LTE from my carrier (yousee, Denmark), second time I had to scan manuely, third and fourth time I got the carrier by it self on start up.

So maybe the pin code make some problems both in finding carrier at start up but also if you tinker whit the SIM card pin setting in settings?

But in other words the no pin code on SIM can maybe be a temp fix at the moment?
[HTC One A9] Matthew98405:
I enabled "require pin to start device", but after entering my pin on startup, my phone reboots. Wiped data and didn't re-enable. Anyone else have this issue?
[HTC One A9] Ultramanoid:
Don't think this affects the SIM issue, but please be aware that if you need support from Lineage for a problem, they have their own implementation of root, which is what they support :

https://download.lineageos.org/extras

If Magisk is breaking something or causing problems, that's not for Lineage to solve. First you should test with the native root option, if there is no problem with it, then it is not for Lineage to solve.
[HTC One A9] jjakajonas:
I think there's a misunderstanding.

My problem is not magisk related.

It was a passable fix for those (like my self there had to manually search for the carrier)

But a change of lineage setting (there's having absolutely nothing to do whit root) and that messed up my device so there's maybe a bug there..

That was all...

There's no problem whit magisk nor is there with google Pico apps.
[HTC One A9] Ultramanoid:
Yes, the first thing I wrote was that I didn't think it had anything to do with the SIM or network problem. But it could have a lot to do with reboots for instance, so keep it in mind when reporting bugs. They may not be Lineage bugs at all.

Many maintainers will write it in the OP when posting in XDA a Lineage build to make it absolutely clear, no support for kernel changes, Xposed, etc. To get support from Lineage, they will accept reports only from Lineage installations without additional hacks or alternative system parts, such as SuperSU, Magisk, etc.

The most recent SuperSU versions, 2.80 and 2.81 have broken a lot of systems, for instance.

It doesn't mean you cannot use mods or hacks, everyone is free to do what they want, but don't expect support or report bugs if the Lineage installation has been modified.
[HTC One A9] jjakajonas:
Yeah i know.

But when more than one have the same problem whit different configurations (here I talk about the network there seems to be a problem in Germany)

I took the task up my self to find a solution to it.

Yeah I have magisk but magisk do not have interactions whit settings.

Also after I removed the SIM card code the device finds network on its own at start up and that's whit the exact same configuration as before I removed the SIM card pin

Except that the pin code on the SIM is off...
[HTC One A9] J2ghz:
I unsuccessfully tried to flash Lineage OS, the 24/05 and 16/05 builds. I found this ^^ post, does that mean it will not work for me if I have 2.17.401.2?
[HTC One A9] Ultramanoid:
Correct, you need to downgrade to 1.5x firmware to use Lineage for now. Also, the last working build is the one from May 9th, later ones have a problem with WiFi.
[HTC One A9] J2ghz:
Do I understand it correctly that to downgrade I need S-OFF and at the moment no free options exist?

Edit: I should search more before posting: https://xdaforums.com/showpost.php?p=71627179&postcount=10

Edit2: Does not apply to downgrading nougat to marshmallow.
[HTC One A9] Matthew98405:
As the person who ditched Arch Linux for Ubuntu just because RetroArch didn't work well, I'm going back to stock just for Google Camera (and other bugs). The flashlight bug was the tipping point when it turned while I was holding my phone in public, and got in an argument because a woman thought I was trying to take a candid picture. Anyways, back to stock for a while.
[HTC One A9] ClearD:
Updated to version from today (30th) and can confirm after a dirty flash that wifi works again. :)
[HTC One A9] DeadlyByNite:
Yup, the newest build (lineage-14.1-20170509-nightly-hiaeul-signed.zip) has fixed the wifi bug, but the flashlight bug is still there. Hopefully it will be fixed soon, but not too big of a deal to me. Sometimes I can rotate when the flashlight is on, and then it turns off after tapping it one time in the quick settings, but sometimes, it completely freezes the phone, causing me to have to reboot by holding power+vol up.

Overall I think it's stable enough to use on my main device everyday.

The only problem I am having is a kernel wakelock mmc1_detect. Maybe the latest build will fix it. I have attached a screenshot of bbs overnight. Is anyone else having this issue? I think probably formating the memory card would probably fix the issue. haven't tried it yet.
[HTC One A9] mrspeccy:
Yes, wifi works fine again. I use a flashlight app from Play Store (https://play.google.com/store/apps/details?id=com.peacock.flashlight) to circumvent the bug with the built-in flashlight.
[HTC One A9] megatomic:
Guys, on the latest build (05302017) how is the camera? I've read through this thread and seen that there have been tons of issues with the camera, but there have been numerous commits of late to Lineage for Snap camera. My A9 is on the latest official ROM but I'd be willing to flash an old RUU to use this version of LOS if things are stable enough. Thanks for your opinions.
[HTC One A9] Dragonkind:
"Latest official ROM"

Android 7.0, right? Then you may not be able to use current LineageOS, unless you S-OFF and flash 6.0 RUU. Coz HTC hasn't released the hardware for 7.0, LineageOS can only support earlier firmware now.
[HTC One A9] Ultramanoid:
Seems like he already knows Lineage runs on 1.5x firmware until Nougat kernel source is released.

The question is how well does the camera work, Snap particularly. Can't speak about Snap as I don't have it, or social media applications that use camera function. But the open source third party cameras I use work well enough, both for stills and video. Image quality is not as good as it used to be on CM 13, but it's fine. Also no constant crashes or freezes as it used to happen on CM 14 and early Lineage.
[HTC One A9] megatomic:
Thanks for the feedback guys. I just wish HTC would hurry up and release the source code for the latest firmware so LOS maintainers could build for it. Maybe I'll just go ahead and flash an old RUU and use the current version of LOS, this way I can see how much the new firmware improved on the 1.5x version... But it will be just my luck that no sooner do I do that that HTC releases source code lol.
[HTC One A9] Ultramanoid:
Consider also that Lineage regularly merges Google's monthly security updates, which basically no OEM does, and running Android without the latest patches for vulnerabilities is really a terrible idea.
[HTC One A9] megatomic:
That is a plus, but HTC has been doing okay with updating the A9. It's got the April 2017 security updates currently. They missed May with the rollout of the U11 taking all their resources though.
[HTC One A9] mlecho:
I've no idea why i keep trying this without luck. Attached is my downgraded About info. Here's my fastboot vars:

(bootloader) kernel: lk
(bootloader) product: htc_hiaeul
(bootloader) version: 1.0
(bootloader) max-download-size: 1164800000
(bootloader) serialno: HT5B3BE06038
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: {hidden, because i don't know if i should make public?}
(bootloader) version-main: 1.57.617.60
(bootloader) boot-mode: download
(bootloader) version-baseband: 1.1.U40062.1@61214
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ912000
(bootloader) cid: BS_US001
all:
finished. total time: 0.003s

I am using twrp 3.1.1 . No matter how many times i try this , after flashing the lastest lineageos, i'm kicked back to the bootloader screen. And it will always boot back to that terrible rainbow font screen. My steps:

fastboot flash both boot/system 1.57.617.60

reboot to twrp

wipe -> Factory reset

NOTE: ( i have also tried Advanced-> (Dalvik,System,Cache,Data))

install -> lineage-14.1-20170530-nightly-hiaeul-signed.zip

reboot

....device boots back to bootloader....ugh!

Anyone have an idea what i've done wrong? It is my understanding i have to first be in 1.57.xxx before i can apply lineage. (Correct?)

Can i get logs or share anymore info to finally get things to flash? I can flash .img (boot,recovery, system) just fine, but zips are not playing fair.
[HTC One A9] megatomic:
I found the RUU I want to flash but I did read that the flash will fail due to the key not matching the one in the RUU so I need to flash a firmware first then I can flash the RUU. What I'd like to know is if I flash the firmware from Marshmallow days can I just then install TWRP and then flash LOS?

Also where do I get the firmware by itself?
[HTC One A9] Ultramanoid:
Check in the A9 RUU thread, should be there or linked. Also any questions about firmware probably the OP there can answer much better than any of us here.
[HTC One A9] megatomic:
In that thread it's stated that you have to download the firmware and flash it but I couldn't locate a reputable place to get a copy from. Reminds me of the old days downloading cracked software. :/
[HTC One A9] Ultramanoid:
I believe you can extract the firmware you need yourself :

https://xdaforums.com/showpost.php?p=72454691&postcount=927

Just ask alray, he's quite willing to help people in that thread.
[HTC One A9] megatomic:
I've exhausted my ability to search and have failed to flash back to Marshmallow. I've asked alray to help me in his thread. Hopefully I haven't made serious mistakes and look like too much of a noob. Working with the A9 is no where near as easy as the Oneplus One.
[HTC One A9] Ultramanoid:
hTC is quite a pain with firmware, after a few years with SONY devices ( unlock bootloader, done, flash whatever, any time ) even more so to me, but ironically that's because they update it. You can have the latest best ROM on a SONY, which is running on top of positively ancient firmware. In many cases developers are using blobs for camera or kernel from three Android versions back... Not sure which way of doing things is better.
[HTC One A9] megatomic:
Well I hope HTC releases the source code to the Nougat ROM soon, I semi-bricked my A9 and can't fix it. Hopefully alray can help me out. Ugh.
[HTC One A9] mlecho:
i've used the RUU extraction tool (https://xdaforums.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) and that's how i've reverted back to MM. Currently my device is using the boot/system from that tool. I wonder if that has to do with my loop issue...the mismatch key
[HTC One A9] Sympl3x:
Does anyone have any straight forward instructions on how to downgrade from Nougat HTC version 2.18.617 to 1.57.XX in order to install Lineage? I've searched around for the past hour but it is mostly confusing info I am getting.

From what I understood in the RUU collection thread I need to flash a 1.57.XX ROM first then run the 1.57.XX RUU? That would get me downgraded. I've tried, but it didn't work. Here's what I have attempted so far.

Flashing a 1.57.XX ROM and then running the 1.57.617.60RUU. The RUU failed to install. I am S-OFF and unlocked bootloader. Do I need to relock to run the RUU?

Any help is appreciated.
[HTC One A9] Ultramanoid:
Not a rom you need to flash, but firmware. hTC changed the key when releasing Nougat ( 2x ) firmware, so downgrading is not straightforward as there are different keys between 1.5x and 2x.

At any rate, this better be asked in the RUU thread. How to upgrade or downgrade firmware belongs there, and the OP can answer better than anyone here.
[HTC One A9] mlecho:
this thread (https://xdaforums.com/showpost.php?p=72043212&postcount=451) helped me out. You'll end up here: https://xdaforums.com/showpost.php?p=63640734&postcount=2. Since you are S-OFF, you hopefully won't have to alter partitions like i did. If so, make sure you know which partition is indeed your "/misc"... For me it was not mmcblk0p28 but rather mmcblk0p29 - which may explain my reboot issues since i did modify some bytes on mmcblk0p28.
[HTC One A9] Fudgehog:
Okay guys here is a quick and dirty guide to downgrade to marshmallow. I have the 1.57.617.60 firmware uploaded on my Media Fire.

1. Please make sure you are S-OFF, IT IS REQUIRED TO DOWNGRADE.

2. Bootloader unlocked, latest TWRP installed of course

3. I recommend doing a full wipe, while connected to your computer and with ADB connected.

4. Download my uploaded marshmallow firmware at https://www.mediafire.com/file/jc3jp4afacb01rv/1.57.617.60.zip.

5. Rename file to 2PQ9IMG.zip.

6. Move zip file to your SD card and reboot to download mode,

OR fastboot flash firmware.zip from ADB. It is recommended you use the universal ADB tool here on XDA to install ADB and move your firmware.zip file into the root folder of ADB, usually C:/adb/firmware.zip. Once inside root folder, hold shift and right click and "open command window here". Then whilst in download mode, simply fastboot flash firmware.zip.

7. Hit the volume up button to flash firmware. Watch it go through the motions.

8. Some phones require flashing firmware twice, to overwrite everything.

9. You now have MM firmware, use your RUU of choice to install stock sense ROM and update to latest firmware for your phone/carrier. THIS is important, also always make sure your MID and CID are correct. Always use BS_US001 rather than SuperCID or it will cause problems.

10. This is the exact process I did, now on 1.57.617.60 firmware after using the RUU.

11. Install Lineage Build of choice, 5-30 broke incoming calls for me. And due to the WiFi malfunctions, I went back to the 5-9-17 build.

TIPS: You can rename the latest TWRP to recovery_signed.img and after injecting it into the firmware zip using a program like 7Zip, flashing the firmware you will have TWRP immediately.

For example: https://www.mediafire.com/file/0l420t9d4604afs/1.57.617.60+-+with+TWRP.zip

IMPORTANT: AFTER FLASHING FIRMWARE you need 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 the one in my firmware package, then you're good to go. Wipe everything, THEN install Lineage.

Alray has 1.56.401.70 DECRYPTED Firmware posted on androidfilehost linked here.

https://www.androidfilehost.com/?fid=817550096634758247

P.S. Ultramanoid, I may not be a top developer or OP of a thread, but I can teach people how to flash firmware. It is still related to flashing Lineage, and hopefully this will STOP some of the rhetorical repeating questions.

Hopefully I helped, and as always, have nice day.
[HTC One A9] megatomic:
[MENTION=6575890]Fudgehog[/MENTION], when I tried to download your file I got a 135KB file not a full firmware. Not sure what is up there, using a Win7 computer and Chrome browser. The file from [MENTION=4654136]alray[/MENTION] did download properly but when I went to install it the install failed due to the file being for another version of the A9. Mine is the US unlocked version. Thanks for trying to help me.
[HTC One A9] Fudgehog:
That's odd it is clearly 71MB. Very strange. Perhaps try a different browser? I'm not sure what to tell you, it's definitely not KB lol. And no problem bud, I had to figure it out myself by searching several forums and if someone can come across virtually a single post that answers all their questions, that's the needle in the haystack, literally.

Just tried downloading from my A9 and it easily got past 20MB. (then I canceled)
[HTC One A9] megatomic:
Maybe it was my antivirus program. I downloaded it with another computer but when I went to install it the install failed. Said the header failed.

On a side note, I found a zip file on Captain_Throwback's filehost called HIAE_DEV_EDITION_1.55.617.4_ROOTED_CPTB-odex.zip and it was installable by TWRP. My phone just booted up that OS. I wonder if I can now run an official RUU and get my phone back to normal? I always seem to get the dreaded USB connection error when I run the RUU.exe file even though I can browse the phone with Windows just fine.
[HTC One A9] Fudgehog:
Yes run the 1.57.617.60 RUU. However, even if it installed it did NOT change your firmware. So if you installed it on top of 2.1.617.xxx firmware, that is not correct. It's like putting duck tape over the hole in the boat.

Header failed after complete wipe like I instructed? Did you reboot to bootloader, back to download, and try again?

And yes, I agree. RUUs can be very tricky to be successful, however if on 2.xxx firmware it will not update the firmware whatsoever.
[HTC One A9] megatomic:
Yes, I did. And when you asked if I had done exactly as you instructed I tried it twice more. The exact Error is FAIL22 RU_HEADER_ERROR.

This just sucks. I hope LOS on the A9 winds up being worth all this heartache. :p
[HTC One A9] Fudgehog:
If I didn't want to start all over, I would reflash that firmware right now to make sure it works. Its the same file I have stored on my SD card, along with my N firmware zip. So I find that odd. I guess all you can do is keep searching for the firmware, or maybe I can extract the 1.57.617.60 for you. I'll give it a try.
[HTC One A9] megatomic:
I sure appreciate all your effort to help me.
[HTC One A9] Fudgehog:
No problem, I'm extracting the 1.57.617.60 firmware as we speak. It will be live in a couple minutes.

---------- Post added at 03:49 AM ---------- Previous post was at 03:35 AM ----------

Okay bud, the decrypt tool successfully secreted the firmware and I have uploaded it to my Media Fire, let me know if it works. Hopefully it does. This one is 129MB.

https://www.mediafire.com/file/mshm3jaf9lgia1h/1.57.617.60-firmware.zip
[HTC One A9] alray:
Looks like he was able to flash the firmware he already had on his computer using fastboot instead of the sdcard. I'm leaving for today, he might still need help to install LOS and everything else if you're still around. Thanks for your help :good:
[HTC One A9] Fudgehog:
Interesting, weird how it doesn't work with the SD card. No problem Alray, I don't mind helping when it's something I can do.
[HTC One A9] megatomic:
I've almost got it. LOS and OpenGapps installed but it sits at the boot logo "building" forever. I did notice that when I wiped the system after successfully flashing the firmware that it said it failed to mount /carrier. There must be a problem yet. I'll reflash the firmware tomorrow with the file you extracted [MENTION=6575890]Fudgehog[/MENTION] and then try to install LOS and OpenGapps and see what happens. I must be close now.
[HTC One A9] Fudgehog:
Listen bud! Before you install GAPPS do a format data in TWRP after you installed Lineage. Boot to bootloader then to recovery, and you will find data decrypted and TWRP working in full capacity. Then install GAPPS and you are good to go bud. Personally, I always wipe dalvik, cache, system, data, and internal before a new install. But a format data is needed to remove encryption.

And yes you are close of course.
[HTC One A9] megatomic:
Does anyone know if the fact that I get errors when I wipe data saying that it failed to mount /carrier is a real problem or not? Maybe I am chasing a non-issue.
[HTC One A9] mlecho:
has to be S-OFF?
[HTC One A9] Sympl3x:
I believe the firmware posted by Fudgehog in step 4 is corrupted. I kept getting the same HEADER_ERROR when trying to install. I was able to get it to succeed by using the firmware he posted later from 1.57.617.60, although I had to fix the folder structure. It was one folder too deep in the zip. After fixing that and renaming it to 2PQ9IMG.zip and copying it to the SD card it flashed everything just fine.

Now it looks like I am at the never ending boot logo. I flashed the latest TWRP, booted to recovery, completely wiped everything and installed LOS. Then formatted data, rebooted to bootloader, back to recovery, then installed latest GApps.

Any ideas?

---------- Post added at 02:55 PM ---------- Previous post was at 02:55 PM ----------

I am also getting this error. Not sure if it is a problem or not.
[HTC One A9] megatomic:
I'm not happy that you are having trouble also but you are in exactly the same predicament as I am. My A9 has been at the animated boot logo since 8:15 AM today, it's now 4:02 PM. The only difference this time is that I only flashed LOS, no Gapps to potentially confuse the situation.
[HTC One A9] Sympl3x:
Stand by. I think I got it working. I had to go back to an old unofficial TWRP that I remembered having to use for another ROM that gave me the same never ending boot logo issues. I successfully booted LOS. Now I and wiping and reinstalling with GApps right now. If that boots I'll post up a link to the TWRP I used.

---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------

Also, it no longer has the mount /carrier issue with this version of TWRP.
[HTC One A9] megatomic:
Awesome. Did using the old version of TWRP also correct the error about not mounting the /carrier partition?
[HTC One A9] Sympl3x:
Yep, just updated my post to say that lol.

---------- Post added at 04:28 PM ---------- Previous post was at 04:14 PM ----------

Alright, I think we are all good. Lineage with GApps is booted! I've attached the recovery I used "twrp-3.0.3-5_CPTB-TEST2-hiae.img". Flash that recovery, boot to TWRP, FORMAT data not just wipe, reboot to bootloader, reboot back to recovery, wipe data/factory reset, flash Lineage OS zip followed by GApps, wipe cache/dalvik and reboot.

This is what finally worked for me at least. Best of luck!

Recovery Link: http://www.mediafire.com/file/uk16acdl37a81s7/twrp-3.0.3-5_CPTB-TEST2-hiae.img