yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Sneakyghost:
Haven't figured that one out yet. First, I thought it was due to stock recovery not being installed, so I flashed stock recovery first and tested again but the same thing happens. Something is messing up the reboot.

But the new "htc_fastboot.exe" has a switch to suppress auto-reboot and you can set that (type htc_fastboot without any parameter and it will list syntax and switches you can use) to avoid a fast auto reboot and do a controlled reboot to download.

Or you just hold VolDown when it goes dark. That will lead you straight back into downloadmode.

[EDIT]

My instructions will be changed to suggesting Bootloader for Firmware flashing with S-OFF - there are massive differences between Download Mode/RUUmode and Bootloader flashing. One such difference is the pre-update fail seems to not happen with Bootloader. Or at least not as much.

[EDIT 2]

Changed my Splash Pull Script. Can you test that on your setup again please?

Android_Tasker_1.2.8_M9_TEST2.exe MD5: 37a8ead7dc7dfd3ebc84dacb44d1903d

Thank you.
[One (M9) Android Development] shivasrage:
For me flashing in bootloader (white screen) is not possible always writes Failed! go to Bootloader mode.

What do you mean exactly with bootloader flashing?

thanks again
[One (M9) Android Development] Sneakyghost:
You sure you are S-OFF?
[One (M9) Android Development] shivasrage:
Dowenloadmode output:

C:\Android\com>fastboot getvar all

(bootloader) kernel: lk

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) imei: 357xxxxxxxxxx

(bootloader) version-main: 1.32.401.17

(bootloader) boot-mode: download

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: 11111111

all:

finished. total time: 0.062s

so yes Im s-off for sure

edit:

if I try in bootloader mode batch tool responding:

C:\Android\com>htc_fastboot flash zip C:\Users\Kofferkind\Desktop\M9\1.32.401.17-Firmware-

noredtext.zip

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

sending time = 2.012 secs

writing 'zip'... FAILFlash zip not support in BL, please go download mode

FAILED (remote: Flash zip not support in BL, please go download mode)

Execution time is 2(s)

maybe I´m doing something wrong?
[One (M9) Android Development] Sneakyghost:
Oh damn I already forgot half the stuff I discussed with my folks at the weekend. I think RUU.zips flash better in Bootloader but regular unsigned zips flash only in DownloadMode. Gotta run to work now. Can't check anymore. Playtime over for this week. Probably only back to sorting everything on monday.

Don't flood the thread please, guys.
[One (M9) Android Development] MPooZD:
I'm confused a little , if i have singed firmware how can i flash it (S-on) ? using CMD or TWRP ?
[One (M9) Android Development] caanda45:
Signed would be a RUU and not here as this thread is for s-off firrmware updates. And it would be using cmd. But not in this thread.
[One (M9) Android Development] timsah:
I wanted to test but the Link does not exist anymore - 404 not found ;)
[One (M9) Android Development] Clark Joseph Kent:
Thread moved here. Thank you.
[One (M9) Android Development] Black-FR:
You did choose the wrong beta. [emoji16]

The link, for the latest version, is quoted above.

Gesendet von meinem HTC One M9
[One (M9) Android Development] timsah:
Thanks! :good:

It says, it successfully created Splash1.png, but the /Dump folder is still empty. :confused:
[One (M9) Android Development] Sneakyghost:
1.32.161.15 added.

Thanks for the new RUU's my German friends [MENTION=5075569]Asselalf[/MENTION], [MENTION=4298837]warci[/MENTION] and [MENTION=4751514]Krocko[/MENTION]

There is a 1.32.401.17 RUU.exe waiting to be added to http://androidruu.com/?developer=M9 and a vodafone 1.32.161.15 RUU.exe for the VF people...

Hope [MENTION=2645378]AndroidFileHost[/MENTION] will see to it soon. Dropped him the links already.Back to work for me...

Notice on my 1.32.401.17 re-upload: I had somehow gotten a wrong HOSD in the package. No harm done, my phone survived multiple flashes of that, yet I recommend you reflash with my re-upload, because we cannot yet see what the outcome would be of a wrong HOSD on the long run. It might interfere with later firmware updates. So, please do correct it and accept my apologies.
[One (M9) Android Development] Sneakyghost:
Thanks, I'll look after that in a bit.

____________________________

Recent Additions

WARNINGS:

Not tested!

NOTES:

The Nougat (Android 7) releases for the HTC One M9 all contain several images that seem to serve no purpose and do not get flashed. Instead, these files throw an error ("WARN") or warning. The flashes end with status "OK" and the phone will work fine. These errors even turn up with the official RUU's. The only reasonable explanation is, that HTC is using a generic build tree for their Qualcomm devices which just contains all partitions, even those, which don' get used. So, please just ignore those warnings.

I have heard of some people not having IMEI show or radio work after Nougat update. I am rather sure this is just an incompatibility. Please make sure to run a matching Nougat ROM before reporting this.. Theoretically, if ROM and Firmware match, everything should work as expected.

CREDITS:

[MENTION=4445238]Golv[/MENTION] for providing the RUU. Thanks mate!

Other stuff

With best regards from the A7 Autobahn... LTE rocks!
[One (M9) Android Development] MC_Ohr:
I flashed no wipe 4.28.401.3 version via SD card and everything went correct. Was on 4.14... before.

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] 160689:
4.27.206.4
[One (M9) Android Development] Luftikus:
I have some questions about my OneM9 with the latest Viper6.1.0 and the FW 4.28.401.3. I have some serious problems with my device.

Every time when I´m rebooting my device the SD Card has a bad removal, and when im wipe dalvik and art cache the device won´t boot anymore. It stucks at the viperone screen. after a long press on the power button the device will start.

I think there are some problems with the drivers or sth else.

is it possible to flash a full wipe fw zip and after that to flash a no wipe fw zip with the twrp at the download mode?

from that point it must be possible to flash the rom again from twrp?

Am I´m right?
[One (M9) Android Development] Sneakyghost:
Yes correct, if your phone is S-OFF, you can proceed as suggested.

However, I doubt the firmware will fix anything, as your problem description lets me think you might just suffer from the corrupted sdcard issue that is plaguing the HTC10 and also rarely the HTC One M9.

The cause for the damage to the sdcard is unknown, but you might want to format it with "SDFormatter V4" with the setting "full overwrite / erase" (the program can be downloaded from sdcard.org).

After doing this, also do what you suggested (full wipe, no wipe, ROM).

Also please be aware that there have lately been several HTC One M9 devices that suffered from defective NAND - it appears to be an aging problem that only begins to show now, after about one year in the wild.
[One (M9) Android Development] Luftikus:
I already send the sd card back to sandisk. and i received a new one, but with the same problem. i never read about a problem with the htc10 and rarely the m9 and the sd card... is it a known problem? is there a statement from htc?
[One (M9) Android Development] Sneakyghost:
HTC never officially or publicly comments on issues with their phones. Never.

The sdcard problem also is unlikely to be a HTC issue. It's more likely caused by a combination of USB3.0, Windows 8/8.1/10 and Intel drivers.

The bad NAND on the M9 is a HTC problem though. Just read back through this thread and follow XDA a little more and you'll find several devices with defective NAND.

Apart from all this, this thread is not a help thread and I do not wish to continue this conversation here, as it is not related to firmware. Unless you have proof that it is related, I'd appreciate if you used the general or Q&A forum to describe your case and ask for help there.
[One (M9) Android Development] P$YCH0:
Hi guys, is there any way to correctly flash the firmware one file at a time through bootloader?

My device is bricked and I can't enter download mode so I need to get that one to work before attempting a RUU flash.

I have tried flashing the zip but bootloader doesn't support this (error msg: "Flash zip not support in BL, please go download mode").
[One (M9) Android Development] Sneakyghost:
fastboot flash <name of partition> <name of img>
[One (M9) Android Development] P$YCH0:
Wow thank you so much. This gives me hope.

I have found a list of partitions: https://xdaforums.com/att-one-m9/development/dev-htc-one-m9-partition-layout-t3078758

Does the order of flashing things make any difference?

Thanks a bunch! :)
[One (M9) Android Development] P$YCH0:
Hi guys, just ran these commands from the 4.28.401.3 FullStock Wipe package and still no luck in accessing download or recovery. Did I miss anything :confused:
[One (M9) Android Development] Sneakyghost:
Hosd should have fixed that. Not sure why you're still not booting
[One (M9) Android Development] P$YCH0:
Very strange. I am getting no errors while flashing:

I did a test and it seems that even though I am flashing the NO RED TEXT aboot the text is still there before the bootloop starts. It's like the phone is not allowing these partitions to be written on or something.

I need to attempt to get it repaired by my carrier but S-Off and unlocked bootloader pretty much guarantee that they won't take it in :(
[One (M9) Android Development] xunholyx:
You shouldn't have flashed the aboot.img
[One (M9) Android Development] P$YCH0:
That doesn't sound good. :( Is there anything else that I can try?
[One (M9) Android Development] xunholyx:
Hmmm. I could be wrong about that. I was thinking I was in the HTC 10 firmware thread, not the M9 and I've never had an M9.

One of the 10 beta testers had to flash all of the partitions separately for some reason I don't remember, and with that the aboot shouldn't get flashed.

Maybe [MENTION=2605798]nkk71[/MENTION] or [MENTION=225495]Mikee4fun[/MENTION] can help? That's who worked out the problem with the 10. I'm mentioning them here so they will get a notification, so don't send them PMs asking for help. They'll hopefully see this post sometime soon and have an idea on how to fix your issue
[One (M9) Android Development] nkk71:
First question would be how you got into that state, what were you flashing when *brick* happened?

You really don't want to be flashing modded aboot or hosd at the moment, best to stick with the

exact

variants for your phone.
[One (M9) Android Development] P$YCH0:
Thank you :)

Hi nkk71, thanks for dropping in to assist. So here is how everything went down:

-A couple of months before my phone was unrooted on a stock rom. Then for some reason some system application kept crashing and couldn't launch (I don't remember which one) so I decided to do a factory reset. After the reset the phone was stuck in a boot loop.

-I found the RUU for my carrier and flashed it through the download mode. Then I decided to unlock the bootloader, root, flash recovery and finally do S-OFF. My ROM of choice was ICE, with the latest compatible WWE radio.

-Everything was good until about a week ago. My "people" application suddenly kept crashing and I couldn't enter the dialer anymore. Before attempting to do a dalvik/cache reset through TWRP I downloaded the latest ICE rom just in case I needed to reflash it again.

-After wiping cache and dalvik through TWRP phone went into bootloop. I then dirty flashed ICE on top of it. After rebooting everything worked well.

-Then two days ago, out of the blue during a whatsapp call the phone rebooted and went into bootlop. I couldn't enter recovery nor download mode since.

-My goal now is to get the download mode to work to flash the RUU again (if I can)

How can I tell that the .img files are compatible with my phone? BTW I already flashed a couple of partitions (see few posts above), so there is a possibility that I already screwed up I think :(
[One (M9) Android Development] nkk71:
That sounds more of a hardware defect, rather than messed up firmware. The *borked* download mode from which you could recover would usually be tied to you flashing something.

You could try entering download mode, when it goes back to bootloader:

fastboot oem last_dmesg
fastboot oem dmesg

To see if there's any indication in those logs of what's up, but I think it's just a hardware problem.

Sorry to be the bearer of bad news.
[One (M9) Android Development] nkk71:
Nothing particularly interesting in there imho, and since

1- you weren't actually flashing anything when the phone died

2- you already tried flashing the partitions normally

3- and it still wont accept changes

I would say the phone is dead, not because of anything you did, just hardware failure, from your earlier post, seems like just a matter of time. I cannot see anything you did wrong.
[One (M9) Android Development] P$YCH0:
Seems like it. Thanks for looking into this though :)
[One (M9) Android Development] cell2011:
What would i use for S-ON mode? To get nougat on AT&T? Im locked and modified on MM. I dont know how to fix my phone my stock recovery is in blue with just a few options and at the bottom in yellow sd not mounted?
[One (M9) Android Development] Black-FR:
You are in the wrong thread.

Check the general forum, there should be a thread, how to update your device... or ask in the q&a section.

https://xdaforums.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698/post64299771
[One (M9) Android Development] xunholyx:
Read the first two sentences of the OP. The second tells you the two most common ways to update while S-On
[One (M9) Android Development] dimric:
Guys please, I can flash 4.28.401.3 in new download mode on my m9? I'm s off.

Thanks

Edit: all right..I did it.

Inviato dal mio HTC One M9 utilizzando Tapatalk
[One (M9) Android Development] Pfaffinator:
Att M9 here, changed cid,mid, to WWE model, flashed no wipe 4.28.401.3 zip, got failed "90", flashed again, success, flashed a 4.28.401.3 WWE rom. Rebooted, no issues with apn, or signals in general, great guide.
[One (M9) Android Development] shpitz461:
Thanks to blueberry, I've spotted some newer firmware as well as no-text versions here:

https://www.androidfilehost.com/?w=files&flid=51139

it contains latest 617 firmware 'firmware_4.30.617.12_NoWipe.zip'
[One (M9) Android Development] xunholyx:
[MENTION=1102297]Sneakyghost[/MENTION] Update your stuff :)
[One (M9) Android Development] Sneakyghost:
That looks like some collection of stuff from someone messing with stuff. I prefer to update from HTC files.

Anyone link me HTC's RUU for those requested files and I will do when I have some time.
[One (M9) Android Development] xunholyx:
http://dl3.htc.com/application/RUU_...880.1510427138.1496810528-43457397.1471806429
[One (M9) Android Development] Sneakyghost:
Screw AT&T. I want to go back to sleep. Now.
[One (M9) Android Development] xunholyx:
Ummm that's 4 30.617.12

WAKE UP! :D
[One (M9) Android Development] Sneakyghost:
Oh it also says unlocked besides AT&T. Right. I forgot it was the same device back then. Yeah well. Too early in the morning...

Sleep well, friend.
[One (M9) Android Development] shpitz461:
LOL

Anyway, I flashed blueberry's firmware as well as his no-text bootloader and it all looks good to me so...
[One (M9) Android Development] Sneakyghost:
Recent additions: Unlocked 4.30.617.12 and AT&T 4.27.502.7

Recent Additions

WARNINGS:

Not tested!

NOTES:

The Nougat (Android 7) releases for the HTC One M9 all contain several images that seem to serve no purpose and do not get flashed. Instead, these files throw an error ("WARN") or warning. The flashes end with status "OK" and the phone will work fine. These errors even turn up with the official RUU's. The only reasonable explanation is, that HTC is using a generic build tree for their Qualcomm devices which just contains all partitions, even those, which don' get used. So, please just ignore those warnings.

I have heard of some people not having IMEI show or radio work after Nougat update. I am rather sure this is just an incompatibility. Please make sure to run a matching Nougat ROM before reporting this.. Theoretically, if ROM and Firmware match, everything should work as expected.

CREDITS:

[MENTION=4987085]xunholyx[/MENTION]

[MENTION=4167768]Pfaffinator[/MENTION] for zee AT&T RUU.zip. Thank you, Sir!

Other stuff

Nothing to see here. Keep walking.

I honestly have no clue whatsoever, why I was putting an older TWRP into the Unlocked pack. I must have been super tired or super drunk or both and just copied the older one from the .2 pack over. I am not going to redo the pack - just flash newer TWRP yourself. Sorry for the mishap, unlocked folks...
[One (M9) Android Development] ELki123:
Hi how much time it take to reboot after i flashed the NO_WIPE_firmware	4.30.617.12 ??? :(
[One (M9) Android Development] Sneakyghost:
Not overly much. It's not redoing ART cache, so should be almost normal boot time.
[One (M9) Android Development] ELki123:
oh my goodness so im still in booting

i guess im into brik

u have idea what i need too do ?

power off ?

i flashed the NO WIPE AS I WROTE UO...

my rom is the reccurtion...
[One (M9) Android Development] Sneakyghost:
You're not bricked. Brick means phone is dead.

Grab a RUU from HTC's site and start over.
[One (M9) Android Development] ELki123:
U dont recommend to flash again the firmware

i checked now and the firmware was flashed but the phone is stuck on rebooting

maybe the	4.30.617.2 !?

here is the log of my flashing :

target reported max download size of 800000000 bytes

sending 'zip' (67312 KB)...

OKAY [ 4.327s]

writing 'zip'...

(bootloader) HOSD CL#669696

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

(bootloader) Perform pre-update

(bootloader) start@21

(bootloader) aboot_signed.img@100%

(bootloader) adsp.img@BYPASS

(bootloader) bootlocker.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

FAILED (remote: 90 hboot pre-update! please flush image again immediately )

finished. total time: 5.516s

PS C:\Android\com> fastboot flash zip Firmware.zip

target reported max download size of 800000000 bytes

sending 'zip' (67312 KB)...

OKAY [ 4.365s]

writing 'zip'...

(bootloader) HOSD CL#894012

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

(bootloader) WARN Skip bootlocker.img due to unmatched partition name

(bootloader) WARN Skip cir.img due to unmatched partition name

(bootloader) WARN Skip cmnlib32.img due to unmatched partition name

(bootloader) WARN Skip cmnlib64.img due to unmatched partition name

(bootloader) WARN Skip keymaster.img due to unmatched partition name

(bootloader) get 20 images from zip(zip_type=3)

(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%

(bootloader) sensor_hub.img@BYPASS

(bootloader) tp_MXM11876.img@BYPASS

(bootloader) tp_SYN3351.img@BYPASS

(bootloader) Update zip file OK

(bootloader) end@Done

OKAY [ 8.879s]

finished. total time: 13.275s

PS C:\Android\com>
[One (M9) Android Development] ELki123:
hi this is my download mode

[IMG="MY PHONE"]file:///C:/Users/osnat/Downloads/WhatsApp%20Image%202017-06-21%20at%2011.22.08.jpeg[/IMG]

this is my download mode can u help me ?
[One (M9) Android Development] Sneakyghost:
Please. I told you what to do.

Your phone won't boot like that. Flash a RUU which you can get from HTC's website for the unlocked version (xx.x617.x).

This is just cluttering up my thread. I am not providing support here.

That that boot issue can happen is a well known fact and so is the fix. Start over. Flash RUU. Sorry.
[One (M9) Android Development] reben:
Hello young, can you give me a link from 4.27.206.4 ubdate?
[One (M9) Android Development] Black-FR:
If it's not on the sheet, then you are in the wrong thread..

You should take s look, at the stock ROM/backup thread in the general section.

There you might find a link.

https://xdaforums.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
[One (M9) Android Development] reben:
Since nothing had been found. Thank you
[One (M9) Android Development] franzrocamolina:
USB Debugging not working

I have my HTC M9 T-Mobile, Unlocked bootloader and S-off.

A few days ago installed M9_4.27.531.6_FullStock.zip (thread https://xdaforums.com/one-m9/development/firmware-t3068243)

Immediately installed ROM Stock_4.27.531.6_Rooted_Deodexed_M9_TMobile_Minhnewpro.zip (Thread https://xdaforums.com/one-m9/development/rom-stock-nougat-4-23-617-1-unlocked-t3553470)

No problems flashing Full Stock zip file.

No problems flashing ROM (with TWRP 1.14)

After update "USB Debugging" does not work.

My PC can not see the M9 unless I uncheck the "USB Debugging" and enable the MTP transfer files, but this does not allow me to use the ADB commands. (which is I want).

Tried different cables, different ports, reinstall drivers. Problem still.

Also the “Revoke USB Debugging authorizations” option is missing in developer menu.

I also have another identical HTC M9 that has the same Android version (OTA Updated )(Relocked and S-On).

In this Smartphone USB Debugging connects my PC.

Please help me

regards
[One (M9) Android Development] Sneakyghost:
Well this has pretty much nothing to do with my firmware thread.

You could try to run the corresponding RUU instead of firmware and stock ROM. Better anyway imho. Why would you flash pieces if you can have an optimized complete flash?

And yeah. I've had that dead adb myself once in a while. Can't recall what it was. Usually just driver issues, wrong adb issues etc.
[One (M9) Android Development] shpitz461:
I suspect it's a driver issue, open up Device Manager and see if you have any devices with yellow exclamation point. If you have none, then it could be an issue with the driver being used.

Here's what mine looks like.

You can also try different recoveries, maybe that would help...
[One (M9) Android Development] franzrocamolina:
Device Manager can't see this device, but with my other HTC M9, Device Manager works as yours.

I mean it's not a driver issue.

regards

---------- Post added at 08:56 AM ---------- Previous post was at 08:39 AM ----------

Before my problem, my HTC was with version 3.39.531.7; Flashing Stock RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6.exe had Signature error 132, so tried your procedure.

Do you think I can try again Stock RUU file?

Can you advice me something else?

Regards