Database Info

[GUIDE] Complete Tutorial for the Beginners and Others

HTC Desire S Tutorials/Guides
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reviews:
1. GSMArena: http://www.gsmarena.com/htc_desire_s-review-590.php
2. Engadget: http://www.engadget.com/2011/04/10/htc-desire-s-review/
3. Slashgear: http://www.slashgear.com/htc-desire-s-review-28142921/
4. Techradar: http://www.techradar.com/reviews/phones/mo...s-930920/review
5. Phonearena: http://www.phonearena.com/reviews/HTC-Desire-S-Review_id2702
Specifications: (From http://www.gsmarena.com/htc_desire_s-3776.php)
Code:
[B]General:[/B] 2G Network GSM 850 / 900 / 1800 / 1900
[B]3G Network: [/B]HSDPA 900 / 2100
[B]Announced:[/B] 2011, February
[B]Status: [/B] Available. Released 2011, March
[B]Size Dimensions:[/B] 115 x 59.8 x 11.6 mm
[B]Weight:[/B] 130 g
[B]Display Type:[/B] S-LCD capacitive touchscreen, 16M colors
[B]Size:[/B] 480 x 800 pixels, 3.7 inches
- Gorilla Glass display
- Multi-touch input method
- Accelerometer sensor for UI auto-rotate
- Proximity sensor for auto turn-off
- HTC Sense UI
- Touch-sensitive controls
[B]Sound Alert types:[/B] Vibration, MP3, WAV ringtones
[B]Loudspeaker:[/B] Yes
[B]3.5mm jack:[/B] Yes, check quality
[B]Memory Phonebook: [/B]Practically unlimited entries and fields, Photocall
[B]Call records:[/B] Practically unlimited
[B]Internal:[/B] 1.1 GB ROM, 768 MB RAM
[B]Card slot:[/B] microSD, up to 32GB, buy memory
[B]Data GPRS:[/B] Up to 114 kbps[B]
EDGE:[/B] Up to 560 kbps[B]
3G:[/B] HSDPA, 14.4 Mbps; HSUPA, 5.76 Mbps[B]
WLAN:[/B] Wi-Fi 802.11 b/g/n, DLNA, Wi-Fi hotspot
[B]Bluetooth:[/B] Yes, v2.1 with A2DP, EDR
[B]Infrared port:[/B] No[B]
USB:[/B] Yes, microUSB v2.0
[B]Camera:[/B] Primary 5 MP, 2592 x 1944 pixels, autofocus, LED flash, check quality
[B]Features:[/B] Geo-tagging, touch-focus, image stabilization
[B]Video:[/B] Yes, [email protected], check quality
[B]Secondary:[/B] Yes, VGA
[B]Features:[/B]
[B]OS:[/B] Android OS, v2.3 (Gingerbread)
[B]CPU: [/B] 1 GHz Scorpion processor, Adreno 205 GPU, Qualcomm MSM8255 Snapdragon
[B]Messaging: [/B] SMS(threaded view), MMS, Email, Push Email, IM
[B]Browser:[/B] HTML
[B]Radio:[/B] Stereo FM radio with RDS
[B]Games:[/B] Yes
[B]Colors:[/B] Black, Red
[B]GPS: [/B] Yes, with A-GPS support
[B]Java:[/B] Yes, via Java MIDP emulator
- SNS integration
- Digital compass
- Dedicated search key
- Google Search, Maps, Gmail
- YouTube, Google Talk, Picasa integration
- MP3/AAC+/WAV/WMA player
- DivX/XviD/MP4/H.263/H.264/WMV player
- Organizer
- Document viewer
- Voice memo/dial/commands
- Predictive text input
[B]Battery:[/B] Standard battery, Li-Ion 1450 mAh
[B]Stand-by:[/B] Up to 430 h (2G) / Up to 455 h (3G)
[B]Talk time: [/B] Up to 9 h 50 min (2G) / Up to 7 h 10 min (3G)
HTC Desire S Guide for Newcomers to Android:
This guide will guide you throughout your Desire S phone. What's the best app to use it on your phone, some tweaks and more!
http://forum.xda-developers.com/showthread.php?t=1097538
Android Versions/History:
The version history of the Android operating system began with the release of version 1.0 in September 2008. Android is a mobile operating system developed by Google and the Open Handset Alliance. Android has seen a number of updates since its original release. These updates to the base operating system typically fix bugs and add new features. Generally, each version is developed under a code name based on a dessert item. The code names are in alphabetical order (Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, and the future version, Ice Cream Sandwich).
Source/More info: http://en.wikipedia.org/wiki/Android_version_history
Roms/radios/fixes/mods/recoveries and everything related to development:
Please refer to this thread: http://forum.xda-developers.com/showthread.php?t=1146601
The Basics of Unix/Linux command / ADB Shell:
Both guides below explains and teaches the basics of using ADB shell commands which is very useful for those who wants to learn more.
Link1: http://forum.xda-developers.com/showthread.php?t=1160222
Link2: http://forum.xda-developers.com/showthread.php?t=517874
How To: Backup or Restore via Nandroid
Nandroid allows you to create a complete system image of your device and stores it to the SD Card on your phone. Making one is very simple but there are a few prerequisites.
1. A rooted Android phone
2. A custom recovery that supports Nandroid (ie: Amon_RA, ClockworkMod, Etc.)
3. A MicroSD card that has enough space for a system image.
A complete image can range from 75-400 MB.
Please follow this link for instructions: http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid
How To: Check if your phone is S-OFF or S-ON and your HBOOT version
1. Disable Fast Boot. (Setting > Power > uncheck Fast Boot)
2. Turn off your phone.
3. Turn on your phone by pressing the power button and volume down button together.
4. You will see a white screen with "S-OFF" or "S-ON" and your hboot version on top of the screen.
NOTE: If your phone is S-ON, you won't be able to root or flash custom ROMs to your phone. To make it S-OFF, follow the guide below.
How To: S-Off your device with Revolutionary: S-OFF & Recovery Tool (For HBOOT 0.98.0000, 0.98.0002)
Unrevoked and Alpharev present: Revolutionary Tool
Please also read the documentation page for this tool: http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Does Revolutionary give me root? No. You will need to flash this zipfile from recovery. (It's better to just skip this.)
S-OFF your phone using Ubuntu:
1. Download Ubuntu 11.04 from the Ubuntu site.
2. Burn image onto DVD/CD or create a USB Stick (I suggest creating USB stick since it loads faster, for me). (Follow instructions provided at the website to create a bootable CD or a USB Stick).
3. Reboot computer. Allow Bootup popup menu (usually F8?).
4. Select DVD/CD-drive or USB Stick to boot Ubuntu.
5. Wait a bit for things to load. Choose "Try Ubuntu".
6. Now, Ubuntu should load up successfully. (see screenshot)
7. Connect phone to your computer and make sure that Debugging Mode is enabled on your phone. Download the tool from http://revolutionary.io/ for Linux (Firefox included with Ubuntu). Keep that browser window open.
8. Extract the downloaded file and put it into the root directory (in Ubuntu, that's Ubuntu/Ubuntu, if I recall correctly).
9. Search for the Terminal (Windows key pops up the search, I think; otherwise, it's the icon on the top left corner of your screen), run Terminal.
10. Type in "sudo ./revolutionary" at Terminal.
11. It'll provide a key. Go back to the browser window where you downloaded Revolutionary tool - there's a form to fill out. Type in the key. It'll generate a second key. Type that key into the Terminal.
12. Make sure it says that everything is successful. It'll ask if you want to flash Clockwork. Type in "Y".
13. Once it shows success, reboot phone.
S-OFF your phone using Windows:
1. Download Revolutionary tool for Windows from http://revolutionary.io/ (Keep the browser open)
2. Extract the zip file to a new folder.
3. Connect phone to your computer and make sure that Debugging Mode is enabled on your phone.
4. Open the new folder and right click on "revolutionary.exe" and select run as administrator.
5. Follow steps from Step 11 above.
WARNING: S-OFF your device will void your phone's warranty. You will need to turn it back to S-ON for warranty. (I don't have a guide to make it back to S-ON right now, so do it as you wish).
How to: S-OFF (Video)
How to: Restore stock ROM and S-On after S-Off
You phone needs warranty? You might need your device back to S-ON mode. Try following this guide to make it S-ON, http://forum.xda-developers.com/showthread.php?t=1187231. I'm not sure if this works 100% all the time because I personally haven't tried this one yet. If this guide works for you, congratulations, if not, try asking around this forum.
How to: Root your device
1. You can achieve root by using Gingerbreak. Follow this link and guide: http://forum.xda-developers.com/showthread.php?t=1044765
2. Or, by using SuperOneClick *recommended* (ROOT ALMOST ALL ANDROID DEVICES): http://forum.xda-developers.com/showthread.php?t=803682
3. Or, you can flash this zipfile from recovery (Source: http://unrevoked.com/rootwiki/doku.php/public/revolutionary).
(You can skip this if you're about to flash a custom ROM since custom ROM are pre-rooted. Unless you want to keep your original ROM, use this to root your device.)
Custom ROMS:
Custom roms can be found in this thread: http://forum.xda-developers.com/showthread.php?t=1146601 or head to the development section.
(Most of these ROMs are pre-rooted, which means that you don't need to root your phone after flashing one of the custom ROM.)
How To: Flash Custom ROMs using Recovery (Method 1)
(You can use your default recovery from Revolutionary tool but I recommend using http://forum.xda-developers.com/showthread.php?t=1377745)
1. Copy your custom ROM "zip" file to your SD card (Root directory).
2. Turn off your phone.
3. Turn on your phone by holding the power button and the volume down button together.
4. Once you see the white screen, choose "Recovery"
5. Make a full wipe/format and clear all cache.
6. Choose "install from sdcard/zip file" and then choose your Custom ROM zip file from your SD card to flash your Custom ROM.
Optional: If you want to use 4EXTRecovery, just flash it like you are flashing your custom ROM(Step 6). Just do it before you flash your new ROM.
How To: Flash Custom ROMs using ROM Manager (Method 2)
(This method might be easier for flashing ROM updates or add-ons)
1. Go to ROM Manager (You can install this software from the Android Market.)
2. If you want to use 4EXTRecovery, please follow steps below, and if you're not using 4EXTRecovery, please skip to step 6)
3. Press your phone's option's button and choose Manual Flash Override.
4. Press OK and choose your phone model.
5. Choose ClockworkMod 3.x (After these steps, your ROM Manager won't ask you to flash new recovery again when flashing new a ROM)
6. Reboot into Recovery and make a full wipe/format and clear all cache then reboot.
7. Now, from your ROM Manager, choose Install ROM from SD Card.
Note: Flashing ROMs can be vary, some custom ROMs may require you to flash some of their own file first. Eg, The LBC Mod ROM requires you to flash "WIPE zip file" before flashing the ROM. Read their instructions carefully to know more.
NOTE: I am not responsible for any faulty or bricked devices after S-OFF or flashing new ROMs. Do it at your own risk.
How To: Flash a ROM in a "Perfect" Way (Method 3 - Recommended)
A great guide from vampire36 for people who encounter the following problems:
1. The ROM you flashed gets stuck on HTC screen (bootloop) while the same ROM works right for others
2. You get the same kernel and radio yet you find your cell to have more battery drain than others
3. Finally some strange force closes and restarts but works perfect for others
So this is basically one of the most perfect way to flash a custom ROM and is a way to help people who face such issues.
Please head to : http://forum.xda-developers.com/showthread.php?t=1257731 to see full instructions and discussions.
How To: Flash Custom ROM (Video)
How to: Flash Radios
1. Download your Radio zip package.
2. Copy your Radio zip package to your SDcard root directory and rename it to PG88IMG.zip.
3. Turn off your phone and turn it back on by pressing volume down and power button together (You need to turn off fastboot under phone settings > power options).
4. Once you're in hboot, the bootloader will ask you if you want to install radio.img, just press yes. (Volume up means "YES", and volume down means "NO")
5. Once the radio flashing is complete press your power button once to reboot device. Done!
Note: You must delete your Radio zip package or rename it to something else when booting your phone after flashing new radio image since the bootloader will always try to flash if a PG88IMG.zip file is on your SDcard.
- Method 2 check here: http://forum.xda-developers.com/showthread.php?t=1178001
How to: Root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
For device with S-ON and a new HBOOT version 2.00.0002. Some ROMs may require you to flash "boot.img" if you're using this method (not needed if you S-OFF your device using "revolutionary" and has older HBOOT), check the ROM thread for info and guidelines.
Please follow this guide: http://forum.xda-developers.com/showthread.php?t=1525100 (Thanks to: n0elite)
How to: Upgrade to new HBOOT version 2.00.2002 / Downgrade to old HBOOT
This is my own guide, I did this on my own phone and it works. This guide is according to those guides made by others(link below), I just made it even more simplified.
1. Download 2.00.2002 hboot.img from http://forum.xda-developers.com/attachment.php?attachmentid=1288640&d=1346184448 (Thanks to Thantos)
2. Copy the downloaded hboot.img to the root of your SD-Card.
3. Reboot into recovery mode.
4. Do a backup of your ROM using nandroid backup in recovery. (Optional, just in case something goes wrong, but I did not do this.)
5. When your phone is in recovery mode state, open up your command prompt (type cmd in run) in windows and type the following commands.
- adb devices
- adb shell
- su
6. You should now see the sign "#" at your command prompt. Now, backup your hboot by typing, "dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img" without quotes.
7. Now, flash your new hboot by entering this "dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18" without the quotes.
8. Your phone should now have the latest hboot. If you reboot to your boot loader, you should see something like this.
*** LOCKED ***
SAGA PVT ENG S-OFF RL
HBOOT-2.00.2002 (PG8810000)
9. Reboot your phone into recovery mode again and "Wipe cache and delvik cache" then restart your phone if you already have a ROM installed or you could flash a new ROM but make sure you make a full format instead.
Others:
Use this guide at your own risks. I have not tested this method yet. Link here:http://forum.xda-developers.com/showthread.php?t=1236890
Simplified version here (Better version): http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
How to: Downgrade to old HBOOT from HBOOT version 2.00.2002 :
Follow this guide: http://forum.xda-developers.com/showthread.php?t=1318919. Thanks to Skanob.
Another one here: http://forum.xda-developers.com/showthread.php?t=1399331. Thanks to mtothearkus
And here if above method doesn't work for you (for recent 2.15.x versions): http://forum.xda-developers.com/showthread.php?t=1443636. Thanks to shadi22.
Note: Check all guides and decide which suits you best.
[Archived] How to: DOWNGRADE Desire S with S-ON (Reason being archived: Guide not needed since revolutionary is able to S-Off HBOOT version 0.98.0002. Unless you really want to, follow guide below.)
To downgrade from HBOOT version from 0.98.0002 to version 0.98.0000: http://forum.xda-developers.com/showthread.php?t=1078497 (Credits to: newrad67)
Warning! I don't recommend this to users who are new to Android since there is a possibility of bricking your device. I will not be responsible if this happens.
NOTE: You may also check sonikz procedure (http://forum.xda-developers.com/showpost.php?p=13780422&postcount=4). I think his procedure is faster. You may use which one is easier for you to follow.
How to: Create/Modify/Porting ROMs
You can try using dsixda's HTC Android Kitchen tool. This tool is only for:
1. Those who are brand new to creating custom ROMs and want an easy place to start learning.
2. Those who just want to modify shipped ROMs or someone else's custom ROMs to their liking.
3. Those who are confused by all those scripts and complex commands required for building and extracting.
Please head to: http://forum.xda-developers.com/showthread.php?p=5626292 for more details and download for this tool.
Note from the developer: This is NOT a tool to automatically turn you into a full-fledged ROM developer. ROM development normally involves work from the ground up and involves time, research and patience. I am just giving the tools to help the average person get things done quickly from an existing base.
- For porting sense to other sense devices tutorial: http://forum.xda-developers.com/showthread.php?t=1222746
- Here's a new guide from proxuser on how to port ROMs to desire S: http://forum.xda-developers.com/showthread.php?t=1563857
Extras:
How to: Fix Broken Screen: Follow this link to replace Desire S screen: http://www.techradar.com/news/phone.../how-to-fix-a-broken-touchscreen-1114324#null
How To: Install Sony's New PlayStation Mobile For Android On Any Rooted Device: http://forum.xda-developers.com/showthread.php?t=1919574
PSP Emulator For Android V 0.4: http://forum.xda-developers.com/showthread.php?t=1970933
How To: Make your Android lag-free: (Seeder 1.1 entropy generator to provide significant lag reduction) http://forum.xda-developers.com/showthread.php?t=1987032
How to: Run Ubuntu within Android on Desire S: http://forum.xda-developers.com/showthread.php?t=1256949 (credits to zacthespack)
Android Partitions Explained: http://www.addictivetips.com/mobile/android-partitions-explained-boot-system-recovery-data-cache-misc/
All About SD-Cards: http://forum.xda-developers.com/showthread.php?t=1947560
FAQs:
1. What's S-OFF and S-ON?
- In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. (Source: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/)
(NOTE: S-OFF is not ROOT, S-OFF your device does not mean that your device is Rooted. They are totally two different things.)
2. How can I backup all my apps and apps' data files before flashing a new ROM and wiping all my datas?
- You will need to root your device first using Gingerbreak(see above). And then, install Titanium Backup and use that to backup all your apps and your apps' data files.
3. I have WiFi death grip/Wifi signal drops when I hold my phone in certain ways.
- There are no 100% right fixes yet for this issue but give it a look here: http://forum.xda-developers.com/showthread.php?t=1175646
4. Is it possible to install 4EXTRecovery/Flashing ROMs/ROOT on Desire S with S-ON?
- No, it is not possible. You must/need "S-OFF" to customize your device.
5. I've just received this system update OTA - 1.47.61.1 or later. If I install it, will I loose my S-OFF and root?
- Yes, you will lose both S-OFF and root once you update because it will update the hboot to 0.98.0002. However, you can try following this guide http://forum.xda-developers.com/showpost.php?p=16110608&postcount=5 to update the OTA but not the hboot. Check this one out also http://forum.xda-developers.com/showthread.php?t=1190992 and http://forum.xda-developers.com/showthread.php?t=1194488 to S-OFF and root if you have updated the OTA.
6. How will I brick my device? and how to prevent it?
- Follow this thread to find out : http://forum.xda-developers.com/showthread.php?t=1226849
7. What is a "Stock ROM" ?
- Stock ROM is basically one that comes straight from HTC with no amendments and probably the one that your phone came with out of the box! -ben_pyett
Click to expand...
Click to collapse
Useful Information for newcomers to Android:
Android Terms, Slang & Definitions: http://forum.xda-developers.com/showthread.php?t=1466228
CPU Governors explained: http://forum.xda-developers.com/showthread.php?t=1663809
[REF]Terminology for the newbies: http://forum.xda-developers.com/showthread.php?t=1394458
[GUIDE]Easy and simple adb and fastboot setup for newbies(Windows Only): http://forum.xda-developers.com/showthread.php?t=1272595
Click to expand...
Click to collapse
Final Notes:
Any Problems or Questions? Please ask around the forum or read the FAQ first, it usually helps. Thanks to those people who has contributed to this thread. Enjoy your phone!
Click the "Thanks" button if you find this thread useful!
WARNING: Please follow those steps carefully, it usually works if you do it properly. However, I am not responsible for any faulty or bricked devices. Do it at your own risk.

include hboot downgrade guide also.
Include the guide to downgrade hboot from version 0.98.0002 to 0.98.0000
http://forum.xda-developers.com/showthread.php?t=1078497

this is very useful but try not to replicate what is in the INDEX sticky thread.
I suggest that you request that this thread is listed in that thread so that its easy to find
Nice
Sent from my HTC Desire S using XDA Premium App

i think this should be made a sticky in the general section
most new comers don't check the development section

kartkk said:
i think this should be made a sticky in the general section
most new comers don't check the development section
Click to expand...
Click to collapse
I agree, general would be a better place for this thread.
In which case PM the moderator, smokestack76
Sent from my HTC Desire S using XDA Premium App

ben_pyett said:
I agree, general would be a better place for this thread.
In which case PM the moderator, smokestack76
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
i made a request

Thanks guys, I will get more stuffs to add here soon... thanks for the downgrading hboot guide suggestion, I will look into that and add it in later...I hope this thread could help out those who are still new, who need more info...
once again, thanks a lot... if you have anymore suggestions or any corrections that I need to make, please tell me.

nodeffect said:
Thanks guys, I will get more stuffs to add here soon... thanks for the downgrading hboot guide suggestion, I will look into that and add it in later...I hope this thread could help out those who are still new, who need more info...
once again, thanks a lot... if you have anymore suggestions or any corrections that I need to make, please tell me.
Click to expand...
Click to collapse
i think you should remove the specs(it makes the guide look complicated & big) & give a link to gsmarena or htc site

I actually like that you added the specs
The only thing you should do is to keep it updated.. thats all
Thanks

Can you please note in the downgrade HBOOT section that RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs. Would save a lot of people asking why they can't downgrade.

Thanks for the support guys. I've added some new guides today. If I made some mistakes and need corrections on those guides, please do inform me. I'm always here to improve it. Thanks!
tigris666 said:
Can you please note in the downgrade HBOOT section that RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs. Would save a lot of people asking why they can't downgrade.
Click to expand...
Click to collapse
Thanks! Added!

*remove this please. sorry for double post*

can you add how to install custom recovery & how to perform a nandroid backup to the guide?

You should also link the downgrade method in post 4 by sonikz. I think it's the easiest and recommended way to do this...
greets

Brilliant. Good job man, very useful

juergen_90 said:
You should also link the downgrade method in post 4 by sonikz. I think it's the easiest and recommended way to do this...
greets
Click to expand...
Click to collapse
yes, I did include the link, please check again thanks
p.s. added a new guide to do nandroid backup and restore. Also another FAQ about s-off and root for the new OTA update.
btw, did I miss something? the http://alpharev.nl/x/beta/ is not working anymore.. it gives me 404 error...

nodeffect said:
yes, I did include the link, please check again thanks
p.s. added a new guide to do nandroid backup and restore. Also another FAQ about s-off and root for the new OTA update.
btw, did I miss something? the http://alpharev.nl/x/beta/ is not working anymore.. it gives me 404 error...
Click to expand...
Click to collapse
new site
& now hboot 0.98.0002 is supported no need to downgrade anymore

This morning I red about Revolutionary: a collaboration between unrevoked and alpharev.
Maybe you can add it to your post
http://revolutionary.io/

I tried the alpharex, but i always get failed t oget root in step 2
Hboot : 0.98.0002, rom stock version 1.47.401.4, android 2.3.3 any thoughts?
cheers

mr.boonet said:
I tried the alpharex, but i always get failed t oget root in step 2
Hboot : 0.98.0002, rom stock version 1.47.401.4, android 2.3.3 any thoughts?
cheers
Click to expand...
Click to collapse
Try using the new revolutionary tool, I've updated the guide(please look back at first post). Hope this helps.

[TOOL][All devices & OS] Fastboot Commander [v.1.51][UPD 15 AUG 2011]

Don't forget to hit that "thanks"/Donate button or check out my APK(s) installer tool found in my signature :0)
Updated to version 1.51.
Added: Conversion of BMP images to ready-to-flash splash files on all 3 systems.
Modified: Graphical layout is now more in sync in all 3 systems.
Modified: All tooltips are now corrected and fully helpful :0)
Hi everyone.
This is a tool written in JAVA for easier flashing of the following partitions:
Radio, hboot/spl, recovery, system, boot, userdata, kernel and splash.
It can do much more, like:
Conversion of 24bit BMP images to ready-to-flash splash files.
Erase/wipe multiple or single partitions.
Reboot device either to system or fastboot.
Print of device info.
Flash of kernel.
Possible to run custom fastboot commands instead of using cmd/shell.
Flash of signed zip files (E.g. fastboot flash zip myzip.zip)
The above(Flash of signed zip) should not to be confused with flashing of custom rom files!
It's only meant for signed HTC roms with complete system layout.
Flash multiple files in one click by using custom folders and tags.
It's basically a GUI over most fastboot commands.
It works for Windows, Linux and Mac.
No need for Android SDK, the jar-file has all needed files bundled!
It's well tested and have more than +10000 users.
It works for all devices which has fastboot :0)
Any feedback is appreciated.
Requirements:
Min 30 % battery!
Engineering hboot/spl OR S-OFF!
Do not reboot or shutdown, if you ever get an error flashing the radio or the hboot/spl!
Ask here for help if it happens!
Instead of having to maintain multiple OPs, i have decided to redirect the OP to the desire forum. It's only the facade and nothing else. All questions and ect regarding the EVO 4G will still be on this thread :0)
The tool is the same and will work on any device which have fastboot mode.
LINK:
http://forum.xda-developers.com/showthread.php?t=1193915

Great idea
Sent from my PC36100 using XDA Premium App

does it work with hboot 2.16.0001 evo 4g

leo72793 said:
does it work with hboot 2.16.0001 evo 4g
Click to expand...
Click to collapse
I'm not an expert on the EVO... but try it out.. nothing to lose. If the command is rejected than nothing will happen :0)
But as rule of thumb: You must have eng spl or s-off. But some s-on devices still allows you some commands... Just try it out.
NB: I was unsure if it had any use in the Evo section... if it turns out to be not useful, i will removed it straight away :0)

Basically, EVO users will need the 0.76 engineering hboot version for all commands to work.

github said:
Basically, EVO users will need the 0.76 engineering hboot version for all commands to work.
Click to expand...
Click to collapse
If you need to get .76 back then check out this:
http://forum.xda-developers.com/showthread.php?t=883548

Cool idea, ill try it when the new kernel is done.
Sent from my PHAT Iconia

Updated to ver.1.51
Enjoy :0)

Works Great on my Evo(Details in Sig.) very user friendly

Just reached 3500+ downloads for version 1.51 :0)
Keep the thanks/donations and REPLIES coming or this thread will die :0(

Fastboot Commander v.1.51 just reached 6300 + downloads
Remember to leave a REPLY or the this threads will die...
Hitting the "THANKS" and/or Donate button won't hurt either

[Q] Flashing 3.16 radio on 3.24

Hey wonderful people of xda, a quick 2 part question.
firstly, I updated from insert coin 4.3.2 to 4.4.4, and found that my cell signal got significantly worse. I was wondering if I could flash the firmware 3.16 radio and ril that came with insert coin 4.3.2 onto 4.4.4?
secondly, does anyone happen to have these radio/ril files, and if not, how do I go about extracting these files?
thanks a lot in advance guys!

MoodyTunic said:
Hey wonderful people of xda, a quick 2 part question.
firstly, I updated from insert coin 4.3.2 to 4.4.4, and found that my cell signal got significantly worse. I was wondering if I could flash the firmware 3.16 radio and ril that came with insert coin 4.3.2 onto 4.4.4?
secondly, does anyone happen to have these radio/ril files, and if not, how do I go about extracting these files?
thanks a lot in advance guys!
Click to expand...
Click to collapse
Hello, you can always flash a 3.16 radio.
You can get them from here- http://forum.xda-developers.com/showthread.php?t=1178143
Just make sure you find the right one.
Cheers

Thanks so much! Took me a bit to find that thanks button =P.
Although I am still a bit lost on which radio/ril 3.16 had, and also where to find said radio/ril in that thread. Its not on the front page, a quick thread search turned up nothing, and the 71 page count seems quite daunting to flip through manually D=. If anyone could enlighten me on this that would be awesome.

I am unable to find the 3.16 RUU, but was able to find the 3.12 RUU.
You can download the *PG58IMG.zip* File. According to the thread, the zip should include:
adsp.img - added to the package [20.01.2012] - This is needed for 3.12.xxx.x/3.24.xxx.x/3.25.xxx.x based ROM to boot!
android-info.txt - updated [28.01.2012]
dzdata_4g.hdr - removed from the package [28.12.2011]
dzdata_4g.img - removed from the package [28.12.2011]
hboot_8x60_1.27.1100_20120113_signedbyaa.nb0 (with unlocked fastboot)- updated [28.01.2012]
pg2fs_spcustom.img
radio.img - updated [20.01.2012]
rpm.img - updated [20.01.2012]
sbl1.img - updated [20.01.2012]
sbl2.img - updated [20.01.2012]
sbl3.img - updated [20.01.2012]
tz.img - updated [20.01.2012]
All you have to to is open the zip file and copy the radio.img.
Drag the radio.img from the Zip file to the root of your adb folder(previously used in Writing SuperCID), Go to your start menu & search for "run" then type in cmd - you should get a black window.
4. Type in the Following Commands into the window(terminal).
Code:
cd C:\adb -Note, this should be your adb file location
adb devices - to check whether is your device connected
adb reboot bootloader - your device should reboot into Fastboot Bootloader
fastboot flash radio radio.img - now let your "cmd.exe" do all the work
5. When the "start here.exe" shows "finished. Total time: ---", type in this next,
Code:
fastboot reboot
Your phone should reboot & everything is done!

And here's the RIL for the 11.56 radio (3.12 leak).
http://forum.xda-developers.com/showpost.php?p=21125258&postcount=258

Thank you both! Even when I did the dumb thing of saying 3.16 when I meant 3.12 .

MoodyTunic said:
Thank you both! Even when I did the dumb thing of saying 3.16 when I meant 3.12 .
Click to expand...
Click to collapse
Quick question, was the signal actually worse or just the bars shown in the notification area ?
The shown bars usually have no real measure of the actual signal strength between ROMs or ROM versions.
The bottom line is: Does it work as you'd expect.

[TOOL][2 DEC] HTC Sensation/XE/4G Super Utility (AIO) by kgs1992 v8.0

OLD INFO:
This old info is not updated. Please read the above post for the link to the instructions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HTC Sensation/XE/4G Super Utility by kgs1992​
THIS UTILITY HAS BEEN FEATURED ON THE PORTAL!
Read Here​
:::: What does this do? ::::
This tool provides a very simple & easy way for any of these:
​
Reboot your device normally, or to bootloader or recovery.
S-OFF for Hboot ≤1.18 devices using Revolutionary
S-OFF for Hboot 1.2x devices using JuopunutBear (Wire trick is needed)
Installing 4EXT Touch Recovery or CWM recovery for all S-OFF / HTC Dev Unlocked devices.
Rooting for all devices (With or without a custom Recovery)
Write SuperCID or custom CID for all S-OFF devices
Install firmware for all S-OFF devices
Flash ZIP from recovery for all S-OFF devices with custom recovery installed
Flash PG58IMG.zip (Depending on what the PG58IMG.zip is, the requirements for this may differ)
Flash boot.img for HTC Dev unlocked/ S-OFF devices
Flash Unlocked =JuopunutBear= Hboot for devices that have S-OFF
*devices implies HTC Sensation/XE/4G wherever used in this post/thread​
Best suited for noobs and people with dead screens or volume/power keys that don't work properly, since 90% of the interaction is with the computer.
I have spent a lot of time perfecting this utility. It is now safe to use!!
Read through the instructions and everything will execute smoothly.​
:::: What do I need to do? ::::
↓ You need to just trust the tool & follow these instructions ↓
Step by step Instructions:
Uninstall all programs that start with "HTC" ; including HTC Sync, HTC Driver, etc. Also uninstall / close any interfering software. (Very important if you're using this tool for S-OFF)
Install HTC drivers from here and reboot your PC.
Make sure you set HTC Sync as default mode with Ask Me Everytime disabled and Enable USB Debugging option.
(Default mode & ask me options are in Settings>Connect to PC. USB Debugging option is in Settings>Developer Options)
NEVER use USB hubs or USB 3.0 ports!
[*]Disable your anti virus program when you run the tool
Ensure that you have a battery level of at least 40% before using this too.l
Download and open the zip file. Unzip it to any convenient location.
Run "Menu.bat" file and follow the onscreen instructions.
Please note that the menu you are presented with shows you the options & not the steps
DO NOT run the file as administrator.
Please ensure that you are connected to the internet while using the tool since files are not packed into the tool & need to be downloaded as required.
When asked for a response, always type 1 for yes & 0 or anything else for no. When asked to press enter to exit, press Enter to exit & not the close button on the window.
​
It's as simple as that ​
Read post #2 in this thread for important tips!
:::: Download ::::
(Click the button to go to the download page)​​
Total number of downloads: 19k (Updated every week)
If you have used the tool, please post your feedback, along with suggestions for improvement!
Also, screenshots in the attachments!
Last but not the least, a lot of time & effort has been put in to bring this tool to you and to make it foolproof. If this tool helps you or if you wish to show your support, please don't forget to hit the thanks button! ​
:::: Donations ::::
sytauro
xan_asmodi
catmanic x2
guidogsbn
markwatson
Gozzeh
Homewrecker
alphaditya
jr_718
​
If you'd like to show your support/appreciation, donations are welcome!
This is of course, entirely optional.
​Thank you. I appreciate your support and it encourages me to do even better.​
Video Tutorials on YouTubehttp://www.youtube.com/playlist?list=PLYPCYqjlXVCaKSq4sxINHL4PPSgltE_F0http://www.youtube.com/playlist?list=PLYPCYqjlXVCaKSq4sxINHL4PPSgltE_F0 <--Click here​(Thanks to locn for video tutorials)​
Additional Info​
:::: TIPS ::::
For JuopunutBear S-OFF, HTC Dev unlock method is recommended because the timing of the wire trick does not need to be 100% exact. The fact that the unlock token has been used will not be visible on the phone. This is what HTC uses to determine whether the bootloader has been unlocked. No matter which method you follow, the outcome is the same. If two identical phones were S-OFF each using one of these methods, you could not differentiate one from the other. (This is not a false claim; I have seen it myself.)
For problems with JuopunutBear refer here or join IRC Channel #juopunutbear on freenode. Note: The method without HTC Dev unlock is not supported by the channel, except for cases where the motherboard has been replaced. NO TOOL RELATED QUESTIONS ON THIS CHANNEL. (only questions related to JB & wire trick are entertained)
For problems with JuopunutBear S-OFF without bootloader unlock, refer here.
For JuopunutBear S-OFF (Hboot 1.2x) you may lose data on SD Card. You should backup or use a spare SD Card.
For JuopunutBear S-OFF using unlock bootloader method, you only need to unlock your bootloader using HTC Dev. Rooting is done within the tool (optional).
For Hboot ≤1.18 S Off, please ensure that you don't have custom recovery installed. If you do, refer this post for the solution.
For writing custom CID, please refer here for a list of valid CIDs based on provider/locations.
For general help, post in this thread or join IRC Channel #helpmenow on freenode. [I can be found here. If you see me there but I don't reply, you can take help from others.]
:::: CREDITS ::::
Revolutionary.io for Revolutionary & Revolutionary CWM recovery.
Unlimited.io for JuopunutBear & JuopunutBear hboots.
madmaxx82 for 4EXT Touch Recovery
sparkym3 for TPSparkyRoot
mike1986. for Rooting Tools from his site
ganeshp for all his help and ideas!
Keylogger_0 for help with logging.
tinky1 , dexter93 & globatron for their help & support.
The Sensation community & anyone I might have forgotten.
​
:::: Changelog ::::
Code:
[CENTER]
v7.1
-Bug fixes
-Hosting changed
-Linking method changed. The tool will never need to be updated due to link changes.
v7.0
-Added ability to start the tool from any screen on the phone
(i.e bootloader/recovery/android.)
-Firmware flashing is now done in RUU mode.
-Now requires almost 0 feedback from the user as most things are checked automatically.
-Automatically attempt to add CID to fastboot flashable zips if flashing fails
-No need to download any files anymore.
Depending on requirements, files are automatically downloaded.
-MD5 checking for downloaded files.
-Choice of recovery added. You can now flash CWM or 4EXT
-On-screen Instructions simplified.
-Few typos corrected.
-Text formatting improved. (Also, colour added :P )
[B][COLOR="Blue"][Released][/COLOR][/B]
Changelog for older Versions:
[HIDE]
v6.6
-Added helpful echos to Hboot 1.18 S-OFF
-Added log feature for tacoroot
-Few typos corrected
v6.5.1
-Menu fixed
-Typos corrected & extra info added
-Minor bugs corrected
v6.5
-Fixed file not found errors
-Fixed ping errors
-Restriction removed on folder name
-ping.exe removed from zip
v6.4.4
-Added ping.exe to fix error on systems with incorrect variable paths*
*This is not a problem with the tool, but some problem with your PCs
v6.4.3
-Fixed link
-Fixed file not found loop
v6.4.2
-Fixed errors in code
-Fixed incorrect links
-Fixed incorrect title
v6.4.1
-Menu bug fixed again
v6.4
-New menu bug fixed
-recovery.img file existence check added
v6.3
-Fixed menu
-Added new method to flash recovery
v6.2
-An error in code for temp root has been rectified
-Added option to flash ENG boot for devices after JB S-OFF that retain *locked* status
-Hboot 1.2x S-OFF now supports HTC Dev Unlocked devices
-S-OFF tested (thanks [URL="http://forum.xda-developers.com/member.php?u=1529048"]anko184[/URL]) and fixed
v6.1
-Corrected wrong info about Super CID & Custom CID working with HTC Dev Unlock
-Added wait time before fetching CID to ensure it fetches properly
v6.0
-Added new options to S-OFF utility making it much safer
-Added ability to flash PG58IMG.zip
-Added ability to flash boot.img
-Implemented new rooting method that supports all devices
-Added ability to reboot the device using the tool
v5.0
-All options tested & working with my phone [Except S-OFF]
-Fixed zip not being deleted after install
-Major fix to ensure integrity of USB connection *
-Added delay effect for all output making it easier to read
-Rooting Utility changed
*Previously, the commands would execute as soon as adb detected the device. Now, I have added a wait time of 90 seconds to ensure that the device boots completely before any commands are executed, thus, making this tool all the more fool proof
v4.1
- Added ability to add custom CID
v4.0
-Added support for S-OFF Hboot 1.2x devices
v3.1
-Added flash zip from recovery option
-Corrected typos and incorrect commands (thanks to [URL="http://forum.xda-developers.com/member.php?u=4546540"]ganeshp[/URL])
v3.0
-Cleaned up scripts
-Added Install firmware feature
v2.0
-Added Permanent Rooting feature
-Added Write SuperCID feature
-Changed most scripts to make them efficient
-Added Menu to make navigation simpler
v1.1
-Fixed delete PG58IMG.zip after recovery install
v1.0
-Added & tested the 4EXT recovery flashing option.
[/HIDE][/CENTER]
:::: Footnote ::::
Warning for non HTC Sensation/XE/4G devices:
This tool is not intended for any other phones, although some features may work for other phones as well.
The reason you see batch files & not an executable is because my script is open to all.
View it, use it, change it, do as you wish!
I am against the uploading of the tool to other locations.
I will NOT provide support to anyone who has not downloaded the tool from the thread.
You will not duplicate my work; you may use the code as you please, but not the entire tool itself.
I don't claim full credit for this utility.
I am not to be held responsible for any damage this program may cause to you or your devices.
Use it at your own risk.
I will provide support for the tool here in this thread & on #helpmenow IRC Channel. NO PMs PLEASE.
I hold no responsibility for the outcomes from the use of this tool.​​
NEW INFO (Duplicate):
HTC Sensation/XE/4G Super Utility by kgs1992​
THIS UTILITY HAS BEEN FEATURED ON THE PORTAL!
Read Here​
:::: What does this do? ::::
This tool provides a very simple & easy way for any of these:
​
Reboot your device normally, or to bootloader or recovery.
S-OFF for Hboot ≤1.18 devices using Revolutionary
S-OFF for Hboot 1.2x devices using JuopunutBear (Wire trick is needed)
Installing 4EXT Touch Recovery or CWM recovery for all S-OFF / HTC Dev Unlocked devices.
Rooting for all devices (With or without a custom Recovery)
Write SuperCID or custom CID for all S-OFF devices
Install firmware for all S-OFF devices
Flash ZIP from recovery for all S-OFF devices with custom recovery installed
Flash PG58IMG.zip (Depending on what the PG58IMG.zip is, the requirements for this may differ)
Flash boot.img for HTC Dev unlocked/ S-OFF devices
Flash Unlocked =JuopunutBear= Hboot for devices that have S-OFF
*devices implies HTC Sensation/XE/4G wherever used in this post/thread​
Best suited for noobs and people with dead screens or volume/power keys that don't work properly, since 90% of the interaction is with the computer.
I have spent a lot of time perfecting this utility. It is now safe to use!!
Read through the instructions and everything will execute smoothly.​
:::: Where can I find all the info? ::::
All info & downloads have been moved to my website.
You can find all instructions & downloads here: kgs1992 - KGS Utility
Please do not download from other sources since it may not be the latest version & older versions should NOT be used!
Remember to read the Known Issues post for fixes to known problems.​
:::: FAQs ::::
Q. How safe is this?​It's as safe as it can get without someone being physically present to ensure that you do everything right. If you follow the instructions, this is very safe.
Here is what makes it safe:
Ample, easy-to-follow instructions.
Dynamic checks to ensure previous steps completed properly & device is exactly as it needs to be.
MD5sum checking for downloaded files before flashing.
If anything fails, it is retried. If it fails constantly, then all changes are undone & error messages are shown.
Regular updates with new features.
Immediate bug fixes when reported.
Dedicated real-time support on IRC (#kgs1992 on Freenode network).
Q. Why did you make this?​Of course, it was intended to be helpful to newbies to S-OFF & flash their phones and also serve as a good example for making a completly n00b-proof toolkit for anyone who wanted to make one.
Started off as wanting to learn something new. Helped me learn not only how to write batch scripts but by extension I learnt many more things & also more about the phone.​
Q. Where can I find support?​If you find yourself in need of help with using this, you can find real-time support on IRC (#kgs1992 on Freenode network). [Please note that as the single person maintaining this project, it is difficult to be online & answer questions 24/7. You might have to wait a while at times.]​
Q. Will you make this for more devices in the future?​If I get enough requests. Requests can be made using the feedback form on this page.​
Q. Will you make this for a different platform (Linux/Mac)?​If I have the time, I may. But this probably isn't going to happen.​
Q. How can I help?​You can leave your feedback, suggestions, comments, etc. here in this thread or use the feedback form on this page.
If you like my work, you can push my thanks button (This can be found at the bottom-left of this post.) & rate 5★ s for the thread. (This can be found at the top-right of the page.)
If you wish to make a donation, you may do so here or do so directly via PayPal to [email protected] .​
​

HTC Sensation/XE/4G Super Utility by kgs1992
THIS UTILITY HAS BEEN FEATURED ON THE PORTAL!
Read Here
NO LONGER SUPPORTED
I no longer own a HTC Sensation, nor do I have the time required to provide help and support personally.
v8.0 is the last increment for this utility. You may still use the utility at your own discretion.
:::: What does this do? ::::
This tool provides a very simple & easy way for any of these:​
Reboot your device normally, or to bootloader or recovery.
S-OFF for Hboot ≤1.18 devices using Revolutionary
S-OFF for Hboot 1.2x devices using JuopunutBear (Wire trick is needed)
Installing 4EXT Touch Recovery or CWM recovery for all S-OFF / HTC Dev Unlocked devices.
Rooting for all devices (With or without a custom Recovery)
Write SuperCID or custom CID for all S-OFF devices
Install firmware for all S-OFF devices
Flash ZIP from recovery for all S-OFF devices with custom recovery installed
Flash PG58IMG.zip (Depending on what the PG58IMG.zip is, the requirements for this may differ)
Flash boot.img for HTC Dev unlocked/ S-OFF devices
Flash Unlocked =JuopunutBear= Hboot for devices that have S-OFF
*devices implies HTC Sensation/XE/4G wherever used in this post/thread​
Best suited for noobs and people with dead screens or volume/power keys that don't work properly, since 90% of the interaction is with the computer.
I have spent a lot of time perfecting this utility. It is now safe to use!!
Read through the instructions and everything will execute smoothly.​
:::: Where can I find all the info? ::::
All info & downloads have been moved to my website.
You can find all instructions & downloads here: kgs1992 - KGS Utility
Please do not download from other sources since it may not be the latest version & older versions should NOT be used!
Remember to read the Known Issues post for fixes to known problems.​
:::: FAQs :::: ​Q. How safe is this?​It's as safe as it can get without someone being physically present to ensure that you do everything right. If you follow the instructions, this is very safe.
Here is what makes it safe:
Ample, easy-to-follow instructions.
Dynamic checks to ensure previous steps completed properly & device is exactly as it needs to be.
MD5sum checking for downloaded files before flashing.
If anything fails, it is retried. If it fails constantly, then all changes are undone & error messages are shown.
Regular updates with new features.
Immediate bug fixes when reported.
Dedicated real-time support on IRC (#kgs1992 on Freenode network).
Q. Why did you make this?​Of course, it was intended to be helpful to newbies to S-OFF & flash their phones and also serve as a good example for making a completly n00b-proof toolkit for anyone who wanted to make one.
Started off as wanting to learn something new. Helped me learn not only how to write batch scripts but by extension I learnt many more things & also more about the phone.​
Q. Where can I find support?​If you find yourself in need of help with using this, you can find real-time support on IRC (#kgs1992 on Freenode network). [Please note that as the single person maintaining this project, it is difficult to be online & answer questions 24/7. You might have to wait a while at times.]​
Q. Will you make this for more devices in the future?​If I get enough requests. Requests can be made using the feedback form on this page.​
Q. Will you make this for a different platform (Linux/Mac)?​If I have the time, I may. But this probably isn't going to happen.​
Q. How can I help?​You can leave your feedback, suggestions, comments, etc. here in this thread or use the feedback form on this page.
If you like my work, you can push my thanks button (This can be found at the bottom-left of this post.) & rate 5★ s for the thread. (This can be found at the top-right of the page.)
If you wish to make a donation, you may do so here or do so directly via PayPal to [email protected] .​
For some reason, this post and the next post were interchanged randomly and hence, I had to duplicate the OP.​

Great...can work on hboot 1.29,i knw it says 1.18 but just askin
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA

Unfortunately I will probably never get to use this tool, but none less thank you and keep up the work. But one complaint, this should have been posted in the Sensation Android Development forum.

kishen80 said:
Great...can work on hboot 1.29,i knw it says 1.18 but just askin
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
Click to expand...
Click to collapse
Well, Revolutionary only supports devices with Hboot 1.18 or less.
Maybe if I modify this to make it work with other programs, it's possible.
EDIT: Yes, now works on Hboot 1.2x
T-Macgnolia said:
Unfortunately I will probably never get to use this tool, but none less thank you and keep up the work. But one complaint, this should have been posted in the Sensation Android Development forum.
Click to expand...
Click to collapse
Well, when I asked dexter, he was of the opinion that it should be placed in general.
And thank you
EDIT: Moved to Sensation Android Development

Added extra function to flash 4EXT Recovery v1.0.0.5 RC3 for S Off devices!

Good work. Once you finished adding stuff to it, we will request to move it to Dev.
Sent from my HTC Sensation Z710e using xda premium

kgs1992 said:
Added extra function to flash 4EXT Recovery v1.0.0.5 RC3 for S Off devices!
Click to expand...
Click to collapse
Nice one buddy added thanks for U...Keep it up

Fixes
Hboot ≤1.18 S Off, removing custom recovery:
Tacoroot won't work with custom recovery. You need to flash the stock recovery.
Make sure that your bootloader is unlocked.
Download this rcovery.img
Put it into the tools folder. (If you get a overwrite warning, just replace the previous file)
Run menu.bat & select option 3 (always select no for method 2). (Method 1 will install any recovery named recovery.img)
Re-run menu.bat & select the appropriate options for S Off.
If it fails again, then perform a factory reset & try again.
If it fails again, It would be a good idea to run an RUU

I've previously S-OFF'd using revolutionary and rooted my Sensation 4G with clockworkmod but failed to get the SuperCID working.
but I've been exploring looking into flashing ARHD and that required both 4ext and SuperCID.
Would I just run this tool without using the S-OFF part and proceed to install 4ext, root, supercid, etc?

NinetoFive said:
I've previously S-OFF'd using revolutionary and rooted my Sensation 4G with clockworkmod but failed to get the SuperCID working.
but I've been exploring looking into flashing ARHD and that required both 4ext and SuperCID.
Would I just run this tool without using the S-OFF part and proceed to install 4ext, root, supercid, etc?
Click to expand...
Click to collapse
Yes, you can choose what you want to perform. So, run the Menu.bat once select the Install 4ext option.
Then run again & select SuperCID.
And then repeat, choose install firmware.
You will have to interact only with the PC, not with your phone.

Finally, the utility now supports devices with Hboot 1.27 using the temproot + JB method!
Please give it a try or look through the code and let me know if there is any bug (doubtful there is any)

This is a nice program, i like the automated supercid, im probably gonna give that a try...anyway to make an option to put the tmobile cid back (T-MOBO10)?

el7145 said:
This is a nice program, i like the automated supercid, im probably gonna give that a try...anyway to make an option to put the tmobile cid back (T-MOBO10)?
Click to expand...
Click to collapse
I'll have to look into that. Maybe you may find it in the coming versions.

This application does S-off in devices with Hboot 1:27 S-on?
How it works?
I find it very difficult to make S-off with the Hboot 1.27, using the method JuopunutBear..
Awaiting your response, to download and install.

PC400 said:
This application does S-off in devices with Hboot 1:27 S-on?
How it works?
I find it very difficult to make S-off with the Hboot 1.27, using the method JuopunutBear..
Awaiting your response, to download and install.
Click to expand...
Click to collapse
the only way to s-off 1.27 is with JuopunutBear wire trick method

PC400 said:
This application does S-off in devices with Hboot 1:27 S-on?
How it works?
I find it very difficult to make S-off with the Hboot 1.27, using the method JuopunutBear..
Awaiting your response, to download and install.
Click to expand...
Click to collapse
If you read carefully, it uses the same method. Just more organized because everything is done from a single program including the temp root.

kgs1992 said:
If you read carefully, it uses the same method. Just more organized because everything is done from a single program including the temp root.
Also doesn't void your warranty since it doesn't use the HTC Dev method.
Click to expand...
Click to collapse
Ok, I'll have to make the process of touching the wire on the card? Mine is 1:27 Hboot Unlocked S-on, I got through the Htc dev.

kgs1992 said:
If you read carefully, it uses the same method. Just more organized because everything is done from a single program including the temp root.
Also doesn't void your warranty since it doesn't use the HTC Dev method.
Click to expand...
Click to collapse
you do know that JuopunutBears new method doesnt use htcdev unlock either?

PC400 said:
Ok, I'll have to make the process of touching the wire on the card? Mine is 1:27 Hboot Unlocked S-on, I got through the Htc dev.
Click to expand...
Click to collapse
Since you have already used HTC Dev to unlock, I recommend you don't use this utility because all you need to do is run the control bear and perform the wire trick.
And yes, the tool will employ the same methods as JuopunutBear (except HTC Dev Unlock) because that is the same application used in this tool.
EDIT: Now supports HTC Dev unlocked devices for SOff

[2017.04.06] S-OFF Firmware flashing (Fastboot) (Current: 4.28.401.3)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This thread is meant for S-OFF phones. People not having their security OFF please refer to HTC RUU methods or “Stock Backup and OTA” method.
Read from top to bottom. No skipping of stuff or you will be confused.
Notice:​Files posted in this thread, which are not added to the first 4 posts should be considered source-material for my work. Flashing them means you know what you do. I only accept some limited responsibility for the files i add to the first 4 posts, because that means they flashed fine on my phone or on trusted peoples phones. However, I encourage people to send me files to work with. I am not able to search all over the Internet for source files myself. If you want some NoWipe or FullWipe firmware package added, send me the original untouched HTC base files required.
This thread serves the purpose of providing both Firmware files and reliable information for safe flashing. The main aspect of this thread is information gathering, processing and presentation for you, the user, to learn how to work with firmware and establish a solid base knowledge, so you can act more independently.
Many custom ROM Teams cannot cope with supporting the entire firmware upgrading procedure. This is something the user usually needs to figure out himself. So, I also see my task as a Team Venom member to provide the information necessary to enable you to learn all this. Of course this is not only suitable for Venom ROM’s.. Its pretty general stuff.
The safest way is still HTC’s RUU and OTA system, yet HTC is not providing RUU’s for the international version, so my files are the best option here. Carrier Version RUU’s can be accessed via HTC’s US Support Site. Select your device and then click on “News and Alerts” at the top of your device’s site - usually, there will be a RUU for Dev/Unlocked (617), Sprint (651), AT&T (502) and T-Mobile US (531). RUU’s are superior to other flashing methods because they carry a tested combination of partition images and the method itself is also known to work well. Also, RUU’s do always reassure you that there is a guaranteed and safe way to go back (psychological advantage).
If you happen to get access to an international RUU, share it with Alex, or me please. RUU’s are hosted on androidruu.com by Alex from Androidfilehost.com within a short time after being made available to him. Hit him up on Twitter with a link and ask him to add it or send it to me and i will! I have a direct channel to AFH and can see to it quickly.
I consider this rather important because androidruu.com is only providing a plattform - it is only as good as our community based additions. There is no secret RUU leaker behind it. It has what we have and organizes that in one place and provides an archive to old stuff. So, we are in charge of looking after it.​
Other than that, we are mostly stuck with RUU components, usually OTA packages. OTA’s usually depend on a certain Firmware version to be already installed, OTA’s only update parts - they are “incremental”. If you happen to skip an update, you might not get all partitions updated correctly and end up with incompatible partitions, which might (worst case scenario) lead to a brick. I am trying to circumvent this problem with my FULL ZIP packages - with these you can safely jump from a very old firmware right up to the newest.
There are several methods to flash Firmware. The “SDCard Method” can be considered the fastest and most suitable for people without a PC. However, I mistrust it because I mistrust SDCards (much experience). Then there is the “RUU Method” which I have altered to a “FUU Method” in the past - It is simple and safe. However, it kept people from learning how to use fastboot and I don’t condone that anymore. For ROM support I need users who are capable to deal with Fastboot and ADB. So, this thread will deal with the “Fastboot Method”. The “FUU” can still be had and used from my Batch Tool in Post #4 though. I just won’t fuss around with it much.
ZIP Variants provided here:​
Full Stock WIPE ZIPs:
Nothing removed - Everything stock! This type of zip also re-flashes the /data partition with HTC’s DZDATA files (meaning you loose everything on your internal SDCARD). Also replaces the Kernel, Ramdisk, recovery and Splash1 with latest stock images! The /system partition will not be touched. (Else this would be a RUU.zip). It also includes the “Apppreload.img” with all the carrier-bloatware.
Be sure to put a ROM onto your EXTERNAL SD before proceeding with a Full WIPE ZIP! Else you can also ADB push a ROM in recovery mode after fastboot reflashing a recovery. The newer TWRP variants also support a normal MTP connection and might support USB mass storage at a later stage. Phone will NOT boot without ROM reflash after using this!
NoWipe ZIPs:
This package is modified. This type of ZIP updates basic Firmware partitions, does not touch the /data partition, leaves kernel, splash and ramdisk (in order to support custom ROM’s modifying ramdisk) alone. The “Apppreload.img is removed, the bloatware partition will remain unchanged (to remove bloat permanently flash Apppreload.img from International/WWE/401). Recovery will be replaced with the current TWRP. Phone will boot normally after using this.
And what you won’t get here (fine print):
Since this is a Firmware Update Thread and not a ROM thread, you do NOT EVER get a ROM (a.k.a “System.img” or plain: “System” here. You understand and agree that you cannot have this from me. You also acknowledge that I cannot be blamed for your non-booting phone due to you not reading or not understanding this.​
I will cover GSM PHONES ONLY - no cdma / sprint firmware except when i wish to do otherwise ​
Firmware ZIP Flash HowTo​
Prerequisites:
You need ADB and Fastboot on your PC. To get ADB and Fastboot up and running I strongly suggest you use my “Batch Tool” setup, because it contains an updated htc_fastboot, which is 100% working with the M9 . This is important: the generic Google fastboot from SDK API Level 22 (latest at time of writing) is NOT FULLY COMPATIBLE. Update December 2015: seems there still are problems with Google Fastboot from API Level 24. You’ll still need the htc_fastboot.exe.
The ZIPs provided here are also repackaged, meaning not compatible with HTC Security, meaning you need S-OFF. Like stated at the top already. However, the method itself can be applied to HTC signed zips too, those could then be flashed to S-ON phones when certain conditions are met.
Step-By-Step:​1. If device is booted into Android, reboot into download mode by running:
Code:
adb reboot download
NOTICE: adb reboot download is new on the M9 for those who come from earlier HTC devices - zips can be flashed in download mode or RUUMode, both work. The on-screen status report is more detailed in download mode. This making it the preferred flashing mode for now.
1.a Or else, if your device is in a different state or you just prefer the button method:
Press Power for 15 seconds and hold VolUP at the same time, when the screen and charging LED go dark immediately slide your finger down to VolDown until you see the bootloader screen. Notice: First VolUp, then VolDown as soon as the screen goes dark (and you hear the windows connection sound if your phone is hooked up). Then use the VolUp and VolDown buttons to navigate to “Download Mode” and then press Power to confirm.
2. Now place the Firmware_xx.zip into your adb/fastboot folder (which will be "C:Androidcom" if you use my Batch Tool).
2a. This is optional - see my notice above:
Type
Code:
fastboot oem rebootRUU
3. Followed by:
Code:
fastboot flash zip Firmware_xx.zip
(replace "Firmware_xx.zip" with the name of your zip)
4. Now check the console output. It should approximately look like this log:
NOTICE: this flash log is taken from a FULL RUU flash on my M9, when you repeat this process, there will be several images missing in your flash, like first and foremost System.img won’t turn up in your log, obviously, since we do not include System. New is also that the checking routine is way more sophisticated and Controller Firmware for e.g. the touch panel or the Infra Red Remote and the like do NOT get flashed if the checks determine that they are already up-to-date. Images that do not get flashed show “BYPASSED”.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
F:WorkfolderAndroid Taskercom>htc_fastboot oem rebootRUU
... OKAY
Execution time is 34(ms)
F:WorkfolderAndroid Taskercom>htc_fastboot flash zip rom.zip
sending 'zip'... (198996 KB) OKAY
sending time = 8.892 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
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 FA539YJ06951...
sending 'zip'... (198996 KB) OKAY
sending time = 10.564 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAILFAIL90 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 FA539YJ06951...
sending 'zip'... (198996 KB) OKAY
sending time = 10.604 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
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 FA539YJ06951...
sending 'zip'... (198996 KB) OKAY
sending time = 7.242 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
sending 'zip'... (463093 KB) OKAY
sending time = 28.801 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
sending 'zip'... (431122 KB) OKAY
sending time = 26.431 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
sending 'zip'... (490966 KB) OKAY
sending time = 30.226 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
sending 'zip'... (390788 KB) OKAY
sending time = 24.510 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
sending 'zip'... (200995 KB) OKAY
sending time = 13.855 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
sending 'zip'... (10850 KB) OKAY
sending time = 1.703 secs
writing 'zip'... (bootloader) HOSD CL#506785
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
Flash Zip Complete
Execution time is 398(s)
F:WorkfolderAndroid Taskercom>
Click to expand...
Click to collapse
Important: When flashing in RUUMode, the flash process halts at around 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output to make sure it is safe to reboot! The bar will only fill up to 100% once you type:
Important: This is not valid for Download Mode flashes - those finish at 100% on phone screen and in console and ask you to hit Power to return to Download Mode screen.
IF you encounter any errors which are not “FAIL90”, have a look into Post #3 or ask in the thread! DO NOT REBOOT THE DEVICE!
5.
Code:
fastboot reboot-bootloader
or press Power to return to Download Mode screen - depending on the mode you used to flash the zip.​
Recent additions​I usually don't provide untested zips, still, you flash at your own risk. Not everything was tested by myself. You're writing to critical parts of your phone. If anything goes wrong along the way, your phone might be bricked.​
M9_4.28.401.3_WWE_FullStock
M9_4.28.401.3_WWE_TWRP3100_NoWipe
M9_3.35.617.31_Unlocked_FullStock
M9_3.35.617.31_Unlocked_TWRP3100_NoWipe
M9_4.27.617.2_Unlocked_FullStock
M9_4.27.617.2_Unlocked_TWRP3100_NoWipe
M9_4.27.531.6_TMUS_FullStock
M9_4.27.531.6_TMUS_TWRP3100_NoWipe
M9_4.14.617.6_Unlocked_FullStock
M9_4.14.617.6_Unlocked_TWRP3030_NoWipe
M9_4.19.617.1_Unlocked_FullStock
M9_4.19.617.1_Unlocked_TWRP3030_NoWipe
M9_3.38.502.12_ATT_NoWipe_TWRP3020
M9_3.38.502.12_ATT_FullStock
M9_3.35.111.14_TMODE_NoWipe_TWRP3002
M9_3.35.111.14_TMODE_FullStock
M9_3.36.709.3_Asia-TW_NoWipe_TWRP3002
M9_3.36.709.3_Asia-TW_FullStock
Click to expand...
Click to collapse
Credits​
Thanks @Herwegan, who has been supporting my thread on the M7 for a good year and sadly decided to withdraw from XDA short.
ly after starting here with the M9. Also i would like to express my deepest gratitude to Team Venom, who aren't only good friends but also let me use their graphical stuff as base for my own stuff. Thank you!
Lately, the biggest props go out to @nkk71 and @captainthrowback because of their fantastic script that makes running bruutveal and ruuveal so much easier. Thank you so much for saving me a ton of time and helping users do their own firmware packages! That is quite an example you set there for the community!
Disclaimer​You are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that I cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones once a file has been posted to the first page, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, I only provide access and information to it.
You understand that you should not do it if you are not willing to accept this risk.​
XDA:DevDB Information
S-OFF Firmware flashing (Fastboot), Tool/Utility for the HTC One (M9)
Contributors
Sneakyghost, nkk71
Version Information
Status: Testing
Stable Release Date: 2016-12-27
Current Beta Version: 4.28.401.3
Beta Release Date: 2017-04-06
Created 2015-04-07
Last Updated 2017-04-06

...
Google Spreadsheet with all links​
Notice:
These links are all tested by at least someone. Nothing here will be completely untested. Most stuff I flash to my own phone. Exceptions might be some carrier zips which would require me to do a full backup and conversion and then restore, which is time consuming, so, simply put: 401's are always tested by me, the others sometimes but mostly by others.​
Credits
I have long lost track of my firmware sources. I am sorry i cannot name you guys all personally. The most common source would be @LlabTooFeR, @djluisbento, @AndroidFileHost (androidruu.com) HTCDev and some occasional random sources that come and go. If you find your stuff here and want to be included in the credits please contact me. I am very grateful for everyone busy providing dumps and direct leaks.​
Disclaimer
You are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones at time of posting, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.​

....
Error Handling Strategies for RUUmode/Fastboot​
IF IT SAYS "FAILED" do NOT immediately reboot the device If you reboot with a FAIL your device could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (don’t use hubs! Always direct-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot...
The least dangerous FAILED messages are listed below and are safe to reboot (below this section you find CRITICAL errors, please observe):
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 10 RU_MODELID_FAIL (MID in android-info.txt does not match phone’s MID)
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 24 android-info fail (means something wrong with android-info.txt in the zip)
- 32 header error (means the zip couldn't be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap CID first as explained below)
- 90 pre-update FAIL (means it only flashed aboot and you have to run the process again immediately to flash all other partitions). The new M9 htc_fastboot.exe now auto-reboots on Error 90! If it tries to boot to your Android System, force it back into download mode - the flashing process will continue again by itself. If it doesn't auto-commence, restart the flashing process as in Step 3.
- 99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues.
- 130 wrong model ID (seems its the same like 41, just that it shows in the FUU as 130.
- 155 seems to indicate different things. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match.
- 170 Check USB - FUU won’t run because of not working ADB.​
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error “10 RU_MODELID_FAIL” do:
- check that the Model ID in android-info.txt matches your phone’s Model ID.
Typically, making your phone “SuperCID” makes it ignore CID and MID mismatches alike. However, lately we have noticed HTC has changed that behavior. MID mismatches are not ignored by SuperCID anymore. You will need to unzip my firmware package, change the MID in there to your MID and rezip it. Or, alternatively, change your phone’s MID, which is a bit trickier.
To un- and re-zip, please refer to Post #5 of this thread for more information!)
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 24 "android-info fail" do:
- check that your ZIP isn’t some HTC OTA or anything thats got no android-info.txt - those cannot be flashed with fastboot flash zip nameof.zip command.
- check that your zip has a good MD5 and is not broken, check android-info.txt etc...
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn't help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successful firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “pre-update FAIL 90 ..." do:
- Let the phone reboot itself into Download Mode. If it doesn't boot to download mode, force it back there (From Android with adb reboot download or with the button method, see "step 1").
- If the flash does not auto-resume, run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definetely this means the ZIP is not signed - get an unmodified zip!
For “Error 130 wrong model ID" do:
- Please refer to Error Code 41/42.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers. One way to solve is to run the ARUWizard with the phone already in Fastboot mode. Else you will have to re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn't work well currently.​
NOT safe to reboot / Flash (partly) happened Errors (if you encounter one of them, DON’T reboot):
- 152 Image Error - Phone Screen shows a little triangle beside a full green bar​
For “Error 152 Image Error" do:
- Error 152 is quite rare, have seen it only once with a friend’s phone and it aborted the flash nearly at the end. The flash was started by the FUU. We could resolve the matter by NOT rebooting the phone and flashing the zip again through a manual fastboot flash as outlined further up.​

Batch Tool updated to 1.3.2
The "Android_Tasker" Batch Tool - a thing i am using for myself since 2012 and which i am sharing just because i have it. It is neither good nor special, but its the way i work and people who follow the instructions here might find it easier to use the same setup as we do.
It also has the "FUU" method included - details on that method will be added at a later stage. We do not consider the FUU a good option to flash Firmware anymore because we realized that getting away from ADB and Fastboot with toolkits makes troubleshooting harder at a later stage - people relying entirely on toolkits and tools will mostly not understand what is happening and helping there is much harder.
Since everything i do basically works out of the C:\Android\com path, all my zipped-up stuff extracts to that location. The FUU and the Task-Batch-Script both work from that location. This is simply to enable easier and faster creation of new zip’s if they all use the same base structure.
If you prefer to work from a different location. you can specify a different path in the installer. However, the batch scripts do not adjust automatically, which means if you use another path, you might need to open up the scripts in an editor and adjust some paths manually.
Preview:
DOWNLOAD
MD5:b25b24a5a7f2bc03dc68a411fb41fca4​
The installer is just a simple WinRAR self extracting archive - there is NOTHING BAD in there i swear! Open it with WinRAR 5 and look inside. You will see if you don't trust me.
Changelog:
1.3.2
Fixed Dump-Script - it wouldn't run properly anymore with newer ADB 1.0.32 for some odd reason.
Updated TWRP to 3.0.3-0
Updated stock recovery to 4.19.617.1 (Developer Edition, no Nougat on WWE yet)
1.3.1
Updated TWRP to 3.0.2-0
1.3.0
Updated stock recovery to 3.35.401.12 and TWRP to 3.0.0-2
1.2.9
Updated ARUWizard to 3.0.4.2015 from HTC’s One M8 DevEd Marshmallow RUU.
Swapped out stock recovery for 3.35.401.10 (WWE Marshmallow release).
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.
1.2.7
Swapped out recoveries for newer versions.
Swapped out ADB and Fastboot for a newer pack (thanks @LlabTooFeR) - now this Tool is fully M9 compatible and even flashes large RUU.zips.
1.2.6
Changed everything to M9 files and methods. I HOPE I didn't oversee anything. Please test carefully!
Added stock_recovery_1.32.401.8.img
Added TWRP Recovery 2.8.6.0 fixed version from Captain_Throwback SOURCE Post #2 Beta version
Added original HIMA Splash1 - S-OFF phones only!
Previous versions:
1.2.5
Added TWRP Recovery 2.8.5.2 from Captain_Throwback (All M8 devices)
Fixed Recovery Screenshot option (20)
1.2.4
Added newer RUU structure (2.0.16.2014 - from 4.16.1540.8 Dev Edition RUU)
Added Stock Recovery 4.16.401.10.img (WWE)
Changed the License and SFX texts again (Installer) - never happy with it.
1.2.3
Fixed some serious crap nobody reported. I just found out myself.
Added Stock Recovery 4.16.1540.8 (sorry still don't have the WWE recovery, but i guess they are identical)
Added TWRP 2.8.4.0 from the M8 tree of Dees_Troy.
1.2.2
Added Stock Recovery3.28.401.7
1.2.1
Added Microsoft's vcredist_x86_2008_SP1.exe to the installer because the ARUWizard is build on the x86 Visual Studio 2008 runtime. This resolves the "side-by-side configuration" error.
Added 3.28.401.6 stock recovery and splash
Added newer RUU structure (doesn't do any difference though, just keeping it up to date)
Added TWRP 2.8.0.3 (it still has slight issues with MTP which will be fixed soon but for now, this is good enough)
Changed a few lines in the script (minor, cosmetical stuff)
Updated the INFO PDF (option 24)
Known Issues:
Kernel Flashing needs fixing - can only work in fastboot now due to SELinux and related crap.
The partition Dumper is not correctly working, probably also due to SELinux.
Anyone used to like @squabbi's fully GUI based toolkit? He's picked it up on the M9 as well - maybe you like GUI better than commandline. Then head over here: http://forum.xda-developers.com/showpost.php?p=59949972&postcount=1

Flash Process Output:
There are a few steps in the flash process which are not really straightforward but i can maybe explain some of them here,so you can better understand what is happening:
sending 'zip' means: fastboot is sending zip over to client (here referred to as “remote”)
OKAY [ 2.839s] means status of sending was good. Transfer succeeded.
writing 'zip'... means the zip is being written to some location on the phone from the /temp location.
(bootloader) zip header checking... means the zip header is being checked for validity, see if it’s a real zip file and check for HTC’s signature, which often resides in the header part.
(bootloader) zip info parsing... means most likely a check on the file hashes in the zip (integrity check - if the zip is borked, it will fail here)
(bootloader) checking model ID... The bootloader checks if the android-info.txt contains the right MID. If it fails here you gotta swap out your model ID in the android-info.txt file.
(bootloader) checking custom ID... The bootloader checks if the android-info.txt contains the right CID. If it fails here you gotta swap out your Customer ID in the android-info.txt file.
(bootloader) start image[hboot] unzipping for pre-update check... means the bootloader is now unzipping the [hboot] image. This line will be repeated before every image that is to be flashed.
(bootloader) start image[hboot] flushing... means the bootlaoder is now beginning to flash the [hboot] image.
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100 these three lines read [RUU] for what mode fastboot is in, WP for “Write Partition” for what is currently being done in RUUmode, “hboot” is the name of the currently flashed partition, number xx is a percent stage of the write process.
(bootloader) ...... Successful means the final status is successful.
Now, before the [RUU]WP,hboot,xx line we often see another line reading [RUU]UZ,radio,50 for example. That reads RUUmode is currently unzipping the Radio.img and at stage 50 percent. UZ means UNZIP.
If you see something like this:
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking... means it is checking the signature of the partition if it matches the expexted signature stored in the hboot.
(bootloader) verified fail means the signature in the image did not meet expectations.
(bootloader) ..... Bypassed means the image got skipped because its got the wrong signature.
This has to be interpreted like this: there are multiple “SBL” images, to be exact: type 1 has 3 variants and type 2 has only one variant. Of type 1 (“SBL1-x”), two get skipped, one gets flashed (see my log above), of type two (“SBLx”) both get flashed. I believe, SBL 2 and 3 are device independent, but SBL1 has three variants, of which only one fits the current device. So, depending on the device you have, you will see either SBL1-1, SBL1-2 or SBL1-3 being flashed and the other two subtypes being skipped (bypassed).
The same goes for the "dzdata" images in the firmware package. They come in two or three size flavors (16, 32 and 64 GB) and resemble the file structure of the /data partition. Depending on your device and model, only the one with the right size gets flashed, the others skipped.
Important to understand: nearly all FAILED messages that do NOT occur while [RUU]WP (write partition) should be considered harmless. Only a FAIL during a write operation will most likely result in a damaged partition. All other fails will probably leave the original partition intact and thus the device can be rebooted. So far my understanding.
General hints for RUUmode zips
- Opening a zip is best done with 7zip as WinRAR and other zipping tools have lead to flash fails in the past.
- Choose low compression, higher compressions often fail. Pick "save" or "normal" to be safe, anything higher could cause the unzip in Bootloader to fail.
- Adding and Removing images is not a problem. The naming of the partition images seems flexible, yet if you encounter an “Error 23: parsing image fail” you need to rename the relevant image to something stock as not all names seem to be recognizable. The Hboot/Aboot determines the right partition from the header inside the image.
- Additional Dots in zip file names are known to have caused issues for a few people.
- Spaces in names are a no-go!
- Custom Recoveries can be added to those zips as well as custom kernels or hboots. In fact, if your phone is S-OFF, you can hex edit any partition and flash it. Be sure you know what you do though lol. I am just pointing out the possibilities. I am NOT saying it is safe!
- With S-ON, those zips only flash if everything is totally stock, from the android-info.txt being right up to all images being the correct versions for that update package and all having the right signatures. Reads: no custom messing with firmware zips for S-ON phones.
General hints for android-info.txt
- Use an Editor that doesn't mess up linebreaks like Windows Notepad does. Use Notepad++
- MID’s can be added one per line. Also supports wildcards i think e.g.: 71******, but i’m not sure.
- CID's can easily be added or removed- one per line, definetely supports wildcards (used by HTC in DevEd phone)
- Mainver line: should hold the version of the most current images, e.g if you combine older and newer files, add the MainVer from the newest. Format 2.24.401.1 (2= Base version always increases by 1 with each android base version rise, 24= Build version from HTC, 401= Regional/Customer identifier, 1= Revision of the HTC Build). This line is being written to the /misc Partition and is thought to identify the whole phone firm/soft version - its not meant to only describe firmware or base alone. Those parts always belong together. My opinion: run Firm/Soft always from the same or very close revisions (eg. 4.06.1540.2 or .3 are no issue, whereas firmware from 1.20 with a ROM from 4.06 can already cause the one or other malfunction).
- hboot pre-update line: usually says "3" but i have seen different numbers. I think they determine if hboot-preflash is required (when you get “Error 90 - please flush image again immediately” this is when the hboot/aboot needs to be flashed separately first and then the rest. If you encounter this, you need to run the flash command you just did, again.
- btype:1 not clear. [Item subject to change]
- aareport:1 Since HTC hboots/aboots, boot and recovery images come as "hboot_signedbyaa” / “aboot_signedbyaa” / “boot_signedbyaa” and “recovery_signedbyaa” i would read this as "aa" representing htc ("hboot signed by aa"). It could possibly mean check on the signature in hboot/aboot/boot/recovery - all of those also come in unsigned flavors - in HTC OTA’s, those are usually without the “_signedbyaa” but in the RUU, they are carrying a signature). So, aareport: 1 can just mean check on signature yes or no.
- Delcache means erase cache when rebooting. Simple. Some firmwares seem to need it, some don't. Line is not present in every android-info.txt. If you mess with a zip that contains the line, leave it active. This is also not referring to the Android OS cache partition. It refers to the separate Kernel and Recovery Cache. Sometimes, not deleting Kernel or Recovery Cache after flashing those leads to malfunctions. If the Kernel is launching and there is an older conflicting copy cached, the phone won’t boot past Kernel stage (before the bootanimation starts), if Recovery is conflicting with a cached copy (usually after flashing a new/different recovery), it will lead to the recovery not booting or malfunction (like aborting an ongoing ROM flash or not being able to execute other functions).
RUUmode:
is the mode used for RUU flashes by HTC. It allows a few more things than the normal fastboot. You recognize it by looking at the phone’s screen. It will be black, showing only a silver HTC logo and if a command is being active, a green progress bar. New M9 RUUMode now shows a percentage counter below the bar.
Recovery flash risk:
It's possible that the one brick i saw on the HTC Ville back in 2012 after flashing a hboot in recovery was caused by flashing it in recovery. I am rather sure that the method used by recovery zip’s to write an image file to NAND is not 100% bit correct and can cause trouble (This is the “DD” method). Due to the nature of this DD method, it can happen that single bits are flipped (no check on the written bit), which results in corruptions in the flashed partition. That can manifest in a full brick or just in faulty operation, in blocked partitions (unwriteable partitions) and many more annoying things. While a full brick isn't really that likely to happen (we had one on the Ville Forums within a year likely caused by DD writing a hboot), a corruption of some sort is a little more likely. Since all types of corruptions can lead to severe problems it is desirable to have a safer method. There is a command for recovery, “write_image”, employed by HTC but i haven’t worked out how to use it and how it actually works and whether or not it is safer. So i decided to just stay away from recovery zips for firmware flashing.
The zip flash executed in RUUmode also utilizes a different write technique and is safer (It most likely is the same as “write_image” in stock HTC OTA zips and their updater-script ).
Please be aware though that this remains an assumption.
Anyway, this is the reason why i don't offer recovery zips. Even though it is perfectly possible to flash partitions in live android (using "dd if=/somedir/yourhboot of=/dev/block/mmcblk0pXX") or recovery i prefer the fastboot method simply because i am sure it is safer.
Plus, since the advent of SELinux, Android 5.xx and up, it has become much harder to write to partitions using DD in live Android. There is much working-around-SELinux to do to actually get it working. A simple rooting of your Android doesn’t suffice anymore, besides S-OFF.
JTAG with a RIFF Box
Every device of these days has so-called jtag test-points. Basically, these are points on the mainboards, where a direct connection to the main chip can be established and then that chip can be read and written to with an external device. Sometimes, these testpoints are hidden (like they are normal contacts of the chip) and no direct visible gold points on the board. It always takes a while after a device is released until the jtag layout is fully discovered but once that is done, companies like multi-com.pl start manufacturing small boards with pins that can be pressed onto the mainboard, so no soldering to the device is required. Once such a board exists, the mainboard can be hooked to the RIFF box which can rewrite a dead chip from the outside.
As long as there is no such small board (called a "JIG") the phone can still be revived but it is necessary to solder hair-thin wires to the test-points. That is perfectly possible, Tecardo can do such a thing, but its not very good for the board and cannot be done very often. At some point the solder points will degrade so much that the board is garbage then.
In case you really brick your device, you can contact Tecardo here: http://forum.xda-developers.com/showthread.php?t=2116062
MID and CID
MID = Model Identification. It serves the purpose of identifying the Model of the phone. There usually are several different ones. The ModelID in android-info.txt is CaSeSenSiTivE!
Some limited Data is here: https://docs.google.com/spreadsheet...ShfYNFAfSe-imhhqtVfeMPVDA/edit#gid=1606643937
CID = Customer ID and describes, for which customer HTC made this phone. HTC has a few own CID's for its regional stores. Then certain carriers decide to have their own CID. Some carriers even have their own Model ID’s.
So, while the MID more like describes the hardware, the CID basically just describes the software set that comes delivered with it. Both get checked on when flashing in RUUmode. How to trick this system? Fairly easy. Just add your respective MID or CID to the android-info.txt file inside the ZIP or make your phone SuperCID (My Batch Tool can do that automatically - but remember: all this only works on S-OFF phones).
S-OFF:
S-OFF refers to the NAND’s security lock. S is for security and OFF means the security is switched off. The factory state HTC’s phones ship with is ON, except for the userdata partition, which of course is always unlocked.
The key for that lock is the most heavily guarded secret in HTC’s software vaults. It cannot be extracted, bought or otherwise obtained from them. There is no official way to unlock the NAND partitions (approximately similar to what Apple fans do when they “jailbreak” their products, although technically not quite as similar). While the HTC Dev Unlock (available through htcdev.com) just unlocks 3 partitions (Boot, Recovery, System), the “S-OFF” hack we use unlocks all partitions, thus enabling the flashing of custom, modified or other devices firmware. This is what you want for this thread and you can get it from the famous reverse engineers Jcase and Beaups over at: http://theroot.ninja/ or alternatively purchase a “Java Card” and learn how to work it, from chinese sellers on Alibaba, sometimes Ebay. Then there is a way to do it with an XTC Clip. But SunShine S-OFF is by far the safest and fairest method. You will only be charged if it works and the guys over at sunshine are really helpful.
A more detailed look at how S-OFF works
[Subject to change - not a definite explanation, just how I think it works]
In the Phones Firmware is a component that checks if certain partitions have a digital signature from HTC and deny write access if the signature is wrong or missing. The checking component is known to be the Security, which can be set to OFF. Then we say the phone is
S-OFF.
System, recovery and boot do not get signature checked at all once you “unlocked” your phone on htcdev.com. The other partitions however do get checked as long as Security flag is set to ON. Partition 3 is where the Security flag is located and maybe also the checking routine that checks the other partions digital signatures,
The S-ON state is resembled by a 3 in the fastboot command to switch security on. It is: fastboot oem writesecurflag 3. You do NOT want to do that while any custom firmware is running. Only after a full RUU that removes any modifications.
Why? For some partitions like the splash screen, it might not lead to a brick if you set security to ON while a custom splash is installed (then failing the signature check), as this partition is not vital for the boot process, it might just be skipped and give you an error message (I have never tried obviously). Other partitions however, boot critical partitions like Hboot/Aboot.... You guys have to understand that altering any of these partitions can be deadly to your phone if you happen to leave them altered when switching security back on.
Determining your “Firmware Version”
I believe there is some wrong info circulating the HTC Fora. People keep saying when running fastboot getvar all it will report the Firmware Version in the line “Version-Main”. This is not always true though. Fastboot getvar all or alternatively getvar mainver pulls a version it finds in the MISC partition and relies on that to be correctly updated. Source
So how does that version string get updated? It is being taken from the android-info.txt file in any firmware zip that you flashed. The last zip you flashed determines what will be reported by the getvar function. So if you mess around with Firmware.zip’s and RUU’s a lot, chances are, that the version reported there is not equivalent to what you are already running. Often the android-info.txt has version entries not appropriate for the actual zip contents, for compatibility reasons, because it wasn’t done properly or whatever. My zips usually have the correct MainVer though.
The "Firmware" as a concept like we use it on XDA does not exist in HTC's terms. HTC does NOT differentiate between the /System Partition (what we know as "the ROM") and the other 36 partitions. Hence, if you run getvar all or getvar mainver on a stock phone, it will report correctly. It does not go looking for a fictitious place where it would find a separate "Firmware" version. That place it is looking at is the Misc Partition and that’s correct as long as you haven’t messed with lots of different Firmware zips... So, if you happen to run a hybrid system with a ROM from one base and the other partition images from another base or multiple bases (like hboot from 1.27, radio from 4.06 and ROM from 3.62) the getvar function will report as "Version-Main" what it finds in /misc/, precisely the last zip you flashed determines the string put there.
Example: you flashed a radio with a RUUmode zip from Base X.YY but the android-info.txt is maybe still an old one because the dude who made the zip, just dropped the new radio into an old existing zip, the getvar function will later report that old version as your mainver.
To check your firmware: boot to bootloader and look at the combination of hboot version and radio version - if you didn't flash those separate, the combination will let you know what base you are on (each OTA and RUU has the radioversion in its name).
Finding out your firmware is a game of guesses and knowing what you did to your device and where you are coming from.
If totally lost, best thing is to reflash some clean stock package to be sure you are on the same level with all partitions.
Long story short: you better know what you do because finding out your firmware is going to be difficult if you don't.
Further reading​ OLD INFO REMOVED - NEEDS UPDATING
Some more useful threads with similar contents. Each has its own bits and pieces and re-wording that you don’t find here or understand here. So those threads might be helpful to you too.
Related/ “Like” stuff
-
- HTC ONE M9 Partition List

Does it work with TMOB101 CID too or only HTC xxx CID?

fearomoon said:
Does it work with TMOB101 CID too or only HTC xxx CID?
Click to expand...
Click to collapse
TMUS has had different Radio requirements on the M8. This is still open to investigation. My buddy @Behold_this is getting his M9 shortly though and he is TMUS. We will work it out in no time.
Other than that, you are aware you will need S-OFF to flash any non-TMUS firmware, right?

Ja but there is no soff yet for m9 isnt it

Sneakyghost said:
fearomoon said:
Does it work with TMOB101 CID too or only HTC xxx CID?
Click to expand...
Click to collapse
TMUS has had different Radio requirements on the M8. This is still open to investigation. My buddy @Behold_this is getting his M9 shortly though and he is TMUS. We will work it out in no time.
Other than that, you are aware you will need S-OFF to flash any non-TMUS firmware, right?
Click to expand...
Click to collapse
Hey guys, just chiming in here. That is actually not T-Mobile USA. Going by his CID, that is T-Mobile Deutschland. T-Mobile USA's CID is T-MOB010. The two CID are very similar so easy mistake to make. Unfortunately I have no access to any firmware for T-Mobile Deutschland.

fearomoon said:
Ja but there is no soff yet for m9 isnt it
Click to expand...
Click to collapse
I expect it to arrive shortly. SunShine has already tweeted they managed to find a vulnerability and create an exploit, so all they have to do now is automate the process enough for Eejits. Guess it won't be long.
Behold_this said:
Hey guys, just chiming in here. That is actually not T-Mobile USA. Going by his CID, that is T-Mobile Deutschland. T-Mobile USA's CID is T-MOB010. The two CID are very similar so easy mistake to make. Unfortunately I have no access to any firmware for T-Mobile Deutschland.
Click to expand...
Click to collapse
Oops! Thanks for the correction. Looking into my sheet reveals you are spot-on once again. Eagle Eye friend!
In this case, fearomoon, you can flash 401 (WWE) firmware no problem. TmoDE uses international frequencies for GSM, UMTS, LTE and WiFi. But you will still need S-OFF.

fearomoon said:
Ja but there is no soff yet for m9 isnt it
Click to expand...
Click to collapse
Apart from not having s-off at the moment i'd really recommend you to wait with firmware flashing until we made some testing (which also depends on when we will get s-off).

herwegan said:
Apart from not having s-off at the moment i'd really recommend you to wait with firmware flashing until we made some testing (which also depends on when we will get s-off).
Click to expand...
Click to collapse
Wise words!
@ everyone
Soon all aspects of hima development will take off. We just need to all practice a little patience and caution at the moment.

here's dev edition 1.32.617.30 firmware zip, no signature on it. was able to extract in linux from the ota and rezip
https://www.androidfilehost.com/?fid=95916177934550601

HolyAngel said:
here's dev edition 1.32.617.30 firmware zip, no signature on it. was able to extract in linux from the ota and rezip
https://www.androidfilehost.com/?fid=95916177934550601
Click to expand...
Click to collapse
thanks mate.
this is not adressed to @HolyAngel; he provides those files to us to be worked on. I just want to state it clear for all you guys right from the beginning:
Do NOT(!) post any other (modified) Firmware files in my thread meant for general public to be downloaded! Except you provide those files for me to work with them (not meant to be downloaded by public and declared like that!). Thank you.

I might need to add (because that statement wasn't entirely clear to me when i read it):
Files from the first post have undergone flash tests and can be considered reasonably safe. Files posted along the line of this thread can be anything. Only files moved to the first post and the Link Sheet can be considered safe.
Any other file - since it is public here in this thread - can of course be flashed but we do NOT take any blame for issues arising from flashing such.
There is an exception currently though: the files available for download on Post 1 at this time are "In Waiting" for being tested. There is no S-OFF yet. So, these files cannot be flashed and cannot be tested either. Once S-OFF is available to me or Herwegan or both of us, we will get on it and see if its possible and safe to flash stuff like we used to on the M7 and M8.
Things will slowly evolve.
Also, everybody scouring the forums for input is warmly invited to contribute knowledge. We all know things have changed with the M9. Stuff works slightly different now. To establish a "safe flashing" hub, we need to find out as much as possible.
I expect Error Codes to (maybe) change, methods to change, just basically anything we know from before is in question. The first page posts will be updated along the way. Up until now, most stuff has been taken from my M8 thread and is not automatically valid for the M9 just because it says it in this thread. Things WILL change. The posts WILL be altered. So come back and read occasionally.
Whenever there are important news to share about anything, we will also post about it and keep you updated. Not only change the first page
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
HolyAngel said:
here's dev edition 1.32.617.30 firmware zip, no signature on it. was able to extract in linux from the ota and rezip
https://www.androidfilehost.com/?fid=95916177934550601
Click to expand...
Click to collapse
@HolyAngel do you by chance have the base RUU.zip that goes before this OTA firmware? Its incomplete, so in order to create our FullWipe and NoWipe stuff for Dev, we'd need a complete base that can be updated by this OTA.
HTC ROM Downloads doesn't cater for M9 yet.

@Sneakyghost
I unfortunately do not have any RUU for dev edition, I wish I did :crying:
There's a ton of RUU's on ir-files but none for dev there either.. I do have stock system.emmc.win nand from 617.6 that is confirmed to work from @Nemeth27 to ota up to .30 with and what I just used myself to ota up not 10 minutes ago, but thats about it at the moment :/

HolyAngel said:
@Sneakyghost
I unfortunately do not have any RUU for dev edition, I wish I did :crying:
There's a ton of RUU's on ir-files but none for dev there either.. I do have stock system.emmc.win nand from 617.6 that is confirmed to work to ota up to .30 with and what I just used myself to ota up not 10 minutes ago, but thats about it at the moment :/
Click to expand...
Click to collapse
Yea ok thanks mate. That'll be cool for people just wanting to update the stock way but not for creating full RUU like firmware packages unfortunately, as you might have guessed

HolyAngel said:
@Sneakyghost
I unfortunately do not have any RUU for dev edition, I wish I did :crying:
There's a ton of RUU's on ir-files but none for dev there either.. I do have stock system.emmc.win nand from 617.6 that is confirmed to work from @Nemeth27 to ota up to .30 with and what I just used myself to ota up not 10 minutes ago, but thats about it at the moment :/
Click to expand...
Click to collapse
Sneakyghost said:
Yea ok thanks mate. That'll be cool for people just wanting to update the stock way but not for creating full RUU like firmware packages unfortunately, as you might have guessed
Click to expand...
Click to collapse
Not sure where I found it but I have the Developer Edition RUU.zip here >> https://www.androidfilehost.com/?fid=95916177934550733
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426167_signed.zip

617 isn't De as far as I know. At least I don't even have it in my list. Can you post the CID's from the RUU? I'm mobile the next few days.
[EDIT]
DE as in dev edition sorry didn't get that... Thought you meant DE as in country code.
So that's the new dev edition SKU then?

Sneakyghost said:
617 isn't De as far as I know. At least I don't even have it in my list. Can you post the CID's from the RUU? I'm mobile the next few days.
[EDIT]
DE as in dev edition sorry didn't get that... Thought you meant DE as in country code.
So that's the new dev edition SKU then?
Click to expand...
Click to collapse
Yup.
Developer edition ROMs for previous devices, like the M8, have been built off of the generic BrightstarUS World Wide English ROM base and used region/carrier code 1540, example:
BrightstarUS_WWE_4.16.1540.8 (from HTC One M8)
The developer edition ROM for the M9 is built off of the ATT North America ROM base and use region/carrier code 617, example:
ATT_NA_Gen_Unlock_1.32.617.30 (current HTC One M9 dev/unlocked)
There are many ROMs built off of the ATT_NA base. All Canadian ROMs for example, but for Dev edition, just remember:
1540=Brightstar Unlocked/Dev Edition (pre M9)
617=ATT North America Unlocked/Dev Edition (M9)
Anyway, that is the reason behind the change, but don't ever forget, you know HTC, sometimes they just change for change sake.?
Happy Easter everyone!