yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] jxcorex28:
Where in that message did I say anything about specifically asking for "mikes stuff"

Is it possible to take the 2.22.1540.4 OTA file from mikes thread...I asked if it were possible, I used the renaming the file to 0P6BIMG for the downloads you've used on dropbox.
[One (M8) Android Development] Sneakyghost:
Wrong thread. And if you fixed your "bricked" note yourself you at least know how to operate a jtag RIFF box or a similar jtag device, which again means you know exactly how all this works. So in this sense, why do you even ask? You're wasting people's time.
[One (M8) Android Development] Sneakyghost:
You may flash any firmware package for the M8 with either of three methods available.

Method 1: use HTC's RUU structure, which i call FUU for differentiating it a little from HTC's RUU.

Method 2: use the Fastboot method, which is essentially the same as the FUU/RUU without the clicky UI.

Method 3: use the hboot method, which lets bootloader flash a given zip from sdcard directly.

Now, method 1 and 2 are covered here. Every detail on how to use them is to be found in Post #1. Method 3 however, is detailed in Skulldreamz' thread and not covered here.

Which one you pick depends entirely on your preference. All methods are used by HTC, each one has its downsides and positives. I prefer the ZIP method as it appears to be the safest one in my eyes. Clearly, the FUU method is the easiest one and the least safe because it involves yet another program between the chip and the zip. Whether method 1 or 3 are safer remains open. Both appear to be pretty safe.

While the ZIP method involves a USB connection that can fail for various reasons, the Hboot methods involve a transfer-to-SDcard via USB or Internet which is just as unsafe, and it also includes a risk of a badly performing NAND chip that could screw up.

Now, i have seen plenty of ZIP method flashes fail, i have seen a few hboot method flashes fail, so i would argue neither one is the "safest".

Now to answer your question directly: yes, you can use that other zip and flash it with either of the three methods, as long as the ZIP is set up properly. I hope it is. However, i take no responsibility and also do no support on stuff that is not set up by me. How could i possibly? I have no insight into any other dudes zips and processes.
[One (M8) Android Development] Sneakyghost:
Thanks to my friendly neighborhood-spider who keeps track of all stuff TmoUS, here's HTC's direct link to a new TmoUS RUU for whom it may interest.
[One (M8) Android Development] gadibob:
Full stock wipe Vs. No wipe

Hi,

Is there any advantage to perform the "Full Wipe" Vs. "No wipe"?

The "NO WIPE way" is compared to "Dirty ROM flashing"...?

Thanks for the answer

gadibob
[One (M8) Android Development] DROITURK182:
Does anybody have access to a link for the new T-Mobile firmware 2.22.531.6 with no wipe, and not signed with no red text. If not what do we need to do to get this added to the op? Do we get the official RUU and hack it? Because I don't need the stock recovery or Boot.IMG in the firmware.

Sent from my HTC One_M8 Space Banana.
[One (M8) Android Development] Behold_this:
Only useful firmware image in that update is RCdata.img. And last time I checked this thread didn't want hacked Hboots.
[One (M8) Android Development] fmedrano1977:
Whats the difference from wipe, no wipe zips? And be a TmobileUS user, should I go with that one or the international one?
[One (M8) Android Development] Sneakyghost:
I really shouldn't bother writing guides and long entry posts.

T-Mobile can flash international if S-OFF. Some problems may arise, you might lose functions like Wi-Fi calling, reception might be worse or flakey etc. etc...

You just have to try.

The T-Mobile firmware is in the list. You've all heard Behold_this: only rcdata is new, which isn't really that important. I haven't been able to look at it myself but I reckon behold_this knows what he's talking about.

The difference between wipe and no-wipe is, well, outlined in post #1. Have other things to do than write it all up again.
[One (M8) Android Development] Iceberger:
can't S-Off with Firewater

Hallo Sneaky,

Tried to S-Off my new M8 this morning (HTCDEV unloacked and rooted) with firewater,

What i get is:

********** whelp, this sucks, firewater can not work on your device **********

********** no amount of reflashing, retrying, or ruuing will fix... **********

********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********

********** if we are able to fix this issue, it will be announced **********

********** bye bye.....sorry it didn't work out. **********

Do you have maybe a different way to S-Off it?
[One (M8) Android Development] Sneakyghost:
I'm not a member of that dev team. Sorry. But they do offer a better and always working solution called SunShine over at http://theroot.ninja.
[One (M8) Android Development] Iceberger:
Thanks, but Sunshine is also incompatible .... :crying:
[One (M8) Android Development] ViNOK16Bit:
Flash a nearly stock Rom and run sunshine again. It will work then

Sent from my HTC One_M8 using Xparent Red Tapatalk 2
[One (M8) Android Development] Sneakyghost:
They do have an IRC based support channel, you realize that, right? This is not an S-OFF support thread.
[One (M8) Android Development] wdeydwondrer:
Have the dev edition m8 and flashed the international 401.4. After booting now I get the red text on the bottom and I tried to use the search bar to see if there was a way to get the text gone w/out having to use someone elses modified firmware files. Wasn't able to find an answer one way or the other if we just have to live with the red text?

Also, just double checking, international covers all gsm variants of the m8, right?

Thanks for the FUU loader, made it tons easier!
[One (M8) Android Development] peteri8706:
Hello.

Don't hesitate to use any modded 'no red text' fw zip package which is for your GSM m8.

It will get rid of the red txt and no issue thereafter. You're right to have flashed the 2.22.401.4 fw, which I assume full wiped the fw. Now use the no red text zip and it'll go. Don't stress if the phone doesn't reboot bootloader twice on rebootRUU method of the flash of the no red text zip file, it still works properly.

Check your boatloader after doing this. If the OS is blank, flash latest TWRP which fixes this.

Yes, international is for GSM. Bypass verizon, att, t-mob, they'll softer icky if you flash and if the phone actually accepts the fw to begin with (which I'm not sure if it will or won't with a dev edition).

Cheers.
[One (M8) Android Development] Sneakyghost:
I wish not to have this type of advice here please. I stopped making the No Red Text hboots for exactly the reason you call safe: flashing ANY hboot to SOME device is what got a row of people into bricks because >some< firmware does NOT play well with >some< hboots. This has become a very dangerous thing to do.

No cleaned hboots from me. No support for them from me. If you still wish to have them, check my thread on the M7 forum with the instructions how to do them - that's where most others who offer them picked up the method as well. Unfortunately they ALL forgot to take along the safety infos.

If you want to minimize bricking risks, just leave hboots alone and follow this rule: never flash hboots from another firmware pack unless it matches MD5.

This is not being paranoid but based on reading a lot of stories on XDA and taking my guesses.
[One (M8) Android Development] donmarkoni:
[MENTION=1102297]Sneakyghost[/MENTION]

*cough* *cough* *cough* :D

OTA 3.28.401.6 from here: [ota] 3.28.401.6, thanks to [MENTION=4860093]SoLdieR9312[/MENTION]

Firmware 3.28.401.6 from here: [ota] 3.28.401.6, thanks to [MENTION=4860093]SoLdieR9312[/MENTION]

unsigned firmware 3.28.401.3 from here: [ROM] MaximusHD | 8.0.0 | Android 4.4.4 | Sense 6.0 | EYE | ART | OTA | 3.28.401.3, thanks to [MENTION=494185]LlabTooFeR[/MENTION]

Just to get your attention. ;) I'll look at those myself too, when I get home from work.
[One (M8) Android Development] Sneakyghost:
I have them since a bit :D

(Working, nothing happening here before Friday night or Saturday)

Full Pack (3.28.401.3) has a new file i never saw before: "Bootloader" (Hboot and AppsBoot are still there too)

OTA (3.28.401.6) has new files called "emmc_fw16.img" and "emmc_fw32.img" which, according to some qualified source, replace dzdata with a no-wipe system. However, i doubt this is true since the dzdata images hold an APK-like folder structure inside, whereas these clearly are NAND Controller Firmware files.... whatever it may be, they change something deep down in the chip.

Now, my biggest concern is this: the OTA is meant to update from 2.22 but does NOT contain this EMMC Firmware, whereas the full package DOES contain them. None has the dzdata. Whatever i choose - data won't be wiped. Which i think is weird considering this is another base transition. Also, why would one update the NAND controller firmware, while the other would not?

Time to speculate, investigate, think, give me input. Once again i prove to be a nosy clueless idiot. Whoever knows more, you are welcome to share for the benefit of all. Thanks.

[EDIT]

K guys i am officially past the first flash of my custom RUU to 3.28.401.3 and i am stopping for the night to get drunk. Will be back tomorrow with several packages for you to safely flash your substitute brains up to the latest.

Thanks for sticking with me, my loyal small fanbase :D
[One (M8) Android Development] solace88:
Hi all, hoping to get some help

After some running around with firewater that didnt start at all - I had success with sunshine and superCIDed the phone to prepare for the 3.28.401.6 upgrade

Stock phone was HTC CID_622 firmware 1.60.708.2

This is the following output

(code) C:\adb>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.16.0.0000

(bootloader) version-baseband: 1.16.21331831.A16G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.60.708.2

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

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B63000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: c3d94491

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.212s

C:\adb>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.020s]

finished. total time: 0.024s

C:\adb>fastboot oem rebootRUU

...

(bootloader) Start Verify: 0

OKAY [ 0.022s]

finished. total time: 0.026s

C:\adb>fastboot flash zip firmware.zip

target reported max download size of 1830711296 bytes

sending 'zip' (51216 KB)...

OKAY [ 2.249s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) shift signature_size for header checking...

(bootloader) zip info parsing...

(bootloader) checking model ID...

FAILED (remote: 41 model id check fail)

finished. total time: 2.563s (/code)

The model ID obviously doesnt match the one in the android-info.txt file in firmware.zip but I thought the superCID negates this?

Will it be safe to edit the txt file and put my modelID in there?

Thanks
[One (M8) Android Development] Sneakyghost:
Yeah that's kinda odd really. What model is this anyway? My list says it's "Asia-HK-CHT" according to CID but this odd model-ID is new to me. Not the dual SIM version by chance?

Also, what you're trying to do is kinda dangerous, because the 3.28.401.6 is an incremental update to 2.22.401.5 but you're way below that version. Chances are, you're gonna kill your device (worst case) or at least run into some random trouble. Also, yours is a 708 while the update is a 401.

I'm not really wanting to support cross-flashing anymore. I've come away from that lately. Not really the best idea. Usually just causes hiccups and degraded user experience if things don't properly match up, like unexplainable wakelock's, Battery issues, connection issues etc.

To simply answer your question:

Yes, If you look at page one you'll find notes on the best practice for working around the MID check fail, including how to best edit it in the zip. Please keep in mind what I said above.
[One (M8) Android Development] solace88:
Thank you for your reply - It is not a dual sim , it is a grey import from HK - not sure how to provide further detail

I saw a post on ARHD that showed someone altering the model ID to get the firmware flash working - just as I had done this and pressed the flash command, I read your post and shat a brick

It didn't boot on the ARHD 8.1 version at all - I flashed the 20.1 version and subsequently shut off - wouldn't turn on for a awhile and I thought that was it - bricked..

Sprang to life after holding all the buttons in desperation and stayed on the HTC logo screen for a good 5 minutes - its booted through and it appears to be working just fine now.. I will update on any strange behaviours ; Did not realize jumping up version numbers drastically was a Bad Thing

Thanks again
[One (M8) Android Development] Sneakyghost:
The original OTA clearly states it's meant to update 2.22.401.5 - meaning partition images that aren't included in the OTA because HTC assumes they were updated in 2.22 will not get their update. So, depending on which partitions this affects, it can have no or bad adverse side effects.

On the M7, there was a brick scenario when jumping from 4.xx to 6.xx, which is depicting the worst case scenario.

I would adapt a habit of researching firmware properly before flashing some random packages you find somewhere.

My FUU packages are made to eliminate this risk, by the way. They're always updating all partitions like a RUU would do. So this particular problem will not happen with my packages.

[EDIT]

Recent additions​

​

The ZIP's are up. Links are available in the sheet under Post #1/DOWNLOAD. The FUU might only follow tomorrow, i still have cosmetic issues with the new WinRar 5.20 and it bugs me that i have to upload ugly installers because the Text Formatting doesn't work :D

The Batch Script can be downloaded from Post #3.
[One (M8) Android Development] Black-FR:
Nice to see, that you uploaded the latest firmware.

Thanks for all the work.

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Android Development] Sneakyghost:
thank the generous donor who decided to send me an S-OFF device when i couldn't S-OFF mine and beaups didn't have SunShine ready yet. Making the ZIP's is more of a careful putting together job which requires zero development skillz. So, thank the donor.

Sorry just needed to leave this here because today i somehow remembered why i am actually able to do this and why my wife can enjoy an M8 (my old S-ON unit) and i just realized i am still so totally grateful for this humbling move of some nice guy.
[One (M8) Android Development] rmthx:
hi sneaky

the new zip 3.24.401.6 no wipe with twrp 8.0.3 its with no red text??

thanks
[One (M8) Android Development] Sneakyghost:
No. I'm not doing that anymore. Too risky. Sorry.

mobile post
[One (M8) Android Development] rmthx:
ok sneaky

I do not much about the changes made by the new htc fimrware and hboot

in the post of the viper rom

I saw a zip of the new firm without red letters

you say you do not because it's too risky then not recommend to flash this ??

there even with the flags s.on locked
[One (M8) Android Development] Sneakyghost:
modified hboots are posing a risk. I am not supporting that anymore. They do work, but they can cause issues. People need to know what they are doing.

Since many people come here who have no idea about all this, i cannot provide stuff that is potentially unsafe. I have said this like a million times before. No red text removal from me anymore. Go somewhere else to get that.
[One (M8) Android Development] Iceberger:
*** Software status: Official ***

Are you also getting *** Software status: Official *** in your bootloader after flashing the new 3.28.401.6 firmware?
[One (M8) Android Development] Captain_Throwback:
http://xdaforums.com/showthread.php?p=55958536
[One (M8) Android Development] Kent21:
i'm download ZIp's: M8_3.28.401.6_WWE_FullStock_rename_to_ROM.zip 90.1mb and flash through ADB but see in bootloader, os show 3.28.401.3 not 3.28.401.6. Choose recovery, my phone is reboot and lost wifi. i'm s-off, super cid :(
[One (M8) Android Development] nysoprano:
I have a T-Mobile US M8 that's s-off and when the firmware 2.22.401.4 came out I updated to it. Now I want to update to the new one, 3.28.401.6.

Does it matter that I'm on .4 and the new one is .6?

Do I have to upgrade to another firmware before the new one? I'm clueless on partition tables and don't want to brick my phone.
[One (M8) Android Development] Iceberger:
A yes or no answer would have been sufficient.

Just liked to see this info added as a part of what's new in this firmware.

At least you know the new banner is nothing to be worried about.
[One (M8) Android Development] jxcorex28:
Would these new files you mentioned a few pages ago have a direct correlation to twrp being unable to mount dalvik cache,system,etc....I switched to 3.28.xxx.6 a few days ago,tried flashing a dirty flash of maximusHD because of a messed up recovery. It took me 5 hours of tinkering to finally realize I had a saved BU of beanstalk b4 I flashed the latest FW...there is more detail in a post I posted in the Q&A...I was not sure if firmware problems could wreck recovery. I'm back on 2.22.501.4
[One (M8) Android Development] Captain_Throwback:
Unfortunately I couldn't give you a yes or no answer, as I don't have any device on which to look :rolleyes:. So, I referred you to the most thorough answer I'd seen on the subject. I'm sorry if you didn't like the response, but I thought it was appropriate.
[One (M8) Android Development] mathrania:
I dont have access to my laptop for further 2 weeks. Is it possible to flash this firmware by putting it in sd card and then using the bootloader mode? Bcoz i remember i flashed previous firmware this way which was without the Red Text Warning....
[One (M8) Android Development] Sneakyghost:
I think I wrote in post one, there are three methods and the zip's work with all of them, provided the phone is S-OFF.

mobile post
[One (M8) Android Development] Sneakyghost:
One more unfriendly comment towards users doing exactly what I want - provide useful, thorough information - and I'll have you a ten page post served and make you read it.

You might have noticed that this thread isn't about yes or no answers.

The reason I didn't provide info on the matter simply is that I hadn't bothered to look for info on it because it's so obvious what it is, no?

mobile post
[One (M8) Android Development] Sneakyghost:
I'm interested how did you exactly flash this? Can you outline what you did exactly? Certainly not flashed through ADB because ADB doesn't communicate with the Bootloader.

I flashed the very same zip like 10 times yesterday to observe the process and learn about the new firmware parts and I can assure you, it's leaving a .6 in Bootloader like it's supposed to.

mobile post
[One (M8) Android Development] Kent21:
i'm download M8_3.28.401.6_WWE_FullStock_rename_to_ROM.zip, no extract, copy folder to C:\ADB M8 and rename firmware.zip. reboot bootloader connect my phone fastboot usb and flash.

fastboot oem rebootRUU

fastboot flash zip firmware..zip
[One (M8) Android Development] Iceberger:
I'm very sorry if my post sounded unfriendly. That was not my intention. Not at all.
[One (M8) Android Development] Sneakyghost:
What firmware were you running before flashing that?

Did you observe the command output? Did you maybe save it?

Do you mind running it again and then posting the log?

mobile post
[One (M8) Android Development] Kent21:
I'm flash fw 3.28.401.6 50mb htc firmware collection for different mike 1986. Sorry, I cant flash because i'm going out :D
[One (M8) Android Development] Sneakyghost:
I'll do a bit of stereotyping here just for my own entertainment.

The way you write suggests you must be italian. Backed up by the fact that you refer yourself to Clark Kent. Italians often use Super Heros as their Nicks and Avatars. Furthermore, you have no clue what you actually did but you seem to be quite ok with it. Then you hint at going out which is again something i frequently hear from italian dudes. Phone in a somewhat strange state, but, well, go out anyway and drop a smilie showing a friendly confused face.

Hmm. Am i right? :laugh: :D :angel:

(Your Profile says you are from Vietnam, but anyway....)

Well man, to be honest, you screwed up somehow. To fix this, you should re-run the fullwipe package. I am sure it will be OK then. And when you do, post the log. You can put it into

Hide Tags

to make it less big.
[One (M8) Android Development] Sneakyghost:
Ok cool. Do this:

1.) Boot to bootloader (press power and volume up until the display goes dark, then quickly slide the finger to vol. down button)

2.) Download my Task Batch Script from Post #3 and set it up. Just double click the archive, it will extract to C:\Android.

3.) Double-Click the Tasker_1.2.1.bat Batch Script. It will offer you 24 commands readily available. You don't need to worry much about typing.

4.) Choose command 3 and you will be in a normal commandline interface (pretty pink to make it less scary :D )

5.) now place my firmware zip into C:\Android\com folder and rename it to only "rom.zip"

6.) Now type into the pink command window:

htc_fastboot oem rebootRUU

.

7.) Device now boots into the RUU Mode black screen / silver HTC logo. Now type:

htc_fastboot flash rom.zip log.txt 2>&1

8.) Now the flashing process will run into a text file. Both streams Standard Out and Standard Error should be redirected into a text file. The file "log.txt" should be in C:\Android\com afterwards and contain the full flash log. The problem is, with redirecting both streams you will not see anything happening in the command window. Once the green bar on the phone screen reaches nearly 100% you can run another command

htc_fastboot reboot-bootloader

to get back to regular bootloader. There you should now see the correct info.

I didn't try this redirecting into a textfile myself yet, i just googled it. If it fails, you can do like i do:

1.) open a normal command prompt (not my task script because that has a fixed window size and you wont be able to see the full log) by pressing SHIFT and RightCLick on the folder C:\Android\com (download and install my batch script like suggested before).

2.) type

htc_fastboot oem rebootRUU

3.) type

htc_fastboot flash rom.zip

4.) Wait until its finished (Success! in console) and then type

htc_fastboot reboot-bootloader

5.) Right-Click in the console window and choose "Select All", then just press CTRL+C for copying, and open some text file and press CTRL+V to paste it there...

wow that is one hell of a noob spoonfeed lessen huh? Basic Command Prompt stuff...

Go play with it. You will benefit from it in the future.

Wow by the time i wrote up this sh!t you figured yourself. Guess i underestimated your ability :D Cool stuff.

The flash Process is 100% OK. 3 of four SBL images are bypassed, one flashes, all other images flash too. Just the way it should be.

Where do you read this 3.28.401.3 info from now? Are you looking in your ROM under Settings/Info/Software? That will only tell you the ROM's version, not the firmware version.

Use my batch script command 12 to run fastboot getvar all to report the correct firmware info.
[One (M8) Android Development] Kent21:
i remember when i at my company, don't connect my phone with pc. i'm download recovery.zip, flash through hboot. after i arrive home, i flash recovery.img through adb. i think i flash recovery continuous make my phone is crazy. so this time, i decide flash your Zip's and post log for you. all thing are ok. It's my problem and i don't understand me. Sorry my bad english and tks alot for your help :o