yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] jbfountain:
I thought the Wi-Fi only preference was there so it would not use the cellular network, so why would this be a issue . If you want it to switch from Wi-Fi to cellular then the proper setting would be Wi-Fi preferred, and if you don't want to use Wi-Fi at all then the setting would be Cellular only. It seems to me that it's working properly if it's not switching to cellular when Wi-Fi only is selected or am I not understanding the issue here . I'm just happy that the T-MOBILE firmware is now available.

Cheers

I Truly Enjoy XDA-Developers with this Fabulous HTC One M9
[One (M9) Android Development] Sneakyghost:
I reckon there's virtually no point in discussing that here. I have answered a question regarding firmware changelog, which is already a bit weird because we usually don't even get changelogs, but this time I had something from our beta team to share.

If things work on TMUS or not is now to be seen for everyone and I reckon a discussion of that is best moved to the general forum. Or T-Mobile US forum or whatever.

Its not that I am not interested but this is gonna end with 10 pages of back and forth what everybody thinks, if I open it up, so I am going to ask to move that somewhere else.

Sorry and thanks for understanding.
[One (M9) Android Development] jollywhitefoot:
Here is the OTA update package. If I have time tonight, I'll piece together the no wipe and full stock packages from your 1.32.502.31 packages.

https://drive.google.com/file/d/0B8OH6sFjVE1leUQza2FLdDM0cTA/view?usp=sharing
[One (M9) Android Development] Behold_this:
You thought wrong quite frankly and this isn't the place to discuss it. I was very clear and succinct of what the issue is and this is a new issue that wasn't on the previous firmware or base. Your data connection should always reenable when you leave your WiFi network regardless of which option you choose. The options in the wifi calling menu are ONLY for calls and not data. Your data connection should re-enable on mobile whenever you leave wifi network no matter what setting! I'm sorry you don't understand that. Let me be clear 1 more time wifi calling options have nothing to do with data and should not kill your data when Wi-Fi connection is lost and never did on previous bases!
[One (M9) Android Development] jbm0329:
I have a T-Mobile SIM-unlocked, with S-Off and an unlocked bootloader and I am on AT&T, but I want to install the latest update. I realize that I can update it by installing the full ROM from HTC but that would wipe the phone. I saw on another forum where someone provided the OTA only.

I see on post 525 that there's supposed to be a download in post #1 but I only see a link to a Google Drive account and those links go to files that are extremely small in size. For example, the one that says 'no wipe,' it's 62MB.

What's the best way to install the full OTA without wiping the phone? Would I just use ADB? I can to change the name of the file to 0PJAIMG (may be a bit different) so that it won't show 'modified'?

Thanks
[One (M9) Android Development] bigp951:
md5 does not match

Those files are the firmware which is esentially the same thing as an ota... If you are running AT&T why don't you change you cid and mid and convert to an AT&T model(since you're concerned with getting an update)?

You can get everything you need here . There is no way that I know of to recieve an ota without a wipe once you have modified the system image. Best thing to do is use titanium backup, google and htc backup before you wipe... This way you can get most of your data back...

---------- Post added at 06:20 PM ---------- Previous post was at 06:08 PM ----------

@sneakyghost Saw that the tmobile firmware was up but noticed that the md5 was different on the google drive page and the afh page. Is this something you are aware of and is it safe to flash?

166616bda6bc383b09163b9a7ecad77e google drive

7836585297e980493dd24d7a467449c4 afh
[One (M9) Android Development] jbm0329:
I actually converted to the Developer Edition but it only gave me the H+ and I didn't like that, especially when I had the 4G icon on AT&T before I converted to the Developer Edition. T-Mobile's and AT&T essentially have the same bands from what I could tell (maybe them having different modems had an affect on it... if you know something else that I could try and get 4G/LTE while on the Developer Edition, please let me know); I went back to the T-Mobile ROM since I hated having the H+. I'd love to sell it as a Developer Edition but I'd want to say it works perfectly on T-Mobile/AT&T (which means it should have 4G on both).

Believe it or not, we got the OTA today... we didn't have to use ADB or anything else; I'm pleasantly surprised. Not sure why that would be the case when I'm on a different carrier unless OTAs are allowed because it's S-Off and has an unlocked bootloader. My son was on WIFI and he checked for an update and there it was... Shocked but happy.
[One (M9) Android Development] bigp951:
There is another thread here if you wanted to try to add the bands . I have a true dev edition straight from htc and an att edition I got off of ebay. So far the att ed has been att, dev ed, and tmobile. My signal actually went up after flashing the tmo RUU and returning to stock and taking an ota.

Personally I wouldn't attempt to take an ota if my system wasn't stock. That;s an easy way to end up with a brick. Maybe you should convert it to att model. It's not hard and you have already done it once... I do know the thread says att and dev ed are identical hardware. But I'm unaware of any differences on a tmo version.
[One (M9) Android Development] jbm0329:
I'll check out the forum that you provided. I read where one guy had an AT&T version, converted it to Developer Edition (DE), moved to T-Mobile and he dropped to 3G/H+ too, so I presume something's happening with the modems when they are converted to DE.

We've already accepted the OTA and it works just fine. I had to get rid of the heat ASAP so hopefully, the heat will be fixed with this update. This has been the only thing that's keeping us from really enjoying these phones.

Thanks again...
[One (M9) Android Development] Sneakyghost:
This all so doesn't belong here...
[One (M9) Android Development] jollywhitefoot:
At least they're talking about the right phone....
[One (M9) Android Development] bigp951:
Sorry dude... Did you see my post about the md5 being different for the T-Mobile update?
[One (M9) Android Development] Sneakyghost:
Yea sorry corrected. I accidentally copied the MD5 from the DevEd package. No problems. Thanks for reporting!
[One (M9) Android Development] Sneakyghost:
The filename is not the original HTC OTA filename anymore. I can't tell which previous version that OTA was meant to update. I am not going to re-learn ruuveal. I don't want to mess with RUU's at the moment. I am stuck with the M8 Viper ROM at the moment and tomorrow Windows 10 starts rolling out. RUU is nothing I want in between. Not at all.

Can you find me the exact name of the AT&T OTA so I can see which version it was mean to update? It should say something like "2.6.502.16-1.32.502.31" the first part being the new version and the second part being the previous base this can be run over. I assume I even guessed those numbers right but I need confirmation, or else I cannot make sure the ZIP will be up to my self-imposed safety rules.
[One (M9) Android Development] jollywhitefoot:
post-build=htc/himaulatt_cingular_us/htc_himaulatt:5.1/LMY47O/556209.16:user/release-keys
post-timestamp=1435031298
pre-build=htc/himaulatt_cingular_us/htc_himaulatt:5.0.2/LRX22G/506785.31:user/release-keys
pre-device=htc_himaulatt

The name of the file was OTAPkg.zip. (/data/data/com.redbend.vdmc/files/fumo/OTAPkg.zip)

Inside the OTAPkg.zip were:

firmware.zip
fotaBoot
META-INF
preload
system.new.dat
system.patch.dat
system.transfer.list

What I sent you was the contents of firmware.zip.

Do you want me to:

A) Send you the complete OTAPkg.zip file (900 MB)

B) Send you nothing because you either have all you need OR you don't feel like messing with this

C) Take your 1.32.502.31 full stock firmware, update it with the new firmware files from the 2.6.502.16 OTA and send you the complete package with the updated files. I can do the same with the no wipe package.
[One (M9) Android Development] Sneakyghost:
Wow, that is really weird, that they went back to that old FUMO and OTApkg thing on AT&T. I just read about that today in a 3 year old Forum (some old HTC device i was checking something on) - they used that path 3 years ago. On the INT version of the M9 the OTA package still goes to /data/data/com.htc.updater and is named "OTA_HIMA_UHL_blahblah_versionnew_versionold".

If you feel confident to not mess up the FullStock package you can of course build that. Its no wizzardry, just being careful.

Make sure, that:

- 1.32.502.33 is the base folder you are putting the new images in. Overwrite existing ones. All files.

- Double check after that, that there are no doubled files (very rarely, HTC changes the name of some image around, leaving you with a duplicate when you do this C/P job) Example: RUU: recovery_signed.img; OTA: recovery.img - delete the older version. check for each image.

- Most often, the base package on M9 has android-info.txt, android-info2.txt and backup-android-info.txt. The OTA only has android-info.txt. copy the version lines and all switches that are set in the OTA version (e.g. eraseonflash:cache) over from the NEW android-info.txt to android--info2.txt and backup-android-info.txt so they all tell Fastboot/Aboot/ARUWizard the same. No contradicting info in there, NEW goes before old.

- ZIP the whole lot up with 7zip please! NOT winrar (has caused many flash fails in the past!) and definitely NOT WinZIP!. As compression level choose "Normal" - Aboot can read "Save", "Fastest", "Fast", "Normal" but not "Maximum" and "Ultra".

- Please stick to my naming-convention and use CT's TWRP 2.8.7.1 B1 from here: http://xdaforums.com/devdb/project/dl/?id=13383

For the NoWipe same rules apply. Removal: Boot, RamDisk, DT, SP1 (splash), Recovery, dzdata_xx.img and dzdata_xx.hdr. Add: TWRP as linked above, rename to "recovery.img".

Finally, flash that to your own device before you hand it to anyone else. Since you don't want to break your phone, that will force you to be careful (my rule :D ).

Once you are sure it is good, send them to me and I will up them here for everyone and credit you. Thanks a TON mate!

That is what I want here, people contributing and learning ;)

That is how I learned my stuff (which is less than everyone thinks anyway, I am a potato).
[One (M9) Android Development] jollywhitefoot:
A little clarification here...

1.32 FULL STOCK AT&T android-info.txt AND android-info2.txt is

modelid: 0PJA11000
cidnum: CWS__001
mainver: 1.32.502.31
aareport:1
btype:1

The android-info.txt file from the 2.6 OTA is

modelid: 0PJA11000
cidnum: CWS__001
mainver: 2.6.502.16
hbootpreupdate: 3
nohardreset: 1
eraseonflash: system
eraseonflash: userdata
eraseonflash: aboot
eraseonflash: adsp
eraseonflash: boot
eraseonflash: cpe
eraseonflash: hosd
eraseonflash: hyp
eraseonflash: radio
eraseonflash: recovery
eraseonflash: rpm
eraseonflash: pmic
eraseonflash: sbl1
eraseonflash: sdi
eraseonflash: tz
eraseonflash: rfg_1
eraseonflash: sp1
eraseonflash: cota
erasepartition: ddr

Are you saying both of these files should get all of the switches even though the original files contained no switches?

Meanwhile, the 1.32 version of backup_android-info.txt contains more switches than the new file and different switches than the new file. (new switches bold, changed are red)

modelid: 0PJA11000
cidnum: CWS__001
mainver: 1.32.502.31
[b]btype:1
aareport:1[/b]
hbootpreupdate: 3
nohardreset: 1
[b]resparseoption: -S800M[/b]
eraseonflash: cache
eraseonflash: system
eraseonflash: userdata
eraseonflash: aboot
eraseonflash: adsp
eraseonflash: boot
eraseonflash: cpe
eraseonflash: hosd
eraseonflash: hyp
eraseonflash: radio
eraseonflash: recovery
eraseonflash: rpm
eraseonflash: pmic
eraseonflash: sbl1
eraseonflash: sdi
eraseonflash: tz
eraseonflash: rfg_1
eraseonflash: sp1
[b]eraseonsoff: frp
eraseonsoff: absolute[/b]
[COLOR="Red"]erasepartition: cota[/COLOR]
erasepartition: ddr

Thanks.
[One (M9) Android Development] Sneakyghost:
Yeah bud gimme gimme pleeez, just drop in irc or hangouts
[One (M9) Android Development] Sneakyghost:
Looks all perfect to me bud. [MENTION=2605798]nkk71[/MENTION] you gonna post me a link I can drop into the sheet or what? I can now do the firmware myself otherwise. Now that the stupid Win10 Update decided to lag out on me since hours...
[One (M9) Android Development] nkk71:
both wipe and no_wipe are in dropbox, upload whenever M$ stops harassing you :p

f0d4647e2a6804c57425d6ca0900d65c *M9_2.6.502.16_FullStock_rename_to_ROM.zip.zip
dceaef01a0d2c4045c9dbd816acab001 *M9_2.6.502.16_NoWipe_TWRP_2871b1_rename_to_ROM.zip.zip

EDIT: why are they .zip.zip .... huh :banghead:
[One (M9) Android Development] Sneakyghost:
AT&T 2.6.502.16 NoWipe and FullStock is on Sheet

I just added them to the sheet.

Can't be arsed to make proper post right now.

At everyone: AT&T 2.6.502.16 is on Google Download-Sheet.

By the way: this is all [MENTION=2605798]nkk71[/MENTION] work. He put it together and flashed it. All good. You are fine flashing it.

Lazy me goes back to messing with Windows 10 now. Thanks for patience and blah blah.
[One (M9) Android Development] nkk71:
I've been on "M9_2.6.502.16_NoWipe" firmware for almost 5 hours (even though I'm on a "normal" GSM device)... downgraded from 2.10.401.1, and everything working fine,

Bluetooth, WiFi, 3G/4G, even calls, yay
[One (M9) Android Development] Smokem_I:
Thanks Sneaky and nkk71!

Sent from my HTC One M9
[One (M9) Android Development] VelosCohagen:
Does anyone know if there's a 2.x firmware (2.x.161.x) for Vodafone M9 with cid VOPAP102 ?
[One (M9) Android Development] Asselalf:
not yet...you have to wait for the official release
[One (M9) Android Development] grv00711:
with the M9_2.7.531.6_NoWipe_TWRP_2871b1_rename_to_ROM.zip i can flash in twrp then dirty flash venom 3.5.0 and install tmobile settings.... i am running 2.10.401.1 international ..i am on tmobile usa ..with venom 3.5.0. currently
[One (M9) Android Development] Behold_this:
Dude, read the OP! firmware can never ever be flashed through TWRP!!! All the name of that zip means is that it includes the TWRP recovery as opposed to the stock recovery or no recovery.
[One (M9) Android Development] grv00711:
thats what i thought .sorry!
[One (M9) Android Development] grv00711:
unable to fastboot flash the> M9_2.7.531.6_NoWipe_TWRP_2871b1_rename_to_ROM.zip.....looked though venom rom.. and this thread ..i am developer unlocked ..super cid11111111 .currently on 2.10.401.1 with venom rom 3.5.0.
[One (M9) Android Development] donmarkoni:
Wait... Wait for it... I'm reading your mind... Looking through your eyes.... I don't need more info, I'll just read your mind and see what commands you wrote and what output you got...
[One (M9) Android Development] grv00711:
will try to send it telepathically..standby .. adb reboot download..fastboot oem rebootRUU..fastboot flash zip rename....i will get the error momentarily for the flash ..thanks /////. cannot open file

C:\adb>adb reboot download

C:\adb>fastboot oem rebootRUU

... OKAY [ 0.048s]

finished. total time: 0.048s

C:\adb>fastboot flash zip t7.zip

sending 'zip' (25970 KB)... OKAY [ 2.586s]

writing 'zip'... INFOHOSD CL#576582

INFOERR lzipv2_init : Cannot open file /dev/fastboot_download_k

INFOySeVs

INFOERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea

INFOder

INFOERR [SD_UPDATE_ERR] sddownload failed: 22

INFOERR Update zip file failed.

INFOERR ZIP ERROR, exit read zip loop

INFOUpdate zip file OK

INFOERR ZIP ERROR CODE, 22

INFOend@Done

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

finished. total time: 4.697s

C:\adb> tried with out using >>fastboot oem rebootRUU<< no luck
[One (M9) Android Development] Behold_this:
Possibly a corrupted download did you verify the md5?
[One (M9) Android Development] donmarkoni:
Got it... You are skilled at telepathy... ;) Strange error... Have you checked md5? Looks like broken zip file to me.
[One (M9) Android Development] grv00711:
i did will.. will do again..does not match md5 ..that was the download from the spreadsheets ?
[One (M9) Android Development] nkk71:
is "t7.zip" supposed to be "M9_2.7.531.6_NoWipe_TWRP_2871b1_rename_to_ROM.zip"

cause mine shows about 64MB not 25MB as seen above
[One (M9) Android Development] donmarkoni:
Zip got broken downloading. Re-download until you get the right md5, it's a must.
[One (M9) Android Development] grv00711:
yes .i renamed thanks for the proper zip!!

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

will do !!

---------- Post added at 05:36 PM ---------- Previous post was at 05:30 PM ----------

success !!!! thanks guys .. now dirty flash venom and select t-mobile options..
[One (M9) Android Development] theloneranger08:
I can flash 2.10.401.1 which is international firmware to a developer edition phone right?
[One (M9) Android Development] xunholyx:
If you go superCID, or convert to a WWE/International CID, yes.
[One (M9) Android Development] theloneranger08:
Great thanks!
[One (M9) Android Development] metalgod862:
Sorry if this is a dumb question but if I understand correctly, I can just download the firmware update from HTC directly and follow their directions instead of what was posted here if I am using the AT&T version of the phone?
[One (M9) Android Development] Behold_this:
HTC doesn't post firmware zips. They post full RUUs. That means they include system, pre-load data and firmware and will completely wipe your internal storage. Nothing at all like the packages included here.
[One (M9) Android Development] d-pak:
10-4. I will switch back to my M7 as primary device and test against M9 this weekend. Other road this week and I'd hate to be out of a device all week and also rather not use a mac for this.

If I change the CID in the "android-info.txt" file that within the "0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426167_signed.zip" to "CWS__001" and rezip it, I am assuming that it breaks the "signed" nature of the zip by altering the hash which would not cause it to load.

It is worth a shot. This would be a lot safer if we had a "back-to-stock" way for ATT or HTC posted the RUU. I have asked HTC support for the ATT RUU and still awaiting a response. I am afraid they might just say use your "uh oh" instead of "here is the official RUU".
[One (M9) Android Development] Behold_this:
Correct. You cannot modify the package in any way. That will break the signature. Since you are s-on, you must have a signed package.

BTW AT&T's camera update should be available this Friday and the RUU for it will be posted the following week on HTC's AT&T m9 download support page, here:

http://www.htc.com/us/support/htc-one-m9-att/news
[One (M9) Android Development] Sneakyghost:
The thread will be maintained by me from now on. OP transfer is in progress according to Moderation ([MENTION=2746542]Stephen[/MENTION] and [MENTION=4592755]coal686[/MENTION]).... when? Err.. whatever. I am off to bed. Thanks for helping.

Unfortunately I am back to work from tomorrow on (Vacation ended). So it'll be kept hanging in limbo for a few before i can redo it my style and start putting in new info for the M9, which was worked out by a number of nosy people during the past 2 weeks.
[One (M9) Android Development] Clark Joseph Kent:
You want it, you got it! Done! And the other Posts, in this thread #2, #3...
[One (M9) Android Development] coal686:
I was just waiting for your confirmation via PM, but it looks like the Judge already took care of you. If you need anything else from us, feel free to ask.
[One (M9) Android Development] Sneakyghost:
I thought I had replied to you, Coal686, but I see its all done and well. Thank you for your assistance guys.

Much appreciated.

[EDIT]

Interesting trivia noticed by [MENTION=918378]Basil3[/MENTION]: apparently the new Aboot structure leads to the Google Drive activator.apk not recognizing the phone's lockstate anymore - you can now claim your 100GB free drive space even with an unlocked bootloader. Maybe Google also changed their policies. Who knows. Who cares.
[One (M9) Android Development] Cryosx:
Good to be S-Off again :)

:( Forgot WIPE mean't wipe everything off sdcard
[One (M9) Android Development] muzza19751975:
will this method work

will renaming the firmware to 0P6BIMG.zip work ? much easier way
[One (M9) Android Development] Behold_this:
As the thread title clearly states, this thread is in support of flashing firmware via FASTBOOT. That being said, to answer your question, no that won't work. That zip name is for the m8 not the m9. The m9 is a different model phone with a different model number and so of course it would use a different name on the zip. It should be named, 0PJAIMG.zip, however, that is not what this thread is about currently.
[One (M9) Android Development] clsA:
I tried the google activator and got the error "This Account cannot Redeem the Offer Please choose a different account" I went on HTC Chat and they said they activated it.

now when i check all that changed was when the 100 gig of storage expires (I already had it with my M8) .. they did not add another 100 gig, they just extended it.
[One (M9) Android Development] Sneakyghost:
FFMPG for Splash Screen conversion

Hahahaha Oh well...

Anyhows, in case anyone is looking into custom splash screens now that we have s-off, my converter in the batch tool is not working. The script even contains some errors with block addresses, so please don't use the function to pull the stock splash to disk. Its no good. And the function to flash a splash back to phone currently gives me headaches too bu that has something to do with SELinux and ADB on the Viper ROM.

I am trying to use this FFMPG parameter string to convert the raw partition pull: ffmpeg -f rawvideo -pix_fmt rgb565 -s 1080x1920 -i mmcblk0p15 -f image2 splash1.png and am getting error:

[image2 @ 030e82d0] Could not get frame filename from pattern
av_interleaved_write_frame(): Input/output error

Anyone came across a fixed splash converter for the M9 already?

[EDIT]

Nevermind I decided to play with pushing images to NAND because [MENTION=2632943]Whiskey103[/MENTION] was nice enough to just do it without trying to convert RAW to image first and see if the image properties are still the same... :D

I was a bit worried about blindly pushing an image, assuming the parameters haven't changed from the M8, but it all went well.

Modifying Aboot also works just as well as the old hboot. Nice. I like being S-OFF again. It was a hard time, the past three weeks :D

​

The pictured modified Aboot is a 1.32.206.15 version and a demonstration of it being still modifiable like we were used to with the hboots. I will not offer "red-text-removal" and the like.

401.15 and 206.15 Aboots are nearly identical except for some leading encrypted block and a slightly differing trailing block, by the way. So I think it would probably be no problem at all if O2__102 and HTC__001 and such would swap out firmware components. Just FYI.
[One (M9) Android Development] JagSem:
I'm using a stock 1.32.161.7 rooted with s-off. I'm yet to change the cid number but it is currently vodap001. What do I need to do in order to get the latest firmware? Im pretty confident in following the steps in this thread as ive updated firmware before on previous htc phones. Im just unsure as to which zip file I can flash.

Any help appreciated. Thanks.