yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] bigjailerman:
Thanks I will try again amd recheck what i did first time around.
[One (M9) Android Development] darkenedpath:
I just wanted to give input of something I noticed. So please sneaky don't get mad at me lol. On the 1. Xxx firmware and the 2.xxx firmware, I was able to flash a splash screen on my developer edition m9 only changing the CID to SuperCID. I flashed your full whipe firmware for the developer edition for the 3.xxx firmware, and tried to flash a splash screen that I already had, and noticed I had to change the mid. I'm sure I'm no help, but I wanted to at least let you know for your batch tool. I don't use it, I use fastboot myself, but didn't know if you needed to know in case you needed to change something. If it is different for some other people then sorry for my post. Thanks for all you do
[One (M9) Android Development] Sneakyghost:
Thanks I'll check it out. I meant to try it a since a while but haven't gotten around to it yet. I had a feeling ever since I noticed that there was a change to how the splash screen is displayed.

[EDIT]

Sorry, I wasn't quite awake when I wrote my answer this morning.

I am assuming you tried to flash a splashscreen using a fastboot zip with a splash.nb0 inside? If yes, then read the following:

The case is pretty clear. Earlier in this messed up piece of junk thread, I had outlined, that HTC has changed the behavior of SuperCID.

From 3.xx and up, I reckon for good, SuperCID will not ignore both CID and MID anymore. SuperCID will now just ignore CID. MID needs to match.

So, of course, a splash-screen zip will have to be flashed the same way as a firmware zip now. In case the MID isn't matching, android-info.txt needs an edit. Simple as that.

The other method, flashing a splashscreen solo, without zip, just using "htc_fastboot flash sp1 splash1.nb0", should not be affected since there are no CID/MID checks for image flashing. Welcome to test - my batch tool does it that way. I'd be happy about a report, no time to mess with phone at the moment.
[One (M9) Android Development] Mostafa Wael:
Fastboot is not recognised as an internal or external command! Using your batch tool and I have copied the firmware file to C;\Android\com like stated. I tried with minimal ADB & Fastboot also, it said "cannot load firmware_xxxx file" ?! :eek:
[One (M9) Android Development] Sneakyghost:
Look inside the folder. See how fastboot is called. Spoiler: it's htc_fastboot...
[One (M9) Android Development] Mostafa Wael:
Already did that, it says "cannot load M9_3.35.401.12_NoWipe_TWRP287b1.zip file"
[One (M9) Android Development] Mostafa Wael:
[MENTION=1102297]Sneakyghost[/MENTION] never mind, I was not that awake and I forgot to type a 1 before the b1 at the end! Sorry for disturbance and confusion.
[One (M9) Android Development] jaxenroth:
Hey guys bask on the HTC scene after a year or so hiatuses. Pick up an att branded M9 that's running 2.11, but is S-Off and Super CID'd and BL unlocked. My question is, am I able to flash the latest 3.35 developer RUU from the HTC site. Thx guys.
[One (M9) Android Development] jaxenroth:
[MENTION=1102297]Sneakyghost[/MENTION], reading through the thread, I saw this. Will I have to change MID in order to flash the 3.35 developer RUU? Just trying to get a clear answer. Thx.

"The case is pretty clear. Earlier in this messed up piece of junk thread, I had outlined, that HTC has changed the behavior of SuperCID.

From 3.xx and up, I reckon for good, SuperCID will not ignore both CID and MID anymore. SuperCID will now just ignore CID. MID needs to match."
[One (M9) Android Development] darkenedpath:
Will let sneaky answer. Sorry.
[One (M9) Android Development] jaxenroth:
I saw your response, but I'm unclear, like I said I've been away from HTC for a bit. Not trying to offend. Just doing some research prior to flashing. Device should be here this weekend.
[One (M9) Android Development] jaxenroth:
As it looks the dev unlocked and att share the same MID, so I would assume I'd be good to go.
[One (M9) Android Development] darkenedpath:
You have soff. Cid 11111111 should work. If not, then change it to BS__US001. Mid is fine. But you should be OK. If not, change cid as I said. As long as you have a stock aboot.
[One (M9) Android Development] HUB107:
Any news for cid 621 and s-on?
[One (M9) Android Development] donmarkoni:
Yes, you can go here and S-OFF your phone, then flash whatever FW you like. :)

That's the only news I have. Not very fresh though... ;)
[One (M9) Android Development] Sneakyghost:
You were going to say he is in the wrong thread, weren't yo? :p
[One (M9) Android Development] spastikitten:
im not sure how to go about fixing this ( target reported max download size of 800000000 bytes

sending 'zip' (48266 KB)...

OKAY [ 3.762s]

writing 'zip'...

(bootloader) HOSD CL#669696

(bootloader) ERR Model ID not matched

(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED

(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10

(bootloader) ERR Update zip file failed.

(bootloader) ERR ZIP ERROR, exit read zip loop

(bootloader) Update zip file OK

(bootloader) ERR ZIP ERROR CODE, 10

(bootloader) end@Done

FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )

finished. total time: 5.869s )

I get this after changing the cid and changing the model number in the txt doc. i should be doing these correctly but after this im not to sure.

i have an Australian htc one m9 (no carrier) with the model number on the rear showing 0OPJ100. some help would be much appreciated.
[One (M9) Android Development] Rogi1997:
Is it possible to put my own designed picture as the bootloader logo, instead of the HTC Bootloader Logo?
[One (M9) Android Development] Sneakyghost:
Use my splash flashing part of the batch tool. Image needs to be in proper size and bmp.
[One (M9) Android Development] Rogi1997:
I'll try it, thanks
[One (M9) Android Development] bighleo114312:
I broke my bootloader mode and RUUmode. I tried to flash a no red logo In my m9 tmo. How can i restore those 2 images again?
[One (M9) Android Development] Sneakyghost:
See. That's why I'm not doing those no red things anymore. Thank you for the demonstration. Since I'm at work all week, I won't be able to help find out what exactly went wrong. Also, this is absolutely not a support thread. Especially not for issues that weren't even caused by my packages.

You can try if the sdcard method still works but other than that I don't have an idea. I'd need to properly look into that with you which I can't.

Also I know for a fact that several other cases like yours exist. Best thing is to use XDA search to find them. Or use Google search limited to xda -that sometimes works better.

Plus, I'd advise you to get help where you got the package.
[One (M9) Android Development] Mostafa Wael:
AFAIK the only other way to get things working again is the sdcard method. Make sure that the firmware file is placed in the root of the sdcard and that the sdcard is FAT32 formatted. Also you should rename the firmware file to a certain name that I can't remember right now. Then boot into download mode and proceed with flashing.

Good luck!
[One (M9) Android Development] darkenedpath:
I have to agree with sneaky..... I bugged him about helping me with the edits, and he said to not make them. Hard headed I figured out how to do them, and have been using my own for a little while, but with the way HTC have been, especially with Android M, I wouldn't do it anymore. Just because of the risk at hand that has affected you yourself. My comment won't help, but as said, flash it from SD card. And don't..... I mean never, as sneaky told me, "absolutely not, flash a modified hboot/aboot" again. The red text is NOT that important to loose your phone. Sorry for the long message, but good luck. And leave the aboot alone.
[One (M9) Android Development] shahnaz:
Rename the Firmware file in sdcard to : 0PJAIMG.zip

:o
[One (M9) Android Development] Mostafa Wael:
Yeah thanks for reminding me :)

Always get confused in the OPJA part of the name haha :D
[One (M9) Android Development] akinkoff85:
Good Afternoon, I am trying to flash the latest firmware to my M9 and I am getting error 10 stating My MID does not match the MID info in ANDROID.INFO. Can someone please advise me on how to proceed? Thank you.
[One (M9) Android Development] Mostafa Wael:
Yes

Read the OP
[One (M9) Android Development] cknuth:
Hello, I at first I get the MID error, even though i am already SuperCID. So i follow OP instructions and edit Android info in the zip and retry. Now I get (remote: 22 RU_HEADER_ERROR) any helps?
[One (M9) Android Development] eban44:
Download 7zip, open the zip inside of the program, right click on the Android text file and open within. Change the mid to yours hit save. It will ask if you want to update the zip, hit yes. Then try and flash.

I had the same issue everytime I would unzip and zip it, but worked editing the file directly in 7zip.
[One (M9) Android Development] RussianCode:
"Change the mid to yours hit save. It will ask if you want to update the zip, hit yes."

That bit of info right there, is priceless. eban much thanks man!
[One (M9) Android Development] blueberry60:
I wonder,is there any file instead of htc_fastboot.exe in ubuntu,or can we flash M9 RUU and firmware zip files with large size typing "htc_fastboot flash zip ruu.zip" without any problem?
[One (M9) Android Development] Chezbel:
I use Ubuntu and I just use fastboot, but it needs to be the newest one. I forget the version number and I'm not home.
[One (M9) Android Development] Sneakyghost:
I can't remember where I got my Ubuntu Fastboot from but I think I just took the one from htcdev.com - not sure though.

It reports as version: "htc_fastboot 2.0.0"

The current PC version is 3.0.9.2.

I've attached the thing I use. Maybe it helps.
[One (M9) Android Development] Chezbel:
I haven't tested this, but for reference this link claims that fastboot is available via apt-get

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Debugging/Installing_ADB

Also, I just checked Ubuntu Software Center and searched for fastboot and there is a match.

If it matters, I'm running Ubuntu 15.10
[One (M9) Android Development] jaxenroth:
[MENTION=1102297]Sneakyghost[/MENTION], looking to see if you can provide some help? Got a TMO M9, S-Off and Super CID, BL unlocked. Changed MID to DEV and flashed the DEV MM 0PJAIMG. Everything went fine, but wanted to try an INT ROM, so I Changed MID to INT, flashed latest 401 FW than flashed ROM (ARHD for example) Goes through Android is Starting screen, but when it gets to optimizing the last apk, it boots the all white HTC screen. Any input would be wonderful. Wondering if I would have to flash full 0PJAIMG from lollipop 401, than flash ROM, than flash MM 401 firmware.
[One (M9) Android Development] bjgood:
First, thanks SneakyGhost for all the great info here.

I just got S-OFF for my at&t M9, and I'm planning to flash the 3.35.617.12 (developer/unlocked) no-wipe firmware. I've already previously unlocked the bootloader, rooted, and flashed a custom rom. But flashing firmware feels a little more scary to me so I want to make sure I have everything correct first.

First I need to change CID from CWS__001:

fastboot oem writecid 11111111

I don't think I need to change MID from 0PJA11000, since at&t already matches the dev edition. Is that right?

Is there anything else I need to be concerned about having a compatible version/setting ahead of time (ROM, radio, etc)?

Doing this won't affect the phone's ability to work on the att network, right?

Edit: One more thing, ATT/tmobile firmware is listed as device type: hima_ul, while all others are all hima_uhl. I'm not sure what that means. Does it matter that I'm currently using hima_ul firmware but would be flashing to hima_uhl?
[One (M9) Android Development] Rogi1997:
himaul and himauhl sharing all Roms there is no difference between these for Rom flashing

your way is right. Changing mid is only needed for firmware flashing

Always look into first posts and read.

Read all what you can find on XDA about your theme (fastboot, s-off, .....) And often use the search box

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] donmarkoni:
If I may... Doesn't look like you did anything wrong. White HTC does screen appear after optimizing apps, seen it too, but I was being patient enough to see it go away. ;)

Oh... and please use some real custom ROM, ViperOne for example. :)
[One (M9) Android Development] jaxenroth:
Thx donmarkoni, ARHD, was just an example;) I ended up doing what I said in my last sentence and was able to get it to boot. Thx for your input.
[One (M9) Android Development] ahmedesamsh:
what is the proplem
[One (M9) Android Development] Sneakyghost:
hima_ul and hima_uhl are having a different set of radio frequencies unlocked.You might be needing AT&T firmware to have VoLTE / HDVoice working. Not sure. Maybe it is enough if your ROM chef makes sure the correct settings are applied for AT&T. But it could also need an AT&T radio... you will need to find out.
[One (M9) Android Development] rasteck:
Error Code 7

Hi, while flashing the new firmware, it gives me this error:

C:\Android\com>fastboot oem rebootRUU

...

OKAY [ 0.043S]

finished. total time: 0.044s

C:\Android\com>fastboot flash zip M9.3.35.401.12_NoWipe_NoRed.zip

target reported max download size of 800000000 bytes

sending 'zip' <48274 KB>...

okay [3.888s]

writing 'zip'---

<bootloader> HOSD CL#506785

<bootloader> ERR CID not matched

<bootloader> ERR [SD_UPDATE_ERR] CID NOT ALLOWED

<bootloader> ERR [SD_UPDATE_ERR] sddownload failed: 7

<bootloader> ERR Update zip file failed.

<bootloader> Update zip file OK

<bootloader> ERR ZIP ERROR CODE, 7

<bootloader> end@Done

FAILED <remote: 7: fail to flash via downloadzip>

finished. total time:6.402s

I dont know which error it is, dont appear in error list. I still have the device without reboot, but it cant stay so much in this state.

Please, some help. Thanks.

EDIT: My CID is "CID-VODAP304"
[One (M9) Android Development] Sneakyghost:
I'm sorry I don't support other people's firmware packs because I don't know how they're set up. Wouldn't have a clue what that error is from. Maybe you find something in my error description post though?
[One (M9) Android Development] donmarkoni:
Oh... You use some other guy's FW package and you come here to ask [MENTION=1102297]Sneakyghost[/MENTION] for advice? Rude, just plain rude.

Also, I feel compelled to tell you that your knowledge seems so limited, that you shouldn't be flashing firmware, let alone modified one, if you can't solve basic problems.

Have a nice brick. ...erm... I mean day.
[One (M9) Android Development] rasteck:
Hi Sneakyghost, thanks for answering.

Ok, as I want to update to Marshmallow, I needed 3.35.401.12 firmware, and I saw that yours is 3.35.401.10. I checked the error description, but I cant find an "error 7".

Should I retry with one of your firmware? Like the 3.35.401.10.

And sorry for my english, is a little poor (not my native language).

Thanks

---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------

I do not want to offend anyone, and sorry if I did it. And no, my knowledge is limited, Im only trying to update firmware to be able to install Marshmallow ROM in my device. I asked for some help, because I dont want to brick my device. And I come here for advice because in the other post, with the guide I was following, redirect to this error post.

So, sorry if I disturb.
[One (M9) Android Development] Sneakyghost:
Please post the output of the command "fastboot getvar all"

Please remove your IMEI from that output before posting.
[One (M9) Android Development] rasteck:
kernel: lk

product: htc_himauhl

version: 1.0

version-main:1-32-161-15

boot-mode: RUU

version-bootloader: 1.0.0.0000

mid: 0PJA10000

cid: VODAP304
[One (M9) Android Development] Sneakyghost:
And in the other mode? Run it again in bootloader mode and let me know the rest...
[One (M9) Android Development] rasteck:
Ok, there is:

(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

all:

finished. total time: 0.104s
[One (M9) Android Development] Sneakyghost:
Well you've got the same exact device as I do, except for a different CID. I run SuperCID. Have a guess what your error message says. Maybe you understand, if you look at it properly. "CID not allowed". *hint hint*

[SD_UPDATE_ERROR] most likely refers to "Software Download" update error. It refuses to flash the software because your CID doesn't match the allowed CID's in android-info.txt inside the zip.

Solutions to work around that are suggested in my first five posts. Yes they are. Only thing you need: know the terms and understand the logic of those weird outputs (remember: the programmers over at HTC aren't native English speakers. You find a lot of confusing output. You need to "think around the corner").

Like my favorite error 90: "please flush [down the toilet?] image again immediately!"
[One (M9) Android Development] Mostafa Wael:
Yeah that "please flush image" just blown me away.

Ohh and btw, I found that in RUU mode, after the pre-update error 90 fail, it automatically reboots to RUU mode again :) which is better than rebooting in OS and force rebooting back to download mode,...etc. So maybe you can still recommend this RUU mode still ;)

Also, can you mention that the way the phone starts up in MM ROM now is a bit different ? Now it keeps hanging on the "splash screen" with the Red Text (that some people hate with no reason :p ) till it finishes booting then it plays the boot animation ;) also when rebooting to recovery mode, the first splash screen you see before TWRP's one is the dark screen of the RUU mode with HTC written in silver, instead the usual white screen with HTC written in green ;)

Just so people don't pee in their pants haha :D

---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------

Yeah that "please flush image" just blown me away. :laugh:

Ohh and btw, I found that in RUU mode, after the pre-update error 90 fail, it automatically reboots to RUU mode again :) which is better than rebooting in OS and force rebooting back to download mode,...etc. So maybe you can still recommend this RUU mode still ;)

Also, can you mention that the way the phone starts up in MM ROM now is a bit different ? Now it keeps hanging on the "splash screen" with the Red Text (that some people hate with no reason :p ) till it finishes booting then it plays the boot animation ;) also when rebooting to recovery mode, the first splash screen you see before TWRP's one is the dark screen of the RUU mode with HTC written in silver, instead the usual white screen with HTC written in green ;)

Just so people don't pee in their pants haha :D
[One (M9) Android Development] Sneakyghost:
I'm not recommending RUU mode anymore as primary method. Download mode is superior simply because we have much more control, functionality and error return than in RUUmode. And as far as I have seen, there's nothing that "needs" RUUmode.
[One (M9) Android Development] hgoldner:
Not to hijack the thread but "ain't that the truth." You should see some of the messages I get from R&D at HTC while testing (and the grammatical and spelling errors I catch in early ROM versions).

On the other hand, I wouldn't stand a chance if I had to work in Mandarin, Cantonese, or for that matter any other language than English. And the USA is the land of the monolingual (as opposed to just about everywhere else on the planet).
[One (M9) Android Development] Sneakyghost:
"Not to.... but" always means its a "but"

Pretty much like saying "I'm not an a-hole, but...."
[One (M9) Android Development] xunholyx:
Not even RUUs?
[One (M9) Android Development] Sneakyghost:
You can flash RUU zips in download mode, no?
[One (M9) Android Development] Black-FR:
Yes you can...

Just a RUU.exe will go to RUU mode.

But as long as you manually flash RUU.zip's / firmware.zip's, you could always do in download mode.

Gesendet von meinem HTC One M9
[One (M9) Android Development] BillTheCat:
disregard
[One (M9) Android Development] xunholyx:
.exe

The RUU in its natural habitat. :D

The post I made was in jest.
[One (M9) Android Development] ogevilmike69:
Sad day..

Ok so pretty sure I fked and it bricked but here goes... I used the fastboot and flashed my firmware it error 90 and rebooted... now it in a bootloop.. I hold the three buttons it goes to the white screen with options.. I scroll with vol -/+ to anything like recovery, download, press power to enter the mode it then just resumes the boot loop over and over again.. I select power down it turns off. I plug in the cord to charge it while it off, it shows the battery icon then turns on and resumes the boot loop, and before anyone asks no at anytime my pc will not recognize it on the white screen otherwise would fastboot oem rebootRUU and try again.. any help would be most appreciated.
[One (M9) Android Development] xunholyx:
You can fix this.

The problem is, you didn't read what it said after "error 90"

It says "pre-boot update, please flush again". HTC is made in Asia, and "flush" is obviously a misprint for "flash"

You updated from fairly old firmware, correct? The first flash if you are on old stuff only updates your boot partition. It tells you to flash again to update the rest with the new hboot.

What you need to do is hold down the power button + vol up. AS SOON AS THE SCREEN GOES BLACK slide from vol up to vol down. This will take you to bootloader. Hook your phone up to your PC, and run the firmware.zip again.
[One (M9) Android Development] Scabes24:
Not to be an a-hole, but aren't you the one that once told me this wasn't meant to be a support thread? Maybe you need to make those first five posts a little longer =)

(Obviously kidding, cause I'm an a-hole) ?
[One (M9) Android Development] caanda45:
I am using the AT&T base on LeeDroid, so far no problem.....but we will see how it goes, being s-off means I can flash almost anything...which I like. Gives me such freedom....On my M8 I also used the .401 firmware..I may have to go test it now to see if much of a difference. And then report back here.
[One (M9) Android Development] user602:
My M9 is still on its original Dev Edition firmware, and Viper works fine. However, I'll be flashing Sneaky's .401 no-wipe zip this evening; hoping for some improvement in battery life.
[One (M9) Android Development] Adam182:
Let us know how it goes, ill be flashing the NOWIPE onto my original ,401 UK EE firmware aswell - Adam
[One (M9) Android Development] Sneakyghost:
If you use both a 401 ROM and Firmware, its a good idea to use the full wipe option first in order to give you the kernel parts that do not come with a custom rom necessarily like ramdisk.img and dt.img. Or you grab the fullwipe zip and remove the dzdata files and place the twrp recovery image in there but leave the rest alone and then flash it like that. Just to make sure you update everything that's not gonna be changed by the ROM. I don't fully understand what the dt.img is doing but I know its a part of newer android kernels and therefore I think it might differ from carrier to carrier.
[One (M9) Android Development] user602:
Thanks for the advice, Sneaky. Not what I was planning on doing, but I cannot deny your logic. Fullwipe zip sounds like a good weekend project anyway. :D
[One (M9) Android Development] Adam182:
Im currently using Viper 1.2.0 and .401, do i need to fullwipe aswell? All i want to do is update to the latest firmware and NOT have to reinstall everything over again, i imagined with S-OFF it would be a piece of cake but its sounding alot harder than i thought - Adam
[One (M9) Android Development] Sneakyghost:
Yea same with SDCard method. If you use that way to flash, its also download mode acting. I guess I wrote in the OP the texts are still a mix of M7, M8 and M9 crap... time to update... thanks for the headsup