yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Chezbel:
If first flash is fine, why are you flashing again? It's not a rule to flash twice, only do that if the first time falls.
[One (M9) Android Development] Sulphy:
Thanks... but i was following the guide, which showed multiple flashes, and i just wanted to make sure :)
[One (M9) Android Development] Sneakyghost:
Your log is interesting indeed. First time I see bootloader actually TELLING you to do a hardware reset :D

The log is pretty straight-forward, don't you think? All bootloader and security relevant images flashed fine, then a reboot is required to continue the flash. Do just that.

But PLEASE do use my Task Script because it contains the correct htc_fastboot.exe (which will actually auto-reboot on error 90!).

Once the (correct) htc_fastboot auto-reboots your device (upon receiving error 90), your phone will boot right back to android - you do NOT want that. You want to go back to download mode or bootloader. So, observe the flashing process closely and once it reboots, immediately press VolDown and keep holding it until you're back where you were before. Then htc_fastboot should be continuing the flash on its own. If it doesn't, relaunch the procedure (just arrow-up on your keyboard will get you the last command in console again).
[One (M9) Android Development] PaoloMix09:
Does anyone know which one is the exact 1.40 firmware I could flash on my T-Mobile US HTC One M9 variant?
[One (M9) Android Development] qriozum:
[MENTION=1102297]Sneakyghost[/MENTION] has not yet updated the title of the thread, but it is already in the database new firmware, designated:

v1.40.401.5 with TWRP 2.8.6.4 :)

Link to download the second post of this thread.

regards

q.
[One (M9) Android Development] Sneakyghost:
1.40.401.5 and 1.32.531.33 published

Yea I didnt post in the thread because its untested and from an unsigned modified firmware I got. Did for myself and whoever finds it.

Guess now the secret is out :D

Well guys I have that zip running on my phone just fine but flashing was a b!tch, it wouldn't work with ARUWizard (the newer one) because it kept throwing a USB error once the Error 90 turned up and the phone auto-rebooted (new htc_fastboot.exe auto reboots on error 90, remember?). htc_fastboot basically forces the reboot but ARUWizard "sees" a lost connection for some reason and reports a USB Error 171 and aborts.

So, if you flash that, put phone into download mode, then run fastboot flash zip nameof.zip as usual, hit arrow up on your keyboard as soon as the screen of the phone goes dark and launch the flash command again. Fastboot will wait for the rebooting phone and continue flashing then.

----------------------------------------------------------------------------------------------------

|________________________________________________________|

Had to look into the T-Mobile US RUU today and thought I could as well make some zips out of it while I'm at it.

Find them - untested - in the link sheet.
[One (M9) Android Development] Behold_this:
If you want to keep your T-Mobile specific functions like wifi calling you need to stay on the T-Mobile firmware which actually DOES work on Viper 2.0
[One (M9) Android Development] Chezbel:
Has anyone else with an HTC Dot View case tried 1.40.401.5?

After flashing the no wipe version, if I tap on the case, which should cause the screen to turn on the phone reboots. I tested that 3 times and the phone rebooted every time for me. I flashed back to 1.32.401.17 and it's working fine.

I don't have time to experiment right now, but I'm wondering if it could be the sensor_hub.img, but that is only a guess.

[MENTION=550917]sneaky[/MENTION], in your experience do you think it is safe to remove the sensor_hub.img from the .zip file and flash it that way? I may try that later today when I'm back home.
[One (M9) Android Development] mick_soul:
Which base is your rom, 1.40.401.5 or 1.32.401.17?

Old based roms force reboots when turning screen on, with newer firmware.

Its a known problem. You have to update your rom too.
[One (M9) Android Development] lyldz:
in fastboot mode

C:\Windows\system32>fastboot flash zip Firmware_xx.zip

error: cannot load 'Firmware_xx.zip'

give me error whats wrong :(
[One (M9) Android Development] WreckTangle:
Do you have the firmware zip in system32 folder? If not, browse to folder where zip file is in command prompt and try the command again

Sent from my ViperOneM9
[One (M9) Android Development] Chezbel:
I'm using LeeDroid and that ROM base is the older 1.32.401.17. Thanks for that info, it saves me from wasting time on useless experiments. :good:
[One (M9) Android Development] donmarkoni:
[highlight]EVERYBODY: ATTENTION![/highlight]

Old firmware (1.3x) and old kernel (for example EX0.3) will work good on old and new base ROMs, as will do new FW (1.40) and new kernel (stock 1.40) on both.

Any mixing of old and new FW and kernel will cause reboots on screen off/on and maybe some other issues.

So, it has nothing to do with anything in particular, but the combination on stuff, and especially with [MENTION=1102297]Sneakyghost[/MENTION]'s FW packs, those are perfect. Well, he's German. ;)

BTW, Sneaky, you can report me for bold highlighted text, if you find it inappropriate. :D
[One (M9) Android Development] Jwtiyar:
iam s-on , how i can upgrade firmware?
[One (M9) Android Development] Sneakyghost:
Wait for HTC to update you -.-
[One (M9) Android Development] Jwtiyar:
but its rooted :(
[One (M9) Android Development] Sneakyghost:
Look, if you've got no clue about the difference between root and S-OFF,I suggest you go do some research. I see you can type here, then you can type into Google search too. This isn't a Q&A thread.
[One (M9) Android Development] liam_davenport:
Use RUU when update is available
[One (M9) Android Development] eban44:
I am having CID issues, trying to flash 1.40 to an rooted/S-off ATT M9.

I pulled my MID and CID and I get MID:0PJA11000 and CID: CWS__001

So, I unzipped this 1.40 firmware and edited the android-info.txt file, at first I just added in my CID, next I edited the MID to match mine.

I zipped the extracted files again, but I keep getting the following, when I try to flash.

C:\Users\Eric\Desktop\HTC M9 Root>fastboot flash zip M9_1.40.zip

target reported max download size of 800000000 bytes

sending 'zip' (47440 KB)...

OKAY [ 4.431s]

writing 'zip'...

(bootloader) HOSD CL#506785

(bootloader) ERR [SD_UPDATE_ERR] Parse zipped android_info fail!

(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14

(bootloader) ERR Update zip file failed.

(bootloader) ERR ZIP ERROR, exit read zip loop

(bootloader) Update zip file OK

(bootloader) ERR ZIP ERROR CODE, 14

(bootloader) end@Done

FAILED (remote: 14: fail to flash via downloadzip)

finished. total time: 6.526s

I don't see error 14 on the error page, my guess is when I re-zip the file something messes up. To re-zip, I am selecting all the files in the folder and then in windows 8.1 going to share and zip. It then makes a zipped folder, which I rename to M9_1.40 and place it back in my fastboot directory.

I am wanting to go to 1.40 as it is needed for the newest Android Revolution 7.1 ROM. I am currently on 1.32 and AR5.2

Thanks
[One (M9) Android Development] Sneakyghost:
While the error handling post is indeed out of date, one info still holds true:

Please use 7zip to compress, with "normal" profile. Other zipping methods have down to cause such errors countless times before.

But also that solution is less reliable than the SuperCID solution, which is also mentioned for error parsing Android-info. Please look it up.
[One (M9) Android Development] Tecardo:
Also check if you edit correctly, could be that you made some mistakes

Gesendet von meinem HTC One M9 mit Hilfe von XDA Forums Pro.
[One (M9) Android Development] eban44:
Thanks, the SuperCID cmd worked perfectly and was simple. haha
[One (M9) Android Development] vegetaleb:
Hello!

I have S-ON and CID_J15 can I flash the International 401.5 non-wipe from your downloads?
[One (M9) Android Development] Behold_this:
Nope
[One (M9) Android Development] vegetaleb:
I thought I just needed that my CID is listed in the international version no?
[One (M9) Android Development] Sneakyghost:
S-ON won't flash unsigned zips, only original HTC signed zips.
[One (M9) Android Development] grv00711:
?i need to rename 1.40.401.5 + Firmware + NoRedText ABOOT + RUU to something .zip to flash in fastboot.. sorry for the redundant question.. device not found ? have all necessary drivers ?
[One (M9) Android Development] dawexxl:
I installed thy wwe no wipe 1.40.401.5.zip . Everything is OK but the download menu still sees the old firmware. it is normal? viperone2.00 install and everything runs ok.thx for answer
[One (M9) Android Development] Stephen:
Thread has been cleaned at OP's request.
[One (M9) Android Development] kruuth:
Hi guys. I'm getting this error when I flash:

C:\Android\com>htc_fastboot flash zip rom.zip

sending 'zip'... (61680 KB) OKAY

sending time = 4.547 secs

writing 'zip'... (bootloader) HOSD CL#506785

(bootloader) ERR CID not matched

(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED

(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7

(bootloader) ERR Update zip file failed.

(bootloader) ERR ZIP ERROR, exit read zip loop

(bootloader) Update zip file OK

(bootloader) ERR ZIP ERROR CODE, 7

(bootloader) end@Done

FAIL7: fail to flash via downloadzip

FAILED (remote: 7: fail to flash via downloadzip)

Execution time is 7(s)

This is an at&t phone in dev mode with everything off. When I getvar all I get the following:

C:\Android\com>htc_fastboot getvar all

(bootloader) kernel: lk

(bootloader) product: htc_himaulatt

(bootloader) version: 1.0

(bootloader) imei: 357227060889019

(bootloader) version-main: 1.32.617.30

(bootloader) boot-mode: download

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA11000

(bootloader) cid: BS_US001

all:

Execution time is 0(ms)

What am I missing here?
[One (M9) Android Development] Golv:
Please see the file android-info.txt in your rom.zip and compare your CID and MID with the contents of TXT file.
[One (M9) Android Development] Behold_this:
The error you posted is telling you exactly what is wrong. Your CID does not match the list of compatible CIDs within the firmware.
[One (M9) Android Development] vegetaleb:
If you are S-OFF just convert your cid to supercid
[One (M9) Android Development] kruuth:
How do I convert my CID?
[One (M9) Android Development] grv00711:
have the batch tool on windows 7 32b machine .. trying to understand this ..new to htc m9 ..have developer edition s-off .unlocked...running venom 1.9.1 with elemental kernel / would like to upgrade the firmare and flash venom 2.1.0 .. i placed the 1.40.401.5 HTC One M9 Latest • No Red Warning • No Wipe zip into the <com> folder drive c android then i open batch tool connect the m9 usb debugging on ..computer sees device ..so i get choose task ..choose task 1? so i get bootloader on m9... next do i want to choose 3 for fastboot promt ?get the purple window in c:\android\com ..now i try fastboot flash zip 1.40.401.5-Firmware-noredtext i drag file into cmd promt ..then i get error cannot determine image file name for zipc;\android\com\M9_1.40.401.5_NoWipe_NoRed.zip... i am at a loss ..really am trying to figure this out ..nobody else seems to have a problem updating the firmware ..this is day 3 of trying to do this 3 different computers ..windows 8.1 .windows 7 64bit. now windows 7 32 bit..also tried ubuntu ..help
[One (M9) Android Development] Chezbel:
http://lmgtfy.com/?q=convert+to+super+cid
[One (M9) Android Development] kruuth:
Ok I flashed the supercid I found on the first page. I'm getting this now:

Execution time is 0(ms)

C:\Android\com>htc_fastboot flash zip rom.zip

sending 'zip'... (61680 KB) OKAY

sending time = 5.109 secs

writing 'zip'... (bootloader) HOSD CL#506785

(bootloader) GPT is up-to-dated. [17408]

(bootloader) Perform pre-update

(bootloader) start@20

(bootloader) aboot_signed.img@100%

(bootloader) adsp.img@BYPASS

(bootloader) cota.img@BYPASS

(bootloader) cpe.img@BYPASS

(bootloader) hosd_signed.img@100%

(bootloader) hyp-8994-1.img@100%

(bootloader) modem_st1.img@BYPASS

(bootloader) modem_st2.img@BYPASS

(bootloader) pg2fs_ship_signkey.img@BYPASS

(bootloader) pmic-8994-1.img@100%

(bootloader) rcdata.img@BYPASS

(bootloader) recovery.img@BYPASS

(bootloader) rpm-8994-1.img@100%

(bootloader) sbl1-8994-1.img@100%

(bootloader) sdi.img@100%

(bootloader) sensor_hub.img@BYPASS

(bootloader) tp_MXM11876.img@BYPASS

(bootloader) tp_SYN3351.img@BYPASS

(bootloader) tz-8994-1.img@100%

(bootloader) radio.img@BYPASS

FAILFAIL90 hboot pre-update! please flush image again immediate

FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)

For "hboot-preupdate" response, restart the same procedure for device FA53XYJ182

83...

< waiting for device >

sending 'zip'... (61680 KB) FAILED (status read failed (Unknown error))

Execution time is 18(s)

C:\Android\com>htc_fastboot flash zip rom.zip

sending 'zip'... (61680 KB) FAILED (data transfer failure (Unknown error))

Execution time is 1(s)

C:\Android\com>htc_fastboot flash zip rom.zip

sending 'zip'... (61680 KB) FAILED (data transfer failure (Too many links))

Execution time is 1(s)

Ideas?
[One (M9) Android Development] vegetaleb:
It's the same for m9 but you have to be in "download mode"

http://sakitechonline.com/how-to-change-the-cid-number-of-your-htc-one-to-supercid-m8-or-m7/
[One (M9) Android Development] liam_davenport:
[MENTION=3090397]kruuth[/MENTION] Did you redownload, Try different usb ports/cables?
[One (M9) Android Development] kruuth:
Can I reboot safely at this time?
[One (M9) Android Development] Black-FR:
You need to reboot to the download mode again and then flash the firmware zip a second time.

---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------

As you could see, in your previous log, you currently only made the pre-update.

Now you need to go back to the download mode, as stated above and execute the command again:

htc_fastboot flash zip rom.zip
[One (M9) Android Development] kruuth:
Yep. That did it. Thanks.

---------- Post added at 05:55 PM ---------- Previous post was at 05:55 PM ----------

Does changing the cid back do anything?
[One (M9) Android Development] Sneakyghost:
Oh God. I think I'm gonna call it quits on firmware. Why am I making my life hard and write up everything around firmware flashing if people still gonna bomb the thread with the same old questions? Again: this is not a Q&A thread and I'm having a hard time following it cuz I'm quite busy and I don't want pages full of support crap here.

You've got two options: either run a question on the official Q&A forum (or add to an existing thread there respectively), or second: just read the damn info out there.

Even HTC has now introduced HOSD on the HTC one M9, which is a kernel, and enables a full system assessment (HOSD= hybrid operating system discovery) - it's sort of a micro Linux specialized on detecting what's on your phone and then throw verbose errors (full human readable errors).

Just too bad when humans don't read.

Should automatically generate a video of the error and fix.
[One (M9) Android Development] grv00711:
sorry!
[One (M9) Android Development] j to the 4n:
Getting Error Code 1337. Please help.
[One (M9) Android Development] Ducati Scar:
Hi, my CID num is BM___001 and firmware version is 1.32.666.30, S-Off and with TWRP installed. Can I flash the 1.40 International zip?
[One (M9) Android Development] WreckTangle:
First go supercid, then you can flash international firmware package from this thread.

Sent from my ViperOneM9

---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------

[MENTION=1102297]Sneakyghost[/MENTION] do you know what those 2 tp_ image files are for? They always seem to get bypassed. Can't remember if I ever seen those getting flashed.

Sent from my ViperOneM9
[One (M9) Android Development] donmarkoni:
If I may... Those are touch panel drivers. FW packages have all possible files, but only appropriate and needed get flashed. Meaning: only driver for your model of touch panel will be flashed, if it's not already on that version, which is obviously the case here. Mine didn't update too.
[One (M9) Android Development] vegetaleb:
LOL ;)
[One (M9) Android Development] PaoloMix09:
Thanks, I'll be just waiting on the official one. I'm actually on LeeDroid and all T-Mobile specific functions work just fine.
[One (M9) Android Development] 030575753:
if i am on .15 base (intenational rom S-OFF), and i want to flash the "Combined, NoWipe ZIP's" (Cause i dont know "Full Stock, WIPE ZIP's" if it touch the "radio" part)

did i need to flash 1.32.401.17 first and to 1.40.401.5.

Or can be directly to flash 1.40.401.5

Cause dont know the "Combined, NoWipe ZIP's" is including the "previous OTA"?

Solved by j to the 4n Reply on Viper Thread as said Combined, NoWipe ZIP's is Combined with previous OTA

Correct me if iam wrong

Thanks

But can i flash the Full Stock, WIPE ZIP's directly, does it touch the radio part?
[One (M9) Android Development] jcb1985:
hi, looking for some help. Tried flashing the 1.40 firmware and i get an error message that is not listed. I think it is trying to install the firmware to my SDcard? not sure. i am s-off with root and bootloader unlocked. error message i get is this.

C:\Users\JON\Desktop\fastboot>fastboot flash Firmware M9_1.40.401.5_NoWipe_NoRed

.zip

sending 'Firmware' (46476 KB)...

OKAY [ 3.275s]

writing 'Firmware'...

(bootloader) HOSD CL#506785

FAILED (remote: 35: SD_PARTITION_NOT_SUPPORT Firmware)

finished. total time: 4.285s

If it is the SD card that is the issue, how would i get it to install to the internal memory. thanks in advance.
[One (M9) Android Development] omaison:
Hello,

I have try to flash the firmware 1.40.401.5 with the batch tool.

The first time I have the FAIL90 and my phone have rebooted. When the phone was returned in download mode, fastboot have try to resend, but I have this message:

sending 'zip'... (61680 KB) FAILED (status read failed (Unknown error))

So, I have rewrite the command, and I have this message:

sending 'zip'... (61680 KB) FAILED (data size is too large(61680 KB) for device to download ZIP file 'ROM.zip'

I have rewrite one time the command, and now it was blocked on that: sending 'zip'... (61680 KB)

and on the screen on my phone, the downloading has stopped at 51%

Was can I do now to restart the dowloading?

The button of my phone make nothing.

Thang you for your help.
[One (M9) Android Development] ParanormalBat:
I understand the "Combined, NoWipe ZIP's" will not wipe my internal storage, but will it wipe my data (apps and their data)?

Sorry for the question but I'm on my mobile and can't (properly) search.

Thanks for the help

EDIT: And any idea how to remove the annoying red text on boot? :)
[One (M9) Android Development] user602:
The no wipe zips will not affect your apps and their data; this info is in the OP.

You will have to search elsewhere for red text removal. IIRC, Sneaky does not support it in his threads because it is a sensitive operation requiring hex editing.

Edit: BTW, search works just fine on mobile if you use a browser in desktop view. :good:
[One (M9) Android Development] blueberry60:
Press Power and Volume Down keys and put the device to download mode again (don't reboot) and type same command again,flashing process will be completed,don't worry.
[One (M9) Android Development] ParanormalBat:
Much better idea.

Thanks

Found out I was searching for the wrong thing for the red text (searching for hboot instead of aboot)
[One (M9) Android Development] omaison:
Thank you for your reply.

Sorry I was not to home since yesterday.

All is ok. But the htc_fastboot from the batch tool will always stop on my PC with Windows 8.1 64 bits. But with the fastboot from Google it work good.

Thank you for you help.
[One (M9) Android Development] Sneakyghost:
Google Fastboot is ok for basic things. However, the new htc_fastboot is modified (by HTC) for working with larger-than-2GB files and their new compression standard. Also, it supports the output from HOSD which It is adjusted to follow HOSD errors - it can (and will by default) auto-reboot on error90, which the generic won't. These are the observable signs of HTC's modifications. I am concerned there might be vital under-the-hood changes which could influence the flashing process. This is why I suggest to rather use HTC fastboot. The new one.

And yes, it does crash on Windows 8.1 x64 - It might help to play with HTC Sync Manager to obtain the newest drivers and then try again (make sure that "playing with sync manager" is removing it, downloading a newer copy, installing it again, then removing it again).
[One (M9) Android Development] omaison:
Ok. thanks for the explanation.

And for the crash, I will try your solution for the next time I need to flash a new firmeware.

Thank you.
[One (M9) Android Development] iElvis:
Do you know if there's an OSX version? Because the only one I've been able to find is Windows.
[One (M9) Android Development] blueberry60:
So you mean try on HTC_fastboot flash.... commands, update HTC sync manager for latest drivers and uninstall HTC sync manager for preventing crash on Windows 8.1
[One (M9) Android Development] Sneakyghost:
I've seen a few experimental Linux-variants float past me but never bothered to pursue those and their development. I am not familiar with Linux.

According to what I could gather, there's a chance that the Linux binaries might be functional on OSX, since that, apparently, shares a lot of common ground with Linux.

However, not my territory at all. If I happen to come across anything useful, I'll post it.
[One (M9) Android Development] Sneakyghost:
No. I am not describing how to fix the crash. I was just saying it is necessary to remove HTC Sync Manager because it has a habit of blocking/interrupting the ADB/Fastboot USB connections and thus interfere with flashing. Although HTC apparently designed HTC Sync Manager to go along with RUU's and certainly not cause issues for RUU's, it actually does. So its better to remove it. But its also quite certainly not causing the fastboot crash. That would much rather just be slack in HTC's coding department, if i am to take a guess.

My htc_fastboot crashes have just disappeared. Guess it was incompatible with something on my PC that has now gone away. I never really cared to find out what crashed fastboot because those crashes seemed rather harmless. They never happened in a critical flash stage.

I suggest you don't worry too much about it either.
[One (M9) Android Development] Joloxx9:
Does anybody tried 1.40.401.8?
[One (M9) Android Development] aka120:
Yep, running good so far, although I'm not sure what's been changed since 1.40.401.5, but it seems(?) the lag issues with the swipe/wake up gestures are now gone. I can't say for sure that has been fixed but I haven't experienced any since flashing 1.40.401.8.

Scratch that, still getting the wake up lag issue.
[One (M9) Android Development] Behold_this:
HTC posted fastboot compiled for Mac OSX and it can be downloaded from HTCdev.com

**edit HTC link:

https://www.htcdev.com/process/legal_fastboot_mac
[One (M9) Android Development] exocetdj:
This is just the .8 firmware I take it?
[One (M9) Android Development] blueberry60:
It's very unwilling situation during flashing 1.40.401.8 at ,I couldn't catch power and volume keys to type same command second and enter download mode,device reboots very quickly besides removed htc sync manager.
[One (M9) Android Development] donmarkoni:
No need for power button, volume down is enough to press to boot to DL mode again. ;)
[One (M9) Android Development] ParanormalBat:
I'm using the 1.40.401.8 firmware right now and haven't yet come across any of the issues in the 1.40.401.5 firmware. Charging works fine so far and the gestures lag is the same since I got this phone. Bootup seems faster, but bootdown is a little slower.

Wondering why it was taken down though.