Database Info

[Updated 02-05-12] ClockworkMod Recovery v5.0.2.8 port for the HTC Chacha.

Clockworkmod Recovery for the HTC Chacha.
Please note I don't have the device and therefore can't give any support. I'm sorry.
You will find adlx.xda's cwm HERE [source]
My older, own CWM 4 port can be found HERE or from the attachments
02-05-12: Updated thread and dropped S-OFF tag.
15-04-12: adlx.xda has updated his 5.0.2.8.
05-02-12: adlx.xda has built a 5.0.2.8 CWM Recovery.
23-01-12: adlx.xda has built a 5.0.2.7 CWM Recovery.
24-07-11: Updated with huge CID list for ALL s-off users.
25-07-11: Updated with CWS__001.
14-10-11: Added original recovery update.zip
15-10-11: Fixed Error 6 bug for stock recovery
Code:
Put PH06img.zip on your sdcard, reboot into bootloader mode and flash CWM.
Quick tut to boot into bootloader mode:
Code:
Go to settings -> Power -> untick Fastboot
Turn off the phone
Hold VOL Down + Power for 5 seconds
If you are already rooted and want to flash the CWM recovery on your Chacha, you can also:
- Use Alex.C's 1 click recovery flasher,
- Use Goo Manager
Both applications are available for free on the Market.
-----
Update: Here is the stock recovery.
You can flash this in order to help you update to version 1.52, which can be found HERE
Code:
A quick how-to on upgrading version 1.33 to 1.52
Step 1: Install Stock Recovery
Step 2: Rename the OTA_blabla.zip into PH06IMG.zip and put it on your SDCard
Step 3: Flash the image by rebooting into bootloader
Step 4: Put CWM's PH06IMG.zip on your SDCard again
Step 5: Flash CWM by rebooting into bootloader.

Jagaroth has s-off and posted it, it seems to me he would be more than willing to help.

Got help from Geek78, which will order the XTC Clip.
Edit:
Nevermind, I found all I need thanks to Football from the RUU.
I am setting up my build environment (Read: Installing Linux and downloading 11gb of stuff) and will compile the first trial recovery, availible for all S-OFF users to try. For now, those only are people which got the device in an S-OFF state, or ordered an XTC clip, though I believe Alpharev will offer an option to get S-OFF for free. Time will tell!

Really? No single person? You just need to type out two commands. It won't do anything to your phone, I pinky-swear!

Do i have to be S-OFF for that?
When not, i can supply you with a screenshot in a few hours...

I will have ChaCha in next few days.
I run gsm service - got xtcclip and htxdongle also.
Will help as soon as i will get chachacha
Sent from my HTC Vision using Tapatalk

Got the result from XDA user knotdevel, thanks a lot for that. Now I have everything I need to work on a cwm port!

First CWM trial build is UP!
Please try this

Mikevhl said:
If you still have to root I recommend superoneclick, which can be found Here.
Click to expand...
Click to collapse
Did you get a root with a Superoneclick?

Grr.... I will have to wait untill the 26 to test it. I am on hollidays without my chacha...

osahiro said:
Did you get a root with a Superoneclick?
Click to expand...
Click to collapse
I don't have the device, and that root method only works for S-OFF users, I'm sorry

geek78 said:
Grr.... I will have to wait untill the 26 to test it. I am on hollidays without my chacha...
Click to expand...
Click to collapse
I'm very excited about this too! Can't wait for someone to try
IF it doesn't work (might be that the buttons are not configured right), you can just flash the 1.18 OTA (faster than full image dump) and your original recovery will be back, though I don't see any point of restoring to the stock recovery.. I'm also not sure if updating will remove your S-OFF, so you're best off just keeping this recovery build.
oh, I'm going on vacation Juli 28th (which is also my 17th birthday, hurray!), so I think I'll be able to read your response, but don't think I'll be able to build a new recovery before I'm back, if it's not perfect yet, that is

i tried to root with super one click and it doesnt work any other way to gain root im s-Off

Dubee24 said:
i tried to root with super one click and it doesnt work any other way to gain root im s-Off
Click to expand...
Click to collapse
z4root or gingerbreak, the last one works on s-off htc sensation devices so should work on the chacha as well.

Hi man, got a Chacha yesterday S-Off. I'm wiling to try that, but I couldn't root it yet. Also I'm totally new to HTC Phones (I come from Moto).
I've tried that:
C:\>fastboot.exe boot recovery-cwm-chacha.img
downloading 'boot.img'...
OKAY [ 1.795s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.802s
Duh? So I guess it means we can't try it like that? Gonna need to actually flash it ?
Anyone has the stock recovery.img I could flash back in case this one doesn't work?

adlx.xda said:
Gonna need to actually flash it ?
Click to expand...
Click to collapse
C:\>fastboot.exe flash recovery recovery.img
sending 'recovery' (3154 KB)...
OKAY [ 1.534s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.542s
So I tried to remotely fastboot flash a recovery and it failed too... Seems we can't.

How to S-OFF ChaCha ? ( I'm new to android phones )

saeidonline said:
How to S-OFF ChaCha ? ( I'm new to android phones )
Click to expand...
Click to collapse
Buy XTC Clip.

it won't work. we don't have engineer s-off.
Mikevhl said:
First trial build is up. Can any ROOTED S-OFF user flash it?
If you still have to root I recommend superoneclick, which can be found Here.
IF you have fastboot (I don't know if your phones support it), try from a command prompt
Code:
su
fastboot boot recovery-chacha.img
otherwise get the file on your phones sdcard, mount the sdcard on your phone and from either a command prompt or using a terminal emulator type in
Code:
su
flash_image recovery /sdcard/recovery-chacha.img
Thanks for trying! Unfortunately a recovery is all I can do without actually owning the device, so no custom roms or cyanogenmod port by me.. I'm sorry.
recovery-chacha.img can be found HERE
Quick thanks to the people who made this possible:
koush for his amazing work on clockworkmod recovery
TeamDouche for their awesome build system used for CyanogenMod
HTC for the device and update
Football for sharing the update
knotdevel for sharing information about the partition layout of the htc chacha.
Click to expand...
Click to collapse

Ah, thanks, I guess we would need an engineer HBOOT for that then, I believe seeing someone with an engineering hboot around.
The inability to use fastboot does not mean we can't flash recoveries. We could still flash_image from the device, but I don't know if that'll work with just ship s-off..
Another (rather painful, but working) method is a fake recovery, which I really would dislike to see, but might be a last resort.

[Q] Please help...Think i messed up BIG

Hi,
My phone freezes on the boot up screen (where T-mobile pops up) I know there are LOADS of threads on help for problems like that, but I think it's fair to say, I've tried quite a few of them (or at least looked to see if they could help me) but I'm still epically stuck I'll describe what i can in order, because I tried quite a few things..... -.-
I've got Htc desire S, from T-mobile UK
Hboot- 2.00.2002
I tried to root it to get pdroid, of course, found out that i needed to downgrade it to 0.98 for zergRush......got the "Hellions with BLUE flames" message so moved on to tacoroot. it was fine until i got permission denied at the last cmd code. (the posts on the thread suggested using zergRush if tacoroot did not work -.-)
this is the most problematic part i'm guessing. I gave up on those 2 and found this "guide-how-root-desire-s" on android forums, it uses revolutionary and cwm
But while i was trying out that, i found revolutionary-0.4pre4, which sounded alot easier therefore i alternated between both since the rev 0.4 made the guide a lot easier (took out half of part 1 and whole of part 2). I managed to finish, reboot.
At this point Hboot screen had ***locked*** on top and S-off, but it was still on 2.something
I realized I had a RUU left over from one of the previous guides....(RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed)
so thinking i had to use it (since i was still on hboot 2.00.something), I stuck my phone on fastboot USB and started RUU up. it ran smoothly and soon finished, I rebooted my phone to check if i was in 0.98, which i was,and happily booted up my phone. But i didn't notice S was ON. Next thing i know, I've frozen on the boot up screen, so i take the battery out, booted to Hboot.
Now i can't access recovery menu, factory reset, and i can't reboot since it freezes on "t-Mobile" screen.
Have i broken it for good? if not what can i do to fix it?
Sorry this was a bit wordy, i didn't know what was useful so i just put it all in (well as much as i can remember accurately)
-quick summary-
HTC desire S
T-mobile
Hboot: 2.00.2002 (now 0.98)
S-ON (now, managed to have it off at a point...)
zergRush > tacoroot > revolutionary + guide using cwm recovery > messing it all up cause i forgot to put rom in SD card + used RUU > mega stuck...
I'm completely new to this rooting and stuff, please help. Thanks
edit..
oh, i don't know if it'll help but on cmd (I've installed adb, fastboot correctly) adb commands do not work, and says something like "device not found" or "waiting for device". Fastboot DOES work when on fastboot USB only.
edit....
change hboot version listed here from 2.00.002 to 2.00.2002
carelessness

Have you tried changing your miscellaneous version then running the RUU again and then use revolutionary to gain S-OFF then flash any rom you want P.S >>>> FALLOUT is probably the best at the moment
Good luck.

Hi, Duty09
Thanks for the quick reply. how do i change my misc version?i can't "adb push" since my phone wont register with cmd.....adb devices show nothing. Do i stick it in root and flash from fastboot?
Thanks

Try following this and see if it will srt your issue out
http://forum.xda-developers.com/showthread.php?t=1525100

Since you are now back to old hboot can't you just run revolutionary again to gain s-off then flash a new Rom?
Sent from my HTC Desire S using XDA

Forcefire said:
Try following this and see if it will srt your issue out
http://forum.xda-developers.com/showthread.php?t=1525100
Click to expand...
Click to collapse
i dont think it'll work. htc desire S in not listed under htcdev. i know some people how been saying it can still work, but i can't find how...

Eclipse_Droid said:
Since you are now back to old hboot can't you just run revolutionary again to gain s-off then flash a new Rom?
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
I can't, because when i run revolutionary, it gives me "waiting for device". i've tried running it while in Fastboot USB, HBOOT USB PLUG, even during the frozen t-mobile screen..... is there another way of doing this?

iinock said:
i dont think it'll work. htc desire S in not listed under htcdev. i know some people how been saying it can still work, but i can't find how...
Click to expand...
Click to collapse
From what I recall, you just select "All Other Supported Models"

SimonTS said:
From what I recall, you just select "All Other Supported Models"
Click to expand...
Click to collapse
hi, just tried it and I'm stuck at step 8 at the cmd command "fastboot oem get_identifier_token" the result it gives me is
...
<bootloader> [ERR] command error!!!
OKAY [ 0.016s]
finished. total time: 0.016s
What can i do??

iinock said:
hi, just tried it and I'm stuck at step 8 at the cmd command "fastboot oem get_identifier_token" the result it gives me is
...
<bootloader> [ERR] command error!!!
OKAY [ 0.016s]
finished. total time: 0.016s
What can i do??
Click to expand...
Click to collapse
Did you type
/android/fastboot oem get_identifier_token
Click to expand...
Click to collapse
or
./fastboot oem get_identifier_token
Click to expand...
Click to collapse

SimonTS said:
Did you type
or
Click to expand...
Click to collapse
neither,
started up cmd, cd to file with adb, fastboot, and the other one. and typed in fastboot oem get_identifier_token
i've just tried both 2nd one gave me
'.' is not recognized as an internal or external command,
operable program or batch file.
the first one gave me
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.031s]
finished. total time: 0.031s
0.015s longer than fastboot oem get_identifier_token.......

Putting that into Google and getting many results, it looks like the HBOOT version needs to be spot-on for that command to be present. What version of HBOOT are you running?
Ignore that - just reread the thread. You did have v2.00.002, but you've changed it to v0.98 something?
Have a look here http://androidforums.com/desire-s-all-things-root/444571-unlock-using-htcdev-com.html
You need HBOOT v2.* upwards to use HTCDEV unlock method.

SimonTS said:
Putting that into Google and getting many results, it looks like the HBOOT version needs to be spot-on for that command to be present. What version of HBOOT are you running?
Click to expand...
Click to collapse
right now its 0.98.0000
it was 2.something, but after loads of attempts at tweaking, it changed. think it was the RUU i ran after revolutionary, guessing thats what messed it up as well. but that's just my blind guess...
problem is, i can't change it back, OR change it to anything

Try following this post to restore your 2.0...... HBOOT
http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
I'm no expert but the guides on this site are wicked and I'm learning so much just reading them.

Forcefire said:
Try following this post to restore your 2.0...... HBOOT
http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
I'm no expert but the guides on this site are wicked and I'm learning so much just reading them.
Click to expand...
Click to collapse
Thanks, will definitely try that when adb works again. but i can't do that yet since adb is not working with my phone, it wont show up on "adb devices" any commands given just get "waiting for device" as a reply

just found this thread that seemed to have a lot in common with my problem
http://forum.xda-developers.com/showthread.php?t=1412398
but i'm running in to problems with CID, tried to do it with gold card but still no luck (i think gold card is done properly...)

im going to try get gold card with a different SD card.
IF it does work what RUU should i use? what steps should i do after, if it goes smoothly? (trying to get my phone working again and if possible get pdroid...)
thanks

@iinock not sure if this will help but ive got a T-Mobile RUU if you need it or have you already tried this ?
and have you tried android flasher yet ?

iinock said:
im going to try get gold card with a different SD card.
IF it does work what RUU should i use? what steps should i do after, if it goes smoothly? (trying to get my phone working again and if possible get pdroid...)
thanks
Click to expand...
Click to collapse
This is my dropbox link that contains Android flasher with english HBOOT and a T-Mobile RUU. Try and flash the english HBOOT first via android flasher then try and run the RUU but if the HBOOT fails via android flasher then just try the T-Mobile RUU and see if that works if not i am fresh out of ideas mate and hope that some more experienced devs can help you.
Best of luck.
https://www.dropbox.com/sh/0i5xlxrwvut1olf/4Vr_YuH60y
MD5 for RUU - F0773C207F0A87D6FB3A2AB42F1FA637
MD5 for android flasher.rar - FAD89057F68363A1D134E93CE6429BFF

DuTY09 said:
This is my dropbox link that contains Android flasher with english HBOOT and a T-Mobile RUU. Try and flash the english HBOOT first via android flasher then try and run the RUU but if the HBOOT fails via android flasher then just try the T-Mobile RUU and see if that works if not i am fresh out of ideas mate and hope that some more experienced devs can help you.
Best of luck.
https://www.dropbox.com/sh/0i5xlxrwvut1olf/4Vr_YuH60y
MD5 for RUU - F0773C207F0A87D6FB3A2AB42F1FA637
MD5 for android flasher.rar - FAD89057F68363A1D134E93CE6429BFF
Click to expand...
Click to collapse
Thanks for the links.
I managed to fix my phone by using a different SD card as a gold card (used LG 1gb) then flashed OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210uj1q93xrps74xzje
now it works , got to try install rom and pdroid now
thanks for your help guys :good:

Help for HTC Sensation

Hello,
I have HTC Sensation Hboot Version is 1.17.1111, S-OFF I am trying to unlock bootloader but whenever i use fastboot command it shows:
... INFO[ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.018s
Then i used revolutionary tool and it made it S-OFF and showing Revolutionary on top now i want to root it and want to install CWM recovery on it but not able to unlock boot loader because it is not showing token please tell me what is wrong and what i have to done, its very important please..

You could try and instll 4Ext, and this should have been posten in General forum and not i Dev.

Why would you want to unlock your bootloader when you are S-Off? :S

Wrong section dude..
Sent from my powered HTC Sensation.
Press thanks if it helped

Look for the user-friendly firmware by Kohr-Ah.
Download the relevent one for the Android version you wish to install...
Remove phone battery
Put the PG58IMG.ZIP on your SD card (not in any folders)
Put SD card in phone, put battery back in
Hold vol down + power until bootloader screen comes up... Follow on-screen prompts
Flash a custom recovery (4ext preferred) using 4ext recovery updater or via ADB/Fastboot (put recovery.img in ADB folder, Start up CMD.exe ,CD to ADB folder eg cd c:/adb, then type fastboot flash recovery <nameofrecovery>.img
Tuts all over the place mate.
BTW This is the development section, the inappropriate location for a question like yours.
Regards,
Matty

from where i will get 4ext recovery?

efuzone said:
from where i will get 4ext recovery?
Click to expand...
Click to collapse
4Ext Recovery

efuzone said:
from where i will get 4ext recovery?
Click to expand...
Click to collapse
why don't you try these tools, these are very useful.
http://forum.xda-developers.com/showthread.php?t=1497404
http://forum.xda-developers.com/showthread.php?t=1668276

hello recovery done now how to root? when i press there root in kgs utility it close the window..

Hi, there's rooting method existing innis forum, sry icannot provide, don remember it. Jus search u could find. But a summary is so:
Download and install jopontubear from unlimited.io
Then the rest of the guide is there on their web site.
FIRSTLY READ N LEARN THE WIRE TRICK ON THE WEB SITE EXACTLY BEFORE STARTING, so thatcha could respond rapidly to ur phone.
I recommend u to make a backup of contents of ur sd card, or copy them to ur pc, i did none though.
Press thanks if i helped
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

efuzone said:
hello recovery done now how to root? when i press there root in kgs utility it close the window..
Click to expand...
Click to collapse
if you want just to root flash this from recovery
http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
done

[Q] ISO hox rogers 4.1.1 / 3.18 ruu..

Phone is the HTC One X, 4.1.1 / 3.17.6312 (evita )
Carrier is Rogers
Unlocked, s-on
Custom recovery installed ( openrecovery-twrp-2.5.0.0-evita.img)
And was rooted with (Superuser-3.2-RC3-arm-signed)
Phone seemed to be stable and working fine, But the ear speaker wasn't working ( couldn't hear callers unless I went into speaker mode )
Figured I would try a re-install to see if that would help.. But in the process I must have formatted to corrupted the OS...
After trying: C:\Android>fastboot flash system OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23
a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip the os won't boot... stays in HTC quietly brilliant screen..
I am able to get into fastboot / bootloader / recovery. I'm wondering if it's the OTA ... Perhaps a newer RUU ? The only one I can find is outdated and I can't install cause s-on..
RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe
Click to expand...
Click to collapse
Anyone know of a RUU for 3.17 ( rogers / evita )??? Or perhaps an alternative way to re-install the OS?
Cheers and Thanks.

Fleasus said:
Phone is the HTC One X, 4.1.1 / 3.17.6312 (evita )
Carrier is Rogers
Unlocked, s-on
Custom recovery installed ( openrecovery-twrp-2.5.0.0-evita.img)
And was rooted with (Superuser-3.2-RC3-arm-signed)
Phone seemed to be stable and working fine, But the ear speaker wasn't working ( couldn't hear callers unless I went into speaker mode )
Figured I would try a re-install to see if that would help.. But in the process I must have formatted to corrupted the OS...
After trying: C:\Android>fastboot flash system OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23
a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip the os won't boot... stays in HTC quietly brilliant screen..
I am able to get into fastboot / bootloader / recovery. I'm wondering if it's the OTA ... Perhaps a newer RUU ? The only one I can find is outdated and I can't install cause s-on..
Anyone know of a RUU for 3.17??? Or perhaps an alternative way to re-install the OS?
Cheers and Thanks.
Click to expand...
Click to collapse
did you flash the ota using stock recovery with a locked bootloader? I'm assuming you didnt supercid since youre s-on and with rogers.
to ota with s-on you must flash stock recovery and relock.

exad said:
did you flash the ota using stock recovery with a locked bootloader? I'm assuming you didnt supercid since youre s-on and with rogers.
to ota with s-on you must flash stock recovery and relock.
Click to expand...
Click to collapse
I did a factory reset, cleared cache, oem lock and ...
C:\Android>fastboot flash system OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.2
a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip
sending 'system' (650005 KB)...
OKAY [ 25.835s]
writing 'system'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 87.419s
Click to expand...
Click to collapse
hang's on HTC quietly brilliant screen,,,

Fleasus said:
I did a factory reset, cleared cache, oem lock and ...
hang's on HTC quietly brilliant screen,,,
Click to expand...
Click to collapse
Are you sure you have 3.18 software on your device? Looking at the output, it's not accepting because you're using the wrong RUU.
Find redpoints index thread in the dev section, it will have the correct RUU in there.
EDIT: Well... Looking at OP it seems you are using the wrong RUU. 1.94 isn't what you have on your phone.

Myrder said:
Are you sure you have 3.18 software on your device? Looking at the output, it's not accepting because you're using the wrong RUU.
Find redpoints index thread in the dev section, it will have the correct RUU in there.
EDIT: Well... Looking at OP it seems you are using the wrong RUU. 1.94 isn't what you have on your phone.
Click to expand...
Click to collapse
Thats exactly the issue... The only executable ruu I can find is the 1.94 version... I need 3.17. ( 3.18 was my typo in the title .oops ) and for some reason flashing the 3.17 OTA isn't working also.. I'm assuming cause it's an update and not the entire OS install..
I noticed when in TWRP recovery, if I reboot it asks if I'm sure cause there is no OS installed... The question is now, how the heck do I reinstall said os?
Thanks.

Yeah you can't fastboot it you have to flash it from within stock recovery.
Unlock.
Extract recovery.img (may also be called recovery_signed.img) from the ota zip
Fastboot flash recovery recovery.img
Relock.
Select recovery from bootloader.
When a picture comes on the screen, hold volume up and press power
Then select install from phone storage (not from sdcard)
Then select your ota.
It will flash successfully
Sent from my HTC One X using xda app-developers app

When in Android System Recovery <3e>
Device_CW_Install: Can't mount /data
"install from phone storage" gives the following error
Invalid operation... rebooting

Did you factory reset within bootloader at any point? This would have corrupted your sd card.
It's also possible you got a bad ota download.
Sent from my HTC One X using xda app-developers app

It's very possible I did a factory reset within bootloader... As for the OTA, it took nearly an hour to download it..not sure if teh host was slow or if it was my end .. Perhaps it corrupted on transfer?

Do i need to mount ( in twrp recovery ) and copy the OTA file onto the sdcard in order to "select install from phone storage"??

That's right. But you'll need to copy the file to your phone first, then unmount, then flash it.
Sent from my HTC One XL using xda premium

Should I place it in a specific folder?

No you can put it anywhere
Sent from my HTC One X using xda app-developers app

device_CM_Install: Can't mount /data
Invalid Operation
I don't even have an option to select the OTA file after selecting "install from phone storage"...straight to invalid Operation error.
ANy ideas how to fix the mount?

Attempted the Nocturnal guide for corrupted sd card.. same result.

Fleasus said:
Do i need to mount ( in twrp recovery ) and copy the OTA file onto the sdcard in order to "select install from phone storage"??
Click to expand...
Click to collapse
yes
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
Fleasus said:
Do i need to mount ( in twrp recovery ) and copy the OTA file onto the sdcard in order to "select install from phone storage"??
Click to expand...
Click to collapse
It doesnt need to be on the internal memory to select install from phone storage. It does need to be on there to select the OTA though.
Mount the SD card in twrp and format it. then copy the ota over

Formatted and trying to scan / repair sdcard... hopefully able to repair..

formatted sdcard in windows ( after mounting in twrp ) .. Not sure if that helped any... I was able to wipe / clear in twrp also... which seems to have remounted the /data, /system /cache and /sdcard partitions..
Now, if I can only get the OTA to flash....

C:\Android>fastboot flash zip OTA.zip
sending 'zip' (650005 KB)...
OKAY [ 25.760s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.618s
HOw does one get past the signature verify? ( phone is locked, and recovery.img was run prior to OTA rom )

Fleasus said:
C:\Android>fastboot flash zip OTA.zip
sending 'zip' (650005 KB)...
OKAY [ 25.760s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.618s
HOw does one get past the signature verify? ( phone is locked, and recovery.img was run prior to OTA rom )
Click to expand...
Click to collapse
You have to flash stock recovery before locking.
*edit* my bad, misread. do fastboot oem readcid
no wait.. Why are you fastboot flashing it? Flash it from within Stock recovery. "install from phone storage". Sorry -_- I am in an altered state of conciousness

[Q] Trying to upgrade HTC Desire S to HTC Android 4.0 (without Windows)

Thought I would try to upgrade Android from 2.3.5 to 4.0. HTC said it would work...
I've now got it stuck, though and can't move on. I do not own a Windows computer (I'm on Ubuntu).
What I did
I unlocked the phone using HTC's website tools. It uses adb, and you have to send some key to them and they generate an unlock code for you which you then do: fastboot flash unlocktoken Unlock_code.bin
I downloaded the RUU (RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068) from HTC.
Try 1: OpenRUU
I extracted the rom.zip file by using Wine, then searching on rom.zip. I moved it to ~/rom.zip
I then tried running the OpenRUU scripts which failed on attempting to flash (and failed on the automatic reflash attemtp, too):
sending 'zip' (410735 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
Try2: using hboot
I then tried with the hboot script. This is not for the "desire S" and has the wrong code in for the renamed rom.zip file. I then tried manually putting rom.zip, renamed as PG88IMG.zip into the root of the SD card as clearly summarised at (1)
I booted up into fastboot and the phone opened the zip file but then said "Wrong zipped image!".
Try3: using WinXP in VirtualBox
I then tried to run the RUU exe file in an XP VirtualBox VM. To do this I enabled USB devices for the phone (i.e. added filters for it both in fastboot and android modes), installed the stuff (HTC Sync) and tried running the RUU file.
It keeps saying "error 170 usb connection error". I've tried with the phone turned on (normally) and plugged in via USB, in charge only, Disk Drive and in USB debugging modes. I've also tried with the phone in fastboot mode. I always get this error.
...disable VirtualBox's USB2.0 support
Then it's able to connect to the phone. It ran all the way through the update process except that (a) there was never a progress indicator on the phone itself, (b) at the end it gave an 155 "image error". The recovery process then didn't really relate to anything I could see on the phone. The phone is again back in a2.3.5, so at least not bricked.
Trying to re-lock bootloader...
Then I thought that maybe the bootloader should be locked again (step 11 at (2)) - I had skipped this step before because I thought "I've just UNlocked it, why would I now want to RElock it?". But this won't work either! In fastboot mode, from a terminal, I type
Code:
$ fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Protocol error))
then the phone reboots itself, and it still shows unlocked. My fastboot screen (in case it's useful) says:
Code:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 20111, 15:22:13
HBOOT
Can anybody help?!
Links: (1), (2) : see pastebin dot com slash 1wKTF8Am (I am not allowed to post links here)

Rename rom.zip to PG88IMG.zip (not .jpg) then put on the root of ur sdcard (not in any folder) then boot into bootloader, it should find it

jmcclue said:
Rename rom.zip to PG88IMG.zip (not .jpg)
Click to expand...
Click to collapse
Doh! my bad - I had of course named it .zip not .jpg. (I have edited the post since). It WAS found by the phone, but error-ed after opening it, as described.

I flashed my RUU on Linux simply by doing:
Code:
fastboot oem lock
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip YOURRUUZIP.zip
fastboot flash zip YOURRUUZIP.zip
fastboot reboot
(yes, you flash it twice - it asks you 'please flush[sic] image again immediately' because it's upgrading your hboot)
obviously, replace YOURRUUZIP.zip with the zip file you extracted (e.g. PG88IMG.zip)
From the looks of your errors, though, it looks like your zip is simply corrupt...?

shinyblue said:
Doh! my bad - I had of course named it .zip not .jpg. (I have edited the post since). It WAS found by the phone, but error-ed after opening it, as described.
Click to expand...
Click to collapse
What error exactly? What does it say?

Aquous said:
I flashed my RUU on Linux simply by doing:
Code:
fastboot oem lock
Click to expand...
Click to collapse
As you'll see above - I can't do this, it errors about protocols and reboots the phone immediately!
Aquous said:
From the looks of your errors, though, it looks like your zip is simply corrupt...?
Click to expand...
Click to collapse
Could be but I don't think so. I've extracted it twice, once under Windows and once under Wine and the md5s are the same. I have no way of testing the integrity of the file I downloaded since htc don't apparently provide any hashes, but I would think that the .exe file probably checks its own integrity before running.
Thanks anyway! it looks like I need to re-lock it as a first step, maybe.

jmcclue said:
What error exactly? What does it say?
Click to expand...
Click to collapse
As posted: "Wrong zipped image!". Here's an (awful!) screenshot: (new members aren't allowed images...) i.imgur.com JqsG71r.png

shinyblue said:
As posted: "Wrong zipped image!". Here's an (awful!) screenshot: (new members aren't allowed images...) i.imgur.com JqsG71r.png
Click to expand...
Click to collapse
and is the PG88IMG.zip on the root of ur sdcard? im guessing not coz that green writing comes up every time u enter bootloader. make sure the PG88IMG.zip is NOT inside a folder
EDIT: heres a wee guide my mate wrote, its for the htc desire but its the exact same method.
PG88IMG Method

jmcclue said:
and is the PG88IMG.zip on the root of ur sdcard?
Click to expand...
Click to collapse
Yep. And the phone reads it all (takes it about 3 minutes to open, with the little vertical progress bar), then gives that error. The error goes away fast, so I had to make a video and freeze frame to get that picture.

shinyblue said:
Yep. And the phone reads it all (takes it about 3 minutes to open, with the little vertical progress bar), then gives that error. The error goes away fast, so I had to make a video and freeze frame to get that picture.
Click to expand...
Click to collapse
Oh rite. Must be corrupt download id say, coz it should work. When u downloaded the ruu, was there a md5 next to the download? If so, check it, make sure it matched, if not then try re download the ruu and try again.

Good suggestion. Just done that and the md5s are the same. It's
RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
from htcdev site.

shinyblue said:
Good suggestion. Just done that and the md5s are the same. It's
RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
from htcdev site.
Click to expand...
Click to collapse
Hmm strange one. I have that ruu on my laptop so il upload the PG88IMG tonight, i know it works coz i already used it. Only thing i can think why its not working is maybe something to do with taking the rom.zip from the ruu using ubuntu, i got no idea why tho.

jmcclue said:
Hmm strange one. I have that ruu on my laptop so il upload the PG88IMG tonight, i know it works coz i already used it. Only thing i can think why its not working is maybe something to do with taking the rom.zip from the ruu using ubuntu, i got no idea why tho.
Click to expand...
Click to collapse
u can't use auto install from sdcard with s-on, u can flash ruu by using fastboot commands

turekk said:
u can't use auto install from sdcard with s-on, u can flash ruu by using fastboot commands
Click to expand...
Click to collapse
Haha what a tit i am.
I know that u need to be s-off, cant believe i forgot, what a noob. I even made 16 hboots for the desire and 4ext recovery this way. Hope thats the last noobie moment for the year :sly:

shinyblue said:
As you'll see above - I can't do this, it errors about protocols and reboots the phone immediately!
Click to expand...
Click to collapse
That's probably because you're trying to run this through VirtualBox - does this also happen if you use adb from within Ubuntu rather than putting VirtualBox between your OS and your phone for no reason?

Aquous said:
That's probably because you're trying to run this through VirtualBox - does this also happen if you use adb from within Ubuntu rather than putting VirtualBox between your OS and your phone for no reason?
Click to expand...
Click to collapse
Maybe, but I think VirtualBox was working fine (e.g. HTC Sync worked).
As for "for no reason", I have read that the executable does quite a bit of stuff in terms of resetting various low level bits, and of course, being an HTC, there are hundreds of flash options, not just the usual handful.
I have been in touch with HTC directly (they told me initially the 4.0 upgrade was available), but they now say that this won't work with my phone.
I believe that the update is not accepted during the normal means because it is the WWE not the UK edition, and therefore the CID/MID do not match and are getting rejected because of S-ON.
Thing is, I don't want to risk bricking the phone by trying to get S-OFF and forcing the update because handsets are expensive! I've given up on this project for now...
Thanks to all for the help and advice.

shinyblue said:
As for "for no reason", I have read that the executable does quite a bit of stuff in terms of resetting various low level bits, and of course, being an HTC, there are hundreds of flash options, not just the usual handful.
Click to expand...
Click to collapse
Nope, all it does is this:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip YOURRUUZIP.zip
fastboot flash zip YOURRUUZIP.zip
fastboot reboot
This is what I did with my phone (I never ran the RUU) and it updated to ICS just fine.
I believe that the update is not accepted during the normal means because it is the WWE not the UK edition, and therefore the CID/MID do not match and are getting rejected because of S-ON.
Click to expand...
Click to collapse
My phone wasn't WWE either and that was no problem for me.

Aquous said:
This is what I did with my phone (I never ran the RUU) and it updated to ICS just fine.
My phone wasn't WWE either and that was no problem for me.
Click to expand...
Click to collapse
Was yours a Desire S? I was going on this article: http://android-revolution-hd.blogspot.co.uk/2013/06/do-we-really-need-s-off.html

shinyblue said:
Was yours a Desire S? I was going on this article: http://android-revolution-hd.blogspot.co.uk/2013/06/do-we-really-need-s-off.html
Click to expand...
Click to collapse
Yeah it was a DS. The article you link to even mentions that flashing a WWE RUU should always be possible: 'Everyone can de-brand his device easily by flashing a stock system image' (although, that sentence continues, that will make you unable to receive carrier OTAs, but that doesn't matter for our device)

Can I confirm that
Aquous said:
Code:
fastboot flash zip YOURRUUZIP.zip
Click to expand...
Click to collapse
means the whole RUU.zip as downloaded from HTC, or the rom.zip as extracted from running the .exe file within the downloaded RUU?
And also, http://www.htc1guru.com/2013/09/new-ruu-zips-posted/ says "You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first."
AFAICS the RUU I have downloaded has a different CID so won't work. Also my bootloader is unlocked (and the oem lock command fails, as mentioned above). (And I'm S-ON.)