yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] 3ogla:
remote: 21: fail to flash via downloadzip

Hello,

I followed steps carefully I dont know what went wrong, error code 21 doesnt seem to be listed in the "possibly safe" fails and I cant find an answer for it , I hope im not in a bad position,

First I got the Fail 90 then I flashed again as it is mentioned but after I got this, now it looks like the green bar stopped at 90%

remote: 21: fail to flash via downloadzip

I have S-Off through Sunshine
[One (M9) Android Development] 3ogla:
[FIXED]

Ok I dont know what was wrong but I downloaded the Firmware from another thread and it worked perfectly

Thank you
[One (M9) Android Development] donmarkoni:
Have you checked md5 after downloading such a critical thing as firmware?
[One (M9) Android Development] Sentinel196:
Can anyone confirm it's safe to flash from the newer 2.4.401 firmware including bootloader back to the older 1.40 version via RUU?

I have an S-OFF, Super CID M9 thats running ARHD 10 with the 2.4.401 bootloader, radio, etc and I want to flash it back to stock with the 1.40 RUU to sell.

Thanks :)
[One (M9) Android Development] blueberry60:
I went back to older 1.40.401.8 via 0PJAIMG method from 2.40.401.1 firmware,I had never any issue.I confirm it is safe.
[One (M9) Android Development] Sentinel196:
Thanks very much!
[One (M9) Android Development] Sneakyghost:
You guys seriously gotta read the HOSD output. It tells you in your face the zip was broken when you flashed it.

Which zip was it, one of mine?
[One (M9) Android Development] Sneakyghost:
Can you please try and confirm, in order to contribute some info?

Thanks.

I haven't tried it yet. Or have I? Actually I believe I did try. Or no? Not sure.

Just flash it and report.
[One (M9) Android Development] Sentinel196:
I'll report back either tonight or tomorrow. But the earlier poster confirmed it worked for them. Hopefully I don't brick my 7 day old phone. lol. I don't see any reason why it would be an issue. I just remember there were issues with the M7 when backward flashing bootloaders which is the only reason I ask. I'm used to Sony and Nexus devices where you can just flash anything.
[One (M9) Android Development] 3ogla:
MD5

I downloaded the your Firmware 3 different times from 3 different servers, all 3 times MD5 did not match, is that strange? but when I downloaded the "NoRed" firmware it worked fine from the first try.
[One (M9) Android Development] Sneakyghost:
It's not strange, it just means the upload is messed up and I thank you for the report. Please specify the exact package that didn't work so I can correct it later after work and to let others know what not to download as well.
[One (M9) Android Development] 3ogla:
No I didnt at first :crying: But now I learned a lesson because I think I almost bricked my device, its working well now but with the one from the other thread, I downloaded many times and MD5 never matched. Maybe its my connection but i was not able to locate the problem.

---------- Post added at 02:21 AM ---------- Previous post was at 02:09 AM ----------

Alright, when I get back home from work tonight will update with the packages, Thank you
[One (M9) Android Development] Goldenstarc:
is there any way for s-off except sunshine ?

i want to update my firmware to flash viper3 but my device is s-on
[One (M9) Android Development] liam_davenport:
No sunshine is only way just pay the £17 it's not a huge amount and you will benefit from it greatly or if you don't want to pay return to stock and capture OTA till latest base
[One (M9) Android Development] Sneakyghost:
Java card. Very expensive, sources are mostly Chinese shops and I personally don't trust these cards.

However, here in Germany there are many people on eBay who bought Java cards and I'm sure you find them in your country too. The prices vary a lot, ranging from 5 to 30 Euro.

The reason most of us usually recommend sunshine is because Beaups and Fuses and Jcase and whoever else helps them put the utmost care into ensuring the process is as safe as ever possible and because these guys try to make it as easy as ever possible.

The dedication, honesty, sincerity these guys put into their work more than justifies the price they ask. And above all, paying that license ensures they can keep buying phones which often run once and then die in the experiments.
[One (M9) Android Development] Sneakyghost:
The only way to know is if someone wants to try it. I am often enough the reckless Guinnea Pig. I don't mind others jumping aboard. By the way: I have never bricked a device except with the "brick downgrade method" on the OneS, to obtain S-OFF by manually bricking the device and writing the modified P3 back to phone in QHUSB mode. Which worked but eventually killed the phone two weeks later because, yea, the write process only "seemed" to have worked. The bootloader was corrupt afterwards, still booted, but failed often and at some point just died. Learning curve.

I believe HTC is taking a lot of precautions for our messing, while never admitting to it, there have been a number of changes clearly directed at our community, like the partitions which are now locked to DD writes - a security measure taken so that people can't DD critical partitions. DD is an unsafe writing method. If you DD a bootloader and it corrupts it, see above. Even with S-OFF, you cannot DD every partition anymore.

So, yea, I think you would be pretty safe. Other than that, yes, its been tried already. Just trying to make a general point. I am more than willing to risk my device for finding out stuff but I am happy for each time I dont need to.
[One (M9) Android Development] clsA:
I flashed back to the 1.32.617.30 Developer Edition RUU using the 0PJAIMG.zip on the External SD_card with out any problems

I was on the M9_2.7.401.1_NoWipe for only one day
[One (M9) Android Development] techlogik:
There should be a standard tag when people say "use sunshine" then have afterwards (except Verizon customers)..haha

Sorry, couldn't resist..hoping for VZW...otherwise, Javacard method is going to be the way....back to that forum..sorry, I'm in the International/General area, most doesn't apply when it comes to VZW/Firmware etc..

Come on Sunshine!!!

Good thread though...bookmarking.
[One (M9) Android Development] Sneakyghost:
[MENTION=2450054]Sentinel196[/MENTION] and [MENTION=3952508]3ogla[/MENTION] I am still waiting for the reports which files are broken.

I have time today to fix all broken uploads and I will add the new DevEd firmware 2.8.617.4 as FullWipe and NoWipe packages too in a few.

Would be helpful if you guys could get back to me.

Developer Edition users please be advised that HTC is delivering your OTA with a wrong Changelog. When you get your update notification, it will tell you 2.6.651.11 is gonna come to your device.651 being Sprint :D - don't get excited. It will flash the correct version anyway. Just that HTC messed up their changelog.
[One (M9) Android Development] Sentinel196:
Sorry mate. The person who purchased the phone decided to keep ARHD on it so I never attempted to flash the RUU.
[One (M9) Android Development] Sneakyghost:
Developer Edition FullWipe and NoWipe for version 2.8.617.4 available

I just checked every single file on my AFH against my local copies and there is not one broken one on server- unless my local copies are broken.

I am very much inclined to believe that the day you guys tried to download, AFH has had one of its sudden hiccups. Alex is very transparent about it and if I decided to ask him if his server array has had issues that day he could certainly tell me. But that would be asking a little too much of that overbusy guy :D

So, I will bury this, assuming it was a random thing. Two reports in a day but none before and after strongly suggest a temp server failure.

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

Notice to developer edition users: I'd appreciate one or two quick confirmations on each zip as I didn't get to testing those. They are intact, not corrupted. That's for sure. And zipped up according to working standards. There is no indication that they shouldn't be working.

However, the files are now tested.

NoWipe & FullStock tested by [MENTION=5957136]jollywhitefoot[/MENTION] - thanks!

Please also notice that this is firmware taken from the OTA that HTC rolled out with the wrong version number of 2.6.651.11 (Sprint :D ) - so, it is the same you get via HTC OTA, but with added files from the previous full RUU (those files which weren't updated). It can replace the full RUU from the HTC ROM Site if you prefer smaller downloads or just do it for the "NoWipe" effect.

Creds to [MENTION=3547597]frankcck[/MENTION] for getting me the OTA fast and for checking out the packs later (sorry for the long backup times, dude! :D )

Notice to ViperOneM9 3.0.0 users: according to early tests by [MENTION=3547597]frankcck[/MENTION] (AT&T network) everything works well, except DevEd firmware still doesn't support VoLTE on AT&T.
[One (M9) Android Development] Chezbel:
[MENTION=550917]sneaky[/MENTION], you work too hard and are too nice, LOL.
[One (M9) Android Development] Sneakyghost:
Liar :laugh:
[One (M9) Android Development] jollywhitefoot:
I flashed the No Wipe version without issue. Thanks for continuing to provide your spreadsheet and downloads.
[One (M9) Android Development] Sneakyghost:
The dev edition?
[One (M9) Android Development] jollywhitefoot:
That's correct. 2.8.617.4 - No wipe.

edit: [MENTION=1102297]Sneakyghost[/MENTION] I'll go ahead and test the full wipe now
[One (M9) Android Development] jollywhitefoot:
No problem with Full Wipe either. Thanks again.
[One (M9) Android Development] Joloxx9:
Quick question, do I need to change CID or MID to install latest dev firmware? Im using International m9 and I did s off

Wysłane z mojego HTC One M9 przy użyciu Tapatalka
[One (M9) Android Development] Sneakyghost:
S-OFF and superCID and you can flash any firmware.
[One (M9) Android Development] PlatinumNick:
ok so since the dev edition came out straight from HTC i believe its more stable than the leak from the international version?
[One (M9) Android Development] clsA:
Yeah and the camera updates are included, that were missing in the beta leak
[One (M9) Android Development] 3ogla:
Hello

Hello,

Sorry for the very late reply, yes seems like the servers had issues that day because the day after I re-downloaded from all servers and all were working well, but the issues before were with the "Texas" and "Canada" Mirrors, now they seem to be working well :) Thank you for your good work
[One (M9) Android Development] Sneakyghost:
We can't discuss that here because we only have the firmware in this thread. You gotta look for a ROM based on dev edition to see what's different.

Other than that, dev edition got the same touch panel and sensor hub firmware now that international had in the 2.7 firmware. I didn't notice any difference in touch and sensor behavior though. Must have been some minor adjustments. If I were to take a blind guess, I'd say everything they optimise in hardware must be related to energy consumption because that still is the M9's biggest problem. Or whatever. I'm pretty much done guessing my way around update changelogs and would prefer this not to be placed here for reasons I've outlined like quite a few times already. If you happen to come across some important facts, share them.
[One (M9) Android Development] Sneakyghost:
Batch Tool / Android Tasker 1.2.8 finalized and added to Post #5

Changelog:

1.2.8

Splash1 converter works now. Flashing Splash1 now needs a reboot to Bootloader - it's not working in Download Mode! (limited DD support on the M9 and general flashing system changes).

Swapped out recoveries for newer versions.

Finally added the complete file set from RUU 3.0.1.2015 - the newest M9 RUU. ADB and Fastboot are identical to the previous version from Llabtoofer though.

Screenrecord removed - can’t be bothered figuring out why it doesn’t work anymore. Probably SELinux and general Android 5.x security like with the screenshot function. Not really needed either. There are other solutions.

[EDIT]

I forgot to mention this:

Due to the changes HTC has made to the entire flashing system, the Splash Converter only works to flash a new splash1 in Bootloader mode. Not in download mode. Bootloader mode is the white mode with colored lines of text.

Formerly, I used to flash the splash by means of DD with an adb shell command while booted into android or recovery. This is not supported anymore. The Sp1 partition has been locked away from DD and can only be manipulated with generic fastboot commands, however, these also refuse to work in Download Mode or RUU Mode. They only work in bootloader mode.

Therefore, if you start the Splash Converter batch script while the phone is in Download Mode, it will fail. I forgot about this. I will add an additional reboot command that will reboot the phone to bootloader if it is in download mode, for the next version.

For now, you can start the Splash Converter in both Android and Recovery - it will then reboot to bootloader. You can also start it while already being in Bootloader of course.
[One (M9) Android Development] jdub1983:
Awesome Guide!

Thanks man for this forum! your explanations and directions are easy to follow!
[One (M9) Android Development] czarg7:
I just flashed the WWE zip and everything seemed to go well. was prompted to go back to Download mode when everything was finished. After I rebooted into system from Download mode, i find that I'm still on 1.40? any idea why?
[One (M9) Android Development] PlatinumNick:
did you fastboot flash zip once or twice? your suppose to do it twice the first one is to prepare the system and the second is the actual flash
[One (M9) Android Development] czarg7:
i did it twice. the first one was a fail90. which I note that this has been covered in the step by step guide, so i flashed again immediately. the second time i flashed i got the same flash log as shown in the first post, but once i reboot, I'm still in old firmware.

---------- Post added at 06:39 PM ---------- Previous post was at 06:35 PM ----------

C:\Android>fastboot flash zip M9_2.7.401.1_No

target reported max download size of 80000000

sending 'zip' (47933 KB)...

OKAY [ 3.230s]

writing 'zip'...

(bootloader) HOSD CL#560065

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

(bootloader) start@19

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

this is how mine looked like
[One (M9) Android Development] PlatinumNick:
are you supercid?
[One (M9) Android Development] czarg7:
yeap.
[One (M9) Android Development] PlatinumNick:
how are you checking what firmware your on? are you using the fastboot getvar all or your going to your settings page on the phone?
[One (M9) Android Development] czarg7:
settings page. is that wrong?
[One (M9) Android Development] PlatinumNick:
yeah totally wrong go into download mode and type in fastboot getvar all

next to the word main should be your real firmware
[One (M9) Android Development] czarg7:
holy.... it is 2.7.401.1.... so this is never meant to be reflected in my settings screen? does this mean I can proceed to flash Venom 3.0.0 now? Damn i'm so relieved. 2am now and i'm tinkering with my phone!
[One (M9) Android Development] PlatinumNick:
yes you can proceed the one on the settings page is what the system rom is based on,
[One (M9) Android Development] jollywhitefoot:
The settings>about>software>build number is for the ROM you're using and has nothing to do with the actual firmware that's on your phone.

edit: errrrrrr what [MENTION=4908677]PlatinumNick[/MENTION] said........
[One (M9) Android Development] czarg7:
THANK YOU SO MUCH GUYS! I'm not sure if i thanked correctly through the forum though. I assume when its not highlighted, i thanked you?

Once again, thanks alot, running Viper3.0.0 as i type. Will get to the office a happy guy.:laugh:
[One (M9) Android Development] jollywhitefoot:
Highlighted = Thanked

Not Highlighted = Not Thanked
[One (M9) Android Development] BillTheCat:
Is it possible to just delete the app preload and dzdata files from any given .zip archive and flash it successfully if we don't want the contents? Specifially, I'm thinking of the 1.40x firmware that is factory, but contains the AT&T crapware along with partition wipe. I was tempted to just open the folder in windows, delete those files, and flash away. Would that work?
[One (M9) Android Development] jollywhitefoot:
[MENTION=1034670]BillTheCat[/MENTION]. It's possible to remove the apppreload.img file from the zip, but that's only going to leave your existing pre-load partition intact. So...if your current pre-load partition has att bloat, you'll still have that. The best solution I've come up with is to flash the preload from the dev firmware.
[One (M9) Android Development] Sneakyghost:
100% what you said. Leaving it out will leave you with the bloat you had before. Flash a generic preload and you're clean. International and dev edition are suitable to kill carrier bloat.

A Rom install might be required to remove the bloat from system though - I think an install looks into the preload partition and flashes the apps in there, so if you just flash an empty preload underneath an existing Rom, it'll change nothing.

Gesendet von meinem HTC One M8 mit Tapatalk
[One (M9) Android Development] Alan-B:
Hi,

For my, Fastboot and M9_2.8.617.4_NoWipe_NoRed.zip not work !!! error error error....

M9_2.7.401.1_NoWipe_NoRed.zip it is ok. But the Rom 2.8.617.4 works with the Os 2.7.401.1
[One (M9) Android Development] jollywhitefoot:
You probably didn't change your CID. For the 2.8.617.4 package to work you either need BS_US001, BS_US002, or 11111111

or

add your CID to the android-info file in the firmware package
[One (M9) Android Development] BillTheCat:
Ok, so here's my confusion. Your first post says:

It's probably just me, but I'm not sure if ALL your files are full zip packages, or if only the ones that say 'full stock, wipe'. If only those are the 'full' versions, then some also include carrier bloatware.

I'm asking, because I seem to recall the behavior of 2.8, was to skip some components, such as the sensor hub. My problem is that I'm still battling that infuriating proximity sensor lag, and thinking it might be due to missing files in the firmware, I wanted to "start from scratch" with 1.40.501.32, delete the at&t crappware, and then jump to 2.8 so I can replace anything that might be missing.

However, if you tell me that 2.8.617.4 is a full complement of drivers for the M9, I can save myself the pain of reflashing everything.

Sorry, I know it's just my confusion, but your help to clarify would be appreciated.

Thanks in advance!

Thanks in advance!
[One (M9) Android Development] Sneakyghost:
"True" FULL packages are only those that have it in their name, however, the NoWipe packages can be considered full as well, since the removed bits are all non-critical.

I always remove these files in my "NoWipe":

- Boot, Ramdisk, DT, which is the set of kernel files that get delivered with custom ROM's anyway.

- Splash1 - the Splash screen that needs no changing as its always the same (rarely, HTC changes it) - I remove it for those who chose to run their own Splash1 to save them the hassle of reflashing it.

- DZDATA - the files that re-structure the internal SDCard- the only files I am not 100% sure about. Personally, I prefer to run them once when there is a base upgrade. I keep thinking we never know what HTC decides to do with the data partition. On the OneS, they once completely reformatted and changed everything around, on later devices I have seen ROM's run faulty when they didn't have their matching DZDATA re-write before. However, they are usually not required and in my FullStock Wipe packages, those ensure that the wipe is done.

- Recovery. Self explaining. I chose to replace it with the latest or best working TWRP at the time of package creation.

- Apps Preload: a new thing on the M9. The Carrier Bloat now even has its own partition. Who would want that...

That is about it. All other partitions, first and foremost all vital ones, remain in the package. So, if you "only" want to update your firmware, those are perfectly fine and safe to upgrade. The critical bits which shouldn't be left out are mainly Aboot, pg2fs. all sbl files, some others. Those always come with my packages.

So, I consider it correct to speak of my NoWipe as "Full" packages in the sense that they still emulate a RUU without System.

Makes sense?
[One (M9) Android Development] BillTheCat:
Roger that. Thanks for the clarification.
[One (M9) Android Development] PlatinumNick:
wow that clarification should be moved to the OP
[One (M9) Android Development] jbfountain:
Ok, I did this once before with a 64gb micro sdxc card, and since there seems to be some disagreement I decided to do it again. This time I used a 128gb micro sdxc card. I used HP USB Disk Storage Format Tool v2.2.3.0 and formatted the card to FAT32 using a micro sd to usb adapter. I then copied [MENTION=1102297]Sneakyghost[/MENTION]'s M9_1.32.531.33_NoWipe.zip to the newly formatted card and renamed it to 0PJAIMG.zip. I did this because my ABOOT has no red text and this zip does. I put it in my M9's micro sd slot, and I booted into bootlaoder. Then the M9 responded;

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

press VolUp to start flash

press VolDown to cancel

I pressed Volume button Up and it began flashing. I know that it worked, because afterwards I had the red text and had to flash a no red text ABOOT.

I hope this helps.

One more thing I would like to add is I had to go into recovery and go to mount then uncheck extsd and recheck it. It vibrated twice when I rechecked it. Kinda strange I thought.

I Truly Enjoy XDA-Developers with this Fabulous HTC One M9
[One (M9) Android Development] sdamark:
[MENTION=6420972]jbfountain[/MENTION]

It should be noted... Once you format any card to FAT32 your max file size becomes 4gb.

Only work around is splitting data into multiple files, on the card.

This will put a great limit on HD video recording time.

There is no file size limits on EXFAT (max file size is the card size).
[One (M9) Android Development] starbase64:
not correct, max is 16 Exabyte :P (https://en.wikipedia.org/wiki/ExFAT)
[One (M9) Android Development] xunholyx:
test
[One (M9) Android Development] jbfountain:
My post was not meant to advocate using large cards formatted to FAT32. It was merely to explain that it can be done to flash firmware on the HTC One M9 which will only read FAT32 in the bootloader.

I Truly Enjoy XDA-Developers with this Fabulous HTC One M9
[One (M9) Android Development] sdamark:
All I said is "It should be noted"

I can see people reformatting their expensive 128gb cards to an old technology, and then wondering why they can't take a 30 minute HD video anymore.

I think your findings are very useful, and I'm certainly not arguing. Only trying to help.
[One (M9) Android Development] Alan-B:
Hi,

******************

Delet
[One (M9) Android Development] BillTheCat:
Ditto - this really ought to be in the 1st post - the explanation is excellent!