Changing phone image version - to solve 140 bootloader version error for hTC RUU - Android Software/Hacking General [Developers Only]

Not sure if anyeone has posted this before. I found a way (from china) to change the phone image version, in order to prevent the error 140: bootloader version error that would occur when installing an inappropriate version of hTC RUU. I made a flashable to do that automatically.
down_version-signed.zip:
will backup the misc partition to /sdcard/misc.img if not exist
change the phone image version to the content of /sdcard/new_region_version.txt if available, or *.1.*.*(format as original pattern) when it is not.
restore_version-signed.zip:
will restore /sdcard/misc.img to the phone.
Actually, this one is not necessary. Just to give you guys one more option.
Installation:
root your phone and install a custom recovery (eg. ClockworkMod) if you have not done that yet
save the zip file in sd card
save a new_region_version.txt in sd card if you want to set a specific region version
boot your phone in recovery mode
install zip from sdcard
reboot system
an example of new_region_version.txt
Code:
1.01.708.4
It will work for downgrading phone image version (*.*.*.*) and even changing the region version (*.*.*.*).
One more thing,
Please DO NOT install RUU over models!
For example, DO NOT install an Aria RUU on a Legend.
I'm pretty sure that will brick the phone.
update:
Currently the version pattern can only be *.**.***.*
Let me know if there is any others. I'll fix that.
Now it should work for all sort of version pattern, such as *.**.***.* ; *.**.****.* ; *.**.***.** ; etc...
down_version_r3: bug fixed - when new_region_version.txt contains invalid content, phone image version will become blank.
someone told me that he can install an Asia-TW Aria RUU on an Optus-AU Aria, so it works on different region by setting RUU image version in /sdcard/new_region_version.txt

so will this change my canadian virgin legend to unbranded legend so i can install the official htc froyo for unbranded phones? can you specify a new CID that the phone will have?

has anyone tried this?
what happens, if i don´t put a new_region_version.txt on sd card?

nikst4 said:
has anyone tried this?
what happens, if i don´t put a new_region_version.txt on sd card?
Click to expand...
Click to collapse
According to the first message, if there is no new_region_version.txt, the tool will restore the original pattern.

ok, than I understood this right.
would be best option i think.

Can't do anything with the zip archive.
Do I need to rename it update.zip (Well I try it didn't work) ?
Di I need to do something in particular ? like being root or something ?

hm, tried ,too, but i cant even get the bootloader started with the files on sd card.
all i get is the dam red triangle...

Your phones have to be rooted and have a custom recovery installed. Otherwise you won't be able to flash the zip file.
Sorry, I didn't make it clear.

I'm not sure which region is currently able to receive the froyo update. I presume that's WWE. For that region, the code would be 405. So you should put 1.01.405.1 in new_region_version.txt. Then flash the zip in your rooted Legend's custom recovery mode. After that, reboot your phone in Fastboot bootloader by either `adb reboot bootloader` or press volume down and power buttons at the same time and then select fastboot. When it shows "fastboot usb plugged", install any WWE version of Legend RUU that could be found in Shipped ROMs. If it succeed, you will have a stock unrooted WWE rom on your phone and ready to receive OTA.

it works
labadios you gem!
finally installed an RUU - the WWE Buzz 1.14 etc
first time without errors as well
cheers

just booted phone up - took a while at HTC screen and when it asked for my PIN touch screen wouldn't work :s
quite worried now - any comments gratefully appreciated.

Just wanted to say THANK YOU for finding this fix.
I had the issue of not being able to run the 2.27.651.6 RUU due to my boot loader being a newer version.
Once I applied your .zip, I was able to successfully run the RUU and get back to my stock image. I was using Fresh's 2.1 image which was great. But I needed to get back to stock as I'm planning to trade it in for an EVO!

thanks a lot for this patch, now i can use ruu setup

Which model is this for?..... Can I run it on my HTC magic???.....
I have the 140 error, too...

When flashing this zip file, I got this error:
E: Error in down_version
(status 256)
E: Failure at line 10:
run_program PACKAGE: down_version
Click to expand...
Click to collapse
What can I do now?>...

Dude you are AWESOME!!!!!! Thank you sooooo much.

B_C_M said:
When flashing this zip file, I got this error:
What can I do now?>...
Click to expand...
Click to collapse
I have exactly the same problem on my HTC desire haven't found a way to install a clean ruu on it..

B_C_M said:
When flashing this zip file, I got this error:
What can I do now?>...
Click to expand...
Click to collapse
For all those who get that error it seems the only way to flash this is with clockwork recovery does not work on amon ra. Thanks OP for this great find u saved my hero from being smashed with a hammer )

No longer works on cwm 4.0.1.4 on GSM Evo 3D:
Code:
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to Clockworkmod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.

same
waltibaba said:
No longer works on cwm 4.0.1.4 on GSM Evo 3D:
Code:
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to Clockworkmod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.
Click to expand...
Click to collapse
I get same error as this guy

Related

RUU Updates HTC: BE CAREFUL

--- Updated and simplified
Updates from HTC are randomly released for countries and regions. These Update may lock your phone. As of today, phones can be unlocked again by using the GOLDCARD approach. However, there is a much simpler way to prevent bad things from happening:
If you like flashing HTC roms and have no intention to lock your phone, follow these steps:
On the PC
1. Double Click the .exe from the update. Wait for the first window to appear (DO NOT CONNECT YOUR PHONE). Don't close the application but do not continue
2. Open explorer and navigate to the hidden directory:
Windows 7: \users\$username$\AppData\Local\Temp\... followed by something like ...\{2A3DF7FC-1693-4C53-8883-6CF09DED700D}\...
Vista: documents and settings\.....
3. You should find the install application files along with a file "Rom.zip" (40 to 90 Megs)
4. Extract the ROM.zip to your SDK Tools directory, where fastboot.exe resides
5. open command shell and navigate to your Tools directory (supposing SDK, adb and fastboot are installed)
On the Phone
6. Enter recovery console on phone (press "home" + then "on")
7. Do a nandroid backup
8. Select Wipe your phone
9. Hold "back" and select "reboot system" in recovery to enter Fastboot mode
On the PC
10. Type: "fastboot flash boot boot.img" .... wait to complete
11. Type: "fastboot flash system system.img" .... wait to complete
12. Type: "fastboot flash userdata userdata.img" .... wait to complete
13. [Optional] Type: "fastboot flash radio radio.img" .... wait to complete (note: some HTC radios locked windows mobile phones. I am not sure whether this applies for Android)
14. Reboot your phone
15. Keep the update if you like it, revert to backup via recovery and nandroid in case you don't
And sorry for any confusion caused...
Regards,
fde
Thanks a lot mate... I will try the official sense for my magic then using this method first =D...
Are you sure....
That this will work? I have made the RUU Flash: RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_Nordic_release_signed_NoDriver
And that resulted in:
HBOOT-1-33-0014
CPLD-12
RADIO-3-22-23-18
I don't understand what you are meaning about the Radio.img file.
And what about the HBOOT file?
Yes it works. Just verfied it aigain. What the RUU package does is:
1. Extract the application to a temp file
2. Use ADB to flash the ROM to your phone
By the approach described in the first post, the application unpacks itself into a temp directory. This allows you to access the ROM-File which is stored as ROM.zip or something similar. By moving only the vital Boot, System and Userdata, you avoid flashing your Recovery console or Bootloader (Hboot).
It implies of course, that you DO NOT continue with the RUU application as soon as the first window becomes visible. (I will adjust the above Tutorial and make it simpler).
Problem
But the problem is that I allready have flashed my phone, is this the way to revert is så I can root it again and put custom roms on it again?
same here
ZeaDK said:
But the problem is that I allready have flashed my phone, is this the way to revert is så I can root it again and put custom roms on it again?
Click to expand...
Click to collapse
I also want to know how I can flash new ROM since people said that my spl is perfected after upgrading
I was learned that we need to use goldcard method to root again.
In our case, any idea which ROM to use as we gotta use higher ROM?
Or are we able to gain root access without touching the existing ROM?
Now even cannot boot to recovery mode.
So stupid to upgrade it although the ROM is stable and fast but no root access sucks.
any help would be appreciated.
thanks,
thihaz
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
feicher said:
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
Click to expand...
Click to collapse
The problem with the goldcard method is that you lose the roms as well...
Sir, would you please let me know how to flashing engineering SPL, right now i have HBoot-1.76.007 which shipped with the Singapore HTC sense rom.
BTW: i don't care i will lose the rom or not.
Many thanks!
I flashed using RUU_Sapphire_HTC_Asia_WWE_2.16.707.3_SG_release_signed_NoDriver.exe with golden card, but got "check main rom verion" error msg.
then flashed using RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe with golden card, same error msg again.
I really have no idea how to flash back to engineering SPL, i'm stuck in Singapore HTC sense rom.
feicher said:
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
Click to expand...
Click to collapse
i got 1 rom.zip(11mb) & another one rom1.zip(89mb).
But both I also can't unzip. Any idea? Thanks.
radonsg said:
i got 1 rom.zip(11mb) & another one rom1.zip(89mb).
But both I also can't unzip. Any idea? Thanks.
Click to expand...
Click to collapse
I did this twice on a Swiss Update, which btw wasn't worth applying. Just by the Size it's rom1.zip.
Let me download the Singapore and see what I can do.... But then looking at the guys post it seems the second file in the post is what you need. Download this package and only flash boot, system and data in fastboot mode. (From Step 4. onward in the guide). Anyway I will have a look.
phygee said:
Sir, would you please let me know how to flashing engineering SPL, right now i have HBoot-1.76.007 which shipped with the Singapore HTC sense rom.
BTW: i don't care i will lose the rom or not.
Many thanks!
I flashed using RUU_Sapphire_HTC_Asia_WWE_2.16.707.3_SG_release_signed_NoDriver.exe with golden card, but got "check main rom verion" error msg.
then flashed using RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe with golden card, same error msg again.
I really have no idea how to flash back to engineering SPL, i'm stuck in Singapore HTC sense rom.
Click to expand...
Click to collapse
Please follow the GOLDCARD method. I am not a recovery expert. I try to be cautious and was lucky until now (so I never tried it myself, but it is reported to work). Sorry for that. If :No-Frost: knows of a better guide with regard to GOLDCARD, please post!
Regards,
fde
feicher said:
Please follow the GOLDCARD method. I am not a recovery expert. I try to be cautious and was lucky until now (so I never tried it myself, but it is reported to work). Sorry for that. If :No-Frost: knows of a better guide with regard to GOLDCARD, please post!
Regards,
fde
Click to expand...
Click to collapse
For now the only method I know is the goldcard one... But in my country, using the goldcard method, makes the magics lose the 3g, edge or any internet mobile connection... =(...
Be careful, by using this method you can not upgrade to Snese UI (example TW). The reason being system image in Sense UI is larger than the previous 1.5 ROM system image, so system partition needs to be re-sized, which the RUU update does it for you. Otherwise you are struck with failed system image flashing.
signiture verifiaction fail
I get a signiture verifiaction fail when trying to write the .img files using fastboot. Any suggestions?

*Root-safe* stock OTA 1.47.651.1 *incremental* update w/ radio+WiMAX

IMPORTANT: The process described in this post breaks WiMAX, so I have removed the download links, and I recommend that no one attempt it. Please see this thread for a way to get from the original stock everything all the way up to the latest rooted OTA with the latest radio+WiMAX firmwares without even needing adb.
~~~ remainder of this post retained for historical interest only ~~~
Background: I didn't want to flash a full /system partition to upgrade my EVO 4G from Flipz's rooted stock 1.32.651.6 ROM to the latest 1.47.651.1, and I feel better using a barely modified "official" update from Sprint/HTC, so here's what I did:
Allowed the phone to download the update from Sprint/HTC. (It downloads into /cache.)
Copied the update to my computer and unzipped it.
Edited the META_INF/com/google/android/updater-script. (See below for a diff.)
Removed the recovery.img from the firmware.zip. (I don't want to go back to a stock recovery.)
Deleted the patch files for Sprint_Qik.apk and Sprint_TV.apk, since I've deleted those apps from my phone.
Edited the /system/build.prop file on the phone to remove the line that Flipz added at the bottom, thus restoring it to its stock condition (sha1=ee40d5143cf1089af2575045a9db9061f0d0dca9).
Zipped the update back up and signed it.
Download the update here:
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip
(md5=913c7594ca8ca94594a2c8e1ec9b5564)
Download the original build.prop file here:
build.prop-1.32.651.6
(md5=a29ab0ec25ad976bd12bc8bad5a97063)
Alternate: If you kept Sprint TV and Sprint Qik, use this update zip instead:
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(md5=410f57feeaebcf89c5497cd6e599a807)
Before you begin: You MUST be using a rooted stock 1.32.651.6 ROM, such as this one released by Flipz. Because this update is an incremental update, it cannot apply to any other ROM, even custom ROMs having the same base system version.
How to install this update:
Caution: There has been a report that updating using this method breaks the WiMAX. If that's true, it can only be because HTC must have added some new function to their recovery program that the custom recoveries don't have. It is recommended that you run a Nandroid backup in case you need to revert.
Download the two files linked above.
adb push OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip /sdcard/ (Or copy the update zip to your SD card by some other means.)
adb remount
adb push build.prop-1.32.651.6 /system/build.prop (See below for what to do if this step fails.)
adb reboot recovery
Run a Nandroid backup just in case.
Flash from the update zip and reboot.
The radio+WiMAX updates will install. This takes a while. Don't touch it. When it's finished, it will reboot on its own.
You'll find yourself in recovery one last time. Reboot.
It'll sit on the "4G" splash for a long time. Don't panic.
Once the home screen appears, go to Settings, About Phone, and verify that your "Software number" is 1.47.651.1 and your "Baseband version" is 2.05.00.06.10.
You may need to remove and re-add some home screen widgets.
If you're still using su and Superuser.apk from Flipz's stock rooted ROM, you will need to install the su-2.1-e-unsecure-signed.zip from this thread. It's a much, much newer version than the one Flipz included. It's an update zip, so install it via recovery.
Enjoy!
What to do if pushing build.prop fails:
This probably means you haven't unlocked NAND by flashing the engineering SPL. That's okay. Your custom recovery program probably supports adb while in recovery mode. If so, you can simply reboot the phone into recovery, perform step #4 from above, skip step #5, and continue from step #6.
For the curious, here's the diff of the updater-script from the stock update to mine: updater-script-1.47.651.1.diff
Troubleshooting
If you're getting an error that says assert failed: apply_patch_check, it means something about your system is different from a totally stock 1.32.651.6 system. Most likely you're running a custom ROM, not a rooted stock ROM, you've already applied the update, or you've installed some kind of hack like QuickBoot. Because this update is an incremental update, it can only be applied to a rooted (but otherwise unaltered) stock 1.32.651.6 ROM. Try flashing Flipz's stock rooted 1.32.651.6 ROM and then proceeding with the steps above under "How to install this update."
If Wireless Tether gets stuck when starting tethering, it probably means you still have the old and crusty su and Superuser.apk. Install the su-2.1-e-unsecure-signed.zip update mentioned above to get the latest set of superuser tools. Then Wi-Fi Tether should work fine.
Thank you. Will see if this fixes my broken 4G.
wsantiagow said:
Links Please?
Click to expand...
Click to collapse
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.
please add back in Qik and TV... let users delete that after? many people use those programs.
either way, nice work
Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?
blehzz said:
please add back in Qik and TV... let users delete that after? many people use those programs.
either way, nice work
Click to expand...
Click to collapse
Get the rootsafe-Sprint.zip instead. The only differences between it and the stock update are that it doesn't include the recovery image and it preserves setuid+setgid root for /system/xbin/su.
wsantiagow said:
Thank you. Will see if this fixes my broken 4G.
Click to expand...
Click to collapse
I'm assuming broken as in you ran the unrevoked update?
Any luck?
Also, OP:
Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.
wphend00 said:
Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?
Click to expand...
Click to collapse
It's exactly the update package furnished from Sprint over-the-air (the 30.2 MiB one), but with one line added to the updater script so that the update doesn't kill the setuid permissions on /system/xbin/su.
That means it changes everything Sprint changed in the latest update, including kernel, radio, WiMAX, and anything else.
So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?
whitslack said:
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.
Click to expand...
Click to collapse
..........
ViViDboarder said:
Also, OP:
Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.
Click to expand...
Click to collapse
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.
FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.
bjrmd said:
So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?
Click to expand...
Click to collapse
I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.
whitslack said:
I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.
Click to expand...
Click to collapse
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Thanks, btw!
whitslack said:
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.
FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.
Click to expand...
Click to collapse
Right... Well, here it scans and then turns off wimax and then turns it back on and keeps doing that. Working with joshua_ last night I got it to keep scanning... It never did get an IP though but the interface was definitely present. I could see it with netcfg from the adb shell.
I pointed joshua_ to this thread to see what he things of these patches. I had been trying to help him use my phone to debug this issue so I don't want to mess things up too much for him.
I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.
BTW I am now using a Fresh and not DC on my phone. And I am fully rooted(NAND unlocked) and have been able to run several other updates.zip without issue, currently using Clockwork MOD for recovery and not RA
rugedraw said:
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Thanks, btw!
Click to expand...
Click to collapse
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)
Badious said:
I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.
Click to expand...
Click to collapse
What recovery are you using? Amon RA 1.7.0.1 wouldn't work for me. It kept complaining about no signatures, even though I had signed the update. I used toast's recovery successfully.
If that's not the problem, then it can only be that some file on your phone is not identical to the version from the stock 1.32.651.6. Did you replace the /system/build.prop file with the stock one linked in the OP? In particular, this update will not apply against Flipz's stock rooted ROM unless you replace that file with the really stock one.
Yep downloaded the buildprop in the OP and copied that over via ADB successfully(checked softwar version and it shows stock buildprop info)
Let me try it one more time and see exactly what it is bawking about.
Ok. Error Reads as Such:
Verifying Current System....assert failed: apply_patch_check ("system/app/AccountandSyncSettings.apk" . TWO LONG SETS OF HEX NUMBERS[if you need them I can provide them])
E: Error in /sdcard/OTA..(name of full file)
(status 7)
Installation Aborted.
ERROR:
Verifying current system...
assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]
E:unknown command [56479c22c")]
E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(Status 7)
Installation aborted.
Can someone assist please, would like to get this new Radio OTA flashed....
Edit: Running DC 3.2.1 with Aloyisus Theme
whitslack said:
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)
Click to expand...
Click to collapse
Thanks for the quick response! I am running a rooted version of 1.32.651.6 and I've been waiting for something like this. So I should be OK using clockwork recovery to run this?
rugedraw said:
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Click to expand...
Click to collapse
You can put it on your SD card by any means available to you. The only requirement is that your recovery program does not care that it's signed by someone other than HTC.
TheMike1 said:
ERROR:
Verifying current system...
assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]
E:unknown command [56479c22c")]
E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
That can only mean that you're not using the stock ROM (w/ root added). This is an incremental update straight from the official sources with one slight tweak to preserve root access, so you must be using a stock system in order for it to apply.
Users of custom ROMs should be flashing new versions of those custom ROMs. The incremental upgrade path here will not work on custom ROMs.

[Q] Problem : hboot 1.17.0005 can't permit unlock bootloader and update phone....

Hello,
I didn't found the solution for my problem, so I post a new thread for explain it.
I have a french SFR HTC sensation.
My phone doesn't prurpose me OTA update, so I tried to update my phone (who was in 2.3.3 stock rom, and after did a nandroid backup) with this file :
RUU_Pyramid_Vodafone_FR_1.23.163.1_Radio_10.38.900 7.00P_10.11.9007.06_M3_release_190415_signed
http://www.filefactory.com/file/cfdd...415_signed.exe
(found here : http://forum.xda-developers.com/showthread.php?t=1074559)
My phone stay in 2.3.3 SFR Rom but with an old version of Hboot (1.17.0005)
With this version of Hboot, impossible to Unlock bootloader with revolutionary because Hboot is not compatible and impossible to flash recovery...
So, I tried to intall this file :
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.900 7.00U_10.51.9007.27_M3_release_198179_signed
http://www.filefactory.com/file/cfdd...179_signed.exe
(fond on the same post of precedent file)
But the installation stop to step 2 with an error (version not adapted for phone if I remeber...)
Just before try the first Update, I did a backup (nandroid backup) of my phone with clockworkmod. So, I have in my computer the original version of the phone in Clockworkmod folder. There is 7 files :
.android_secure.img
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
(1 more file in download folder : -2110140792 and 1 other file : .settings)
Problem : I can't install clockworkmod with this version of HBoot (or I don't found who to do that)
Is it possible to use those files without clockworkmod for put my phone in original configuration?
I try to flash boot.img with adb (flashboot flash boot d:boot.img, boot. img is the nandroid backup file), it's doesn't work (FAILED : remote: signature verify fail)
I try to flash recovery.img with adb (fastboot flash recovery recovery.img, (recovery. img is the nandroid backup file), it's doesn't work (FAILED : remote: signature verify fail)
So, I don't know what I can do more... Is there someone who can help me for put my phone in original version?
Thanks
(sorry for my english)
are your files compressed into a .zip? or are the saved as seperate files? make sure to compress your files into a .zip in order to flash.
im a little confused to what your trying to do exactly. are you trying to s-off but cant because of your software version?
sorry just a lot to read with files and links lol.
pushing your boot.img through adb wont do anything.
Hi,
I am not sure if this will work,but go to my signature and get 4EXT.
This can be installed from your home screen.
rddocke said:
are your files compressed into a .zip? or are the saved as seperate files?
Click to expand...
Click to collapse
It was a nandroid backup, so the files are in différents folders, but no compressed
rddocke said:
make sure to compress your files into a .zip in order to flash.
Click to expand...
Click to collapse
I'll try that, and back for say if it's OK
rddocke said:
im a little confused to what your trying to do exactly. are you trying to s-off but cant because of your software version?
Click to expand...
Click to collapse
I want update my phone, but I can't because i'm not S-OFF. So I try to S-OFF but I can't because my bootloader is in 1.17.0005 version...
rddocke said:
pushing your boot.img through adb wont do anything.
Click to expand...
Click to collapse
malybru said:
I am not sure if this will work,but go to my signature and get 4EXT.
This can be installed from your home screen.
Click to expand...
Click to collapse
Thanks
I'll try that this evening and say you if it's have an effect.
I tried your solutions :
malybru said:
I am not sure if this will work,but go to my signature and get 4EXT.
This can be installed from your home screen.
Click to expand...
Click to collapse
I tried but it's Doesn't work... In fact, it's normal because I'm not root... So I can't install busybox (need for use 4ext)
And I can't root my phone because I have 1.17.0005 S-ON version of bootloader... and that is the problem...
rddocke said:
make sure to compress your files into a .zip in order to flash.
Click to expand...
Click to collapse
I put those files in .zip file
I tried 2 solutions :
- First time : I created update.zip and put it in /sdcard, I reboot in recovery mode (stock recovery) : doesn't work, I have a error message when I click on "install updtade from SD card" : ------invalid command-------- write in yellow
- Second time : I created PG58IMG.zip and put it in /sdcard, Reboot in bootloader mode : Doesn't work too, nothing happened, the file seems not be reconize...
tdomikael said:
I tried but it's Doesn't work... In fact, it's normal because I'm not root
(I can't root my phone because I have 1.17.0005 S-ON version of bootloader... and that is the problem...)
Click to expand...
Click to collapse
Doh!
Sorry, I'm not sure how to help.
tdomikael said:
I tried your solutions :
I tried but it's Doesn't work... In fact, it's normal because I'm not root... So I can't install busybox (need for use 4ext)
And I can't root my phone because I have 1.17.0005 S-ON version of bootloader... and that is the problem...
I put those files in .zip file
I tried 2 solutions :
- First time : I created update.zip and put it in /sdcard, I reboot in recovery mode (stock recovery) : doesn't work, I have a error message when I click on "install updtade from SD card" : ------invalid command-------- write in yellow
- Second time : I created PG58IMG.zip and put it in /sdcard, Reboot in bootloader mode : Doesn't work too, nothing happened, the file seems not be reconize...
Click to expand...
Click to collapse
Ok when you compress you don't have to name it update.zip or pg58 file.
Just compress and place in you clockworkmod/backups then in recovery volume down to backup/restore and find your file you placed and select yes. That's how you restore your backup check back with me
Ima get you through this
rddocke said:
Just compress and place in you clockworkmod/backups then in recovery volume down to backup/restore and find your file you placed and select yes.
Click to expand...
Click to collapse
Unfortunaltly, I haven't got clockworkmod recovery on my phone. But only stock recovery (who seem doesn't work...)
Because I have the version 1.17.0005 of bootloader, I can't install it...
So, I there an other solution for use those files?
Or is there an other solution for install clockworkmod on my phone or root my phone??
Finaly, I found alone the solution for solve my problem.
My problem was :
- An old hboot version (1.17.0005) was installed on my phone after used an old vodafone's RUU (1.23.163.1) found on this post http://forum.xda-developers.com/showthread.php?t=1074559
- With 1.17.0005 hboot version, it was impossible to use revolutionary.io for tuen S-OFF the HTC Sensation
- Impossible to install an other version of Vodafone's RUU
- Impossible to install an other recovery
Solution :
- After a long time, I found on japanese site this official RUU (stock rom SFR/Vodafone FR 2.3.3) : RUU_Pyramid_Vodafone_FR_1.24.163.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190763_signed.exe
- I install it and after that, my hboot was in 1.17.0006 version!
- So, I can use revolutionnary for S-OFF my phone, root itand be super CID!
I wasted long time for found this RUU, so, I uploaded it on filefactory. For download it : RUU_Pyramid_Vodafone_FR_1.24.163.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190763_signed.exe
Hope it can help an other person!
tdomikael said:
Finaly, I found alone the solution for solve my problem.
My problem was :
- An old hboot version (1.17.0005) was installed on my phone after used an old vodafone's RUU (1.23.163.1) found on this post http://forum.xda-developers.com/showthread.php?t=1074559
- With 1.17.0005 hboot version, it was impossible to use revolutionary.io for tuen S-OFF the HTC Sensation
- Impossible to install an other version of Vodafone's RUU
- Impossible to install an other recovery
Solution :
- After a long time, I found on japanese site this official RUU (stock rom SFR/Vodafone FR 2.3.3) : RUU_Pyramid_Vodafone_FR_1.24.163.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190763_signed.exe
- I install it and after that, my hboot was in 1.17.0006 version!
- So, I can use revolutionnary for S-OFF my phone, root itand be super CID!
I wasted long time for found this RUU, so, I uploaded it on filefactory. For download it : RUU_Pyramid_Vodafone_FR_1.24.163.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190763_signed.exe
Hope it can help an other person!
Click to expand...
Click to collapse
Hi,
You should add it to THIS SITE ,if you want to help others.
malybru said:
Hi,
You should add it to THIS SITE ,if you want to help others.
Click to expand...
Click to collapse
Unfortunatly, I can't post in this thread because I haven't got 10 messages...
I tried send private message to Football but I don't know if he receive it...
test
why I can't post message in the other topic?
I can only post in this topic...
How to have 10 message if I can't post?
tdomikael said:
I can only post in this topic...
How to have 10 message if I can't post?
Click to expand...
Click to collapse
you already have 10 posts..now you can post in development section i guess
I seen that, my problem is solved...
Sorry for the up. If moderation want delete my last messages in this topic, no problem.
tdomikael said:
I can only post in this topic...
How to have 10 message if I can't post?
Click to expand...
Click to collapse
The script for permissions runs either every few hours or everyday. Wait till it updates your permissions.

[OTA]OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2_release_258562

Good evening/morning all
Just grabbed this new OTA from my One S so i thought i would make an appearance... And before anyone asks, yes - I am working on a ROM
OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2
Please note: This OTA takes you from 1.53.401.2 to 1.78.401.2
Change log from the updater service (rather vague):
System enhancment
Enjoy
P.S > Had no time to analyse the actual content but the OTA contains full firmware updates including HBoot & Radio.
Edit: Just noticed paul has done a repack of the base already.. may still come in handy for you devs out there
I knew you would come just like I asked for and others.
Thanks Lee.
If you can work on a T-Mobile ROM/EU ROM.
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Can't wait for some goodness from you!
Sent from my US HTC One S using Tapatalk 2
Dimson75 said:
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Click to expand...
Click to collapse
Certainly will be
Sent from my LeeDrOiD One Xtreme loaded HTC One X
woohoo !! about time you made an appearance !! I knew you was hanging around here somewhere
missed you since i left the sensation forums
I know this is probably a really stupid question but I'm going to ask anyway...
Can you actually install an OTA package on the phone somehow or is it just useful to take files out of it?
And the other question, my phone doesn't find any OTA updates anymore since I've 'tampered' with it so is there a way to make it find and install the OTA updates again?
Thanks
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
LeeDroid said:
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
Click to expand...
Click to collapse
The other thing is that when I try installing the stock RUU it's telling me it's for the wrong device or something like that, although it's definitelly the correct RUU.
Also, my phone is HTCDev unlocked but is still S-ON so if I install the OTA package usign CWM is it going to update the radio and the hboot (I thought it can't do that if you're S-ON)?
Thanks
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Did'nt work for me, wrong CID...
edit the info.txt to match your CID
azzledazzle said:
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Click to expand...
Click to collapse
Ok, maybe I'm not getting this right but I'm talking about two separate things:
Issue 1. My understanding is that I can install the OTA zip package using ClockworkMod, is that correct?
Issue 2. The RUU package won't install on my phone:
i) I have restored via ClockworkMod the nandroid image of the stock ROM (image that I've taken straight after I unlocked the boot loader and flashed a custom recovery, but before I rooted the phone). Then, I flashed the stock recovery image using fastboot. So now my phone should be back to stock.
ii) I then tried to install RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
When I do this, the RUU goes through right up to the step where it says 'Updating signatures' and then it stops saying 'unknown error' and it leaves my phone on that screen with black background and white HTC logo. Then, I have to hard boot and the phone starts up fine but in the state it was before the RUU - not even the user data is missing. To me this means that for some reason it doesn't even try to flash the RUU onto the phone but it stops when checking the signatures - I just can't understand why this is happening...
Can you help?
Thanks
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
azzledazzle said:
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
Click to expand...
Click to collapse
Sorry for my ignorance, but how do I initiate the installation of the OTA zip package using the stock recovery? As I said, I can't actually get it 'over the air' but I've just downloaded the zip package from this thread...
ok put the package on your sd card.
boot into fastboot, flash the stock recovery using the command ''fastboot flash recovery recovery.img'' (or recovery_signed.img) (also no quotes)
when thats done, select recovery from fastboot using volume button..
When you get a red ! press volume UP and power button, That will take you into stock recovery
Then look for the option, install from sd card or something like that
select your OTA package and BOOM !!! job done
Reflash CWM and away you go
Damn... I had no idea that you can actually get into the menu of the stock recovery... It all makes sense now...
me neither till about 3 days ago
I might not seem like a noob,,,,,but deep down i am
azzledazzle said:
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
Click to expand...
Click to collapse
I've tried that again and it actually breaks down when it gets to 'Checking Header...' and it exits with 'ERROR [155]: UNKNOWN ERROR". Maybe this is a bit more specific...
this is what i found for error 155
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Alternatively (in some cases) right click on the file and choose "Run as Administrator".
Or use the rom.zip -> PGXXIMG.zip flashing method.
Click to expand...
Click to collapse
I dont know if it will fail when flashing the rom.zip in CWM - usually you have to rename it to the model number and flash in fastboot, however you cant do this with S-ON

MY BRICKED HTC ONE A9 won't flash custom ROM via TWRP

Somebody should please help me, if I'm posting wrongly or in the wrong section, I do not know, I am new here and I need help. I have searched and read countless posts on here but I still can't get a solution.
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
I downloaded this officially from the HTC website
RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.10
when I run the file, it will start then disappear into thin air (I use windows 8.1 on my computer).
so I decided to go in the way of custom roms, phone is already S-OFF and Bootloader UNLOCKED. I installed adb & fastboot, I flashed TWRP and was able to boot into twrp recovery.
I downloaded the first custom rom (can't remember from where I downloaded that) and from the instructions, I was told to rename it to 2PQ9IMG.zip which I did and in attempt to flash it, got this error code,
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
Error flashng zip '/sdcard/2PQ9IMG.zip'
I had to go download another custom rom with the below file name
OTA_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.1-1.57.617.60_release_493556mv4q5xb4fbi8qvyk
and in attempt to install this as well, I got the errors below
Checking for MD5file...
Skipping MD5 check: no MD5 file found
N70QCT.01.000.004
E:unknown command [set_err_msg]
E3004: This package is for "htc_hiaeul" devices; this is a "htc_hiaewhl"
E:Updater process ended with ERROR=7
Error flashing zip '/sdcard/OTA....................
then this fourth rom again.
Sprint-A9-1.57.651.1
which I believed should work perfectly after a lot of research and in attempt to install this rom, I got this error
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
I am now totally fed up, I have been having a bad phone for 4 days now and I need my phone back ASAP. Somebody should please help me as a noob with the simplest well understood instructions, I will show gratitude.
mneynaire said:
Somebody should please help me, if I'm posting wrongly or in the wrong section, I do not know, I am new here and I need help. I have searched and read countless posts on here but I still can't get a solution.
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
I downloaded this officially from the HTC website
RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.10
when I run the file, it will start then disappear into thin air (I use windows 8.1 on my computer).
so I decided to go in the way of custom roms, phone is already S-OFF and Bootloader UNLOCKED. I installed adb & fastboot, I flashed TWRP and was able to boot into twrp recovery.
I downloaded the first custom rom (can't remember from where I downloaded that) and from the instructions, I was told to rename it to 2PQ9IMG.zip which I did and in attempt to flash it, got this error code,
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
Error flashng zip '/sdcard/2PQ9IMG.zip'
I had to go download another custom rom with the below file name
OTA_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.1-1.57.617.60_release_493556mv4q5xb4fbi8qvyk
and in attempt to install this as well, I got the errors below
Checking for MD5file...
Skipping MD5 check: no MD5 file found
N70QCT.01.000.004
E:unknown command [set_err_msg]
E3004: This package is for "htc_hiaeul" devices; this is a "htc_hiaewhl"
E:Updater process ended with ERROR=7
Error flashing zip '/sdcard/OTA....................
then this fourth rom again.
Sprint-A9-1.57.651.1
which I believed should work perfectly after a lot of research and in attempt to install this rom, I got this error
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
I am now totally fed up, I have been having a bad phone for 4 days now and I need my phone back ASAP. Somebody should please help me as a noob with the simplest well understood instructions, I will show gratitude.
Click to expand...
Click to collapse
File name starting with "OTA" are ota updates (patches) not full rom and can't be used to restore a phone. Renaming files "2PQ9IMG.zip" is used only when flashing RUU.zip or Firmware.zip in bootloader mode using the sdcard, not for flashing custom rom in TWRP. TWRP can't be used to flash RUU.zip or Firmware.zip. If your phone is a whl variant (Sprint) use the Sprint RUU or follow the guide to convert to Us Unlocked. Good information about RUU in the ruu collection thread at post #2. If you need more help tell us your CID, MID and version-main and what your goal is (re-flash the sprint RUU or convert to US Unlocked).
mneynaire said:
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
Click to expand...
Click to collapse
How are you rooted? If you can, boot into TWRP, pull your data off it, and then I'd say your easiest option is to start fresh using an RUU. Download and run the full RUU.exe for your Sprint phone following the instructions from the RUU thread.

Categories

Resources