yashsingh1/xdaforums huggingface dataset:
[HTC One A9] joemossjr:
Seems like the camcorder I'd somewhat fixed whenever I send someone a video on Snapchat it sounds fine but when. I listen on my phone its really low. And Facebook messenger I can't hear the other person talking but they can hear me
[HTC One A9] hedgehogmd:
All i did was go to play store install Busybox.

click on Busybox in app drawer then click on red x then click install then click red x then back button twice that was it. i then uninstalled the busybox app

Root Explorer works great hope this helps.
[HTC One A9] scott8281:
The first two apps I tried didn't work. The third did. Thanks man
[HTC One A9] scott8281:
Is anyone else using a Mac? I haven't had any luck getting Android file transfer to work.
[HTC One A9] AntikerTa:
Yes, me too. With Stock Rom no Problem. With CM13 AFT does not work. In Recovery Mode it does work. But only in Recovery Mode.
[HTC One A9] JochenP:
Also on stock it fails for me. I use virtual windows mashine instead
[HTC One A9] Tikerz:
I can't access storage in Windows either.
[HTC One A9] Tikerz:
Darn, I thought the sound would be fixed with today's nightly since there were commits for the sound amplifier. Still doesn't work in some apps/games.
[HTC One A9] loner.:
Then it may be a hardware problem, like a weak circuit, chip, or faulty circuit connection.

Sometimes the mic on my zenpad will not work until I reboot...
[HTC One A9] intervigil:
HTC never released kernel source code for 1.27.xxx.y or 1.57.617.x (just 1.56.770, which I'm unsure about), and I haven't been able to figure out how to make the modem initialize with any firmware/kernel past 1.55.xxx.
[HTC One A9] rouyal:
Has anyone contacted HTC about releasing the source, or are they refusing to? You'd think they wouldn't have a problem with it seeing as how they label the unlocked version as a dev device. I did send them an email a few days ago about the situation.
[HTC One A9] theNdroid:
It isn't. It works fine on stock. I've gone to CM and back to stock 3 times now. Same results every time.

---------- Post added August 29th, 2016 at 12:07 AM ---------- Previous post was August 28th, 2016 at 11:56 PM ----------

Does ignoring my comment mean there's no fix for the microphone issue? I don't mean to be a pest but I don't want to continue reporting an issue that can't be fixed. Some closure would be nice. I mean that in the most respectful way possible. I'm willing to post any logcats that need to be posted. I really want this mic to work, lol. Sorry again if I'm being annoying.
[HTC One A9] intervigil:
I don't know what your issue is.
[HTC One A9] theNdroid:
The microphone is staticy when recording and background noise overpowers the sound of who or what you're trying to record. I have to get extremely close to the microphone (nearly holding it to my mouth) to record audio clearly. It's especially annoying when recording video selfies. I can't hear anything I'm saying in the video. I either sound extremely far away or I'm overpowered by background noise. Initially I thought it was a hardware issue, but when I went back to stock everything was fine. I've trouble shot with and without xposed and root , but nothing seems to get it functioning normally.
[HTC One A9] intervigil:
Is this when using the camcorder?
[HTC One A9] theNdroid:
Yes when using the camcorder through any application ; CM Camera, Google Camera, Snapchat, Instagram, etc.

EDIT: I found an LG G2 thread of people reporting the same issue http://xdaforums.com/lg-g2/help/low-mic-volume-crdroid-cm13-marshmallow-t3270054
[HTC One A9] intervigil:
I can check it, but I think we're using the same audio config as stock...
[HTC One A9] theNdroid:
I was reading on some other threads reporting the same issues that overly aggressive noise-suppression algorithms may be the cause. LG G2 had an issue where the mixer levels were at 64 and then the mic worked normally at 82 but I checked my device's mixer and it was already at 82. I'll see if I can find any other useful information but I'm glad I was able to report the issue to you directly. Thank You in advance.
[HTC One A9] loner.:
Does anyone have any ideas on how to deal with the "forced encryption" that was put in the nightly on the 26th? The nightly that came out the 24th may be the last one I can use, unless there is some kind of fix that will let twrp mount the partitions.
[HTC One A9] theNdroid:
Another thing [MENTION=1815755]intervigil[/MENTION]. Is it possible to enable wi-fi calling? I know that the Nexus 6 has it so I'm assuming that it should be able to work for this device too especially since it works with the stock rom. Thanks again.
[HTC One A9] intervigil:
Possible yes, likely no. It's on my list of things to look into, but it seems like new blobs are required, and getting everything else working with said blobs is proving difficult.
[HTC One A9] Maribou:
Does anyone have a link to the nightly for hiaeul that released on the 22nd or 24th? I can't seem to find a link for them.
[HTC One A9] scott8281:
Has anyone had trouble updating since the forced encryption. I'd like to try or more recent build but once I flash an encrypted nightly it won't boot to twrp recovery. It will boot to an older version of twrp but it still fails when writing to memory.
[HTC One A9] RomyRodriguez:
Can i install this on sprint variant? Thanks
[HTC One A9] ValdOr7:
My A9 heat too much on everything (movie, game, charging) and with the last modif on forced encryption i cant do nothing on twrp. Cant flash exposed cause of i cant access to internal memory due to the forced encryption . So cm13 dont be usefull anymore :/ . Anyone solved this ? :confused::rolleyes:
[HTC One A9] scott8281:
I haven't had any problem with overheating. But I would really like to see a workable solution to the forced encryption. I can tell you that if you flash twrp 3.0.1 (one version back) your phone will boot into recovery and you can restore a back up. However with the most recent twrp 3.0.2 it won't even boot recovery. You get the splash screen and then the phone reboots. Cm recovery will boot but it's useless (can't even do a backup).

I went back to the 8/13 nightly and will stay there until they sort this cluster**** out. But as it stands right now, if a person has the latest twrp and flashes anything after 8/26 it's the last update they'll ever be able flash without downgrading the recovery and either restoring a back up or wiping phone and data and removing the encryption and flashing an update and repeating the process all over again for the next update they want to flash.

Needless to say it's a massive pain in the ass.
[HTC One A9] loner.:
I had troubles at first, and just went back to a earlier backup.

Then instead of using the first nightly to force encryption (20160826) I used 20160828 and then tried to boot to twrp recovery.

The phone locked up on the twrp splash screen and I couldn't power off or reboot. I then hooked up to my pc and used ADB to reboot the phone and the rebooted into twrp recovery and twrp ask for a password to decrypt the data on phone and since I don't have a password for that, I just hit the cancel button and go into the twrp menu. Phone works very well and I updated to 20160904 and all works as long as I hit the cancel decrypt button when I boot into twrp recovery. With every new nightly I think its getting better.

I use the latest twrp 3.0.2-0.
[HTC One A9] theNdroid:
If you have an SD card you can access your SD card, via Android File Transfer, from TWRP 3.0.2 if you enable MTP in "Mount".
[HTC One A9] scott8281:
I noticed that. But the main problem is that once the phone is encrypted, any nightly downloaded won't flash because twrp can't write to the phone. Is this fixed on any of the more recent builds ? 9/1 is the last nightly I attempted to flash. It wouldn't even let me boot into twrp 3.0.2. I ended up having to boot into download mode and flash 3.0.1 and it booted but still wouldn't allow a ROM flash so I ended up wiping everything and reinstalling the 8/13 nightly
[HTC One A9] Ultramanoid:
Getting an "error: 6" with the latest nightly ( September 5th ) on TWRP, and no way to flash it so far. Searched but can't find anything meaningful regarding this error. Anybody knows what it refers to ? Here's hoping it's just something wrong with the build and the next one is fine.

For all those wanting to disable encryption, there's a boot patcher zip in the TWRP thread for the HTC A9 that will do that, flash it after flashing the nightly and before rebooting, but do read the FAQ first.
[HTC One A9] theNdroid:
I downloaded the nightly on my laptop and transferred it to my SD card via TWRP MTP,I was able to upgrade from 8/26 to 9/1 that way.
[HTC One A9] scott8281:
Thanks man. I had that boot patcher in the folder I keep my a9 files in on my computer and haven't even thought of using it since I flashed the first ROM. I felt stupid after I downloaded it and went to drag it in the folder and seen the first one I downloaded [emoji39]
[HTC One A9] loner.:
I believe "error: 6" is just a error in the updater script.

http://xdaforums.com/showthread.php?t=3328958
[HTC One A9] Ultramanoid:
Thanks. I haven't touched the updater script myself, whatever they changed is still broken in today's build, another error 6. My device is not encrypted, and wiping it all doesn't help. Not good, anybody been able to use these last two builds ?

I see there were several kernel commits and the size of the build went up by about 30 MB which seems remarkable.

Edit : wonder if this has anything to do with it, which would mean updating firmware is needed, I guess.

https://review.cyanogenmod.org/#/c/159964
[HTC One A9] loner.:
They probably don't even know the updated script is in need of repair. They should check-in with this forum once in a while.
[HTC One A9] scott8281:
I know the newer firmware was needed to flash the 6.0.1 sense ROM. There's a flashable zip for it. But I'm on att and s-on. If I remember correctly flashing the firmware requires s-off?
[HTC One A9] Ultramanoid:
S-on here too, and nowhere near a laptop to start messing with firmware myself now, and won't be for a while.

But, I have the results of fastboot getvar all from the device saved with me, and seeing there is a list here ...

http://xdaforums.com/one-a9/general/wip-ruu-htc-one-a9-t3240344

... As I understand it, if the firmware corresponds to the device / region, even with S-on, updating to a newer version should be just fine ? Hope someone can confirm.

Edit : Yes, it seems updating is not a problem with S-on, as long as : "The RUU must match your phone MID, CID and Version-main to be flashed", and downgrading is not possible afterwards without S-off.
[HTC One A9] scott8281:
I figured that was the case. The is the first HTC I've had since the One X so I'm relearning quite a bit. S-on is an HTC thing. I'd like to read up on it some more. I don't remember any previous phone I've ran Cyanogenmod on dependent on a firmware update (with regards to updating CM). I maybe be mistaken. I would think their wound be a work around. Even Nexus phones have security enabled (s-on for lack of a better term) but it has no bearing on flashing the partitions people like us are interested in for installing a ROM. Hopefully this can be the case for HTC as well.
[HTC One A9] Ultramanoid:
My last HTC was the Sensation, imagine that. All this S-on-off is a bit silly. Wish they did what SONY does, OEM unlock, forget about it from then on, install, modify, whatever.

So, just to confirm, I've gone ahead, downloaded a hefty 1.8 GB RUU, put it in an SD, updated, and voila, from 1.10 something I'm up to 1.56 something. How wonderful that a device I bought completely new a couple of weeks ago came with the firmware from October of 2015. Sigh.

Everything working just fine. Except that I'm running a stock Sense rom for which I have no use whatsoever, now to restore my backup with TWRP and check if the latest CM wants to install.

I've seen there are some commits already for CM 14, so that's good too.

Edit : Well, I'm remembering why I stopped using HTC devices now... While the 6.0.1 Sense rom works, it's useless for me. Restoring a backup or trying to reinstall CM 13 just gets the device into a bootloop on firmware 1.56* ( as mentioned several times in the thread, but I had hoped it was a past issue already solved, well -- no. ), so now it's back to downgrading to 1.27* if I can, which is going to be fun, and yet Ethan Chen comments on that commit that 1.27* might be blacklisted as well, so what the hell ?

If using a newer firmware, CM can't be installed. If using an older one, maybe soon it will be the same. I don't get the logic here. Why build CM at all for this device then ?

And checking the updater script in the last build for A9, there's a line checking for HIMA, which is another device entirely ( the M9 ), no wonder installation spits an error.

Ah, well.
[HTC One A9] intervigil:
HTC updated firmware (RPM/TZ/SBL1) around 1.55 or 1.56, which is why CM was unable to boot on any firmware past 1.27 previously. There's a fundamental incompatibility with the HTC 3.10.73-based kernels (which CM was, prior to a few days ago) and firmware found in 1.55/1.56/1.57. It wasn't until relatively recently that HTC bothered to post kernel code for the 3.10.84 kernel they used in 1.55/1.56/1.57. That kernel requires the newer firmware, or it too won't boot. I recently updated the kernel to one based off HTC's 3.10.84, so recovery asserts were added. They will prevent installation on anything with a ~1.12 firmware version since firmware < 1.55 will not boot (I'm unsure about 1.27, I know 1.10 and 1.12 won't).

EDIT: WARNING: do not upgrade firmware (ie. flash a firmware.zip file) from 1.10 or 1.12 directly to 1.57 if you are s-on, you may render HTC's download mode (HOSD) inoperable.
[HTC One A9] theNdroid:
So basically 1.55+ is the required firmware moving forward?
[HTC One A9] loner.:
I tried to flash the 20160907 nightly and now receiving a "error: 7" instead of the "error: 6". ?
[HTC One A9] jupppo:
Wouldnt it be enough to flash the latest vendor.img withe twrp before upgrading?e
[HTC One A9] Ultramanoid:
Thank you for the explanation, it all makes sense, no pun intended, at least a bit more. So I guess downgrading from 1.56 to 1.27 is not such a good idea anymore.

Same here :

Checking for SBL1 version 0.0.020.1.50
assert failed: hiae.verify_sbl1("0.0.020.1.50") == "
Updater process ended with ERROR: 7

Backup before kernel change goes into boot loop and the newer builds can't be installed, so this little soldier is taking a drawer break after only two weeks of service.. A new record.

(^_^.)
[HTC One A9] Ultramanoid:
Turns out there's no need for S-off to downgrade either, just adb and a laptop needed and I finally got near one so I just downgraded and restored the backup I had. Fully functional again as long as CM build is any before September 5th, when the kernel was changed to the new one.

Went back from 1.56 to 1.27 just to check if the latest builds will install on 1.27 and as expected they don't. So basically, whatever the kernel or firmware, seems like right now the last CM usable build for the A9 is the one from September 4th.
[HTC One A9] scott8281:
Yea. I'm on 1.27 and have been since I first got the phone. I could have saved you some time [emoji39] . But I've been running cm since the January builds and Att has never updated the a9 so I've stayed on the same firmware. You should be able to go up or down while s-on as long as its firmware made for att. S-off is only required to flash ruus that are for other a9s (which would come in handy with the new kernel). As it stands now the only option is to pay for sunshine or wait on an att update. I would say sunshine is a safer bet. Att may not update the phone until Android 7 and I'm sure that will take a while. A 6.0.1 update is possible. But I'm not holding my breath with att
[HTC One A9] djsubtronic:
I'm currently on the 21/08 nightly before the force-encrypt was enabled and I'm quite keen to update given all the recent changes and improvements, however I don't want encryption. I read above someone was able to restore a backup/decrypt and then skip a few nightlies and managed to get an unencrypted version of a new build. I'm currently on firmware 1.27.707.5 and I understand I need to update this in order to use the newer nightlies.

Does anyone have a set of simple instructions how I can get to the latest nightly from where I am now and avoid the encryption?
[HTC One A9] Ultramanoid:
Thanks, I don't mind testing and messing with it. Just got it new sim-free unlocked for use in Asia, shamefully it came with 1.10.

Yes, good luck waiting on a carrier's whim ! I haven't bought a device from a carrier or run a stock rom and not my own... Well, ever, I guess.

Hope I can keep using it and not have it locked down already by firmware / kernel issues. The new CM builds won't flash on any firmware apparently right now. I haven't tried 1.57 but if they don't work in 1.56..
[HTC One A9] scott8281:
With firmware 1.27 the 9/4 nightly is the most recent you can go due to kernel changes. To avoid encryption you'll need to flash the boot patcher after you flash the 9/4 nightly. Here's the link http://xdaforums.com/devdb/project/dl/?id=15348

So basically -

1. download the 9/4 nightly the and boot patcher

2. Boot into recovery and make a back up

3. Flash the 9/4 nightly

4. Flash the boot patcher

5. Reboot

6. Profit
[HTC One A9] djsubtronic:
Thanks dude I will try this tonight and see how it goes. After I do that should I be able to update the firmware and flash the newer nightlies as well (without having to repatch or deal with encryption etc)?
[HTC One A9] scott8281:
If your firmware is 1.27 the 9/4 build is the most recent build you flash. Anything past 9/4 will require 1.57 due to kernel incompatibility on the builds after 9/4 (which if you're on att will require s off).

As far the encryption, you'll need to flash the boot patcher on every build after 8/25 or 8/26 (one of the two) because after that encryption is forced and the boot patcher has to be flashed after the build is flashed.
[HTC One A9] loner.:
Is there a easy way to turn S-off?
[HTC One A9] scott8281:
Sunshine will S-off your phone with a download of the apk and a click. But it's $25. If there's a free way to do it I'm unaware of it. Someone else may know of a way.
[HTC One A9] theNdroid:
Can anybody confirm boot on 9/5+ with 1.57 firmware?
[HTC One A9] loner.:
So if I use sunshine and turn s-off can I flash the new nightly or do I have to flash the 1.57 firmware first?
[HTC One A9] scott8281:
S-off is needed to flash the newer firmware of your on att and the newer firmware is needed to flash any nightly past 9/4 due to kernel compatibility.

S-on would be fine if you had an unlocked a9 because they've received updates. It would be fine on a carrier branded device as well as long as the carrier had updated the firmware. Unfortunately att hasn't. I'm not sure about any other US carriers.
[HTC One A9] ValdOr7:
Ok i had a Hiaeuhl version (euro) so i'm S-on.Can i flash the latest nightly ?or good bye CM13 ? (i dont pay 25$ fo this **** :) )
[HTC One A9] scott8281:
To clarify-

S-on/S-off has nothing to do with flashing a custom ROM.

The problem with the a9 right now is that the newer builds of CM have the kernel that's only compatible with later firmware versions.

Long story short, boot into download mode and check the firmware version. If it's below 1.57 you'll need to update your phone with a newer version. This is possible without s-off as long as the firmware is for your device.

---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------

Here's a great article by Koush explaining S-on/S-off

http://www.koushikdutta.com/post/soff
[HTC One A9] ValdOr7:
yes it's what i think but to update the firmware we need to back to stock and ota or flash the RUU i'm right ? if i'm back to stock it's ridiculous to return on cm13 :eek:
[HTC One A9] scott8281:
You can update the firmware by itself but their are exceptions and I wouldn't risk it. Honestly it's not that bad to flash the ruu. The bootloader is already unlocked so you'll just -

1. Flash Ruu

2. Put cm and Gapps on SD

3. Boot into download mode

4. Flash recovery

5. Wipe/Factory reset

6. Flash CM and Gapps and boot patcher (if you don't want encryption).
[HTC One A9] rouyal:
Just to clear things up... CM13 is now compatible with the latest stock firmware (I'm on 1.57). The only thing need to do is flash TWRP, and flash CM13. No downgrading needed anymore (actually people need to now upgrade the stock firmware).

This sound about right?
[HTC One A9] scott8281:
Correct
[HTC One A9] Ultramanoid:
So it works with 1.57, but is that then the new minimum going forward ? I thought 1.55 and 1.56 were fine too, but I couldn't get latest builds to flash on 1.56.
[HTC One A9] rouyal:
Yup. I'm stuck. I was on 1.57 and getting error 7. I formatted and wiped everything several times (except sd card).

Is there a stock recovery laying around somewhere that I can flash over TWRP so I can do a factory reset, trying to avoid having to download and run the .exe tool from HTC again. I should've just booted twrp instead of flashing it. Oh well. After I get it back to stock, I think I'm done trying to mess with this phone. I have a OP3 going to be here in next few days.
[HTC One A9] Ultramanoid:
Thanks for the confirmation of troubled upgrading, and sorry that it's such a mess. If there is a corresponding zip for your device in the RUU thread you could just put the zip in an sd card and boot to download mode to let it get you back to stock.

I guess many of us are now stuck on 1.27 with a working September 4th build until the recent builds can be reliably flashed on 1.5x...
[HTC One A9] Ultramanoid:
By the way, it seems forced encryption was reverted a few days ago :

https://review.cyanogenmod.org/#/c/159411/
[HTC One A9] rouyal:
It might just be me or my phone, so maybe it would work for someone else. I just went ahead and downloaded the RUU exe from HTC and it actually completed with no errors. Last few times I tried to use it, it wouldn't complete. I hope someone else can either confirm that flashing latest CM13 does or doesn't work (with latest firmware), so I know if it's something on my end.
[HTC One A9] djsubtronic:
Sweet!

Edit: doesn't look like it's merged though.
[HTC One A9] Ultramanoid:
Nobody has been able to use the new kernel builds as yet then ?

So they won't boot on pre-1.5x firmware ( which is expected ) but also give error 7 on 1.5x firmware.
[HTC One A9] RomyRodriguez:
i got it to boot on my second attempt, i just modified the script and remove everything related to verification to install, such as the variant of the device.
[HTC One A9] Ultramanoid:
I've been ｔｅｍｐｔｅｄ to do that for a couple of days... Which firmware are you on ?

Edit : I'm guessing removing...

assert(hiae.verify_sbl1("0.0.020.1.50") == "1");
assert(hiae.verify_trustzone("TZ.BF.3.0-00624") == "1");

... Should do the trick. ( ゜- ゜ ')
[HTC One A9] RomyRodriguez:
1.57 the thing is that there is a problem with the script, and it doesn't have a version specified for the file to be flashed, so it just shows an error
[HTC One A9] loner.:
I have to ask why don't they offer two ROMS, one build that continues with the AT&T 1.27.xx based kernel like they started with and the other with the Sprint? 1.57.xx based kernel they have now?

My at&t HTC one a9 was unlocked, s-on, rooted and ran well with this Rom until they changed the kernel for some reason. Now I can't flash the nightly updates. So I used the sunshine app and turned s-off but I haven't been able to find answers yet on exactly what to do with s-off to change the MIDI, and CID or decide even if I should.

Hopefully someone may take pity on us noobs and direct us to the proper guideline. Yes this is my first HTC.