Database Users

Recovery Image Errors

Hello. I'm really new to the g1, I got it just two weeks ago, and right now I have JFv1.50 ADP1.5 installed right now. I'm not familiar with many of the technical terms, but I'm starting to understand everything.
I went through the root process, trying to follow some guide using a root.apk application to download/ install the right files, but it bricked my phone. I was able to manually get it to JFv1.50 ADP1.5 later on though.
Now my problem is that I believe I still have the normal recovery image on the phone. In recovery mode there is a picture of an exclamation mark in a triangle.
So I figured I'd go try to use JF's 1.43 recovery image. I put the zip on my SD card and renamed it update.zip. When I go into recovery mode now, though, and press ALT+S, I see the installation/ update bar pop up for like 3 seconds, enough for the orange progress bar to move a few millimeters, and then it just stops. No error message or anything.
I tried installing the test keys recovery image also, but it didn't work at all.
I really need JF's recovery image though, so I can make backups etc.
I've searched for this, but the closest problem I can see is this one:
http://forum.xda-developers.com/archive/index.php/t-505950.html
But for me, I don't even get an error message when using the update.zip...
Sorry for my lack of technical knowledge here, but try to bear with me
Thanks for any help you can give me!

The cooked roms are signed with testkeys, so the original recovery mode will refuse to flash them. You'll have to get the recovery image modified by JF and flash it. The latest version is included in JF v1.43. You can find recovery.img in a folder called data in that zip.
Copy it to your sdcard or adb push it to somewhere on the phone. Then type these commands on the phone:
su
flash_image recovery /path/to/recovery.img
You must have root in order to do this. Alternatively, you can push the file to /system and the init script will flash it for you the next time you boot.

billc.cn said:
The cooked roms are signed with testkeys, so the original recovery mode will refuse to flash them. You'll have to get the recovery image modified by JF and flash it. The latest version is included in JF v1.43. You can find recovery.img in a folder called data in that zip.
Copy it to your sdcard or adb push it to somewhere on the phone. Then type these commands on the phone:
su
flash_image recovery /path/to/recovery.img
You must have root in order to do this. Alternatively, you can push the file to /system and the init script will flash it for you the next time you boot.
Click to expand...
Click to collapse
Thanks so much! I couldn't figure this out until now. It's working perfectly now.
Feel free to close this thread. Thanks again

Preparing to take the plunge and root - not clear on a couple steps.

This much is what I have clear...
·Format my SD card for FAT32
·Flash down to RC29
·Download recovery.img
·Download hard SPL
·Copy both to the root of my SD card
·Restart, go through the telnet process to gain Root
·Apply the Hard SPL
I already know what build I want - JFv1.51 ADP
However, I've been unable to find instructions on how to install it once I've gained root. I keep hearing some stuff about the radio and whatnot and I'm a little lost. :3

Blarg. Had a nice reply typed up almost ready to submit, and we had a power outage at work. Guess I get to type it up again.
After you gain root access, you need to download the radio update from here and the JF 1.51 update from here (assuming you don't have it already).
Copy the radio zip to your SD card and rename it to update.zip. Turn the phone off and boot it into recovery mode (Home + Power). Apply the radio update with Alt+S. Reboot the phone with Home + Back when prompted.
After it boots back up, move/delete/rename the radio zip and copy the JF 1.51 update to the SD card and rename that to update.zip. Reboot the phone into recovery mode again. Press Alt + W to wipe data (can't remember if this is needed or not for going from RC29 to JF 1.51), and then press Alt + S to apply the update. Reboot again when prompted, let it boot up and you should be good to go.
If you decide to go to other builds, the process will be the same.

I have a question along these lines. I did all of this and it updated fine, but I lost root. Was there a step I left out or something that I needed to do after?

So long as you followed everything in the rooting guide here on XDA to the letter, you should have root. Applying the radio and build image should not remove root access.
To verify if you do, open up the terminal emulator and type su. If it comes back with a # prompt, you have root (Superuser Whitelist may come up asking if you want to allow the action, tell it to allow the action).

And it's safe to flash the radio after the spl?

All I want to do is use nandroid backup.

Ive been reading post after post after post and im confused as all hell.
All I want to do is be able to take a image of my phone once I have everything setup and take new images about once a week in case the phone is ever replaced. I want to be able to get all my ringtone associations apps and app settings like the settings from my k-9 setup etc... phone settings EVERYTHING. I understand the mybackpro and sprite will not do this detailed of a backup. So thats what lead me here.
I have the sprint hero. I have already updated to the newest OTA firmware.
I would like step by step what i need to do. Here is what i think is the correct way from my searches. PLEASE CORRECT ME IF IM WRONG.
1. download ruu from http://forum.xda-developers.com/showthread.php?t=586258 insatll htc sync and run ruu and follow directions. That should bring the phone back to the stock image. Unless I can root from the new OTA firmware which I dont know. Someone lmk if I can.
2. Root the phone following this link http://forum.xda-developers.com/showthread.php?t=583291 or this link http://theunlockr.com/2009/11/18/how-to-root-your-sprint-hero-in-one-click/ or this link http://theunlockr.com/2009/11/07/how-to-root-your-cdma-htc-hero-sprint-verizon/ Which link is best to follow?
3. I setup my phone then turn off then home key power will get to the green menu with nandroid backup as a option. Run that and I have a image of EVERYTHING on my phone?
One last ? Can I ever update to the latest firmware or am I stuck with the stock firmware.
Thank you for your time.

It looks like you have answered your whole question. Yes, you have the process down to a science.
About which links to follow:
Folow the first link to root your phone. That's a thorough, easy to follow, minutes-to-root, fool-proof method. It also contains the download links and everything you need to do EXACTLY what you want.
So yeah,
1. RUU to stock
2. Root by following guide
3. Home/Power and select Make Nandroid Backup
4. (if you want) install rom like fresh .4 (most stable release) that includes the Sprint MR (maintenance release) and application tweaks etc.

Thank you for your response. Though I had it but wanted to make sure
Can I do the OTA update after I have rooted and made my backup? Will this cause any issues with the root or the backup?
also does fresh .4 use the htc sense ui? Ive come to really like that compared to my buddies droid UI.

Actually, if all you want to do is take a nandroid backup, there's no reason to root your phone at all.
Just install the latest flashrec here
Get the Amon-Ra recovery image for the Hero here
Install flashrec, run flashrec, BACKUP RECOVERY IMAGE, then apply the Amon-Ra recovery image.
Now, you can boot to recovery and do a nandroid backup.
If you want to apply the Sprint update, you must restore your backup recovery image (see above in bold) before the update will apply. Once you've rebooted a few times with the Sprint update, you can then apply the Amon-Ra recovery image again (no need to re-backup the recovery image). Reboot into recovery and you can make a nandroid backup.
While it's true that the first link you provided will indeed give you the recovery image to be able to do a nandroid backup, if that is all you want to do, there's really no reason to go through all the steps of rooting your phone (this may change in the future if flashrec stops working with an update from Sprint/HTC - we may even be forced to do a goldcard method at some point in the future if they do something like they did to the gsm Android phones).

jmanley69 said:
Actually, if all you want to do is take a nandroid backup, there's no reason to root your phone at all.
Just install the latest flashrec here
Get the Amon-Ra recovery image for the Hero here
Install flashrec, run flashrec, BACKUP RECOVERY IMAGE, then apply the Amon-Ra recovery image.
Now, you can boot to recovery and do a nandroid backup.
If you want to apply the Sprint update, you must restore your backup recovery image (see above in bold) before the update will apply. Once you've rebooted a few times with the Sprint update, you can then apply the Amon-Ra recovery image again (no need to re-backup the recovery image). Reboot into recovery and you can make a nandroid backup.
While it's true that the first link you provided will indeed give you the recovery image to be able to do a nandroid backup, if that is all you want to do, there's really no reason to go through all the steps of rooting your phone (this may change in the future if flashrec stops working with an update from Sprint/HTC - we may even be forced to do a goldcard method at some point in the future if they do something like they did to the gsm Android phones).
Click to expand...
Click to collapse
So, how do I install flashrec and "apply" the Amon-Ra recovery image? Sorry, but I just got my first Android phone this morning. LOL! And I want to explore all possibilities of what my new toy can do. But I'm not quite sure how to do either of those things.

You Can Root the New O.T.A. Update manually only.
I have a Sprint Hero and to get the OTA Update I had to get the Original RUU file and install it. Then I did the OTA update but the key thing is Amon Ra image and flashrec WILL NOT WORK.
What Does work is:
1. From the home Screen Go to Settings>Applications>Development Check your USB Debugging Mode and Stay awake boxes
(This is just getting set up to use the Android SDK. Im sorry for all the experience folks Im just going step by step for thoroughness)
2) From the Desktop Computer Get to your command prompt and Follow the steps Below:
3. Open the Command Prompt and type the following (hitting enter at the end of every line):
cd\
cd AndroidSDK\Tools\
adb devices
And make sure your phones’s serial number pops up (if not redo section I).
4. Then type:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
5. Then type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
Thats It..After you get the message "ENJOY THE SHELL and get the # sign, IF YOU ENTER EVERYTHING CORRECTLY EXACTLY WHAT YOU TYPED WELL SHOWS UP BELOW WHERE YOU TYPED IT!!)
ROOT USER Programs seem to work but the (PowerButton/ Home Button pressing combination still hangs at "HTC") which is where somehow the Green menu screen is supposed to be. And the NANDROID Backup is supposed to be. If anyone knows how to get this to work or to prevent the Hero from hanging please let us know.

[Q] Getting latest CWM onto Droid X - help!!

This phone is about to cause me to start mainlining some serious drugs. I just do not understand what I'm doing wrong.
I have read and read and read and downloaded and downloaded and downloaded. At one point I think I had about 10 Firefox tabs open, madly switching between them trying to figure this beast out. So, I have tried to do the necessary homework before posting here.
I received a Verizon Droid X (MB810 model) and was wanting to install a 2nd-init ROM. It came with .621, which I know has been problematic in the past, but seems not to be a terribly big obstacle anymore. Here are the steps I've taken:
o I rooted the phone via the Slitaz ISO.
o Via adb, I pushed the Droid 2 (D2) reboot recovery and ROM manager (RM) APKs.
o I choose boostrap recovery in the D2 application. Superuser grants the appropriate permission.
o Within RM, I download and flash the latest CWM (5.0.2.0) based on the 2nd-init Droid X option.
o RM says that the flash is successful and Superuser rights are granted.
o From within RM, I choose the reboot into recovery option.
o The phone reboots...right back into the operating system, completely bypassing CWM. Redoing the above steps and holding down the home key just boots into the stock recovery.
Now, I can reboot into CWM from the D2 application, but I'm then confronted with the old version of CWM. I've also read where this method will screw-up the boot process to the point that installing 2nd-init ROMs won't work. I've (somewhat) verified this by trying to install the latest AOKP with the D2 version of CWM, which just endlessly loops the unicorn animation. In fact, in a thread detailing this problem on another forum, it was advised to stay far, far away from the D2 application altogether and just use RM.
I've also had to SBF back to .621 on several occasions using RSDLite 4.9.
This has been nightmarish. I spent almost the entire weekend trying to get this phone to boot into the latest CWM. Do I have to SBF the Milestone ROM in order for this to work? Is that even necessary anymore?
Any help would be GREATLY appreciated, as I'm out of ideas at this point. Thanks a bunch.
- Fred

did you wipe data before/after flashing SBF?
if not, that could cause issues

sd_shadow said:
did you wipe data before/after flashing SBF?
if not, that could cause issues
Click to expand...
Click to collapse
Yes, I forgot to mention I did that in my OP.
I just don't understand what's going on. It's almost as if RM is lying to me about having successfully flashed the newest CWM. I say this because, when I immediately do the flash procedure after booting the phone, nothing shows up in /preinstall/recovery/ using Root Explorer (RE). It's only after I do the D2 bootstrap recovery option that /preinstall/recovery/ is populated with the CWM files. The problem is that these files represent the 2.0.5.8 version, not the 5.0.2.0 update.
To even deepen the mystery, after I did the above, I then went back into RM and reflashed to the latest CWM. I then looked at /preinstall/recovery/ again and all of the original 2.0.5.8 files were still there. There was no evidence that I could determine that RM installed anything anywhere.
I'm at a total loss.

did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?

sd_shadow said:
did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?
Click to expand...
Click to collapse
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?

i don't think you will get an error
have you tried redownloading D2 bootstrap and rom manager, from market?
have you read this? http://rootzwiki.com/topic/31737-root-droid-x-root-method-for-234-45621-does-not-require-milestone-sbf/page__st__20#entry878745

Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.

the link was to a post that
someone was having trouble updating cwm to 5.0, and some possible fixes
as for the Slitaz ISO, is just a linux program used to run the magic md5 root method

fleggett said:
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?
Click to expand...
Click to collapse
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123

test test test

blindmanpb said:
Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.
Click to expand...
Click to collapse
Slitaz ISO, is just a linux program used to run the magic md5 root method
no it does not install a rom
you only need to update cwm if you want to restore a nandroid backup of a 2nd init rom,
most 2nd init roms come with their own bootstrap, found in the reboot options
you shouldn't install bootstrap or update cwm unless the rom does not install bootstrap

Sorry for the previous "test test test". The forum wasn't letting me post anything until I realized I'm under the ten post threshold and I was trying to quote text that had links.
Thanks, sd_shadow, for the extremely helpful pointers. Unfortunately, I no longer have the phone in my possession, but I might be getting another one to play with soon. I'll let you know if I run into the same problems after applying your potential fixes. Thanks again!

I'm ecstatic to report that the this alternative method by Tomsgt123 worked! Here is what I wound-up doing, from start to 5.0.2.0 finish.
First the facts, all taken from settings -> About phone
System version: 4.5.621.MB810.Verizon.en.US
Model number: DROIDX
Android version: 2.3.4
Baseband version: BP_C_01.09.15P
Kernel version: 2.6.32.9-g1282440 ([email protected] #1)
Build number: 4.5.1_57_DX8-51
ERI version: 5
PRL version: 58012
Bootloader: 30.04
1. Obtain SliTaz GNU/Linux (3.0) root ISO in preparation to root phone. File I used is named Droid2_D2G_DX_DX2-RootCD-2012.iso.
2. Burn SliTaz ISO to bootable media.
3. Enter Windows and boot phone normally.
4. Ensure USB debugging is enabled via the settings -> Application settings -> Development -> USB debugging checkbox.
5. Connect phone to computer via USB cable.
6. Drag from top of phone and select the USB connection -> Charge Only radio button.
7. Boot computer via SliTaz.
8. Choose option 3 (Root Droid X) and follow onscreen directions to the letter, including putting phone in bootloader mode.
9. Boot phone normally and invoke Superuser. Immediately exit Superuser. (This step probably isn't necessary.)
10. Install Droid 2 Bootstrapper (D2B), ROM Manager (RM), and Root Explorer (RE) on phone (I used adb).
11. Invoke D2B and choose Bootstrap Recovery. When done, exit D2B.
12. Make sure phone is connected to internet.
13. Invoke RM and choose Flash ClockworkMod Recovery. Current Recovery should be 5.0.2.0.
14. Choose 3rd option, Motorola Droid X (2nd-init).
15. Tap Flash ClockworkMod Recovery. Wait until recovery files are downloaded and flashed, then exit RM.
16. Invoke RE and navigate to /preinstall/recovery.
17. Rename recovery.zip to recovery.zip.bak.
18. Still within RE, navigate to /sdcard/clockworkmod/download/download2.clockworkmod.com/recoveries.
19. Press and hold on recovery-clockwork-5.0.2.0-shadow.zip and copy the file.
20. Navigate back to /preinstall/recovery and paste the above file.
21. Rename the above pasted file to recovery.zip.
22. Exit out of RE and return to RM. Tap Reboot into Recovery and hit OK at the "Are you sure...?" prompt.
23. Phone should reboot into the 5.0.2.0 version of CWM.
Thanks again, sd_shadow. Without the above "manual" method, I would never have gotten the 5.0.2.0 version of CWM onto this phone. Now, time to play!
- Fred

And guess what? All those previous steps I carefully and deliberately outlined have been rendered obsolete by one, small apk:
http://rootzwiki.com/topic/25017-ro...workmod-flashable-updates-by-ky/page__st__190
(Still can't post links...yet.)
This is the Droid X Bootstrapper 621 MOD (DXB621). Functionally, it is the same as the old D2B except for two huge and critical features:
1. It contains CWM 5.0.2.0 out-of-the-box.
2. It works without having to do the aforementioned file manipulation inside RE.
Because of the above, it negates the need for RM (and D2B) entirely. I immediately installed DXB621 on my freshly SBF'd and rooted Droid X (see previous stats) and it worked flawlessly.
After all this, I'm convinced there is something wrong with RM as it relates to the Droid X with .621 already installed, whether via the OTA update or via SBF.
As a big bonus, after some finagling, I was also able to install HijackedBootMenu 1.1.5 621 1.1, which is a real gift, since it allows booting into CWM (or RZR) without having to first boot the phone to use either D2B, RM, or DXB621 itself.
So, the moral of this long and windy story is to simply use DXB621 for your recovery needs, don't mess with D2B and RM, and don't look back.
- Fred

nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.

sd_shadow said:
nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.
Click to expand...
Click to collapse
Yeah, getting any bootstrap to work on a Droid is the first step (after rooting) in doing much of anything, and using the most recent CWM seems to be required for all the latest and greatest ROMs, so it really should be somewhere on page 1 of that monster thread. I only stumbled across it via dumb luck.
I've run into a bizarre issue, though. With the phone connected to a running computer via USB, it won't boot into either CWM or RZR from Hijacked BootMenu (HB). Once you hit either recovery option, it just goes to a (slightly lit) black screen and stays there. The power button doesn't work at that point, so it requires a battery pull.
A clue as to what's going on might be that Windows recognizes the device when HB runs. It's only when I disconnect the cable before booting the phone that either recoveries invoke normally. Very strange.
I currently have CMKang.b3 loaded on the phone. I was pleasantly surprised to see that both the Camera and Torch apps work just fine, as I thought both were inoperable under CM9. This specific build is 9-20130120-UNOFFICIAL-shadow.
- Fred

sd_shadow said:
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123
Click to expand...
Click to collapse
THANK YOU! I was having a similar problem as the OP, and this FINALLY fixed it!

also take a look at the modified d2 bootstrap that has been upgraded to cwm 5.0
will save a few steps if you have to reinstall
edit: I have rewritten my instructions here
[HOW TO] Install/Use Droid 2 Bootstrap

The modified Bootstrap is the trick. Straight to CWM 5.0. Took me a long time to figure out that ROM manager appears to update CWM but does not work. I found ROM manager to be of no use or value at all to me and don't install it or delete it.

Got 11 Open
Looking for an answer myself. Currently trying to install using Rom Manager then using button presses to get into Recovery. Will post update shortly.

[ GUIDE ] [ Marshmallow Firmware Upgrade ROM install including ViperOneM9 4.x.x ]

Dummy friendly guide how to upgrade, flash and install the latest Marshmallow Firmware and the latest ROM’s such as the ViperOne ROM 4.x.x, this guide is intended for those who are already slightly familiar with the flashing process and have previously managed to flash a ROM on their HTC One M9 device…
CHECKLIST BEFORE STARTING:
1) Phone is S-OFF
2) Unlocked Bootloader
3) Rooted
4) Latest TWRP recovery
5) SUPER CID changed to 11111111
6) External SD Card
7) NANDROID Backup and any or every other form of backup
8) Device drivers, Android SDK Platform Tools including ADB & FASTBOOT.
9) USB Debugging enabled.
10) BACK UP OF ALL YOUR DATA !!!
Before we begin make sure you back up all your data on both the internal and external SD card.
For the purpose of this tutorial we will be installing the latest ViperOneM9 ROM…
a) Downloaded and place the latest ViperOne ROM - ViperOneM9_4.x.x.zip on your External SD card,
Main Thread by j to the 4n is found here:
http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Latest ViperOne ROM for download is here:
http://venomroms.com/htc-one-m9/
b) If you are currently on ViperOneM9 3.5.0 or older and wish to upgrade to the latest 4.x.x than the latest Marshmallow firmware is required (3.35.401.12 or 3.35.617.12 firmware)… This can be found here and within Sneakyghost original thread.
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Now download the latest version of either:
NO WIPE ZIP
or
FULL STOCK WIPE ZIP
For this tutorial we will use the FULL STOCK WIPE ZIP (to archive a clean install – this will wipe everything on your phone excluding the External SD card)
c) Place the downloaded M9_3.35.401.12_FullStock_wipe.zip into your Android SDK Platform Tools Folder (for example C:\Android\ if this is where all your tools are found)
d) Download the latest version of TWRP recovery from
http://www.teamw.in/devices/htconem9.html
Place the downloaded twrp-2.8.7.0-hima.img in your Android SDK Platform Tools Folder
e) Once you are 101% ready to begin the process start by connecting your device and launching the command window (hold shift, right click in window with all the required ADB/FASTBOOT aps and select "open command window here) once the black terminal window appears start by typing in
adb devices
if your phone appears in the list we can continue by typing:
adb reboot download
wait a few seconds for the screen to appear and type:
fastboot oem rebootRUU
your phone should now be in the RUU mode with a silver HTC logo, now type
(if you renamed the original file type its current name, by default it is as follows)
fastboot flash zip M9_3.35.401.12_FullStock_wipe.zip
f) you will most likely receive something like this towards the end after running the above command...
FAIL90 hboot pre-update! please flush image again immediate
FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)
For "hboot-preupdate" response, restart the same procedure for device...
just type the above command again and phone will flash the update again and hopefully it will take at least a minute or more to complete, hopefully there will be no more errors, just in case repeat the above command... Just in case you do see errors try looking them on Sneakyghost's thread found here
g) Once this is done and everything passed than we have successfully upgraded our firmware to Marshmallow... Since we selected the FULL STOCK WIPE option we need to flash TWRP once again (as it was wiped) and don't bother resetting or hoping for the phone to boot normally as it won’t...
(if you renamed the original file type its current name, by default it is as follows)
Type:
fastboot flash recovery twrp-2.8.7.0-hima.img
and once it’s done
adb reboot-bootloader
*if for any reason you need to reset your phone and gain access to the bootloader menu, download mode, recovery etc. you can always do this manually by holding vol up, vol down and power buttons at the same time for a few seconds to reset the device, to get into the bootloader, recovery, download mode etc. After the phone resets continue holding the vol down and power button until you reach the bootloader menu.
*if you type adb devices and you see multiple devices or emulators that prevent the commands from working I suggest running the following:
adb kill-server
adb devices
Now only your connected device should appear…
h) It is now time to enter our recently flashed recovery to finally install our latest ROM.
Enter the recovery manually or by typing
adb reboot recovery
From there you may select the wipe option (swipe to factory Reset) and proceed to the Install section, browse for your ROM file and select it.
i) Within Aroma installer select all your preferred options and begin to install, once the flashing completes your device should reboot and now you keep your fingers crossed and wait (will take several minutes so just be patient…. And DONE!!! You now have the latest Marshmallow firmware and ViperOneM9 ROM installed.
#Please note that I’m no expert when it comes to these matters, this guide is here to help anyone who is unsure what to do, I tried to write it up the best way possible (sorry that there are no fancy pictures) if there any errors or issues with my methods please feel free to correct them but so far they worked for me and hopefully will also work for you. (This guide will also help you flash other ROM's) If you need more help please feel free to ask, there is always someone here on xda who knows the answers 

Excellent write up !!
Many thanks !!!....g

glad i could help

GODSPD said:
glad i could help
Click to expand...
Click to collapse
Very nice writeup. Just got an M9 for the wife. I've been around the block so I get everything, but I've been away from HTC since the One X...well, there's the N9 but it's a nexus. What are the RUU mode and Download mode. If I remember correctly there was only the bootloader to go to on the One X. If it's complicated is there somewhere I can read about the modes?

Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk

Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.

CrazyRom said:
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
Click to expand...
Click to collapse
PM sent, hope it helps.

zrzhu said:
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...

GODSPD said:
PM sent, hope it helps.
Click to expand...
Click to collapse
Also try the following as error 22 was not covered in the error handling section...
http://forum.xda-developers.com/showpost.php?p=59783531&postcount=3
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.
SneakyGhosts post explains this:
Error 22 is new to me too but the string is kind of self explanatory: every archive has a header where the archive-program finds info about what type of archive and what compression. If the error says anything about this header, the logical conclusion is either a corrupted, broken archive or an unsupported archive type.
I suspect the latter simply due to the fact that the zip was unpacked and repacked, which then easily creates an incompatible zip.

GODSPD said:
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
Click to expand...
Click to collapse
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk

zrzhu said:
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.

GODSPD said:
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
Click to expand...
Click to collapse
Thanks. Hopefully ATT will release Marshmallow soon then.

Hi guys i dont have anymore pc. Can i flash new firmware without pc? Plz help

Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder

BLEK0TA said:
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
Click to expand...
Click to collapse
which exact files are you after, the android sdk?

thanks bro!! nice collection!

zrzhu said:
Thanks. Hopefully ATT will release Marshmallow soon then.
Click to expand...
Click to collapse
I'm still kind of "fuzzy" on this whole firmware thing.... IF I don't want to wait (on ATT) and IF I go S-OFF, which firmware can I/should I use for Marshmallow?

Delete

HI, can you please tel me how long does the firmware flash take as mine has been at it for over 2 hours? Not sure if it is stuck?

I am on sprint. How do i get the new firmware? It isnt on the list. Thank you