yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] OSIRIS2010:
Fw 3.28.401.7

there is a new firmware available 3.28.401.7 -> http://xdaforums.com/htc-one-m8/development/ota-3-28-401-6-t2899900

do you know was is the difference ?

i flashed it without any problems (be carefull, do a full backup before)

there´s also a new hboot inside with the 3.19.00000 an before it was 3.19.22000 i think
[One (M8) Android Development] Captain_Throwback:
HBOOT isn't different. Both include 3.19.0.0000. Plus if you search, back 7 posts from yours was this response: http://xdaforums.com/showthread.php?p=56094430

Seriously people. Forum Rule #1.
[One (M8) Android Development] Sneakyghost:
Support questions

I just finished my 13 hour saturday shift.

Will be online for some 2 or 3 hours. Regular support questions go the new Q&A tab at up at the top.

I have to apologize if i dont immediately respond there because i also have to get used to checking that new tab and feature.

I would like you guys to keep this thread clean. I want solid info here mostly. So users searching for firmware related stuff don't have to go through all this back-and-forth of newbie explaining stuff.

This will take away a lot of frustration and make me not report so many posts.

Please use the Q&A Tab. I will try to respond asap. Please also keep in mind that my occupation demands long work stretches were i will not be available and then long off stretches were i am constantly online. Best to ask questions when you see me active if you want fast replies. Else, get used to waiting a week or so. Thanks for understanding.
[One (M8) Android Development] Captain_Throwback:
The .6 would've said the same when you flashed it (you just didn't notice). Those aren't errors.
[One (M8) Android Development] Roma80:
I'm confused. Why my Viper 2.5.0 boot on 3.28.401.6 and not on 3.28.401.7?
[One (M8) Android Development] Captain_Throwback:
Did you reflash the ROM after updating the firmware? If the firmware was stock, it likely included boot.img. Perhaps you updated to the .6 firmware before flashing the ROM?
[One (M8) Android Development] Black-FR:
It works with both firmware versions.

But sounds as you flashed the boot.img from the .7 firmware.

This would explain, why the rom didn't boot.

If you flashed the boot.img too, then you would need to flash the rom dirty again.

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Android Development] Roma80:
God i'm so stupid, i overseen the boot.img in die FW 3.28.401.7 zip file.

In the 3.28.401.6 zip it was no boot.img....

I go to bed and sleep a week, its better :P
[One (M8) Android Development] grinchyboy:
sorry if this has been covered but if I flash this new firmware, would it affect the radio from t-mobile?
[One (M8) Android Development] jkolner:
Going to update my Firmware and have downloaded "M8_3.28.401.6_WWE_TWRP2803_NoWipe_rename_to_ROM.zip".

Can i rename that file to "Firmware_Rom.zip" and install it with adb like in method #2?
[One (M8) Android Development] Captain_Throwback:
There's no need to rename the file.
[One (M8) Android Development] DROITURK182:
Yes it gives you the international radio and it works great for me I'm on T-Mobile also in the US.

Sent from my HTC One_M8 Space Banana.
[One (M8) Android Development] Sneakyghost:
There will probably be an issue with Wi-Fi Calling, but other than that, the international radio should work fine on Tmobile.
[One (M8) Android Development] Lancerz:
I just flashed the new firmware on my T-Mobile M8 and yes it works fine but your LTE speeds will suffer. I normally get between 30-50mbps with the T-Mobile radio, only getting 1.5 mbps at most with the new firmware.

Edit: Well I did a few more tests and got around 22-26mbps, which is decent. I was almost about to go back to the T-Mobile firmware lol.
[One (M8) Android Development] Sneakyghost:
T-Mobile utilizes some so-called "AWS" bands for LTE, which were before used for something else, not really "in-the-know" with these things. It all boils down to international not using these bands at all (the frequency that is running on is currently heavily negotiated in Europe - its still occupied by TV here). So International radios will never support full LTE on T-Mobile. I reckon T-Mobile US uses more than just AWS in more populated areas, so you should get some LTE, even if not the full thing.
[One (M8) Android Development] Lancerz:
Yeah I think those AWS bands come from the buying out of Metro PCS here in the US. But your guide was spot on, everything worked flawlessly. If people would read they wouldn't have so many issues lol.
[One (M8) Android Development] Sneakyghost:
3.28.401.7 FUU and ZIP

Recent additions​

​

FUU and ZIP packages are up. I flashed them all fine to my phone. Should be good to go.

The FUU's are changed now. They install to C:\Android\com like before, but they also run a little batch script that silently installs VCRedist 2008 onto your PC - This is to make sure the FUU can run. It depends on that runtime.

Some clarifying information:

1.) HTC OTA's are ALWAYS incremental. They depend on some previous version and are made for consumers to automatically update their phones. This 3.28.401.7 OTA was made to update 2.22.401.5 but nothing earlier.

2.) HTC RUU's are ALWAYS full, to update a phone from whatever state it is in - they are made for service purposes.

Flashing a HTC OTA firmware to your phone without knowing which version it should be flashed over is not a good idea. It can sometimes lead to undesired side-effects if flashed over an older version it wasn't made for. The M7 suffered a series of bricks earlier this year because people flashed a new 6.xx firmware over an old 4.xx firmware, missing out 5.xx.

My work here is to exactly prevent this from happening. What i do is i merge new OTA Firmware into the older FULL firmware packages, observing carefully what HTC states in their info (Filenames, android-info.txt, etc). So, basically, i create a full RUU-like package for you to flash to any state of firmware. You do not need to worry about what you had before.

Of course, flashing the regular firmware packages from e.g. Llabtoofer's thread is fine too. You might just need to pay special attention to your MainVer or OS-Line in Bootloader and check that you do not miss out a previous update. If you look after that, you will be fine with any firmware package.

Since this only occasionally creates issues (most often it is fine), there is hardly any info on other threads about this problem.

What my ZIP's / FUU's do NOT cater for is safety when cross-flashing devices, like e.g. putting international firmware onto a T-Mobile device (401 to 531) or anything like that. S-OFF users can do this. It also works in many scenarios since the device models are often very similar, but it can also cause problems. The worst is flashing GSM firmware to a CDMA or Hybrid device (like my firmware to Sprint or Verizon) or vice versa. That should be avoided by any means.

Unfortunately i have no compatibility list but i made THIS yesterday and i hope it provides some clues for you.
[One (M8) Android Development] DROITURK182:
Your right I'm on the newest firmware .7 with ARHD 21.0 ROM but after I flashed the recent radio from T-Mobile that came with 4.4.3 my LTE speeds went up on download and upload. I would recommend flashing that radio after doing the firmware upgrade if your on T-Mobile US.

Sent from my HTC One_M8 Space Banana.

---------- Post added at 08:42 PM ---------- Previous post was at 08:38 PM ----------

Here is the radio if anybody needs it for T-Mobile US you can flash it through recovery.

https://www.dropbox.com/s/b3xgk82b202g3en/T-Mobile-4.4.3-radio.zip?dl=0

Sent from my HTC One_M8 Space Banana.
[One (M8) Android Development] Lancerz:
Sweet thanks man, I wasn't sure if you could mix them.
[One (M8) Android Development] schollianmj:
windows 8.1 compatible?

My Windows 7 laptop died and my new one has windoWindows 8.1 on it. For the life of me I cAnnot get any of these fuu tools to run. Either I get a side no side error or it says files are missing... Does any one know how I can get this to work? It's a basic up laptop, core i5, 8gigs ram.... What else do you need to know? Help me help you to help me. Please?
[One (M8) Android Development] vixs:
You said it Download/Upload speed went up, but do you think by flashing the radio , are you able to get the Full LTE speed ? or just a slight Increase ?
[One (M8) Android Development] eroticdagreat:
Run it as administrator and make sure your antivirus software isn't stopping the fuu from running
[One (M8) Android Development] Lancerz:
My speeds are back to normal after flashing the T-Mobile radio
[One (M8) Android Development] Sneakyghost:
The newer FUU's include Visual C++ x86 2008, which is the runtime the FUU uses. It will also work with the Visual C++ x86 2008 SP1 (Service Pack 1) version.

If you're getting the side-by-side configuration error despite using the new FUU, it means my VCRedist install script is not working for your laptop.

In that case, please Google the said runtime and download and install it manually from Microsoft's website to fix this error.

It has to be the x86 version, even if you're on an x64 system.

Also, reading the posts for the new FUU's helps. I might need to put this info in post#1 as well though. Oh. Actually I think I did. Should say you're needing that vcredist where the FUU method is described. Or do I have Alzheimer's already?

[EDIT]

I reworked Post #1 to better reflect the current firmware situation.

- Added more clear hints to Viusal C++ Redist

- Changed Error Descriptions and solutions a wee bit.

- Reworded a lot of stuff.
[One (M8) Android Development] Sneakyghost:
I suggest to rather use the RUUmode for radio flashing. Safer than recovery.

Here is the same radio as RUUMode zip with added android-info.txt version 3.28.401.7 - this zip is for people on that international firmware, wanting to inject the older TMUS radio.

If you wish to see a different MainVer after the flash, just edit the android-info.txt inside the zip accordingly before flashing. Use Notepad++ and 7zip.
[One (M8) Android Development] Flandro:
Newb here. Unzip this file and flash boot.img in fastboot mode? Flash this zip in recovery? Fastboot flash this radio.img in RUU mode? None seem to work for me.

---------- Post added at 12:30 PM ---------- Previous post was at 12:22 PM ----------

My next step was going to be rename this zip to something simple like boot.zip and run 'fastboot flash zip boot.zip' in RUU mode. I just thought I'd confirm this before I royally screwed up my phone. Thanks.
[One (M8) Android Development] Sneakyghost:
fastboot flash zip RADIO_M8_TMUS_2.22.531.5_MainVer_3.28.401.7.zip

yes that is correct.

however, read my instructions in post one, you need to first reboot into RUUMode. That is done by:

fastboot oem rebootRUU

[EDIT]

just seen the radio zip was named oddly with an extra dot at the end. Renamed it. Hope that didn't cause any issues for the 3 downloads it had already :D
[One (M8) Android Development] Stephen:
Moderator Information,

I have deleted several offtopic posts at the OP's request. The OP has a strict no offtopic rule on this thread. Please keep all posts related to issues flashing firmware only please.

Many thanks,

Ghost
[One (M8) Android Development] Sneakyghost:
I appreciate Thanks posts. Don't get me wrong. There is a Q&A tab now though. You can use that one.
[One (M8) Android Development] smeejaytee:
I just spotted this on Google+ I believe the T-Mobile update will come on Tuesday

http://m.androidcentral.com/t-mobile-will-roll-out-eye-sw-update-htc-one-m8-tuesday
[One (M8) Android Development] Sneakyghost:
http://xdaforums.com/showpost.php?p=56156928&postcount=13980
[One (M8) Android Development] smeejaytee:
I thought it may be helpful as it gives reference to a particular day.
[One (M8) Android Development] schollianmj:
well I downloaded all the files you referenced but still no go with the FUU. so I got to thinking about it and just followed your directions and used ADB/fastboot. worked like a charm.
[One (M8) Android Development] bit1:
By the Gods! OP thank you so much for this. I've been reading in Rom threads about downloading zips, flashing twice to make sure it sticks, sometimes having to recover a partial brick. An FUU only makes sense and is the easiest thing in the world. I had my Rom on my SD card waiting, I got upgraded to the latest TWRP in the process and I'm on the latest firmware. I'm literally just gonna point back to this thread and tell people to flash the FUU. It's masochist to do otherwise. Thanks again!

Oh, and by the way I can confirm that it worked like butter on the Windows 10 Technical Preview.
[One (M8) Android Development] Behold_this:
T-Mobile US 3.32.531.2 firmware

https://www.androidfilehost.com/?fid=95747613655048625
[One (M8) Android Development] pottyvick:
Thank you sir...

so now to relock the bootloader and flash this ... s-on kind of sucks lol
[One (M8) Android Development] Captain_Throwback:
You shouldn't need to relock to flash firmware . . . otherwise the OTA would require wiping your data every time there's a update.

Have you tried just flashing it in RUU mode first?

EDIT: Though it's been so long since I tried flashing anything while S-ON, I'm probably wrong, lol.
[One (M8) Android Development] Jbb3393:
I've downloaded this twice, and checked the md5 to be correct but I cannot open the zip to check it's contents. ❔❓
[One (M8) Android Development] Behold_this:
Because it is a signed zip, not all programs will open it. I suggest you use 7zip to open it.
[One (M8) Android Development] Jbb3393:
I did not know that, thank you sir.
[One (M8) Android Development] Behold_this:
No worries.

I usually will post firmware directly as it comes from HTC, which means it will still maintain HTC signature. In that case most archive programs will not open it. These signed packages will also contain the stock recovery and stock boot.img as well. It's not necessarily intended to be flashed "as is" by custom Rom users. I'm only posting it here for the users that are impatient and want to put together their own update now.

Of course I have already spoken with [MENTION=1102297]Sneakyghost[/MENTION] and passed it on to him. He will be putting together a FUU for you guys when he has time.
[One (M8) Android Development] pottyvick:
You could be right, this is the first HTC i have with s-on. I will try flashing with bootloader unlocked

Edit: I get a "wrong zipped Image" error
[One (M8) Android Development] Behold_this:
Unfortunately since you're s-on flashing firmware can get a little finicky. The error you are seeing is likely not the actual error tripping up the flash. More of a generic error (I know that can be confusing).

Being that you're s-on, you do need to relock your bootloader first, then boot into RUUmode and flash the firmware.zip that way. Before you relock your bootloader, I suggest you backup any data you currently have that you would like to restore later.

After you flash the firmware, if you are running a custom ROM it may fail to boot. This will be due to the fact that the firmware you're flashing MUST be stock, so it will contain the stock boot.img and also the stock recovery. Once you flash the firmware you will need to first flash back your custom recovery, then dirty flash your custom ROM to get its boot.img back.

Another option, though it's more involved, would be to flash the 2.22.531.6 stock nandroid found in the t-mobile forum, then accept the OTA, then reflash custom recovery, reflash rom.
[One (M8) Android Development] Captain_Throwback:
So this being the case, it's a good idea to get S-OFF, because relocking then unlocking your device will wipe your data.
[One (M8) Android Development] Behold_this:
It would certainly be my recommendation. Of course, assuming they're running a custom recovery, they can back up their data, but generally speaking, I completely agree. S-off is a good idea and well worth the small investment! I've added a suggestion to my initial post that he back up his data before relocking to avoid losing anything important.
[One (M8) Android Development] pottyvick:
Thanks for the explanation, exactly what i needed... so if i try the "other" option. I would flash the stock nandroid backup, then i believe flash the stock recovery, then take the OTA... would i have to relock my bootloader with the OTA process?
[One (M8) Android Development] Behold_this:
Don't want to take this thread too far OT, but all info you need and good support can be found in this thread:

http://xdaforums.com/showthread.php?t=2714456
[One (M8) Android Development] treetolber:
How difficult is it to simply flash a custom recovery and boot.img after flashing this? Or would it be easier to wait until someone compiles a rooted ROM from this firmware?
[One (M8) Android Development] Black-FR:
It's pretty easy...

Flashing a recovery:

fastboot flash recovery name_of_the_recovery.img

Afterwards:

fastboot erase cache

And for the boot.img...

You could dirty flash the rom again, to get back the boot.img of it.

Or you flash the boot.img manually via fastboot:

fastboot flash boot boot.img

Afterwards:

fastboot erase cache

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Android Development] treetolber:
Thanks again! I flashed new firmware and recovery. Dirty flashing ROM. So far, so good! Now the million dollar question. How can I tell if I've got the proper firmware and not the same modified international version I had before?
[One (M8) Android Development] Black-FR:
The easiest way is, reboot into the Bootloader and check, what the OS-Line is telling you

There you should see the version, of the new firmware.

Other option would be, via fastboot:

fastboot getvar all

Look there for the Line, of the main version.

That's your firmware version (or at least the version, on which your firmware us based).

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Android Development] treetolber:
This is what I get:

C:\ADB>fastboot getvar all

INFOversion: 0.5

INFOversion-bootloader: 3.19.0.0000

INFOversion-baseband: 1.22.213311491.08G

INFOversion-cpld: None

INFOversion-microp: None

INFOversion-main: 3.32.531.2

INFOversion-misc: PVT SHIP S-OFF

INFOserialno:

INFOimei:

INFOimei2: Not Support

INFOmeid: 00000000000000

INFOproduct: m8_ul

INFOplatform: hTCBmsm8974

INFOmodelid: 0P6B13000

INFOcidnum: T-MOB010

INFObattery-status: good

INFObattery-voltage: 0mV

INFOpartition-layout: Generic

INFOsecurity: off

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: 038866fd

INFOhbootpreupdate: 11

INFOgencheckpt: 0

all: Done!

finished. total time: 0.040s

I think everything I right. There is only problem that I can see. I can't send MMS. When I had the int version I couldn't send or receive MMS. Now I can receive, just not send.
[One (M8) Android Development] Black-FR:
Yes it's the latest T-Mobile firmware.

But better remove your imei and serial number, from your post.

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Android Development] treetolber:
Now what to do about the MMS issue? Should I do a full wipe and clean flash of the ROM?

UPDATE!!

The MMS sends with WiFi disabled.
[One (M8) Android Development] Sneakyghost:
T-Mobile US 3.32.531.2 FUU ZIP

T-Mobile US​

Recent additions​

​

FUU and ZIP packages are up. TESTED - working

The FUU's are changed now. They install to C:\Android\com like before, but they also run a little batch script that silently installs VCRedist 2008 onto your PC - This is to make sure the FUU can run. It depends on that runtime.

Some clarifying information:

1.) HTC OTA's are ALWAYS incremental. They depend on some previous version and are made for consumers to automatically update their phones. This 3.28.401.7 OTA was made to update 2.22.401.5 but nothing earlier.

2.) HTC RUU's are ALWAYS full, to update a phone from whatever state it is in - they are made for service purposes.

Flashing a HTC OTA firmware to your phone without knowing which version it should be flashed over is not a good idea. It can sometimes lead to undesired side-effects if flashed over an older version it wasn't made for. The M7 suffered a series of bricks earlier this year because people flashed a new 6.xx firmware over an old 4.xx firmware, missing out 5.xx.

My work here is to exactly prevent this from happening. What i do is i merge new OTA Firmware into the older FULL firmware packages, observing carefully what HTC states in their info (Filenames, android-info.txt, etc). So, basically, i create a full RUU-like package for you to flash to any state of firmware. You do not need to worry about what you had before.

Of course, flashing the regular firmware packages from e.g. Llabtoofer's thread is fine too. You might just need to pay special attention to your MainVer or OS-Line in Bootloader and check that you do not miss out a previous update. If you look after that, you will be fine with any firmware package.

Since this only occasionally creates issues (most often it is fine), there is hardly any info on other threads about this problem.

What my ZIP's / FUU's do NOT cater for is safety when cross-flashing devices, like e.g. putting international firmware onto a T-Mobile device (401 to 531) or anything like that. S-OFF users can do this. It also works in many scenarios since the device models are often very similar, but it can also cause problems. The worst is flashing GSM firmware to a CDMA or Hybrid device (like my firmware to Sprint or Verizon) or vice versa. That should be avoided by any means.

Unfortunately i have no compatibility list but i made THIS and i hope it provides some clues for you.
[One (M8) Android Development] jergutierrez:
Has this been tested?

Im looking to get the FUU no wipe for this T-Mobile firmware update.
[One (M8) Android Development] jcorv58:
Was this a serious question? It says in red-in caps- UNTESTED
[One (M8) Android Development] jergutierrez:
I saw in another post someone having installed the FUU of the new T-Mobile firmware. I was just checking.

I saw the red.
[One (M8) Android Development] beats4x:
as [MENTION=1102297]Sneakyghost[/MENTION]'s official guinea pig, i tested both packages and all is well. flash away minions xD
[One (M8) Android Development] SeVIIn:
Flashed the new no wipe zip for TMO over the latest international and all is fine. :good: Thanks again for the files!
[One (M8) Android Development] npalmy:
Me too all good for me! :)

Thanks for the file.
[One (M8) Android Development] schollianmj:
I still canoot for the life of me get this to run on my windows 8.1 laptop. Im sure it is something simple, but whatever your ADB / Fastboot commands worked just fine. I have installed the vcredist files, the SP1 files... everything mentioned. I click the icon and it will not load...
[One (M8) Android Development] Sneakyghost:
Oh. Lol. Simple that. It's not loading at all you say?

:laugh:

.....

Need to put that in my FAQ more clearly. Doesn't it already say somewhere the FUU won't load if the ZIP inside is called anything else than ROM.zip or rom.zip?

So far that is the only reason I've seen for the FUU not to load at all.

Make sure the ZIP is named properly and make sure you have "show known file extensions" switched on in Windows explorer too...

mobile post
[One (M8) Android Development] schollianmj:
let me clarify... I cant even get the RUU app to work. as in this:

will not run. I downloaded your installer and clicked it adn it installed. created C:\\android\com and put its stuff inside that, but when I try to run the app it will not run. My cursor spins to show that my computer is doing something for about 3 seconds and then it stops. nothing happens.
[One (M8) Android Development] topjohnwu:
Very informative, thanks a lot!! Well I think I would have to do full ruu wipes in the future, the reason I wanted to extract firmware files is that I don't want to wipe all the internal storage to roll back to stock firmware. Flashing FUU is much more convenient than RUUs :)
[One (M8) Android Development] Sneakyghost:
I am now uploading the ROM you linked me to to my Mega account and i notified the guy who does the decrypts. I wait for his response. Maybe you get your decrypted thing and i can do the FUU for you.
[One (M8) Android Development] n1234d:
Which RUU do you have?