yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] coal686:
As requested by the OP, I've removed some of the extraneous posts of stuff that was discussed in the OP. If your post was removed inadvertently, I apologize. Looks like some good work going on here, so carry on. If you have any questions or concerns, please feel free to let me know.

Thanks,

coal686

Forum Moderator
[One (M9) Android Development] Sneakyghost:
Nope I know what it is because it reads clearly CID error. All I have to do now is work my way through all the old error descriptions which do not have much meaning left on the M9 - well the meanings stay but the errors have a fair share of new numbers and the SD_UPDATE_ERROR prefix now from HOSD - so there needs to be some explaining done of what HOSD (most likely) is and how to understand the errors. Don't think you can help with that except if you find another error that makes no sense even when comparing against the old set of errors you can post it here for me, and if its not immediately obvious like with that Error 7, briefly describe what lead to the error so I can try to reproduce it or at least gain understanding.
[One (M9) Android Development] Sneakyghost:
Extraneous... nice. I'll add that to my personal dictionary. Thank you, Sir for the cleaning job.
[One (M9) Android Development] rwleigh:
ERROR.

I'm having trouble flashing this on my new M9.

When I try I get this error:

C:\Android>fastboot flash zip firmware.zip

sending 'zip' (46477 KB)...

OKAY [ 3.337s]

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

When I noticed the ERR CID I thought that must be the problem so I changed it using the batch tool to 11111111, flashed firmware again and it took about 1 minute and said finished.

I'm still stuck on 1.32 firmware so I can't update my phone. :(

Any help appreciated.

---------- Post added at 07:27 AM ---------- Previous post was at 07:18 AM ----------

Further to my last post I've now booted into download mode to look and it says OS 1.40.401.8 so I'm thinking it might have worked.

I was looking in software info in the phone settings/about.

Maybe I am good to go but unfortunately I have to go to work now...:(

I will continue later...
[One (M9) Android Development] xunholyx:
You are good.

What it says in software version in settings is the ROM base: the firmware the ROM you are running is based on.

Your firmware version is what it says next to OS in bootloader.
[One (M9) Android Development] rwleigh:
I have now flashed the latest ROM update successfully and it's all good... :D

Few, and relax...
[One (M9) Android Development] tiho5:
This thread should have "FUU" in its title.

This is a trade mark.

The flashing method(s) are one thing.

They aren't invented by us.

While FUU is a concept of the thread creator. His own contribution. One after which is everyone subscribed to this thread. And also a good key word for searching in each forum where the FUUs have been made available.

Might be wrong. If so, correct me
[One (M9) Android Development] Gordon-B:
I was wondering if anyone could help me.

I followed the directions, and got an error 7, but after the phone rebooted automatically, it finished up installing the new firmware.

Then I flashed a no-wipe zip 1.40.401.8 and tried to install Viper-Rom, but the phone was rebooting each time the screen went off.

so i figured that there was something wrong with the versions and did a full wipe install.

now i can't install any zip. It hangs at the part where it starts the install and freezes, then goes into a boot loop.

I cant see any file system at all.

I've tried putting ADB sideload mode in, but it doesn't recognize it

Please, does anyone know what i should do?
[One (M9) Android Development] Asselalf:
More information please. Can you post the output from Fastboot getvar all? (Remove your Serialnumber & IMEI)

Gesendet von meinem HTC One M9
[One (M9) Android Development] Sneakyghost:
2.7.401.1 NoWipe with TWRP 2.8.6.1 Beta 2

What's new?

New Firmware for Android 5.1 has been made available by Llabtoofer. This is the NoWipe version. Difference to the pack from Llabtoofer: dt.img (part of the kernel) and Splash1 have been removed additionally to the already removed Boot, Ramdisk (both kernel parts) and Recovery. Also the dzdata files (wiping SDcard) had already been removed by Llabtoofer. As such, I cannot create a FullWipe zip unless someone sends me the RUU.zip with the full firmware.

Added: Recovery TWRP 2.8.6.1 Beta 2 from CT.
[One (M9) Android Development] Sneakyghost:
Tiho5, I had previously decided to not provide the FUU anymore, well not aggressively advertise it anymore. Its a product I am not convinced about anymore. Plus, currently, its not working and I don't understand why. The ARUWizard does not like working with modified firmware zips anymore. It will always do the pre-flash of Aboot and then stop and say USB connection error (170 or 171) and I can't figure out why.

So, no, I will not add it to the title. But you can still use it via my Batch Tool, its still integrated. Just be aware that flashing modified firmware zips doesn't currently work.
[One (M9) Android Development] Black-FR:
Nice to see, that you got the full firmware package already done, for the 2.7.401.1 base.

Thanks, for the work.

Gesendet von meinem HTC One M9
[One (M9) Android Development] vegetaleb:
Hello bro!

So the flash by external SD method is good? In which name I have to rename the FW you posted?
[One (M9) Android Development] Sneakyghost:
0PJAIMG.zip - I haven't tried the method with modified zips, only with HTC zips with intact signatures.

Just try and see what the phone returns, report here.
[One (M9) Android Development] vegetaleb:
I used to flash with this method on M8 with nonwipe FW (mainly from yours) the M9 FWs are different?
[One (M9) Android Development] Sneakyghost:
Dude, just try. I already said I have no experience.
[One (M9) Android Development] vegetaleb:
Ok will do
[One (M9) Android Development] vegetaleb:
Damn!

Download mode is saying: No SD Mounted

Mine is PNY 64gb Turbo

Should I use my old 16gb sandisk?
[One (M9) Android Development] liam_davenport:
I'm sure trying it is quicker then waiting for an answer ;)
[One (M9) Android Development] blueberry60:
Do you know how to uninstall batch tool from PC ? I couldn't do it.
[One (M9) Android Development] bzhmobile:
Delete the folder of the tool ...
[One (M9) Android Development] GeorgeReagan26:
please help i need NAND Backup and i can not dowload the file

My version- main: 4.16.401.10

and CID is cidnum:HTC_J15

i cant not dowload your nand backup it says tha file that your trying to dowload is no longer available...

please help me bacause my HTC M8 is brick...please i beg you..help me to download that TWRP Backups by sneakyghost..please..thank u

please Mr. sneakyghos this from the thread HTC ONE M8 FIRMWARE OTA UPDATES,TWRP BACKUPS AND MORE...

PLEASE HELP ME TO HAVE YOUR FILE..PLEASE
[One (M9) Android Development] jollywhitefoot:
This is M9 forum...

M8 Forum is here: http://xdaforums.com/htc-one-m8
[One (M9) Android Development] Sneakyghost:
I am also quite sure there is a BIG RED TEXT in my thread saying no exFAT, no SDXC, just FAT32 and SDHC.
[One (M9) Android Development] Sneakyghost:
Yea like manually searching Windows registry for entries made by my installer? I am sure I'd have chosen another install creator if I had needed registry entries. No, it is just a simple RAR archive with a self-extracting routine and the resulting folder can just be deleted and its gone.
[One (M9) Android Development] rentngo:
hi, while in download mode, nothing happen after typing fastboot oem rebootRUU... also tried with the batch tool and cannot see the zip file after putting it in android\com file... (error 157)... phone is S-OFF, CID HTC 032, os 1.32.401.15... any help pls? thx
[One (M9) Android Development] simonbigwave:
OT- in case anyone wanted to convert to FAT32, i thought these tools might be useful; fat32format http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm and Fat32Formatter version 1.1 http://tokiwa.qee.jp/EN/Fat32Formatter/
[One (M9) Android Development] rickylambert:
Noob question here: I´m currently on 1.40.401.8 firmware, running 1.40.401.8 based ROM, SuperCID(in case that matters). Can I simply upgrade to 2.7.401.1 base?

Thanks in advance.
[One (M9) Android Development] Black-FR:
If you want to run a ROM, based on the new firmware, then you could use the firmware package, to upgrade your firmware.

If you will stay on a 1.40 based ROM, then you still could use the new firmware, but I'm not sure, if it runs correctly with a 1.40 based ROM.

Gesendet von meinem HTC One M9
[One (M9) Android Development] iElvis:
Plenty of people have reported that the 1.40 roms work with 2.7 firmware, though there are apparently a few bugs here and there for some.
[One (M9) Android Development] clsA:
Corrected my post sorry for the confusion

Also the new 1.32.617.30 is posted in the Ruu thread now >> http://xdaforums.com/showthread.php?p=59907878
[One (M9) Android Development] niceguy0815:
S-Off but LOCKED Boodloader

Hello,

i dont know if its the right pace here ???

I Have som questions about fw flashing unlocking :)

I got my new HTC ONE M9 International s-offed and Supercid but Boodloader is locked.

I had it in a repair center in Berlin (Germany) and they S-Offed it for me and do Super Cid, but they cant unlock it without HTC dev.

Because to unlock via fastboot the Android System needs root right(they sayed that to me)?

but if I get it right form my old m7 i can upgrade firmware with S-off and supercid with locked ore unlocked bootloader?

So is it posible to flash a modyfyed prerooted fw via fastboot download mode?

And than unlocking the bootloader manualy via fastboot comand?
[One (M9) Android Development] herwegan:
Hey mate, i'm sorry we can't give you any more detailed information about this stuff atm, since we don't have s-off ourselves at this point.

Will come back to you when we're ready.
[One (M9) Android Development] Sneakyghost:
Just FYI everyone:

AFH's sister site Androidruu.com a.k.a Alex's neglected stepchild is now getting some new attention.

He will be adding RUU's we already have to http://androidruu.com/?developer=M9 folder and whoever has any M9 RUU's can contact Alex over at AFH and shoot him links to add to the M9 folder too.

Notice: we already have almost all available HIMA_UHL and HIMA_UL RUU's (at least those that are NOT available on HTC's own ROM site so only upload RUU's to AFH which you do not see there or on HTC's site.
[One (M9) Android Development] niceguy0815:
I'm now testing to flash a 401.15 Firmware with TWRP and not originaly recovery inside, on my One M9 with S-Off and Super Cid anld locked Bootloader.

I hope to get the TWRP Recovery on my Locked Bootloader device to root the Original Sens Rom. Because I Dont want to unlock it via HTC Dev.

Linke I sayed before on my One m7 and on a frinds M8 I can Flash not sighned FW withe Device that is S-Off and Super Cid but locked Bootloader.
[One (M9) Android Development] Sneakyghost:
We do not have recovery flashable firmware zips in this thread. Please use fastboot.
[One (M9) Android Development] niceguy0815:
yes I used the 401.15 FW and changed the rcovery to TWRP in the zip and flashed it via fastboot.

It works and it istalles the recovery on the locked bootloader device.

But it seams so unlocked bootloader ist neded to do a nadroid backup or install SuperSU ore install custom rom.

Superuser 4.46 flashs with sucsess but no su right in rom and no Super SU app.

tested to flash a custom rom Ledroid ..flashes with status1 hangs on boot

so I Ruu ed it back to stock :)

Now I unlocke the bootloader via HTCDEV :(
[One (M9) Android Development] mick_soul:
You should have tried Superuser Beta 4.48 and the latest TWRP from Captain_Throwback.
[One (M9) Android Development] niceguy0815:
Super user 4.46 i tkink and TWRP 2.8.6.0
[One (M9) Android Development] Captain_Throwback:
Quite an adventure this new device is. HTC always changing stuff up on us. ABOOT, block-based OTAs - when will it stop?
[One (M9) Android Development] Sneakyghost:
Ya whereas the block-based OTA's had me think if maybe Chainfire's FlashFire thing (It was on the news the other day and I read its working on block-based devices) could be outfitted to do HTC M9 flashing now?

I briefly thought of hitting him up on that but then figured its a noobish thought and probably no point even asking so I withdrew back into my cave and fiddled with fastboot.
[One (M9) Android Development] mick_soul:
SuperUser 4.46 causes issues with TWRP 2.8.6.0 on the M9.

Please read about it in the TWRP thread and try SuperUser BETA 4.48 instead, which should work.
[One (M9) Android Development] Tecardo:
To make it clear. This are the errors I encountered.

1. Flashing zip with normal fastboot: fastboot crashes before trying.

2. Flashing with htc fastboot: the phone makes the pre update and wants to flash again. The second try it crashes. Fastboot is also crashing.

This would normally be a brick. As it seems it's not. So first don't reboot and let it flash again. Circle should be activate again. Your now save to reboot. It's possible to reboot before, but it's untested by me.

3. Sdcard: it seems that exfat is not recognized. I couldn't test of it's working correctly as Sneaky said.

So my conclusion: please only flash with an 16gb or below sdcard with fat32. Seems to be completely save.

Thanks sneaky :)
[One (M9) Android Development] Sneakyghost:
I am facing a weird issue after a RUU flash. The second time. I had that already last night and thought it was random but it happened again today after the next RUU flash. System cannot be accessed after the RUU flash. The phone boots fine but TWRP cannot handle System in any way.

Last night i could fix that by restoring a clean stock backup of my 1.32.206.15 and then restore viper, but i could NOT restore viper directly and i was NOT able to mount system manually (mount -t ext4 ....) or by flashing SuperSU or whatever. Only by restoring an untouched stock backup.

[EDIT]

I was later able to get system accessible for custom ROMs again. It started to work after I unplugged the phone and shut it down completely. I will try to reproduce this later today to verify that this "mis"behavior can be fixed by a full power down.

[EDIT 2]

Next test revealed that the "PowerOFF and remove cable" thing was a shot into the blue. Its not reproducible. Still haven't found out what makes /system writable again for custom backups and roms.

Here's the log of an attempted ViperOneM9_1.1.0 restore operation straight after a RUU flash via SDCard method: http://pastebin.com/VrbkquH2
[One (M9) Android Development] Black-FR:
Thanks for all those useful informations.

It worked well, to install the 1.32.401.8 RUU, via the sdcard method.

I used my 32GB SDHC card.

And as additional information, also with S-ON, it works while the bootloader is unlocked.

Pretty nice, that there is no need to lock the bootloader, if you flash the RUU (0PJAIMG.zip) via external sdcard.
[One (M9) Android Development] d-pak:
Can I use this method to write a developer edition ZIP to an ATT version of M9?
[One (M9) Android Development] Sneakyghost:
If the M9's new bootloader tech allows for it like it did on the previous HTC devices, yes. As long as you set your phone S-OFF.

But on another note: I have heard that the new AT&T devices actually ARE the developer edition phones. If that is so, and CID/MID and version number "SKU" are all identical between DevEd and AT&T, you should even be able to do so with S-ON.

You can simply try and report back what happens if you wish to contribute some research aspects.
[One (M9) Android Development] Behold_this:
Mid (0PJA11000) are the same between AT&T, developer, and unlocked editions, however, they have different CID for all three:

BS_US002=DEV

BS_US001=UNLOCK

CWS__001=AT&T

and two different region skus:

502=AT&T

617=dev/unlock
[One (M9) Android Development] Sneakyghost:
So not interchangeable while S-ON then.
[One (M9) Android Development] tmaxraiden:
hi, I have a big problem, while in rebootRUU mode I tried to flash the unsigned firmware 2.7. but something went wrong. I had a failed unknown message and now the phone is dead. I have a black screen like with battery image in the middle like when the phone is charging

Please help

( S-OFF, CID HTC 031)
[One (M9) Android Development] ThePhoneGeek:
Ok I can't take the insanity anymore!!! I changed to T-Mobile (from Sprint) and bought a G4 and have had nothing but problems with it so I am going back to HTC (I'll miss the G4 camera).

So I am going to probably purchase the developer edition from HTC and use on TMO network and will s-off right away. What I want to confirm is that if I super CID I can load the current T-Mobile firmware so that WiFi calling works (depending on the ROM I know) and such correct?

Having been away from GSM for a few years I haven't kept up on that because I didn't have to worry about it on Sprint.

I read the last ten pages or so did a search regarding this and found a reference to someone saying you could load AT&T firmware on a dev ed device so I think it will work but wondered if anyone new for certain.

Thanks,

PG
[One (M9) Android Development] Sneakyghost:
Provided you go buy SunShine or a Java Card and treat your phone to S-OFF and SuperCID you can just flash anything (except CDMA), full conversion that would be called. Stay away from VZW and Sprint firmware (CDMA) and you will be fine.

Notice for returners: earlier HTC devices had the CID put into the usual place and replaced by the SuperCID command - the M9 differs in so far as that it stores a backup copy of the original CID in the /misc partition.

I have not had the time to read, research and mess around with my own phone to see what happens if you just "forget" about that backup CID.

Only thing i know is that I converted my carrier M9 to an international unlocked version and experienced no real hiccups. The backup CID is still in place.

However, I have run across the occasional flash fail (wrong CID/wrong MID and such) which occasionally had me thinking about that maybe being due to that backup CID.

Like it always is in my life these days, I had no time or energy left to actually investigate that (sometimes i just need to come home and relax instead of think through stuff).

So, in order to keep the "spirit" of my thread alive, I can only repeat again and again: the thread is mainly for information gathering / research purposes and anyone contributing by testing out stuff and reporting findings, including findings of unusual error messages, is very welcome.

As usual, I explicitly exclude posts like "please halp fx my brckd phone".

I don't perceive this as a general help thread. I see this as a hub for adding info everyone can use.

If this was a help thread, I would have placed it in general section.

So, if you feel like, if you are a nosy person and like to dig through stuff, feel free to try and report how it went. And should you ever come across unusual stuff that gives you the impression of maybe being related to the backup CID messing with your conversion, I am happy to have that info here.
[One (M9) Android Development] ThePhoneGeek:
[MENTION=1102297]Sneakyghost[/MENTION] Thanks for the info. I wasn't intending to offend or irritate with my question.

PG
[One (M9) Android Development] simonbigwave:
Is there a reason you are not supercid?
[One (M9) Android Development] descenpet:
i think a lot of people with generic europe CID don't bother super cid because almost all of the firmware you find here works for them with their original cid.

and his problem doesn't look like it has anything to do with cid.
[One (M9) Android Development] OGhoul:
Delete.
[One (M9) Android Development] clsA:
[MENTION=1102297]Sneakyghost[/MENTION]

I uploaded an alternate M9_2.7.401.1_NoWipe for the Developer Edition. If it's ok by you I'll post the link Here:

https://www.androidfilehost.com/?fid=24052804347766681

The edits i did were

and I replaced your TWRP with the Latest 2.8.7.0 and flashed it in Download Mode to my phone
[One (M9) Android Development] Sneakyghost:
Yea fine but why not just go SuperCID? Your text edit won't help people who are S-ON and if you are S-OFF, SuperCID is much more convenient...
[One (M9) Android Development] clsA:
Seems easier to flash my edit than change CID and MID to me.

6 of one and half a dozen of the other I guess.
[One (M9) Android Development] descenpet:
Many would prefer super cid because it Just stays after changing it once and don't need to care again no matter what they want to flash.
[One (M9) Android Development] darkenedpath:
No offense [MENTION=1102297]Sneakyghost[/MENTION], that does seem easier for some of the other users. May cut down on some of the error message. But I still respect sneakys thought of this being a learning thread and knowing how to change things to make it work. Thanks for this
[One (M9) Android Development] Sneakyghost:
That doesn't make sense for me. There is no need to change your MID (which has gotten easier on the M9 as well, by the way).

Changing Android-info.txt involves opening a zip and editing the text file. There is a lot inexperienced users can do wrong, from picking the wrong zipping tool to picking the wrong editor to choosing improper formatting and what not.

Changing to superCID involves two commands, takes 20 seconds to reboot and it's all done for good.

[emoji12]
[One (M9) Android Development] blueberry60:
If we change device to SuperCID,don't we have to type "htc_fastboot flash zip firmware.zip" twice ?
[One (M9) Android Development] Sneakyghost:
:crying: ouch who says that?

I assume that is a wild, messed up variant of the info about error90 aboot pre-update requirement.

HTC can force a pre-update of aboot on your phone. The reasons for that will be if changes in aboot would affect the flashing routine, it would need to be flashed separately first, then the phone would need to be rebooted into the newer aboot.

This is because Aboot (on older devices: Hboot) does the actual flash. Fastboot is only responsible for the transfer to the device. Aboot then extracts and (decrypts) and writes the images from the zip. So if HTC changes like e.g. encryption keys or flashing mechanics or whatnot, you would need to flash the Aboot first, then repeat. Simple as that.

We cannot really influence that behavior. There is a parameter in android-info.txt which can control the pre-update behavior but I would NEVER touch it because HTC has reasons to force an aboot pre-update which we do not know (even my assumptions are just guesses). If the Aboot wants a pre-update, give it one. Its really simple too. Just press the Arrow-Up key on your keyboard to call the same command again. Takes you less than a second.

However, I see no connection to SuperCID. Doubt it has anything to do with that. I rather think its a combination of what was on your phone before and the parameter in android-info.txt which determines whether or not you need to flash twice.

==================================================

Request:

I want to fix my Batch Tool for a newer release, some stuff has been updated, some has been fixed already (like Splash converter/flasher).

However, I have a problem getting a screenshot via ADB. I assume its due to ADB not being allowed to access the graphics buffer at fb0 anymore due to SELinux restrictions. If anyone of you knows a way around that, can you fill me in or hook me up to info sources? I am not gonna dig around much, did a quick scan through google and nothing came up.

If that's not easily fixed I'll remove that function from my batch tool. TWRP takes screenies now anyway. I just liked to take screens with ADB while its booted in android cuz its convenient. But its nothing important.
[One (M9) Android Development] blueberry60:
I think we let our devices to be rebooted into a newer aboot to type same command second as your information.