yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Sneakyghost:
Hi!

I am currently uploading new files because after the transition of the thread from Herwegan to me I needed to redo a few things.

Since you are S-OFF, you can download the 1.32.401.17 in a few minutes and test that for me? It is a FULL zip meaning its like the RUU without system. It will fully convert your phone to 401 International GSM, which works fine on VODAP and will remove your bloatware (located in the apppreload.img file). I am pretty confident it will flash once you are S-OFF and SuperCID but like I said, I am struggling hard to catch up on everything (there is SOOO much info to be computed!) and haven't even done the conversion of my O2 device yet.

If you are willing to contribute you can flash the new file and report back what you see and if there is just ANY error message at all, I definitely want to see it please. Copy/paste the fastboot output log.

What I know already (worked out today with the help of the SunShine team geniuses): the new download-mode boots a third kernel (system has its kernel, recovery has its kernel, download mode has sort of a kernel now too) which is the hosd.img in every OTA and RUU. This Kernel provides much more detailed error output in fastboot. Which is nice. If you see any error prefixed with "SD_ERROR..." it is from this kernel and fastboot (SD meaning System Detection). These errors are much more "verbose" and give better clues of what is happening to you.

Observe the flashing process. The first step always is a query of HOSD with a return of your current build environment (returning the Google Build). The next step is always the aboot (download mode i believe, replaces hboot), which is often followed by a pre-update fail. In a pre-update fail scenario, a reboot to download mode from anywhere will automatically trigger the required re-flash. This is new and different in the new htc_fastboot. It has a new toggle to suppress the automatic re-boot and re-flash, but if you dont explicitly specify that, it just reboots and (unfortunately) boots to system. Reboot to download mode then and wait for the automatic reflash to happen.

After this, its pretty much business as usual. All the other images get flashed one-by-one. Some might trigger another reflash, if so, it boots to system again and you need to manually force it back into download mode again.

I think with stock recovery flashed, the automatic reboot returns you to download mode automatically, but with twrp flashed, it will reboot you into android system instead.

Please remember, since I don't provide a full RUU, there might be a broken system on your NAND after the flash and no boot to system possible. Have some custom ROM at hand which you can sideload/adb push/copy to sd.
[One (M9) Android Development] JagSem:
That's a bit more work than what I was expecting lol. I'm willing to test things but what I really wanted was the 1.32.401.15 so I could, along with other things, start flashing roms based on .15. I really need to sit down and start off with that, which I will at some point now that I better understand my options.

If no one else volunteers in the next day or so I'm willing to find some time and help out.
[One (M9) Android Development] Sneakyghost:
Well I'm not gonna help anyone if there's not some return. This is not a support forum. Its XDA. In fact, I'll ask moderation to remove posts which contribute nothing.

Threads should, if ever possible, stay short and with little clutter, so reading them is not a major pain. People look here for info but start asking questions because reading threads is just awful when there's just clutter.

So, help out by reporting what you experience if you ever can.

No need to test the conversion with the 1.32.401.17 zip though. I just did. Mine was 1.32.206.15 and I used my FullStock zip to change it to 1.32.401.17 and then restored my Viper. Works with some hiccups: if you use ARUWizard (my "FUU") or fastboot manually (fastboot and RUU are essentially doing the exact same thing), the phone will auto-reboot into Android-System when the pre-update error 90 happens. It is meant to boot back into download mode though, so the RUU or fastboot fail. One needs to manually boot back to Download Mode then in order for the process to continue.

This does not happen while a stock recovery is installed. Its only happening when the phone runs with a custom recovery.
[One (M9) Android Development] Stephen:
Moderator Information

The OP of this thread has asked for some posts to be removed. Please keep all posts on topic regarding the firmware provided in this thread.

Stephen
[One (M9) Android Development] Chezbel:
Hi Sneaky, I just got my M9 and glad to find this thread and see you back in action.
[One (M9) Android Development] JagSem:
I rewrote the CID 1111111, flashed incrementally up from .7 to .17, and found that there was no trouble aside from those issues mentioned on the first page of this thread. Namely FAIL90. It did exactly as sneakyghost said from .15 to .17 as in that it rebooted system and in order to continue the process, reboot into download mode for it to finish the writing the img files.

Nothing much to add, just a reaffirmation of what sneakyghost said to those contemplating .17 update.
[One (M9) Android Development] Sneakyghost:
Good to see you here. Hope to see valuable input from your side again ;)

Open up the RUU and see the many, many new images in there, some of which have no counterpart in the cat /proc/emmc read-out. Some make sense, some don't- if you find anything useful, do share, please.

[EDIT]

Recently added to the download sheet:​

1.32.401.8 - initial release for international

1.32.401.15 - update for international with camera and thermal fixes (those are in the ROM though. Not in the firmware!)

1.32.401.17 - new update for international with unclear updates.

1.32.206.15 - update for O2_UK/DE/etc with camera and thermal fixes (those are in the ROM though. Not in the firmware!)

1.32.161.7 - initial Vodafone release

1.32.502.31 - Updated AT&T release.

[EDIT 2]

POLL added

[MENTION=4782292]mick_soul[/MENTION] has kindly tested flashing packs without the apppreload image for us. It works fine. I added a poll to find out whether you want to have the NoWipe packages with the preload image or not.

To elaborate:

Before the HTC One M9, the preload stuff used to be a folder in /data much rather than have its own partition. This has changed now. HTC is now delivering the carrier bloatware in a separate partition, which I could include or not. I don't really care much. The point of my "NoWipe" packs was though, to preserve everything on the phone that is NOT firmware in the widest sense. So I remove Splash Screens, Kernel and its dependencies, Recovery and the /data wipe files. The logical choice therefore would be to preserve the carrier bloat partition as well (not include the image file in my packs). It would 1.) make the zips smaller, 2.) not touch your carrier store (it doesn't affect installed apps, its only noticeable when you factory reset the phone, then the contents of the preload image are being installed!). Including it would pretty much just make sense for people who would like to swap from one carrier to another, and THAT is best accomplished with the full wipe packages anyway. Those include the preload.

This is my path of thought for now. Does anyone see ANY reason to leave apppreload.img in the NoWipe packages?

Please use the POLL up at the top and NOT the comments. Thank you!
[One (M9) Android Development] user602:
Thank You!

[MENTION=1102297]Sneakyghost[/MENTION]

If you'll forgive a bit of off-topic, I'd like to publicly thank you for your work here on XDA. Among other things, I've trusted my devices to your combined firmware packages since M7, yet I've neglected to donate to you...

This round of Sunshine is on me: 20091319CH359861K
[One (M9) Android Development] metalgod862:
If I don't care about my data getting erased can I use HTC's method to update to the latest firmware, then flash viper rom over it in TWRP?
[One (M9) Android Development] donmarkoni:
If you don't wanna use [MENTION=1102297]Sneakyghost[/MENTION]'s FUU packages, why you bother people here, please go ask HTC. Thank you.
[One (M9) Android Development] Sneakyghost:
my full wipe zip is doing the same job as HTC's RUU with the added benefit of a smaller download, due to system.img being removed. So it won't give you a stock ROM but it will wipe and give you everything else.

Of course, if you're still S-ON this option isn't available for you and you'll have to dig up a RUU for your model.

For that, you can try Androidruu.com or HTC's ROM download page (US models only).
[One (M9) Android Development] grv00711:
your zips are spot on!
[One (M9) Android Development] timnyce:
Has anyone have a signed stock recovery 2.10.401.1 plz? Mostly appreciate any help. Thanks
[One (M9) Android Development] Asselalf:
Open the latest Fullwipe.zip and look for recovery.img

But next time you should ask in General section

Gesendet von meinem HTC One M9
[One (M9) Android Development] jollywhitefoot:
I'm pretty sure he was asking because there isn't a full stock zip for 2.10.401.1 yet.
[One (M9) Android Development] Asselalf:
Oh ;) https://www.androidfilehost.com/?fid=24052804347787729

Gesendet von meinem HTC One M9
[One (M9) Android Development] Rolando88:
Hi guy's,

I'm trying to get back to stock to get the latest OTA, because im s-on and wants the latest firmware.

I downloaded 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.8_Radio_01.01_U11440261_56.02.50306G_2_F_release_425571_signed.zip

The strange part is everytime i want to copy it to my internal/external sd card on my phone i get error message:

Cannot copy item

The device either stopped responding or has been disconntected

I need to change the file extension and then i can copy the file to my internal/external sd card without issues.

But then i renamed it to 0PJAIMG.zip

I reboot the phone in download mode

The i try with volume up to start flashing 0PJAIMG.zip

Security checking failed NOT_FIND_SMART_IO

FILE /mnt/media_rw/ext_sd/0PJAIMG.zip

Pres Volup to start flash

But then i get error message:

Failed: -2, 19: Fail to flash via Downloadzip

Failed: -2, 19: Fail to flash via Downloadzip

Failed: -2, 19: Fail to flash via Downloadzip

My custom rom is still on it but everytime the phone reboots it resets itself so i have to reconfigure the whole phone again!!!!

Btw im S-ON
[One (M9) Android Development] darkenedpath:
First off, this thread is more for people with s-off. Second, you can't flash an older ruu with s-on. You need to either find the appropriate ruu, "equal or greater than your current version" and flash it if you want to update firmware, or s-off to flash older firmware. Best thing to do is get sunshine and s-off. Other then that, IDK what kind of support you will get, if any from this thread.
[One (M9) Android Development] Rolando88:
I doet het have the money for s off atm how do i know which RUU i need to download?
[One (M9) Android Development] darkenedpath:
This should not be discussed here. Pm me and I'll help you the best I can.
[One (M9) Android Development] zuzu_:
fastboot flash zip 25->31 not working

I have a T-Mobile USA M9 and am attempting to flash 1.32.531.33 on top of 1.32.531.25. I have S-OFF via Sunshine. I've attempted flashing with the phone both in Download Mode and using 'fastboot oem rebootRUU' mode. Both seem to flash successfully, but when I check the Software Information in About on the phone, it still says 1.32.531.25.

Any ideas?

./fastboot flash zip M9_1.32.531.33_NoWipe_TWRP_2864_rename_to_ROM+-+Kopie.zip
target reported max download size of 800000000 bytes
sending 'zip' (61607 KB)...
OKAY [ 3.357s]
writing 'zip'...
(bootloader) HOSD CL#505029
(bootloader) GPT is up-to-dated. [17408]
(bootloader) start@19
(bootloader) aboot_signed.img@100%
(bootloader) adsp.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%
(bootloader) sensor_hub.img@BYPASS
(bootloader) tp_MXM11876.img@BYPASS
(bootloader) tp_SYN3351.img@BYPASS
(bootloader) Update zip file OK
(bootloader) end@Done
OKAY [ 9.110s]
finished. total time: 12.468s
[One (M9) Android Development] zuzu_:
UPDATE: When rebooting into Download Mode, it does say OS version 1.32.531.33! There's a post on page 10 about this problem as well. Apparently the OS is updated, but this is not reflected in the About -> Software Information.
[One (M9) Android Development] 1337jay:
About - Software is ROM base and not the actual firmware.
[One (M9) Android Development] zuzu_:
So, I've had to downgrade from 2.7.531.6 back to 1.32.531.33 because of frequent spontaneous rebooting. The phone has been stable after that.

I suppose what I'm still looking for is how to upgrade the entire ROM to the OTA distributions of 1.32.531.33 (so that Software Updater stops bugging me!) and ultimately to the OTA T-Mobile USA release of Android Lollipop 5.1 (2.7.531.6) without wiping the data partition.

It seems that Android has "evolved" and the old days of just updating ROMs via custom Recovery Mode are gone, and we're supposed to rely on OTA updates (which means flashing stock recovery and masking S-OFF "tampering") or the RUU releases (which wipes the data partition).
[One (M9) Android Development] jbfountain:
The reason you are getting frequent reboots is probably because you are updating the firmware without updating the software. You have a firmware - kernel incompatibility.

I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
[One (M9) Android Development] Sneakyghost:
I understand you're wanting to go back to stock, yet there are specialized threads for that and this thread is solely for the purpose of firmware flashing on S-OFF phones. Nothing else.

And I'm saying it again: I dislike any type of off-topic very very much. I'm not offering support either, because I have very little time and when new info comes up (I like getting new info here) I absolutely hate digging backwards through ten pages of "pleez halp I breaked my phone" in order to find one interesting bit.

So, if you find times have changed, check out post 1 to 5 and learn about the new times. That's what those posts are there for. Maybe you then find out this is the wrong thread.

Then, the venomroms.com homepage has a few articles on firmware vs ROM, on how to RUU, on firmware...

Go there and click through the older articles to learn even more.

Thanks for your understanding.
[One (M9) Android Development] Sneakyghost:
O2 and Vodafone zips added

Today I got a set of files from [MENTION=5075569]Asselalf, [MENTION=4751514]Krocko[/MENTION] and [MENTION=4298837]warci[/MENTION][/MENTION] (thanks guys!) so I made 15 new zips - for Vodafone UK (161) and O2 UK/DE/etc (206) mainly, but also the 2.10.401.1 FullStock which I had forgotten about.

Mostly redundant, but some might still be wanting them. For the German forum lurkers: yea you may re-post them on your respective threads, with source link, as usual. Thanks guys! :D

Please be aware that these will trigger a cache-erase when flashed with ARUWizard, but will be a true no-wipe (applicable to the "NoWipe" versions) when flashed in Download-Mode with htc_fastboot.exe (seems like only ARUWizard is parsing the android-info.txt, which holds the line "eraseonflash: cache").

Download in post #1​

UNTESTED, yet thrown together according to my usual standards, you know, an egg, half a cup of milk, flour, pepper, onion... Any flash confirmation greatly appreciated!
[One (M9) Android Development] mnhs1010:
Please help

M9 Asia tw

s-on

1.40.709.8

I used these commands to update firmware.

To re-lock bootloader, in the command prompt, type: fastboot oem lock.

fastboot oem rebootRUU

fastboot flash zip firmware-2.10.709.1.zip

fastboot reboot-bootloader

firmware updated successfully but it stuck at htc logo.

then i flash again firmware.zip sudden mobile reset and this blue screen appears.

[IMG="Bootloader"]http://i.imgur.com/yq26bmI.jpg?1[/IMG]

[IMG="Blue blank screen"]http://i.imgur.com/iBJ6XlW.jpg?1[/IMG]

Now when going to RUU, download, recovery mode this blue screen appears.

bootloader screen come while pressing vol + and vol - and power button but can't flash anything. while using command on bootloader screen fastboot gives error FAILED (remote: cannot flash this partition in s-on state)

FAILED (remote: Not allow when s-on)
[One (M9) Android Development] Sneakyghost:
Interesting. You were S-OFF before? Send a "fastboot getvar all" output please - you can run that command in boatloader as well. See what that returns.
[One (M9) Android Development] mnhs1010:
htc m9 asia tw with s-on....

C:\adb>fastboot getvar all

(bootloader) version: 0.5

(bootloader) max-download-size: 0x20000000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:cache: 0x14000000

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:userdata: 0x5e0000000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:system: 0x118000000

(bootloader) serialno: HT539YJ02815

all:

finished. total time: 0.103s
[One (M9) Android Development] Sneakyghost:
Forgot it's returning partition data in boatloader. Can you run it in download despite the blue screen?

But let me ask how did you get your security back to on?

I'm assuming you were S-OFF before? Or why did you come here? My packs don't flash on S-ON phones as it clearly states on page 1.

So, how and/or why did you turn security back on?
[One (M9) Android Development] mnhs1010:
Dear it was s-on. i tried to update firmware but sudden mobile reset and this blue screen appears. no download, recovery, RUU mode. while going to RUU mode it goes after 1 sec blue screen appears....

main problem is the blue blank screen...

Please help what to do now...
[One (M9) Android Development] Sneakyghost:
Well can't help you then. You can't update firmware from my thread with S-ON. Quite clearly not possible, if you take the time to read.
[One (M9) Android Development] mnhs1010:
then please guide where can i get help to solve this.
[One (M9) Android Development] nkk71:
stick to one of the threads you have already created (not to mention the random posts in other threads):

http://xdaforums.com/one-m9/help/bootloader-screen-t3170209

http://xdaforums.com/one-m9/help/htc-m9-corruted-bootloader-blue-screen-t3164927

http://xdaforums.com/one-m9/help/blue-blank-screen-error-t3166540

and cross-posting and multi-threading is a seriously bad idea.

and the reason you're not getting much help, is because most of us (well at least me), haven't seen that before... you should try, as Sneakyghost mentioned, to see if fastboot picks up your phone while in that blue screen.

No more OT here please. Thanks
[One (M9) Android Development] mnhs1010:
in blue screen nothing happening. after few sec it reset then htc logo then blue screen vise versa)
[One (M9) Android Development] Sneakyghost:
The only chance you have is to try a RUU. You will need to find the RUU for 1.40.709.8 - an older RUU will not work. Also, I doubt you will be lucky with a RUU. It looks like a semi-brick. Seems Download Mode is broken. That means, flashing anything is probably impossible with the means we have.

The only RUU I can see is 1.40.709.4, which is slightly older than 1.40.709.8. You can try to run it but chances are, it will not work.

Download 0PJAIMG_HIMA_UHL_L50_SENSE70_hTC_Asia_TW_1.40.709.4_Radio_01.02_U11440261_60.03.50505G_F_release_431851_signed.zip from here: http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/HIMA_UHL/

You will need to make an account for that site. It costs money. I don't see that RUU anywhere else.

Google Search found this download: http://xdaforums.com/showpost.php?p=61308179&postcount=783 - you can try it there as well.

Other than that, I remind you again, this is not a help thread and this thread is only for S-OFF firmware flashing.
[One (M9) Android Development] DTHC:
Hello everyone . Sorry for a noob question . I have been in past using HTC devices , but was a little bit off the course if i can say like that :)

I have bought a new M9 2 days ago , and now i am proudly S OFF :D , unlocked,roted,TWRP,etc...... I s-off ed and unlocked and rooted after the update to 5.1 and now is on 2.11.425.6.

It is CID: HTC__059 model with 425. software on it , as i read it is already WWE , for ASIA (precisely speaking i am in Vietnam now )

I will probably tonight change it to SUPERCID , but i am interested should i receive something if i do it , and can i change to 401. firmware version since in few months i will be heading back to Europe.

Thanks in advance .
[One (M9) Android Development] papi92:
Any news on a firmware.zip for the latest T-Mobile RUU?
[One (M9) Android Development] j to the 4n:
Whats wrong with 2.7.531.6?
[One (M9) Android Development] papi92:
I can't find the T-Mobile one and the RUU from HTC doesn't run on windows 10

---------- Post added at 10:19 PM ---------- Previous post was at 10:11 PM ----------

Well nvm found it. Dumby me never saw the Google doc with links. That is my bad. Thank you
[One (M9) Android Development] medoc.murner:
Ruu 2.10.401.1

hello all

i'd urgently need the 2.10.401.1 RUU, i can't downgrade my bootloader because i have s-off and it won't let me flash a lower RUU anymore

can anybody help me please? thank you! i write to you sneaky because i see you have good knowledge in firmware stuff :)

medoc
[One (M9) Android Development] xunholyx:
Pardon?

You have S-Off.

That's the only way you can downgrade. It'll never not let you "flash a lower RUU anymore"

Do you mean you are S-On?

I don't think the 2.10.401.1 RUU is available yet.

Sorry.
[One (M9) Android Development] Sneakyghost:
What xunholyx said above.

S-OFF is the only way you can actually downgrade and no, there is no international RUU 2.10.401.1.
[One (M9) Android Development] Sneakyghost:
The RUU's work on Windows 10. Check that you have dot net and VCRedist 2008 x86 (I think) - it's in my batch tool. If you care to pick that up from page one, install it, you'll get the correct vcredist to support the RUU's.

For DotNET I'm not quite sure which one you'll need but you can track that down by googling error messages from the RUU when it fails on your pc.
[One (M9) Android Development] DTHC:
Sorry for reposting again, i need a small answer . i have an Asian HTC ONE M9 , with CID HTC__059 , it is on software version 2.11.425.6 can i convert it to Europe version with 401 Software? I am already Unlocked and S-OFF with sunshine , rooted and installed TWRP,nandroid already backed up.

What would be the procedure? As i guees it is:

1. Change to SUPERCID

2.Flash 401 Firmware through rebootRUU

3.Flash system RUU with 401 base

4.

Just a short directions please that i don't mess up something :D

Haven't been doing this long time already.
[One (M9) Android Development] Sneakyghost:
Double posting doesn't raise sympathy. This is not the "General" forum. This is the "Development" forum. I dislike Q&A stuff here very much. Next time, please utilize the forum that was created for general questions which do not contribute to my wee little project here (or any project in Dev, for that matter).

Answers on how to RUU can be found on venomroms.com: http://venomroms.com/ruu/

Thank you for understanding.
[One (M9) Android Development] LukiLeu:
Firmware 2.10.401.1

Hi,

I try to upgrade my phine to the latest firmware 2.10.401.1. But somehow it won't work. I tried with the FullStock Version and the Wipe Version but always after the flashing of the firmware there's still the old firmware on my phone (1.40.401.8). So what am I doing wrong?
[One (M9) Android Development] Aldo101t:
check your firmware version in download mode not in settings about phone, that is the rom version not your firmware version
[One (M9) Android Development] LukiLeu:
A thank you. Didn't know that difference. But can I find somewhere the file to update also the ROM?