[One (M8) Android Development] Sneakyghost:
4.16.401.13 added

Recent additions​

​

FUU and ZIP packages are up, see Post #1. FullStock Wipe and NoWipe are UNTESTED

This is a preparatory upload - we are still expecting, hoping, wishing for the promised Marshmallow update for our beautiful M8. The Developer Edition has gotten it already (I might add its firmware at a later stage with some notes once I have figured out the various pitfalls with that). When the Marshmallow update drops, we can expect it to update from 4.16.401.13 to something 6.x.401.x - hence this firmware addition now, so you can be at the right update stage. Other than that, this firmware does you no big improvements, it is also not required for ViperOneM8_4.6.1 but it can be used for that.

I am also providing the FUU again too for anyone who would still like it (not really many looking at the downloads), based on the newest HTC DevEd RUU, hopefully improving the flashing for the upcoming Marshmallow. However, I just noticed I am not having my FUU creation resources and profiles with me (not home for the entire week), so it might be a bit messy, this one. Check it out. Not a biggy. Pretty useless anyway :D

The FUU's install to C:\Android\com and 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 latest 4.16.401.13 OTA was made to update 4.16.401.10 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 in early 2014 because people flashed a new 5.xx firmware over an old 3.xx firmware, missing out 4.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.