yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] marksedge:
Converted to dev software originally from att months ago ,finally took the rom flashing plunge and figured OK I'll do the no wipe zip ,ran into the 90 error and was like "aaaaaaahhhhhhhhhhhhh""", wondering if the uh oh would back me up on this but being sneakyghost dude is a bloody genius that has the batch tool totally fixed my situation and now I stand before the jury a guilty but greatful rom flasher and m9 abuser and I say to you ...

Feels good ! Thanks!!!
[One (M9) Android Development] maxx2210:
hi,

I am new to this so please forgive my noob question here,

I have M9 ( in download mode it shows 2.10.709.1 OS), i have an unlocked bootloader, installed TWRP, rooted, S-off and supercid and have installed Maximus Custom Rom 6.0 ( based on 2.1.401). I have done all this by reading several of xda posts/threads ( thanks to all).:D

I wanted to get the red text removed but am unsuccessful in doing so after trying with both adb/fastboot method sd card way.

Can someone please help me getting this done ? I flashed firmware 2.1.401.1 without redtext and aboot only zips to no success as yet.

Please help !
[One (M9) Android Development] Flippy498:
First, this is the wrong thread for that question since sneakyghost doesn't provide aboots without the red text.

Second,

never ever ever ever flash an aboot that is not compatible with your firmware

. You said that you are on 2.10.709.1 (according to your download mode) which is an Asian firmware version. If you then flash an international aboot like 2.10.401.1 you will probably hardbrick your phone and gain a fancy new paperweight.

But to answer your question: If I were you I would change my CID to HTC__001 and use a RUU like this one. Then you can upgrade your firmware via the OTA function in settings>about. And then after you reached 2.10.401.1 you can try flashing the NoRedText aboot. It may not be one of the fastest solutions but it's one of the safest.
[One (M9) Android Development] maxx2210:
Thanks Flippy498 for helping and apologies for posting in the wrong thread.
[One (M9) Android Development] iElvis:
[Edit: Just realized we're talking about mxing aboots and firmware. I agree that's not a good idea, though I doubt it would result in a hard brick.]
[One (M9) Android Development] nkk71:
nvm & noted.
[One (M9) Android Development] Sneakyghost:
Asian 70x versions are pretty much identical to 40x versions firmware wise. Hardly any differences ever. Mixing Aboot's ain't gonna be a big issue.

Yea, no hard bricks, no softbricks. Just not making any difference.

Indeed, I do mind OT but this might have needed some clearing up. Misconceptions in firmware questions can have adverse side-effects. Better have everyone know the fine print.

So, to sum it up into my uneducated opinion: I think Asia-WWE, DevEd and some few international GSM providers actually share pretty much the same firmware base and their parts can be interchanged without much worry. The only things I'd currently worry about is exchanging CDMA/GSM partition images, but mostly just because I have no real clue.
[One (M9) Android Development] iElvis:
That's what I thought, but never actually having done it, and not knowing for sure, I didn't want to give out bad information.
[One (M9) Android Development] Flippy498:
Well, then I guess I learned something new. Thanks for the clarification. Since I thought those files were incomptabile and maxx2210 said he wasn't able to flash the aboot sucessfully I just wanted to prevent him from bricking his phone.
[One (M9) Android Development] maxx2210:
well, i can now confirm that i was able to remove red text by flashing 2.10.401 no red text firmware. I gave it a last shot and what i did different was to cut paste the file ( earlier i was copy pasting, dont know of that made the difference) in platform tools folder and it ran like a charm.:good:

Thanks to all who helped:D:o and once again sorry for posting in the wrong thread but i hope information might be useful.
[One (M9) Android Development] TogoFire:
Thank you!
[One (M9) Android Development] Sneakyghost:
Cutting and pasting a file does the exact same as copying and pasting a file, except that the source file gets deleted after the copy job. Basic computer knowledge. Believing that would influence firmware flashing borders superstition (superstition has always affected the uneducated the most :p )
[One (M9) Android Development] maxx2210:
I never said it is different, just what i did different the third time round was what i said. Rest i leave it yo your sound and educated understanding.

Thanks again for helping me out.

I also installed Xposed theme and feel you & your team has done an Awesome bit of work ( took silver membership too:o).
[One (M9) Android Development] Sneakyghost:
If I should take an uneducated guess I'd say you probably ran into error 90 on the first run, which you can look up at the first pages. However, if it wasn't that, I am always interested in flashing details from flashes that lead to errors. Sometimes a new bit of info turns up that's worth putting on the front page for others to find. So if you do remember the exact error and what lead to it, feel free to share.
[One (M9) Android Development] maxx2210:
The only thing i remember is that it asked me to flash again but in the meantime phone rebooted itself, post reboot i again flashed going into recovery mode and then phone rebooted again and the script in adb said process complete.
[One (M9) Android Development] Sneakyghost:
In ADB? In Fastboot you probably mean?

Well that sounds like a regular error 90 and then a successful second flash. Nothing appearing to be wrong there.
[One (M9) Android Development] peca_slo:
Sneaky how do we flash firmware directly from download mode, not ruu? And also is it safe?

Tenx
[One (M9) Android Development] maxx2210:
Yes, fasboot was what i meant:D
[One (M9) Android Development] RLKirk:
Sorry if this is a dumb question. But which one do I flash for Verizon. US. Thanks in advanced
[One (M9) Android Development] Sneakyghost:
Did you take the time to read post #1?

I don't support CDMA and that's big bold and red on page 1
[One (M9) Android Development] Sneakyghost:
Download mode offers better error output, in RUUmode you don't see anything on the phone screen.

As far as I'm concerned I've not seen any negative effects of either RUUmode or download mode.
[One (M9) Android Development] RLKirk:
No sir. Sorry I actually skimmed it as I was on break at work and it's not that long. But sounds good.Thanks for the reply.
[One (M9) Android Development] peca_slo:
Ok, I am almost allways too late on error 90 reboot and my phone goes into os and then i go to download again and flash one more time, but everytime I am affraid of brick.

Just one more thing do I have to flash firmware in download also two times or only once, cuz i didnt find any instruction from you for flashing in download mode :)

And tanx for your help
[One (M9) Android Development] Sneakyghost:
It reboots to system in any case. At least for me.

The trick is to keep the finger above the volume down button and hit it once the reboot kicks in, then you won't go back to system.

I prefer download mode because I can actually watch what's happening on screen.
[One (M9) Android Development] peca_slo:
Can you put the lines what to wrote for flashing please?
[One (M9) Android Development] Sneakyghost:
http://xdaforums.com/one-m9/development/firmware-t3068243
[One (M9) Android Development] peca_slo:
so I just hit: fastboot flash zip Firmware_xx.zip
[One (M9) Android Development] japjaan:
edit: nvm, remove post please
[One (M9) Android Development] simonbigwave:
yes. Its in the OP.
[One (M9) Android Development] nkk71:
[MENTION=1102297]Sneakyghost[/MENTION], at your discretion:

US Developer Edition firmwares

untested, but put together in the usual manner (RUU decrypt, made sure it's successful, and packed them), but dont have time to flash them atm.

M9_2.11.617.15_FullStock_rename_to_ROM.zip

M9_2.11.617.15_NoWipe_TWRP_2871b1_rename_to_ROM.zip

the files in red were removed from the NoWipe firmware:

Directory of W:\M9_2.11.617.15_FullStock_rename_to_ROM.zip

01/08/2015 00:39 741,760 aboot_signed.img
01/08/2015 00:20 10,195,968 adsp.img
01/08/2015 00:10 602 android-info.txt
01/08/2015 00:39 93 android-info2.txt
[STRIKE][COLOR="Red"]01/08/2015 00:32 304,087,040 apppreload.img
01/08/2015 00:44 602 backup_android-info.txt[/COLOR][/STRIKE]
01/08/2015 00:24 898,063 bootloader
[STRIKE][COLOR="Red"]01/08/2015 00:39 36,438,016 boot_signed.img[/COLOR][/STRIKE]
01/08/2015 00:20 9,544 cir.img
01/08/2015 00:32 62,914,560 cota.img
01/08/2015 00:20 1,055,744 cpe.img
[STRIKE][COLOR="Red"]01/08/2015 00:24 9,011,200 dt.img
01/08/2015 00:31 11,056 dzdata_16g.hdr
01/08/2015 00:31 598,320 dzdata_16g.img
01/08/2015 00:31 20,160 dzdata_32g.hdr
01/08/2015 00:31 944,320 dzdata_32g.img
01/08/2015 00:32 23,952 dzdata_64g.hdr
01/08/2015 00:32 1,180,560 dzdata_64g.img[/COLOR][/STRIKE]
01/08/2015 00:24 741,760 emmc_appsboot.mbn
01/08/2015 00:08 17,408 gpt_main_32g.img
01/08/2015 00:08 17,408 gpt_main_64g.img
01/08/2015 00:39 39,043,072 hosd_signed.img
01/08/2015 00:20 66,578 hyp-8994-1.img
01/08/2015 00:20 1,572,864 modem_st1.img
01/08/2015 00:20 1,572,864 modem_st2.img
01/08/2015 00:24 4,341,932 persist.img
01/08/2015 00:20 5,484 pg2fs_ship_signkey.img
01/08/2015 00:20 39,286 pmic-8994-1.img
01/08/2015 00:20 52,483,072 radio.img
[STRIKE][COLOR="Red"]01/08/2015 00:27 2,134,144 ramdisk.img[/COLOR][/STRIKE]
31/07/2015 16:40 121 rcdata.img

[STRIKE]01/08/2015 00:39 38,670,336 recovery_signed.img[/STRIKE]
^^ replaced with TWRP2871b1 as recovery.img

01/08/2015 00:20 196,012 rpm-8994-1.img
01/08/2015 00:20 706,914 sbl1-8994-1.img
01/08/2015 00:20 35,168 sdi.img
01/08/2015 00:20 467,372 sensor_hub.img
[STRIKE][COLOR="Red"]31/07/2015 16:40 4,194,304 splash1.nb0[/COLOR][/STRIKE]
01/08/2015 00:20 49,189 tp_MXM11876.img
01/08/2015 00:20 63,004 tp_SYN3351.img
01/08/2015 00:20 531,858 tz-8994-1.img
40 File(s) 575,081,710 bytes

android-info.txt:

modelid: 0PJA11000
cidnum: BS_US001
cidnum: BS_US002
mainver: 2.11.617.15
btype:1
aareport:1
hbootpreupdate: 3
nohardreset: 1
resparseoption: -S800M
erasepartition: cache
eraseonflash: system
eraseonflash: userdata
eraseonflash: aboot
eraseonflash: adsp
eraseonflash: boot
eraseonflash: cpe
eraseonflash: hosd
eraseonflash: hyp
eraseonflash: radio
eraseonflash: recovery
eraseonflash: rpm
eraseonflash: pmic
eraseonflash: sbl1
eraseonflash: sdi
eraseonflash: tz
eraseonflash: rfg_1
eraseonflash: sp1
eraseonflash: cota
eraseonsoff: frp
eraseonsoff: absolute
erasepartition: ddr
erasepartition: carrier
[One (M9) Android Development] Sneakyghost:
Thanks mate. Might have time Tuesday. I'll add those to the document then.
[One (M9) Android Development] nkk71:
thanks, might even have time to flash and put a log up by then :o

---------- Post added at 22:47 ---------- Previous post was at 22:29 ----------

Quick look, but seems quite minor changes (2.10.401.1 vs 2.11/617.15

seems the only major part in the firmware is radio:

2.11.617.15 -> SSD:01.01_U11440601_76.03.50611G_F
2.10.401.1 -> SSD:01.04_U11440601_71.02.50709G_F

though I didnt compare to previous DevEdition, maybe it's in the /system which is still uploading
[One (M9) Android Development] MrGriffdude:
So how do i know what firmware to flash when updating?
[One (M9) Android Development] j to the 4n:
latest
[One (M9) Android Development] Sneakyghost:
Latest of your cid/sku.

If you care to read the initial posts, there's also some info on how HTC software version numbers are being put together.

The "sku" block denotes the market, customer our region the software was rolled out to. Ideally you should stick to what your phone came with. So if it's a 401, stick to that unless you know what you're doing, you are experimenting or you are an idiot.
[One (M9) Android Development] MrGriffdude:
thanks man, also is there a way to check what firmware you are running on the m7 it was on the boot loader screen and it isn't there anymore.
[One (M9) Android Development] Sneakyghost:
This isn't a Q&A. Please refer to the first posts. All info there. Else I'll have this conversation removed.
[One (M9) Android Development] MrGriffdude:
Sorry man, its just a lot to remember coming from the Nexus 5 where software updates were so easy. Won't be a problem anymore.
[One (M9) Android Development] darkenedpath:
I flashed this also since I have a dev ed....... Works great. Thank you for this.

C:\platform-tools>adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

999999999999 device

C:\platform-tools>adb reboot download

C:\platform-tools>fastboot flash zip M9_2.11.617.15_NoWipe_TWRP_2871b1_rename_to

_ROM.zip

target reported max download size of 800000000 bytes

sending 'zip' (65203 KB)...

OKAY [ 6.162s]

writing 'zip'...

(bootloader) HOSD CL#576582

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

(bootloader) Perform pre-update

(bootloader) start@20

(bootloader) aboot_signed.img@100%

(bootloader) adsp.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: 8.221s

C:\platform-tools>fastboot flash zip M9_2.11.617.15_NoWipe_TWRP_2871b1_rename_to

_ROM.zip

target reported max download size of 800000000 bytes

sending 'zip' (65203 KB)...

OKAY [ 6.084s]

writing 'zip'...

(bootloader) HOSD CL#591203

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

(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.469s]

finished. total time: 15.553s
[One (M9) Android Development] lyericwang:
I got a very strange problem on firmware, I posted in viperM9 thread, would you please help out? Thanks. http://xdaforums.com/showpost.php?p=62783783&postcount=8136
[One (M9) Android Development] timkelly0810:
Hey, guys. I'm trying to flash the latest firmware to my M9 device to i can then flash the newest 6.0 MaximusHD. I'm still on 1.0..... Lameee. I got this far and haven't bricked my phone. this is the error I'm getting and it isn't updating my firmware. Any ideas?

C:\Android>fastboot flash zip unsigned_firmware_2.7.401.1.zip

target reported max download size of 800000000 bytes

sending 'zip' (50390 KB)...

OKAY [ 5.083s]

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: 7.233s

C:\Android>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.002s]

finished. total time: 0.003s

---------- Post added at 05:30 PM ---------- Previous post was at 04:34 PM ----------

I'm sorry. I'm having this same exact error. What did you do to fix this problem?
[One (M9) Android Development] donmarkoni:
Please, kind sir, go back to elementary school and learn to read. Thank you.
[One (M9) Android Development] xunholyx:
You probably should have highlighted the "CID not matched" part as well, if not only. Just sayin.....
[One (M9) Android Development] cygnus56:
First I put Super cid and then returned to flash firmware
[One (M9) Android Development] xunholyx:
Post the results of fastboot getvar all
[One (M9) Android Development] ThePhoneGeek:
I understand there is a new update out for TMO US but I don't see it listed here. Call me paranoid but I've reached a point where I don't trust it unless I get it from Sneaky when it comes to firmware.
[One (M9) Android Development] tvgdb:
Hi,

I'm having some difficulty flashing the latest firmware to my M9. The firmware fastboot flashing worked, but when I reboot to TWRP and try to install a ROM via zip, I get an error: "E: Unable to mount '/cache'". The ROM was not installed after that, even though TWRP returned a success code.

Could anyone help me out?

EDIT: I fixed it by going S-OFF, then reverting to a lower firmware, reflash the RUU via putting it on the SD card and then OTA-ing to the latest version.
[One (M9) Android Development] darkenedpath:
Sorry if this is a stupid question sneaky, but I just had to ask, and didn't know if others had this come up. I flashed the 2.11.*** firmware provided in the thread. It flashed fine. Download mode stated the OS was the same as the firmware flashed, so did fastboot getvar. A couple weeks later I flashed a splash screen from another thread. I didn't think of it, but just recently I looked, and after flashing the splash that was based on 401.15 firmware, my Os version stated that same software (401.15). I reflashed the 2.11.*** firmware, and it is up to date now. For the little while after I flashed the splash screen, I had issues with the XDA app connecting correctly. After I flashed the latest Dev edition firmware again, it is working fine.

My question is, why would the software revert to that old version based on the splash, and could it actually do it? It did give me issues after I flashed the 401.15 splash, "ex. XDA app". But is not since the reflash of the newer firmware (2.11.***. I don't have documentation of it, but wil repeat everything if it's something worth looking into.sorry I'm a noob. Just want to learn.

I only posted in your thread because of the knowledge that is here. And I'm not asking help me, I'm asking if, why , and is it possible. I've caught more knowledge from these threads then others, so any advice is welcome. Thank you for all previous help. This just blew my mind.
[One (M9) Android Development] xunholyx:
Hiding the firmware version that you flashed isn't helping to help you. The *** is uncalled for. It isn't sensitive information. The firmware version you flashed shouldn't be edited if you need assistance.

Provide the results of fastboot getvar all (delete the IMEI, MEID and serial # ~~ that is private info) and it will give us more to work with.
[One (M9) Android Development] darkenedpath:
I'm not trying to hide the firmware version. It's the latest Dev edition firmware as I stated. I just couldn't remember the last bit of it off hand. That's why I put ***, to fill in space. I'll give the getvar, but IDK what that will help with the question I've had. Please read it, if it's misleading, sorry sir. I'll post a link to whatever I have to, flash what I have to to show as I ask. I flashed a splash screen, wondering why my OS would show 1.40.401.15 after I flashed it instead of 2.11.617.15 in the OS in download mode. Thanks for the reply, but I ask in the thread because it is the most informative, and hope this is a question that could help others, and IDK why it would change. Not what it seems as you took of it. I am a little more advanced then some. Getvar won't help unless I do all steps as I asked if I needed to do. Trying to help myself understand things, also others if they will read.
[One (M9) Android Development] simonbigwave:
suggest you read his reply again and post your fastboot getvar all.
[One (M9) Android Development] darkenedpath:
I made some time to show this happening on my phone. My computer has bad connection at my house, so when I get to work, I will try to organize all the getvar, with the pictures of my download mode to show. Sorry it's been a while, but I hope this may help in the future. Again..... Tomorrow I can post it, so please don't ask me to before then. Thanks.
[One (M9) Android Development] xunholyx:
It's no problem. Post it when you can.
[One (M9) Android Development] jbfountain:
The reason it changed the version number is because the android-info.txt in the splash screen zip you used had the older mainver listed. It didn't change your firmware just what was being reported. If you open up the splash screen zip you used, and edit the android-info.txt mainver to the firmware you have installed and reflash you will see the correct version number.
[One (M9) Android Development] jony09281:
help updating firmware

I have T-Mobile with 1.32.351.24 and can't flash to the new firmware, help please.
[One (M9) Android Development] nirbo:
Firmware Flash

Hey everyone,

I just got my M9, seems like the Taiwan version - the firmware version it came with is 1.36.709.3.

The device is unlocked and S-OFF now.

I'd like to flash the international firmware, what are the steps i need to take in order to do so?

Asking as a precaution, so I don't brick the device.

Thanks!
[One (M9) Android Development] mattygaga2012:
HELP!!!! Can't flash carrier branded firmware to my One M9!!

Hey guys I'm having some difficulty with flashing Stock H3G (ThreeUK) firmware to my O2 Branded HTC One M9. I changed the CID to HTC__001 and done everything correctly, but this is what happens when I tried to flash it via FastBoot. I did try he TWRP recovery method but it just shuts the screen off then brings me back to the TWRP initial screen... Please help!!

[command prompt info]

Microsoft Windows [Version 10.0.10576]

(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\matty\Desktop\HTC\ADB_new>adb reboot download

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

C:\Users\matty\Desktop\HTC\ADB_new>fastboot oem rebootRUU

... OKAY

C:\Users\matty\Desktop\HTC\ADB_new>fastboot flash zip Firmware_xx.zip

sending 'zip'... (167433 KB) [isLargeZip: 1 fileCount: 1 / 7]

Sending... 10240 KB / 167433 KB

Sending... 20480 KB / 167433 KB

Sending... 30720 KB / 167433 KB

Sending... 40960 KB / 167433 KB

Sending... 51200 KB / 167433 KB

Sending... 61440 KB / 167433 KB

Sending... 71680 KB / 167433 KB

Sending... 81920 KB / 167433 KB

Sending... 92160 KB / 167433 KB

Sending... 102400 KB / 167433 KB

Sending... 112640 KB / 167433 KB

Sending... 122880 KB / 167433 KB

Sending... 133120 KB / 167433 KB

Sending... 143360 KB / 167433 KB

Sending... 153600 KB / 167433 KB

Sending... 163840 KB / 167433 KB

Sending... 167433 KB / 167433 KB

OKAY

writing 'zip'... (bootloader) HOSD CL#576832

(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) ERR ZIP ERROR, exit read zip loop

(bootloader) Update zip file OK

(bootloader) ERR ZIP ERROR CODE, 7

(bootloader) end@Done

FAIL7: fail to flash via downloadzip

FAILED (remote: 7: fail to flash via downloadzip)
[One (M9) Android Development] Chezbel:
Try changing your CID to 11111111, eight 1's.
[One (M9) Android Development] xunholyx:
HTC__001 is the wrong CID for ThreeUK. That is for WWE/International. The CID should be H3G__001.

Or you could change to super CID (11111111) as stated above.
[One (M9) Android Development] mattygaga2012:
thanks dude I figured that out haha!! :D I now have another problem. I am trying to push a modified HEX file (p8) for OFFICIAL status (instead of MODIFIED) and it comes up with FAILED (remote: 35: SD_PARTITION_NOT_SUPPORT pg2fs any suggestions?