Database Info

[Resolved] Downgrade Hboot 2.xxxxx of a Branded Desire S

Pardon me if there is already a thread for this. However, I couldn't find a helpful one. Please let me know if there is one.
I bought an HTC Desire with CID VODAP001. I have boatloader that says "Relocked" and S-ON and hboot is 2.xxxxxxx and it is running ICS 4.0.4 at the moment
I want to downgrade my hboot to 0.98.xxxx to gain S-Off. However, I don't know how exactly should I do that to downgrade my branded DS. I have RUU_Saga_Vodafone_UK_1.32.161.1_Radio_20.28b.30.0805U_38.03.02.15_M_release_179398_signed.exe with me. I also have extracted PG88IMG.Zip out of this RUU. I also know how to create a Goldcard.
However, I am unsure whether I should run RUU.exe (hboot 0.98.xxxx) directly or create a Goldcard and put that PG88IMG.Zip in SD Card (remember my phone is S-ON) and boot into bootloader or would either of these methods will be wrong?
Please let me know. Help would much appreciated :good:
Cheers

1) Unlock again (via HtcDev)
2) Flash a Custom recovery (like 4EXT to have a root adb shell)
3) Reboot to recovery, connect to PC and use the misc_version (you can find it in any of the downgrade guides in the Index thread) Change the version to something below 1.32.161.1. For example 1.27.161.1
4) Reboot to bootloader and relock it (fastboot oem lock)
5) Run the RUU.exe while connected to the PC (you can do it the bootloader, just be sure that there is FASTBOOT USB written on the screen of the device)
6) When flashing is done wait for the OS to load, go to the Developer Settings and enable ADB Debugging. Disable the fastboot option in the Power Settings
7) Use Revolutionary
8) Download and install the 4EXT Recovery updater app. Use it to flash the latest touch version of the Recovery (trust me on this). You will need root for this, so do it after you flash a custom ROM
9) Do whatever you want with your freshly S-OFF'ed device

Re: Downgrade Hboot 2.xxxxx of a Branded Desire S
amidabuddha said:
1) Unlock again (via HtcDev)
2) Flash a Custom recovery (like 4EXT to have a root adb shell)
3) Reboot to recovery, connect to PC and use the misc_version (you can find it in any of the downgrade guides in the Index thread) Change the version to something below 1.32.161.1. For example 1.27.161.1
4) Reboot to bootloader and relock it (fastboot oem lock)
5) Run the RUU.exe while connected to the PC (you can do it the bootloader, just be sure that there is FASTBOOT USB written on the screen of the device)
6) When flashing is done wait for the OS to load, go to the Developer Settings and enable ADB Debugging. Disable the fastboot option in the Power Settings
7) Use Revolutionary
8) Download and install the 4EXT Recovery updater app. Use it to flash the latest touch version of the Recovery (trust me on this). You will need root for this, so do it after you flash a custom ROM
9) Do whatever you want with your freshly S-OFF'ed device
Click to expand...
Click to collapse
Thanks for writing back mate. However, let me request you to elaborate step# 3 (Change the version to something below 1.32.161.1. For example 1.27.161.1
And step# 8) Download and install the 4EXT Recovery updater app from market?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

farazhassankhan said:
Thanks for writing back mate. However, let me request you to elaborate step# 3 (Change the version to something below 1.32.161.1. For example 1.27.161.1
Click to expand...
Click to collapse
The RUU will fail to flash on everything with higher that its own version. Which in your case is 1.32.161.1. So we have to trick the RUU to think that it is flashed over software with the same or lower version. This is achieved by the misc_version binary.
But in your case you are running the ICS software which has a version of 14.01.401.2 (11 symbols). The misc_version binary will replace only the symbols that you give it so for 1.32.161.1 it will replace 10 symbols. So the following will happen:
14.01.401.2
1.32.161.1
-------------
1.32.161.12 -> the resulting version will be higher! And the RUU will refuse to flash
Setting a lower number will produce a lower version (as per the example above it will be 1.27.161.12), the RUU will detect a lower version, although with more symbols and will flash successfully.
farazhassankhan said:
And step# 8) Download and install the 4EXT Recovery updater app from market?
Click to expand...
Click to collapse
http://4ext.net/ - it is at the top
Here is a direct link

farazhassankhan said:
Thanks for writing back mate. However, let me request you to elaborate step# 3 (Change the version to something below 1.32.161.1. For example 1.27.161.1
And step# 8) Download and install the 4EXT Recovery updater app from market?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1318919 see step 4 or just reed the whole thread carefully
u can download the app from here

Re: Downgrade Hboot 2.xxxxx of a Branded Desire S
amidabuddha said:
The RUU will fail to flash on everything with higher that its own version. Which in your case is 1.32.161.1. So we have to trick the RUU to think that it is flashed over software with the same or lower version. This is achieved by the misc_version binary.
But in your case you are running the ICS software which has a version of 14.01.401.2 (11 symbols). The misc_version binary will replace only the symbols that you give it so for 1.32.161.1 it will replace 10 symbols. So the following will happen:
14.01.401.2
1.32.161.1
-------------
1.32.161.12 -> the resulting version will be higher! And the RUU will refuse to flash
Setting a lower number will produce a lower version (as per the example above it will be 1.27.161.12), the RUU will detect a lower version, although with more symbols and will flash successfully.
http://4ext.net/ - it is at the top
Here is a direct link
Click to expand...
Click to collapse
Let me say thanks to you two for helping me out. I am gona try it as soon as I reach back to my town as I am in highway righr now. But seriously thanks a million. I'll report back if I get atuck somewhere. Cheerals
glacier1122 said:
http://forum.xda-developers.com/showthread.php?t=1318919 see step 4 or just reed the whole thread carefully
u can download the app from here
Click to expand...
Click to collapse
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

Guys this worked. However there is a bit of change in procedure. You have gota be booted while executing misc-ver commands instead of being in recovery.
Thanks any way guys

Re: Downgrade Hboot 2.xxxxx of a Branded Desire S
farazhassankhan said:
Guys this worked. However there is a bit of change in precedure. You have gota be booted normally while executing misc-ver commance instead of being recovery.
Thanks any way guys
Click to expand...
Click to collapse
Can you mark thread title as solved
We are what we repeatedly do; excellence, then, is not an act but a habit.
—Aristotle

jugg1es said:
Can you mark thread title as solved
We are what we repeatedly do; excellence, then, is not an act but a habit.
—Aristotle
Click to expand...
Click to collapse
Done
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

[GUIDE] Want to use AOSP-based ROMs but on hboot 2.14 and no working touchscreen?

All credits belong to MirGantrophy (if you wanna donate)
Thanks!
--------------------------------
Requirements:
1. must be s-off (see link)
2. must install this hboot 1.09 from this guide
3. ICS RUU file (see this link). In my case, I downloaded the earliest version for the Telstra RUU so I'm sure it's ICS.
4. working adb/fastboot files (this one worked for me)
5. twrp recovery (link). you can use the recent cwm I suppose but I haven't tested that.
steps:
1. open a command prompt/terminal
2. follow the steps in requirement 2
3.. boot into android
4. adb shell
5.. su
6. dd if=/dev/block/mmcblk0p23 of=/sdcard/p23
7. get out of adb shell (run exit twice)
8. adb pull /sdcard/p23
9. make a copy of p23
10. open p23 in a hex editor
11. look for a sequence that that start with 3.17 (complete format is 3.17.xxx.x. x are numbers)
12. replace 3.17.xxx.x with 1.00.000.0 and save the changes to a new file. In my case I saved it as p23mod.
13. adb push /sdcard/p23mod
14. adb shell
15. su
16. dd if=/sdcard/p23mod of=/dev/block/mmcblk0p23
17. get out of adb shell
18. execute RUU as let it run its course. Took about 10 minutes in my case.
19. install your chosen recovery (boot into fastboot and then fastboot flash recovery my-recovery-here.img)
20. repeat step2 (only if you want to remove the red text in the startup screen)
Notes:
1. These are the exact steps I followed to get it working on my phone.
2. steps 1 to 17 might be optional but the RUU install checks for previous version and I'm not sure if it'll go through if it finds a higher version is installed already. You can obviously experiment on your own.
3. A nice surprise after reinstalling stock ROM via RUU is that the "Tampered" text was removed and never appeared again even after I flash TWRP.
GOOD LUCK!

mrjayviper said:
20. repeat step1 (only if you want to remove the red text in the startup screen)
Click to expand...
Click to collapse
Shouldn't this be repeat step 2 not step 1? Otherwise, this looks great. Thanks to you for writing this up and to Grim also.

this actually worked? this is pretty much the same as [INFO] Downgrading firmware i tried using the old guide to downgrade hboot 1.14 and it didn't work and it didn't work for many others.
also if you have s-off you can run any ruu you want the checks do not matter and because of s-off you do not get the "Tampered" flag again so if you were s-off when you did this then this does not work.

DvineLord said:
this actually worked? this is pretty much the same as [INFO] Downgrading firmware i tried using the old guide to downgrade hboot 1.14 and it didn't work and it didn't work for many others.
also if you have s-off you can run any ruu you want the checks do not matter and because of s-off you do not get the "Tampered" flag again so if you were s-off when you did this then this does not work.
Click to expand...
Click to collapse
This is for s-off users who took the ota firmware update. I didn't know ruu didn't care about firmware versions if s-off so I told him to downgrade the stuff and then run the RUU to give the old firmware for working touchscreen on aosp ROMs

[Q] ROM question about installing

I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!

ps.christos said:
I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!
Click to expand...
Click to collapse
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita

timmaaa said:
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita
Click to expand...
Click to collapse
There are some changes of the planes and because of lack "playing" with my mobile i haven't reply you. So i desided to go for CyanogenMod 11.0 so instractions are:
" 1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU or later.
3.Flash a custom recovery (TWRP/CWM with SELinux capabilities).
4.Download latest nightly from http://download.cyanogenmod.org/?device=evita.
5.Locate 4.4 Gapps via a quick Google search.
6.Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
7.Reboot into recovery and install nightly and gapps."
Before the instraction i think i should root and unlock the bootloader, so i used "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" to unlock bootloader and root the phone. I have done this. I will (haven't do it yet) s-off and then flash custom recovery. Then it is the easy part i thing, (same as in every device, i have done it to htc desire).
So my question is am i rooted? Some apps like titanium backup and adfree gives me error, that is why i am thinging or i am not rooted or i have to "gain" su access through terminal. For flashing custome recovery i will use "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" and for s-off i will try to use this guide "[S-Off] Facepalm S-Off for HTC One XL" any easier suggestions about s-off??
So to make our life easier here is what i get form power button + volume down:
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot

Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita

timmaaa said:
Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita
Click to expand...
Click to collapse
I found what i did wrong so now i have root my mobile! The guide that you posted is very helpfull, thanks for that! One last question though (hopefully last) i still have to go s-off for flashing CyanogenMod 11.0 since it is in the installation procedure right?? Thanks again.

You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita

timmaaa said:
You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita
Click to expand...
Click to collapse
I have done everything exept s-off. So now what i get in the "info" screen is what i had before, but at the begging it says *** TAMPERED *** , root works as well. The thing is i tried s-off using this method "http://forum.xda-developers.com/showthread.php?t=2155071" and i had exactly what it says i mean both in screens and the 92 error, but i always was s-on when system boot to bootloader at the end. I tried more times and after a point i tried the toolkit, from that point error 92 turned to error 99 (unkown error). Now this holds for both ways that i try. Any ideas what i do wrong? By the way i made a backup before starting the whole procedure. Thanks again and sorry for asking, but everything else was solven by reading and i can not reach as many info about s-off as it was for root.

The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just show the so wanted s-off. I read somewhere that error 99 will turn to "normal error 92" after rebooting. So yesterday i did 3 reboots and felt to sleep and today i tried the same procedure and now i am s-off! Sorry for the nagging!!

timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok i need your help again, if it is possible. I try to flash cm11 rom and i got the:
"E:error executing updater binary in zip ..........
E: error installing the zip file ......."
So i did my research and i thing the problem is due to recovery, right??
In this threat "[Q&A][CM 10.1][4.2.2] CyanogenMod 10.1 Questions and Help thread"
you have said: " Originally Posted by timmaaa View Post
No you can't use TWRP 2.6, you need to use the unofficial modified version of TWRP 2.6.3.0 from our Original Android Development section."
The thing is i am using TWRP 2.6.3.0 downloaded from here: "http://forum.xda-developers.com/showthread.php?t=1677447" should i go for "http://forum.xda-developers.com/showthread.php?t=2558503"??????
some more details (bootloader details):
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
e-MMC-boot
Thank you very much.

Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita

timmaaa said:
Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita
Click to expand...
Click to collapse
Do you know if there might be a problem with compatibility?? I mean if i try to restore back up made with TWRP 2.5 when i have the unofficial modified TWRP 2.6.3.0??i bet there is a backwords compatibility, right?
thanks again!

From all reports I've seen, they're not compatible. But even if you didn't want to flash KitKat ROMs you should never use TWRP 2.5 because it's super buggy and will cause issues. I'd say just flash the unofficial TWRP 2.6.3.0 and install the KitKat ROM of your choice. If you need to go back to stock there are other ways apart from a backup you can do it.
Sent from my Evita

[GUIDE][TOOL]FUU/Firmware HTC One Mini

General Information
This Has Been Made To Help Those How Have No Clue What There Doing When Upgrading There Firmware Note And Want A One Click That Mimiks HTC RUU
FUU Definition
Firmware Update Utility
There are a few Firmware flashing threads and lots of zips and good and bad instructions. However, i noticed that many users asked about what they get when they flash what they download and also about how to flash it with S-OFF on various threads. This confusion has occasionally lead to people losing their custom kernels and custom recoveries and/or their SDcard partitions being unintentionally wiped.
I am writing this because i believe in "responsible" sharing. Since the full RUU's aren’t shared but only components (modified as well as unmodified) with often insufficient documentation, which in turn leads to a lot of confusion among the lesser informed users, i will try to catch some of that. I believe that sharing full RUU's would be a lot safer, as only those who actually know enough about it can disassemble them. RUU’s do always reassure users that there is a guaranteed and safe way to go back.
Prerequisites:​All you need is a Windows System with current drivers and maybe HTC Sync Manager installed, it is better to have HTC Sync uninstalled and only the drivers left. Just try if the FUU runs without HTC Sync. On my system, i am always greeted with an “Error 170" if i try to run the FUU on a booted Android - it doesn’t recognize the phone with ADB. This is a typical driver and/or ADB error. Solution here: make sure you have the latest driver suite. FailSafe way to get them is to install HTC Sync Manager (remove it if you don’t like it afterwards but leave the drivers in the sytem!).​
FUU How To​
[*]Download the firmware you want
[*]then run the installer
[*]install it to folder you want to any folder will do
[*]then run the tool and upgrade or downgrade your firmware
ZIP Flash HowTo​
Step-By-Step:​1. If device is booted into Android, reboot into bootloader by running:
Code:
adb reboot bootloader
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 Vol Down at the same time, when the screen and charging LED go dark immediately release Power but keep holding Vol Down until you see the bootloader screen. Notice: If the device refuses to reboot, you might need to hold it to a bright light with its light sensor. This is a very specific bug in the HTC ONE. The light trick always works.
2. Now place the Firmware_named_something.zip into your adb/fastboot folder
3. Now run:
Code:
fastboot oem rebootRUU
4. Followed by:
Code:
fastboot flash zip Firmware_named_something.zip
(replace "Firmware_named_something.zip" with the name of your zip)
5. Now check the console output. It should approximately look like this:
“flush" certainly means “Flash" so press the arrow up key on your keyboard and enter to run the flash command again without reboot...
Important: the flash process halts at around 75% to 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 before reboot to make sure it is safe to reboot! The bar will only fill up to 100% once you type the following command:
6.
Code:
fastboot reboot-bootloader
Error handling strategies:​IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It 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 (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image 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 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)​
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 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 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 successfull 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 “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: 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 with ADB and Fastboot.​
I always test all of these zips on my own device. But as always, flash at own risk. You're writing to critical parts of your phone. If anything goes wrong along the way, you might be bricked.
FUU Downloads (Windows only)​
Update: added Firmware For Sense 5.5 4.3 FUU
Download
MD5: 4cc050c25d2006600dfdbcc186789ef0
This FUU is Stock. Contents: Firmware from vrvr And So You should be good to Go. This package does wipes SDcard.​
Update: added Modifyed Hbbot No Red Text FUU
Download
MD5: 3918b9ca578f6f117a96e39f14873cd2
This FUU is modified. Contents: Firmware from vrvr And And Then Modifyed With No Red Text, So You should be good to Go. This package does wipes SDcard.​
Update: added Firmware For 4.4 KitKat FUU
Download
MD5: 701f1b7c07356e3fd7aaacf2e777d666
This FUU is stock. Contents: Firmware from The HTC OTA So You should be good to Go. This package does wipes SDcard.***NOTE*** The Boot Has Been Removed Because It May Cause You Some Problems And Result In Having To Reflash Your Rom​
Fastboot ZIP Downloads​
Update: added Firmware For 4.4 KitKat
Download
MD5: a0a05707fdbbdc7b7b162a7f6d76c4c8
This package is stock. Contents: Firmware from The HTC OTA So You should be good to Go. This package does Not wipes SDcard.***NOTE*** The Boot Has Been Removed Because It May Cause You Some Problems And Result In Having To Reflash Your Rom
Update: added Firmware For Sense 5.5 4.3
Download
MD5: 1f9f200cf468dc40ddd3c5415c639823
This package is stock. Contents: Firmware from vrvr And So You should be good to Go. This package does Not wipes SDcard.
Update: added Modifyed Hbbot No Red Text
Download
MD5: 2f5467f6fdcc854198a95d6ed7146c7f
This package is modified. Contents: Firmware from vrvr And And Then Modifyed With No Red Text, So You should be good to Go. This package does Not wipes SDcard.​Credits​Thank You Sneakyghost For The Tool And The Op
ramjet73 My mentor for HBOOT Modding
tr1gg3r84 - For Testing
vrvr For The OTA Witch I Modify Of off
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.​
XDA:DevDB Information
[GUIDE][TOOL]FUU/Firmware HTC One Mini, a Tool/Utility for the HTC One Mini
Contributors
Flashalot
Version Information
Status: Stable
Stable Release Date: 2014-02-23
Created 2014-02-23
Last Updated 2014-02-23

For me

Update for 4.4 Firmware has been released enjoy

Thanks for this I'll have a look

coming from stock 4.3 ... tried both methods to update to 4.4.2 ... Both create endless bootloop.
S-OFF, SuperCID ... tried both unlocked and locked bootloader

leungalv said:
coming from stock 4.3 ... tried both methods to update to 4.4.2 ... Both create endless bootloop.
S-OFF, SuperCID ... tried both unlocked and locked bootloader
Click to expand...
Click to collapse
Have you tried wiping cache and davik cache
Sent from a potato running Android

Flashalot said:
Have you tried wiping cache and davik cache
Sent from a potato running Android
Click to expand...
Click to collapse
Yup tried wiping cache & davik. Fixing the permissions. Nothing works. Just goes HTC -> black screen -> off -> HTC -> black screen -> off.
Re-flashing the 4.3 boot.img will get it to boot back into 4.3.

i have stock htc firmware - android 4.3, phone is rooted. unlocked and s-off.
what do i do to get back to 100% stock firmware, without root and stock recovery :/

kabalah89 said:
i have stock htc firmware - android 4.3, phone is rooted. unlocked and s-off.
what do i do to get back to 100% stock firmware, without root and stock recovery :/
Click to expand...
Click to collapse
Flash stock firmware and stock ROM
After if you want to go back to s-on run this command
fastboot oem writesecureflag 3
Please make sure you are in stock hboot if not you will be in a permanent brick
Sent from my SPH-L710 using Tapatalk

Hello,
I;ve tried this and got into a bootloop. i don't know what to do now?
The phone is ocked en not S-off
I know i must flash the RUU, but i cannot find a european RUU.
Please help?

A little confused
What are the requirements in order to perform a firmware update? Does the device need to be S-off or have super CID?
If I'm only wanting to update my hboot, do I just follow the FUU instruction and ignore the Zip Flash instructions? or do I need both?
Sorry, it's just a little unclear to me.
Thanks!
Nevermind - the answer is yes, you do need to be S-Off and THANK YOU! It worked perfectly!

PuffDaddy_d said:
What are the requirements in order to perform a firmware update? Does the device need to be S-off or have super CID?
If I'm only wanting to update my hboot, do I just follow the FUU instruction and ignore the Zip Flash instructions? or do I need both?
Sorry, it's just a little unclear to me.
Thanks!
Nevermind - the answer is yes, you do need to be S-Off and THANK YOU! It worked perfectly!
Click to expand...
Click to collapse
@PuffDaddy_d, can you help me:
1. what method did you use?
2. what firmware did you use to get hboot 2.21 to flash stock 4.4?
3. if you used the 1st method that wipe sdcard, how can you flash the Rom?
pls help, I really want to have stock KitKat on mine. thx.

S-off your device, flash hboot with fastboot command and then you can flash 4.4.2 with adb sideload from twrp recovery
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk

gramateas said:
S-off your device, flash hboot with fastboot command and then you can flash 4.4.2 with adb sideload from twrp recovery
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
thx @gramateas. you helped me with sideload method, but I really need a clear answers (as help) of my other 2 questions.

You can flash modded hboot 2.21
But first you must s-off your device
http://forum.xda-developers.com/showthread.php?t=2584810
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk

Hello, after using this FUU i got into a bootloop. Using fastboot i could install custom recovery, after unlocking the phone via HTCDEV. Now i am running 4.4.2 with S-on and working fine.
Sent from my HTC One mini using xda app-developers app

Zoeriva said:
Hello, after using this FUU i got into a bootloop. Using fastboot i could install custom recovery, after unlocking the phone via HTCDEV. Now i am running 4.4.2 with S-on and working fine.
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
whay hboot are you on?

I am on 2.21 hboot
Sent from my HTC One mini using xda app-developers app

gramateas said:
You can flash modded hboot 2.21
But first you must s-off your device
http://forum.xda-developers.com/showthread.php?t=2584810
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I tried to upgrade my hboot last night and this was what happened.
first I come with :
1. hboot 2.19
2. unlocked bootloader
3. twrp recovery
4. rooted stock 4.3
5. super cid 11111111
6. S-On
so, I tried to make S-off first. I used revone method. when I successfully S-off mine, I entered a bootloop (but when reverted to s-on, the bootloop was gone).
is it safe to continue flash the hboot when I got s-off and bootloop?
thx

edimonoarfa said:
I tried to upgrade my hboot last night and this was what happened.
first I come with :
1. hboot 2.19
2. unlocked bootloader
3. twrp recovery
4. rooted stock 4.3
5. super cid 11111111
6. S-On
so, I tried to make S-off first. I used revone method. when I successfully S-off mine, I entered a bootloop (but when reverted to s-on, the bootloop was gone).
is it safe to continue flash the hboot when I got s-off and bootloop?
thx
Click to expand...
Click to collapse
Well you could have as long as your on stock hboot then your OK but if not and your on a modded hboot you could brick
Also I'm looking in to see why every one is getting bootloops on firmware and I will be makeing no red text soon for Kitkat hboot
Sent from my SPH-L710 using Tapatalk

Problem during back to stock rom S4

Today I tried back from CyanogenMod 12 to stock rom in HTC ONE S.
One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101
During this procedure: https://translate.google.pl/translat...OMu&edit-text=
In this 6. point "6. Turn the phone back - no, it's not over yet, but the worst is behind us. We run suitable for our model and already RUU.exe normally carry out the procedure ROM Upgrade Utility - Using the instructions of the installer. ". I used RUU from this link https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing#list
Installer (RUU) show me error [140]: error bootloader version.
After I close installer phone was reboot and I see only bootloader - On the top I see TAMPERED RELOCKED Security Warning)
I can not run Android now
Could you help me? Please
Update> I unlock it using fastboot flash unlocktoken Unlock_code.bin, but what is next?

noiserobert said:
Today I tried back from CyanogenMod 12 to stock rom in HTC ONE S.
One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101
During this procedure: https://translate.google.pl/translat...OMu&edit-text=
In this 6. point "6. Turn the phone back - no, it's not over yet, but the worst is behind us. We run suitable for our model and already RUU.exe normally carry out the procedure ROM Upgrade Utility - Using the instructions of the installer. ". I used RUU from this link https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing#list
Installer (RUU) show me error [140]: error bootloader version.
After I close installer phone was reboot and I see only bootloader - On the top I see TAMPERED RELOCKED Security Warning)
I can not run Android now
Could you help me? Please
Update> I unlock it using fastboot flash unlocktoken Unlock_code.bin, but what is next?
Click to expand...
Click to collapse
to use a RUU your bootloader need be relocked
---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------
You can try rumrunner to S-OFF and after that try with Ruu

JavierG123 said:
You can try rumrunner to S-OFF and after that try with Ruu
Click to expand...
Click to collapse
I tried it but it not work. I think because it work only with stock rom
How back t stock rom with s-on?

noiserobert said:
I tried it but it not work. I think because it work only with stock rom
How back t stock rom with s-on?
Click to expand...
Click to collapse
Flash the proper RUU for your CID, you don't need S-Off for that.
Sent from nowhere over the air...

@thanks Rapier
I describe as I did it in detaliled:
1. Run fastboot oem readcid and fastboot getvar version-main and receive inforamtion Cid T-MOB101 3.16.111.11
2. Downlaod proper (??) RUU RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe . Is it proper for my device One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101?
3. Run fastboot oem lock
4. Run fastboot erase cache
5. Run RUU (from 1 point)
6. RUU inform me that will be install oddest (something like 2.38.111.xx - I dont remember all number) version then is on my ONE S (3.16.111.11), I accept it
7. RUU reboots my phone, and HTC starts and on blac background was logo htc
8. After few minutes RUU installer show me error [140]: error bootloader version.
9. I accept RUU and it close and my phone reboot to bootloader On the top I see TAMPERED RELOCKED Security Warning)
Where is wrong ?
Plese help me

I resolve it
1. Install a Viper 2.20
2. Use rumrunner.us to set your phone S-OFF

noiserobert said:
I resolve it
1. Install a Viper 2.20
2. Use rumrunner.us to set your phone S-OFF
Click to expand...
Click to collapse
And the RUU works?

I do not RUU because I did S-Off and it was fantastic
I go to Maximums HD (based on stock rom)

noiserobert said:
I do not RUU because I did S-Off and it was fantastic
I go to Maximums HD (based on stock rom)
Click to expand...
Click to collapse
but... for install Maximums HD you don't need S-OFF....

JavierG123 said:
but... for install Maximums HD you don't need S-OFF....
Click to expand...
Click to collapse
Of course you MUST have S-OFF to install Maxiums HD. Please read about it!

noiserobert said:
Of course you MUST have S-OFF to install Maxiums HD. Please read about it!
Click to expand...
Click to collapse
i'm sorry men. my bad

No problem
Only one problem is that not support beatsaudio

noiserobert said:
No problem
Only one problem is that not support beatsaudio
Click to expand...
Click to collapse
in android development or other section like that here in the forum... exist a flasheable zip to get on any device beats audio and other features...

I am wrong, this rom support BA! It is fantastic!