yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] badbwoydes:
Hi,

I remember doing method 2 over a year ago, with help from skulldreamz and xunholyx (http://xdaforums.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048/page119) to flash the necessary firmware for Sense Android L ROMs to work. I now wish to try out the Android M ROMs with Sense 8. I don't know if it's because i've been away for such a long time, but I feel completely lost, even after reading the OP multiple times.

What I gathered so far is:

1. Download the firmware "M8_6.20.502.5_ATT_FullStock.zip" from https://www.androidfilehost.com/?fid=24533103863142760

2. Rename that file to "0P6BIMG.zip" then copy it to my Removable SD Card

3. Restart phone to Bootloader to get prompt to start update

4. Update TWRP to v3 then flash any Sense Android MM ROMs

I have an AT&T One M8 running ViperOneM8 4.6 and ElementalX 4.05

What have I gotten wrong so far guys? I appreciate any assistance. The fear I have of killing my phone because of this is insane.
[One (M8) Android Development] enewman17:
Your on the right track... since your already using the international firmware might as well continue to use that, 6.12.401.4

Only reason I suggest that is some users have reported issues with calls and messaging while connected to LTE. Hard to find a changelog but I think ATT added VoLTE and updates to the radio.img might have adverse effects with ROMs not based on the ATT build 6.20.502.5
[One (M8) Android Development] Sneakyghost:
Yup. Just flash international update. I see no reason to convert to AT&T.
[One (M8) Android Development] tyfoxx:
Thanks
[One (M8) Android Development] badbwoydes:
Okay, on the firmware page I think I see what you're referring to, with the matching carriers/region in the last column. I currently have 4.16.401.10 International firmware so it's best if I get https://www.androidfilehost.com/?fid=24369303960687118 then rename "M8_6.12.401.4_WWE_FullStock.zip" to "0P6BIMG.zip", copy to memory card and flash. (I want the Full Wipe Zip so I can start completely fresh with a new ROM).

Once that's done, I can fastboot flash TWRP 3.0.2.0 from http://xdaforums.com/showthread.php?t=2717932 and finally flash an Android M ROM. That's it?
[One (M8) Android Development] enewman17:
You got it. :good:
[One (M8) Android Development] zolika1:
Does the same procedure if you want to 6.12. downgrade to firmware 4.16?
[One (M8) Android Development] Einwod:
It's only possible to downgrade if you have S-OFF. Though why you would want to downgrade, I have no idea.
[One (M8) Android Development] zolika1:
Why go back to the old firmware because people write on forums ported to HTC 10 rom much longer lasting battery than with MM firmware
[One (M8) Android Development] Einwod:
4.16 firmware is Lollipop, not MM.
[One (M8) Android Development] zolika1:
http://xdaforums.com/htc-one-m8/development/romthe-worlds-first100-m9-port-m8upload-t3064838/page991
[One (M8) Android Development] badbwoydes:
Okay, so I just tried it, but it said it failed and to press power to reboot. Thankfully it did reboot but it got stuck on the splash screen for my ROM. Doesn't look like it wiped anything as it was supposed to. Not sure what to do from here :|

Nothing happened after 10 mins so I did a force restart to Bootloader. OS is not is red. It shows my old OS version with the new one I was trying to flash in parentheses. Also. I no longer see the red text on the splash screen when the phone is trying to boot.
[One (M8) Android Development] enewman17:
Ok so what probably happened is your cid isn't listed in the android-info.txt in firmware zip. Here is what is listed in the zip...

modelid: 0P6B10000

cidnum: HTC__001

cidnum: HTC__J15

cidnum: HTC__E11

cidnum: HTC__203

cidnum: HTC__102

cidnum: HTC__405

cidnum: HTC__A07

cidnum: HTC__304

cidnum: HTC__032

cidnum: HTC__016

cidnum: HTC__M27

cidnum: HTC__K18

cidnum: HTC__002

cidnum: HTC__A48

cidnum: HTC__Y13

mainver: 6.12.401.4

btype:1

aareport:1

DelCache:1

DelFrp:1

DelCarrier:1

hbootpreupdate:3

Without reading back you had super cid??? 11111111
[One (M8) Android Development] badbwoydes:
I appreciate it, but I went back into TWRP, did a complete wipe of everything, reboot to Bootloader and flashed the firmware again and it was successful. Installed the S.Team M8 ROM and omg it is fast and smooooth. Thanks for all the help.
[One (M8) Android Development] Sneakyghost:
SuperCID never needs to be added to android-info.

It's either or.

Either you modify android-info or you use superCID...

Just in case that wasn't clear.
[One (M8) Android Development] jasio2k:
quick question

Hi

I have a stupid question :) Can I Flash AT&T 6.20.502.5 fw [2016.05.22] on europe version of phone ? (bootloader is unlocked)
[One (M8) Android Development] Sneakyghost:
Sure you can, but why on earth would you do that? Moving to the U.S. and getting AT&T as provider?
[One (M8) Android Development] jasio2k:
I got problem with the signal all the time, I think it is was good idea to upgrade to new fw. thanks for help
[One (M8) Android Development] theDude42:
so, I have a problem. I've tried a bunch of stuff, but can't seem to get it to work.

I have an S-off m8 (att). I have old firmware and need to update.

I've tried the RUU (i'm willing to go stock, then reflash), but it won't run. It always says my battery is too low, even when it is 100%.

I've tried the htc_fastboot firmware.zip method above, but when I go to htc_fastboot flash zip firmware.zip, it never finishes sending. Just hangs.

I've tried: different computers. Different usb ports. Nothing works.

Any ideas? I have the latest TWRP, but have actually lost root (due to having to reflash Cyanogen mod because I screwed something up) and haven't bothered putting it back on yet.

Frankly, I'd probably be happy with stock if I could get it to work.

results of getvar all:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 4.0.U605611@50319A

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: XXXXXXXXXXXX

(bootloader) imei: XXXXXXXXXXXXXXXX

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B12000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV NOTE: is this always zero?

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 205bdca3

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0
[One (M8) Android Development] Sneakyghost:
That error is weird. CM and root have no influence on firmware.

Please look at the output of the command "fastboot getvar all" and take note of the firmware version listed there.

Try to flash the RUU that has that exact version number. You might need to hunt that down, not sure but check androidruu.com - it might be there.

Got no better idea right now. About to go to sleep as well.

Have you also tried different cable? Those go bad rather quick...
[One (M8) Android Development] mrrocketdog:
along with Sneakyghost's idea , but have you tried with it plugged up to charger since always says "battery too low" ? prob. a dumb idea or may have already tried. just reaching.

"err on the side of kindness"
[One (M8) Android Development] theDude42:
so, answering questions:

(bootloader) version-baseband: 4.0.U605611@50319A

is that the "firmware version" # I'm supposed to match? Sorry, In the past, I have always just gone back to stock, taken the RUU , then flashed to CM.

Yes, I've tried different cables, etc.

So, I'm sorry, but I went to the site you showed me and honestly? I was a little overwhelmed. I wasnt sure what version #s I should be matching....?
[One (M8) Android Development] xunholyx:
You want to look at version-main. That's your current firmware. It will look like x.xx.xxx.x The numbers you want to match up are the bold ones in red.

EDIT: From your baseband version, it looks like you'll want to find the 4.28.502.1 RUU
[One (M8) Android Development] theDude42:
tried that with 4 different cables. No dice. Always battery too low. I'm at 100%.

Is it curious that you tell me to look at version-main in the "getvar" command output, but in mine it is empty?
[One (M8) Android Development] TharakaKS:
I newly brought a T Mobile 32GB M8. and i need your help guys.

1. Can I flash/install Unlocked RUU on this? or Do I need to flash the T Mobile RUU?

2. Can I unlock boot loader using HTCDev site?

Device status - Not rooted, S-Off, Locked
[One (M8) Android Development] Sneakyghost:
Could you please just copy paste your getvar here for us to see? And remove the IMEI when you do.

Missing version main string could happen if you had flashed an old TWRP which had a bug that erased the misc partition, long time ago. A RUU would restore that info though.

I'm totally not sure but the only thing I can currently think of is a usb port that's about to fail. Question: have you noticed odd behaviour when charging, ever? Like extremely long times to charge, dropping the charge indicator, toast messages saying you're connected to a slow charger when you're not.... Such stuff?
[One (M8) Android Development] c5satellite2:
You can try holding all three buttons for at least 2 minutes. Power, vol+, and vol-. No matter what the phone is doing, hold down all 3.

May help with your incorrect battery info.

You can also try charging to 100% with the phone off and also in recovery.
[One (M8) Android Development] xunholyx:
http://xdaforums.com/showpost.php?p=67158283&postcount=1105
[One (M8) Android Development] drjat:
Are you able to flash recovery (again)?

Try flashing TWRP 2.8.7.0 and then try getvar all command and post your output
[One (M8) Android Development] Sneakyghost:
Oops [emoji23]

I won't be able to properly look after this case, trying to answer in between work.

Well that getvar output looks fine except for the already mentioned missing version-main line.

So, there isn't much more I can say to that issue except for what I already mentioned.

I think what was said about the battery and charging in recovery or while off - could be an idea.

I think I'll need to pass on this case. Out of ideas.
[One (M8) Android Development] theDude42:
ok.. I'm going to try the charging in recovery/off. I haven't tried that.

I did read about resetting battery stats/Calibration. However, I've managed to lose root in this process, so can't .. I guess I could reflash.

I'm on TWRP 2.8.7,0

I wonder if I could restore the missing version flag/string? somehow? maybe there's a setvar on the htc_fastboot.. but I'm not 100% sure what it should be. I've read that the these firmware updates are iterative and you shouldn't skip one.. at least, I thought I read that?

Also to add: I've not really had USB problems. I have had difficulty connecting to charge sometimes. but its pretty on/off, not flickering.
[One (M8) Android Development] Sneakyghost:
No not mine. Mine are put together to eliminate the incremental-update problem.

Usb ports are the weak spot on the M8, they break before anything else, that's why I ask.

The version-main is stored in /misc and of course you can either hex-edit it in or just flash any firmware zip with an android-info.txt file - that's where the phone takes the information from ;)

[EDIT]

I once put "Sneakyphone" there instead of the version... It works...
[One (M8) Android Development] theDude42:
thanks for the help guys, tried charging to 100% in recovery. Is there some way to flash this firmware with TWRP? I can flash things just fine there....
[One (M8) Android Development] Sneakyghost:
No safe way.

If you're S-OFF, you can manually DD write partition images, but that's very unsafe, as there's no error checking in DD, which means it won't abort and warn you if a write encounters issues. That however happens a lot more often than with fastboot. So it's a real risk, not just a hypothetical one.
[One (M8) Android Development] Power user:
Can't express enough gratitude for this!! I don't want to swear cause its impolite and out of respect for the best website in the universe of web sites "XDA" but $#@$%#@#%# you guys are awesome!!!!!!! I used up my days "thank yous" on just this post cuz its so GREAT. THAN YOU!!!!! If ever I get hold of OTA you could obv count me in to give it to you guys right away!!!
[One (M8) Android Development] BryanNikson:
But my software version is 3.31.512.2

Will method 2 still work for me?
[One (M8) Android Development] Kratos90:
This thread is for GSM phones only, I think that's LRA firmware you mentioned... I would strongly advise you to not use firmware provided here.
[One (M8) Android Development] BryanNikson:
Thanks

Is there any other way to update my software without having to root?
[One (M8) Android Development] Kratos90:
Sorry, no idea, maybe an RUU if you can find one
[One (M8) Android Development] redpoint73:
I haven't seen a Marshmallow RUU for LRA, but this should get you to Lollipop, at least:

http://xdaforums.com/showpost.php?p=66044439&postcount=37
[One (M8) Android Development] theDude42:
I tired this and I get very quickly "incorrect or bad image" with that filename that flickers by very quickly when I select fastboot USB from the bootloader. So it doesn't like it. Thanks for the suggestion tho!

Also, I've recalibrated battery, no dice.
[One (M8) Android Development] redpoint73:
The last message by me was not directed toward you, did not quote you, and will not work on your phone (AT&T version, from what I can see in your past posts). It was specifically in response to the user that has an LRA version of the M8. If it flashed on your phone, it probably would have radio bricked it. So be careful what you do/try.
[One (M8) Android Development] theDude42:
oh, whooops. Sorry, I should know better than to try something really quick like that without reading thoroughly.

i'm just frustrated. At this point, my phone will only get phone calls when I have LTE off. Its annoying.
[One (M8) Android Development] redpoint73:
If you are on the the AT&T network and have a custom ROM on the phone, than its a common issue not get calls when on LTE.

Is that what your problem is?
[One (M8) Android Development] theDude42:
Yes.. I've read updating the radio helps.

However, GOOD NEWS AND MANY THANKS TO THOSE WHO HELPED. Somehow, I got the RUU past the battery check. I bled dry, reset battery calibration, recharged, discharged (fully), reset battery calibration AGAIN. I did this sequence at least twice. And it worked, the RUU applied.

I'll probably stick with stock sense, get root back and just use XPosed to apply customization.. unless someone has a rom to try which doesn't have the rec. phone call problems.

Once again, thanks for help!
[One (M8) Android Development] c5satellite2:
You can run a custom rom like Viper, all you have to do is call ATT and have them turn off VoLTE and your phone will receive calls properly. Been covered many times in many threads at this point.

Thanking the posts of the people who helped you is proper etiquette here by the way.
[One (M8) Android Development] redpoint73:
Red herring (and I originally thought the same). Nothing I've seen on the phone side will make a difference (except the less-than-ideal workaround of turning off LTE, or going back to an AT&T ROM). The problem is with non-AT&T based ROMs not playing well AT&T's deployment of Voice over LTE (which they brand "HD Voice"). Your best bet (if the intent is to stay on custom ROMs) is to call AT&T and ask them to turn off HD Voice for your account.

Of course that means no HD Voice. But that IMO is preferable to no LTE (or no custom ROMs).

You can read more, if you like, on the following thread: http://xdaforums.com/showpost.php?p=61746473&postcount=9
[One (M8) Android Development] theDude42:
ok.. well, I had called ATT twice. They won't turn off the flag. They try to give me instructions for doing it, and when I say I don't run stock and can't do that, they say they refuse to support non-stock devices :(

thanks for all the help. At the moment, I've got stock sense and root. I think I will just try to customize with Xposed. Stock sense is ok. I have root and can remove all the bloat.

A question tho: If I convert to goggle play edition, does it have this problem?
[One (M8) Android Development] Sneakyghost:
Thanks for that explanation, I hope it helped the user.

Now as it is now clear that this is not a firmware issue, I consider this case closed? Or any firmware related questions remaining? :D
[One (M8) Android Development] BryanNikson:
Thank you so much. Will try this.
[One (M8) Android Development] redpoint73:
From what has been reported, you need to call and ask for AT&T 2nd tier tech support, the frontline customer service have no idea what you are talking about (or what they are talking about for that matter - at least in this case) and don't have the ability to turn off HD Voice.

They are dead wrong in trying to tell you how to do it, its not a phone side issue, its an account setting that you have no access to. We aren't talking about the HD Voice toggle on the phone.

Call again, and ask for tech support. Don't let on that you are non-stock, that info is not relevant, since you have the right to dictate what features are enabled on your account.

I've seen a similar issue reported by folks on the AT&T company forums, with pure stock ATT devices. So if they prod why you want to turn of HD Voice, you can claim that is your issue.

Most likely yes, it will have the same issue. Any non-ATT based ROM will probably suffer from this issue.

---------- Post added at 09:40 AM ---------- Previous post was at 09:36 AM ----------

Sorry for getting off-topic on your thread; but seemed appropriate to help the guy here. Hopefully my last post sends the user on the right path to sorting out his issue (not related to firmware).
[One (M8) Android Development] enewman17:
I have a converted gpe m8, on AT&T and I don't have any issues with calls on LTE.

Try the gpe firmware without hboot. Then you don't have to "convert".

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

Forgive me if I'm wrong on how this all works but I'm sure the new AT&T radio.img is the issue with other roms. The radio.img is going to have a direct impact on how the radio hands off during a call. When your connected to LTE and a call comes in, (before VoLTE) LTE drops off to HSPA then returns to LTE when the call is ended. With the new radio.img it won't want to do that while connected to LTE. So roms not based on 6.20.502.5 won't have the right ril's and whatnot to correctly communicate to the phones hardware and vice versa.

If it doesn't work out you can simply flash the AT&T firmware again.
[One (M8) Android Development] theDude42:
thanks for all the help everyone.. I'm going to try calling support again, but yes, my firmware issue is resolved.

I would say for anyone hitting the "battery too low", here is what I did:

options 0: make sure to have Root back with SuperSU flash,

1. boot phone into recovery. Charge to 100%.

2. then install a battery calibration app (which as I understand it, just deletes a file).

3. use app to calibrate.

4: on my apps advice, run down to 100%. I used "battery drain" ... Ideally, I don't think this is a real good idea. Watch the temp (which this shows). I took my phone out of case, leaned it against a fan, it was nice and cool.

5: Charge fully (again, I did it in recovery).

6: Try RUU

7: IF (FAIL) {GOTO 1} ELSE { DRINK BEER}.

i did this like 3 times.
[One (M8) Android Development] Sneakyghost:
Pretty sure this is not an issue with the radio partition.

The ROM and the carrier define VoLTE capability.

Believe me, we deal with this terrible VoLTE / Wi-Fi calling / SMS over WiFi / HD Voice problem on every single ViperOne and now Viper10 since it began to become available in the different markets.

First condition is: the carrier allows it on the phone you use (for instance, my WWE phone allows it technically, but my carrier Vodafone blocks it for third party phones - I'd need to change to a stock Vodafone bloat ROM to get it).

Second condition is: the ROM you use contains the necessary libs and apps matching your firmware to build up a voice connection over LTE, to make calls over WiFi, etc. (for instance, Viper flashes a set of TmoUS, VZW, Sprint, AT&T files to the phone when selected in the installer to create compatibility) - also the ROM needs all settings in for instance default.xml and some other places to be reflecting the relevant carrier's stock settings.

Third condition is: yes, you guessed it, correct firmware. On the HTC 10, things have been more unified, simplified, so that more carriers fully work with the unlocked firmware, but on the M8 there's still stronger separation. I'm not entirely sure anymore but I think I remember that AT&T was already fully supported by the unlocked/dev edition firmware/ROM.

My point is, radio swap alone won't fix it.

Oh and something else: don't just suggest a GPE conversion like it was something easy to the unsuspecting, unprepared user. Don't just say "flash this without the hboot" - do you even know how difficult and dangerous that can become?

Redirect the user to the proper GPE conversion thread so he can educate himself on the process and ask his questions in the right place.

GPE conversion changes partition sizes and that's controlled by hboot, so if you're gonna flash that firmware without it's hboot, I dunno man. What a weird idea. Frankenbuilds... I used to make such on the early M7 until I realized how problematic that can get.

Please don't. Not on my thread.
[One (M8) Android Development] clemes:
Hello,

Just to be sure, can I flash the firmware with the FUU 4.16 (the latest) with the ZIP 6.20 inside ? The FUU is just the software used to upgrade, so it's the same through different software versions ? Just the zip in C:/Android/com changes ?

Thanks in advance
[One (M8) Android Development] Sneakyghost:
Yeah sure the "FUU" is only the flashing tech from HTC and that only needs to be updated maybe once a year or so when HTC/Google change stuff in ADB and/or fastboot.

The last three years I've personally encountered only one situation were an update to the RUU was absolutely necessary.

I mean, you can always grab any newer RUU structure if you run into issues, like the most current 3.0.4.2015 (version 3 from April 2015) and see if it makes a difference...
[One (M8) Android Development] Rooks:
I got this on my phone.................

And "android-info.txt" has this one.............

Do i need to change "android-info.txt" values in zip file or or not?

Because "android-info.txt" does not match all specs on my phone e.g. "cidnum" values.

Also i'm not in Americas or Africa or Europe or Australia or anywhere else except "Pakistan"
[One (M8) Android Development] Sneakyghost:
Well yeah 502 to 1540 shouldn't be a big deal really.

You're S-OFF, all you need to do is run the zip and see what happens. Phone won't break.

Just go and try.

Oh yeah and while I'm at repeating myself: you might want to go superCID. And no, don't ask how. It's outlined in the first few posts and it's in my batch tool and it's everywhere on the HTC tinted internet.