yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Sneakyghost:
Header error? You broke the zip. Do as I recommend in post 5. Use 7zip. Use "zip" profile. Use compression level "normal".

[EDIT]

Thanks to [MENTION=5872674]Flippy498[/MENTION] for putting together another decent stock base, this time it's Asia-HK (708 or speaking CID's: this one covers HTC__622

and HTC__044)

Recent additions​

And a little reminder. I am looking for as many answers as possible. I will leave this Survey open till HTC 10 release day, April 12th. Thanks.

Survey Link​
[One (M9) Android Development] ibrahimijk:
Hi, Tried 7zip from windows. With normal. And tried flash. Now its showing

Looks like this is stuck here. I waited for 15min. Please guide if I can reboot or what... Just don't want to brick the phone.
[One (M9) Android Development] Sneakyghost:
If that last line "INFOHOSD" really is the last line (no more info lines past that one?), I would guess the writing process didn't actually start and you are safe to reboot.

I would reboot if it was my phone.

Sadly, I have no information on these numbered HOSD error outputs. HOSD is that third OS on your M9. It is kind of a micro-linux kernel I believe. That means, there is a LOT more diagnosis and error output than with traditional fastboot and bootloader flashing. I have not gathered any information on HOSD output. However, the fact the output ends with "INFO" rather than with something like "Error flashing" or something, means to me, it wasn't actually writing yet. So, no harm done.

Now, you need to figure out what is wrong. Can you show me the output of "fastboot getvar all" please? Remove your IMEI from the output. Oh, and there's different info depending on whether you run that command in bootloader or in download mode... I forgot which one I need to see. Post both :D

[EDIT]

I found your getvar in the ROM thread. Thanks. T-Mobile US according to your MID? I assume you are S-OFF?
[One (M9) Android Development] 99hokie:
Hello all! Not sure if this is the right thread for this question, but does anyone know if I can get TMOUS wi-fi calling on the HTC MM Developer RUU using TMOUS DE 3.35.111.14 firmware? I am, of course, on TMOUS. Thanks in advance!
[One (M9) Android Development] Black-FR:
I don't think, that T-Mobile DE, support Wi-Fi calling yet.

If you want to try it, then you need to use the T-Mobile-US firmware and matching ROM.

But as said, I'm pretty sure, that it won't work.
[One (M9) Android Development] 99hokie:
I can't seem to find the RUU for these TMOUS DE MM ROM, only the HTC DE MM ROM and the firmware numbers don't match. Any suggestions where I can find that RUU?
[One (M9) Android Development] Black-FR:
As said, T-Mobile de, won't help...

You would need T-Mobile US, as they got the feature.

But like I suggested before already, I don't think, that you will get Wi-Fi calling on T-Mobile de.

Gesendet von meinem HTC One_M8
[One (M9) Android Development] Sneakyghost:
Hello,

according to your profile, you are near Denver in the USA. That means, Tmo-DE is not for you. It is German T-Mobile and quite different as its more similar to the WWE (401) versions than to the Tmo-US versions.

Tmo-DE = Germany, regular GSM, UMTS and LTE frequencies, no VoLTE, no WiFi calling, no SMS&MMS over WiFi (although Tmo-DE is just now introducing these features in Germany, first only for Iphones, then for Sammy and Microsoft, and eventually for HTC but it will need entirely different firmware and that will be a while. HTC won't have that ready anytime soon, I reckon, just FYI, German readers).

Tmo-US = United States, has regular GSM, UMTS and LTE frequencies plus "AWS" band for LTE (3G according to Wiki though, not entirely sure) usage, also has code for VoLTE, WiFi calling, SMS&MMS over WiFi.

So, if your situation is: location US, carrier TmoUS = you need TmoUS firmware (531). The DevEdition (1540) won't do. It will only provide regular features and does not support AWS as far as I know.
[One (M9) Android Development] xfoneguy:
If I don't want to wait for the AT&T Marshmallow OTA, is this the correct firmware to use or ?? Thanks!
[One (M9) Android Development] Sneakyghost:
Which?
[One (M9) Android Development] shalpp:
I've recently installed the 3.39 firmware for TMOUS, and for the life of me can't get the SIM card to read properly. Tried it on Android Revolution and ViperOne. They're built on the 3.35.401 firmware, would using a newer firmware like that cause any trouble like that?
[One (M9) Android Development] Black-FR:
If you flash the viper, then select T-Mobile during the aroma installer and it will work.
[One (M9) Android Development] shalpp:
Probably unrelated to the firmware at this point, but after trying to re-install viper this time around setup wont' even start, stuck on the location accuracy pop-up with no way to advance
[One (M9) Android Development] Black-FR:
You use the latest twrp version?

And you did flash the ROM with full wipe?

I would suggest, you check the md5 of your ROM zip, then check your twrp version and update it to the latest.

So that you then could flash the ROM again, with full wipe and don't restore any data via twrp.

As the restore would be the same, as a dirty flash.

Anyhow, wrong thread for this.
[One (M9) Android Development] shalpp:
Reflashed the firmware and the ROM, same as before, and all of a sudden everything is working. I'm confused, but thanks for your help
[One (M9) Android Development] Sneakyghost:
Happens to the best of us. Often. It's random. Before you haven't tried at least two times there's no reason for concern.

______________________________

http://venomroms.com/htc-10-review-poll-giveaway/ - Anyone here planning on M10? Then head over to our website. I put together 3 articles I came across today and thought I'd share because they aren't too bad.
[One (M9) Android Development] fcreeves:
Help! I flashed firmware M9_3.35.401.12_NoWipe_TWRP2871b1.zip and now I boot to a blue screen for Recovery and Download mode.

I only have Bootloader mode? I am S-OFF and Unlocked

What are my options?

No TWRP... Kinda Freaking out?
[One (M9) Android Development] Black-FR:
The MD5 of the downloaded firmware is correct?

The flash process was successful?

What's the output in your cmd?
[One (M9) Android Development] fcreeves:
Laptop Rebooted since then. This is a friends phone...that I am responsible for.

The flash was successful.

I can run some commands with Tasker 1.30.bat.

I tried an ATT RUU. Battery less than 30%! The phone reboots itself every few minutes...and back to bootloader.

Is there a bootloader command I can run to flash the device, partitions and recovery all in one? I can flash recovery with the Tasker 1.30, but I can get to recovery?

I need a complete flashing process from bootloader?
[One (M9) Android Development] Sneakyghost:
Well the phone boots and gives you access to download mode, bootloader and recovery. You're fine then. Just run a RUU made for your device and it will put everything back to stock. Where's your issue exactly now? Lack of options due to not knowing enough? Then it's either: "read more" or "this is not for you".

I explicitly mention, again and again, that I'm not providing support in this thread in order to keep it short and readable. The initial posts are long enough and cover about 80% of the possible issues. I'm only interested in completely new issues not covered and anything else odd or peculiar turning up. Stuff to find out and tinker with. Yet not the recurring, endless flash problem solving that's entirely caused by a lack of understanding your device. For such, join an existing thread in Q&A or create a new one, there (please check first. Doubles are very much unnecessary).
[One (M9) Android Development] fcreeves:
Awake, long night.

This phone was obtained off of eBay already S-Off. I simply flashed the same firmware that used on my phone... Already S-Off was less steps to take.

I already tried RUU. Phone was rebooting approx every 2 minutes and couldn't get to a 30% charge required for a RUU.

I apologize for my panic issue. I have not bricked a device since the Sensation that had a listed firmware that was not compatible. I'll update what happens after work today. I'm not convinced that this phone was 100% when obtained as I didn't do anything out of the ordinary. I know not to flash late at night? ...but did it as I thoughtit was a cookie cutter procesx with less steps. My fault. I've already accepted the fact that I might be paying for HTC to repair this device if it doesn't take a charge.

Once again, I apologize for taking up thread space. This one is what it is. The panic is over. I'm in the acceptance stage.

Edit: Phone won't take a charge. Gotta send back to HTC and just do the complete process that I am accustomed to. I am definitely convinced that this phone was not 100% when he received it used from eBay? I am confident everything will go as planed when the replacement come$ in.
[One (M9) Android Development] nicholasknicks:
Can someone please help flashed the latest firmware on my M9 successfully and it booted just fine. However when i turned it off now i cant power it on again no matter what i try
[One (M9) Android Development] jollywhitefoot:
Try holding power and both volume buttons for a long time (at least a minute). That usually works for me.
[One (M9) Android Development] nicholasknicks:
Everyone else is telling me the same but it aint working
[One (M9) Android Development] Chezbel:
Something else to try. Hold the phone under a bright light while holding down power for 10+ seconds.

EDIT: I just found a wiki "how to" article about this so I might as well add it

https://www.google.com/url?sa=t&rct...D-TePPKMVR7jkg&bvm=bv.119745492,d.cGc&cad=rja
[One (M9) Android Development] xunholyx:
I'm not positive, but I am pretty sure that this method is irrelevant after the M7.
[One (M9) Android Development] steven817817:
hey im probably late to answer this. But on my M9 when mine would not turn on no matter what i read that i needed to hold volume up and volume down at the same time for at last 5-15 minutes. And after I did that it came back on. ATT had already looked at my phone and coulndt get it to turn on either and they were gunna warranty it. But then I found that and it fixed it! My phone is still working today.
[One (M9) Android Development] Kumo2121:
So I messed up and bricked the phone to the point where it booted up saying no OS. Anyways, I was able to fix my phone by using recovery mode, mounted 1.12.617.6 Dev Edition.zip and installed it through TWRP. While my phone works now, I have this issue where my phone turns off as it enters download mode, shuts off the dark htc screen. As such, using RUU.exe or fastboot oem rebootRUU will result in my phone turning off. S off US unlocked 1.12.617.6. converted from S On At&t 1.27.502.5. Recovery mode and bootloader works as does my phone overall. Also I noticed my CID and MID are blank when I check them using fastboot oem readcid and fastboot getvar mid. Fastboot getvar all results in:

bootloader) version:0.5

(bootloader) ramdump-mode:false

(bootloader) variant:MTP eMMC

(bootloader) secure:yes

(bootloader) version-baseband:

(bootloader) version-bootloader:

(bootloader) max-download-size: 0x20000000

(bootloader) partition-type:cache:ext4

(bootloader) partition-size:cache: 0x10000000

(bootloader) partition-type:userdata:ext4

(bootloader) partition-size:userdata: 0x621000000

(bootloader) partition-type:system:ext4

(bootloader) partition-size:system: 0xd9000000

(bootloader) serialno:HT5B2BE03702

all:

finished. total time: 0.077s

Looks very empty to me?
[One (M9) Android Development] jerimy386:
When we will have the new firmware for att, marshmallow is roll out for M9 two days ago?
[One (M9) Android Development] Leebert225:
Just posted today I beleive, see http://www.htc.com/us/support/htc-one-m9-att/news/ I'm sure [MENTION=1102297]Sneakyghost[/MENTION] will add this to the list.

Thanks.
[One (M9) Android Development] deepsouth06:
Question, I currently have 3.35.401.12 installed on my phone. I'm trying to get back to ATT stock (need to send phone in), but I am unable to run the ATT RUU (guessing cause my firmware). Can I roll back to 2.11.502.18 firmware and then retry running the RUU_HIMA_UL_L51_SENSE70_ATT_MR_Cingular_US_2.11.502.18.exe (RUU)?
[One (M9) Android Development] Sneakyghost:
Better post detail about what went wrong with the RUU.

I'd think you might simply have forgotten something. In some scenarios you might need to relock bootloader first for instance. In other scenarios, you'd be successful by using the image zip from the RUU with the sdcard method...
[One (M9) Android Development] Sneakyghost:
How about no ETA questions on XDA?

I'll tell you anyhow: when my family is safe and healthy, my work done, I have slept a little and then another grace period of seven days after the last ETA question.

3.38.502.12 FullStock

3.38.502.12 NoWipe_TWRP3020

Please test and report back - cannot test myself, no time.
[One (M9) Android Development] deepsouth06:
So being on International Firmware and trying to rollback to ATT firm ware wouldnt make a difference? Currently in the process of downloading the latest ATT Firmware from HTCs site. I believe that would but me on a lvl playing field of 3.38.502.12.

---------- Post added at 11:22 AM ---------- Previous post was at 10:37 AM ----------

Ok so trying to run the RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.12.exe (with locked bootloader and s-off) i am getting an "ERROR [155]: UNKNOWN ERROR" not very helpful but that is what i am getting. just seen the following in a word doc. wondering if this could be because of my firmware?

ERROR [155~159]: IMAGE ERROR

One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
[One (M9) Android Development] Sneakyghost:
This is from Post #3 in this thread:

Maybe that helps.
[One (M9) Android Development] deepsouth06:
so from that, it seem like i may need to go back to SUPERCID?
[One (M9) Android Development] bacon612:
I am supercid and changed my mid to 1s and I couldn't flash this either.
[One (M9) Android Development] latinohot:
same here with the twrp version of the 3.38....

don't know what else to do now
[One (M9) Android Development] bacon612:
I haven't had a chance to yet but I'll bet if you change your mid to att, it will flash.
[One (M9) Android Development] Sneakyghost:
I seriously hope you didn't try to flash this with TWRP...
[One (M9) Android Development] darkenedpath:
Maybe set your cid and mid to the original "at&t" one it should be?
[One (M9) Android Development] Sneakyghost:
Find a qualified answer starting with this post: http://xdaforums.com/showthread.php?p=66904477

The gist of it is, from quickly skimming through that thread, that you'll need to be on the last preceding firmware for hboot to be able to decrypt the zip.

You cannot jump versions as the decryption key in the aboot needs to be updated before.

What you can try is to separately flash the new aboot beforehand, then flash the RUU. This will only work S-OFF though. I uploaded the AT&T packages yesterday. You could open any of the two zip's and delete everything inside except aboot.img and android-info.txt (open with 7zip, delete, save). Then flash that zip in fastboot, possibly twice, then run the RUU again.
[One (M9) Android Development] alaa.85:
HTC One M9ew

[MENTION=1102297]Sneakyghost[/MENTION]

I have HTC One M9ew

software version is 3.10.61

Baseband version is 1.1506

Build Number is 1.50.1405.5

Software Number is 1.0.0.M9ew

Can I install ViperOneM9 4.3.0 ? as i read in the web site that firmware must be M and i still on Android 5.0.2 !

if i cant install the said ROM, what i should do to install it ?

Thanks in advanced
[One (M9) Android Development] Sneakyghost:
Sorry this is not for M9ew. Only M9.
[One (M9) Android Development] nkk71:
you're talking about CID not MID, please dont confuse the two, changing MID (modelid) is not very wise unless you know exactly which one you want and

works

.... and if it not, there's a very very high chance you will completely brick your phone.

not sure if the decryption keys changed between those version (actually, I'm quite sure they didnt), but the best way to find out, is to get the log.... since this a RUU.EXE, the [failed] logs will be C:\ruu_log\

that will give you some insight what's going on.... cause it will show the exact commands the EXE is running and it's output

... kinda like manually using adb and [htc_]fastboot from the command line, it's much more "informative"
[One (M9) Android Development] Sneakyghost:
Yea mate although my guts tell me that 155 is the typical ATT "never jump versions" crap caused by the key updating with every version. You reckon no? What else could it be?
[One (M9) Android Development] latinohot:
finally had a good couple of hours to re-learn how to use adb and such,

long story short, I'm rocking my HTC ONE M9(ATT) with the developer edition 3.35 Combined NoWipe https://www.google.com/url?q=https:...669000&usg=AFQjCNHBToVahT12KhIAqR0gKLYsc7WxZQ

Thank-you so very much for the detailed instructions, so I now have LeeDroid rom MM
[One (M9) Android Development] bacon612:
Typo. Apologies. My cid is 1's and I actually haven't touched my mid. Its still T-Mobile. I may try changing cid to att and reattempting the flash this week. Will report back if I do and have success.
[One (M9) Android Development] jerimy386:
Getting desperate for the newest ATT firmware... I don't want to use the RUU and start over...
[One (M9) Android Development] Kratos90:
Be desperate, but whatever you do, don't look one page back....
[One (M9) Android Development] jerimy386:
This comment was so sneaky that I didn't read it...

:good::good::good::good::good:

---------- Post added at 10:51 PM ---------- Previous post was at 10:50 PM ----------

Thank you for make public my stupidity :good::good::good:
[One (M9) Android Development] jerimy386:
Installed after paying $ to sunshine for s-off, then flashed as instructions:

C:\adb>fastboot flash zip M9_3.38.502.12_NoWipe_TWRP3020.zip

< waiting for device >

target reported max download size of 800000000 bytes

sending 'zip' (65805 KB)...

OKAY [ 4.082s]

writing 'zip'...

(bootloader) HOSD CL#682052

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

(bootloader) start@20

(bootloader) aboot_signed.img@100%

(bootloader) adsp.img@100%

(bootloader) cota.img@100%

(bootloader) cpe.img@100%

(bootloader) hosd_signed.img@100%

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

(bootloader) modem_st1.img@100%

(bootloader) modem_st2.img@100%

(bootloader) pg2fs_ship_signkey.img@100%

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

(bootloader) rcdata.img@100%

(bootloader) recovery.img@100%

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

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

(bootloader) sdi.img@100%

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

(bootloader) radio.img@100% <------------- successful

(bootloader) sensor_hub.img@0%

(bootloader) sensor_hub.img@0%

(bootloader) sensor_hub.img@10%

(bootloader) sensor_hub.img@20%

(bootloader) sensor_hub.img@35%

(bootloader) sensor_hub.img@45%

(bootloader) sensor_hub.img@55%

(bootloader) sensor_hub.img@65%

(bootloader) sensor_hub.img@75%

(bootloader) sensor_hub.img@90%

(bootloader) sensor_hub.img@100%

(bootloader) sensor_hub.img@100%

(bootloader) tp_MXM11876.img@BYPASS

(bootloader) tp_SYN3351.img@BYPASS

(bootloader) Update zip file OK

(bootloader) end@Done

OKAY [ 63.067s]

finished. total time: 67.153s

Reboot and notice that I didn't have signal, went to the phone info, and the baseband were not displayed, updated to latest version of ViperOne and still no signal, I should flash again the radio from the previous version? Or try to flash the same?

Standalone...
[One (M9) Android Development] 5m4r7ph0n36uru:
Flash again. Do it twice as the successful message is missing and thus I guess it hasn't been flashed completely and correctly. Then use htc_fastboot so you don't get this max downside size "error".
[One (M9) Android Development] jerimy386:
Thank you for the response, I made the following:

After thinking about the process, I flashed the TWRP 2.8 as recovery, used fastboot to flash again the firmware but this time used the fullstock, reinstalled viperone using wipe, not worked, then, repeated the process, and now gladly is working... I always make this process with confidence since I have done it several times.
[One (M9) Android Development] king200:
I want to flash the full RUU for 3.38.502.12,

"0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R2_Radio_01.01_U11440261_56.02.50306G_2_F_release_427846_signed.zip".

I downloaded the RUU from http://androidruu.com/?developer=M9

Would the "android-info.txt" contained in the firmware of this thread work?

I want to flash the firmware but I don't know how to make 'android-info.txt' and I could use some guidance to make a correct 'android-info.txt'. My phone is S-Off and CID can be changed to 11111111 or whatever is needed. My search of this thread got me this post http://xdaforums.com/showpost.php?p=60417720&postcount=4 but I am lost.

CURRENT:

(bootloader) kernel: lk

(bootloader) product: htc_himaul

(bootloader) version: 1.0

(bootloader) imei: 3572280601xxxxx

(bootloader) version-main: 3.39.531.7

(bootloader) boot-mode: download

(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA12000

(bootloader) cid: T-MOB010

Android-info.txt in downloaded zip:

modelid: 0PJA10000

cidnum: HTC__001

cidnum: HTC__J15

cidnum: HTC__031

cidnum: HTC__102

cidnum: HTC__A07

cidnum: HTC__032

cidnum: HTC__M27

cidnum: HTC__016

cidnum: HTC__002

cidnum: HTC__Y13

mainver: 1.32.401.15

aareport:1

btype:1
[One (M9) Android Development] Sneakyghost:
iirc you can convert a TmoUS device to international, but only partially. I think the radio frequency range is different on the TmoUS device. That is not changeable. And before you ask: no, swapping radio firmware won't change that, as the frequency config is stored elsewhere, not in any firmware image.

You should stick with TmoUS firmware, which you can recognize by the number 531 in the version number. All TmoUS firmwares have the 531.
[One (M9) Android Development] king200:
Thank you for the prompt reply. The frequency range is OK for me.

I can't just flash back the Tmous radio firmware? I can't get WWE?
[One (M9) Android Development] Sneakyghost:
What do you actually want? Why this mess?
[One (M9) Android Development] king200:
When I flash a custom ROM, i.e. LeeDrOiD One M9 V8.2.5, I cannot get USB debugging (ADB) to recognize the phone and neither will Windows file transfer. If I deselect debugging, the pc can recognize the phone. With Venom Rom, either ADB or pc file transfer but not both together. With stock, everything works exactly as it should. Tried another kernel (Clumsy) and would not recognize sim.

I've had great luck with M8/AT&T x WWE and LeeDroid and thought that Tmous with WWE might solve the problem. Clearly, Tmous is different.

I don't think many people recognize the problem.
[One (M9) Android Development] Sneakyghost:
Well one thing I can tell you for sure: firmware will do absolutely nothing about adb. Adb is purely Android.

Firmware could maybe have an influence on fastboot, if there's a large version gap, it can sometimes lead to issues. Not so much adb though.

You can try what I said about the drivers, play with different ones. Afaik I have adb and mtp functioning side by side like you mentioned, on Viper. I am going to check that tomorrow if I don't forget.
[One (M9) Android Development] king200:
Viper does work adb and mtp functioning side. I have not had same experience with other roms.
[One (M9) Android Development] Sneakyghost:
But didn't you say that your adb is NOT working on Viper when MTP is enabled?
[One (M9) Android Development] AeroB:
Hi I don't know what I need to flash !

Been talking to venom support as I falshed a WWE version from here and I wanted to make sure I was safe to update to MM. I was not though as i had a firmware version he had never seen before. They told me to post my output here ! I am s-off BTW! please help as I really want Marshmallow :(