Database Info

[RESOLVED] Researching how to root - Official OTA_Supersonic_1.47.651.1-1.32.651.6

This has been resolved by using the flash lite exploit to gain root access allowing the misc partition to be flashed with a downgraded main version number which allows the old leaked Eng RUU we have to be flashed!
GUI for how to root
http://forum.xda-developers.com/showthread.php?t=720565
Old and Outdated information from the Original Post listed below for historical purposes ONLY
Who is Affected: If you've flashed the official OTA update on top of a non rooted ROM or your new EVO comes loaded with it, right now it appears there is no way to obtain root...yet!
What is Patched by the OTA: Through the radio.img which the OTA flashes, it updates the Main Version in the bootloader preventing Toast's root methods from working. It also flashes back the stock recovery, removing our root access in recovery mode and ability to apply .zip files. And last of all, the OTA patches the exploit hole in /system/bin/hstools used for unrevoked1 root.
Successfully eliminating all released methods of obtaining root access.
Conclusion:
after going through all these methods with a great helpful member of the unrevoked team, joshua_, this was the final answer:
[22:34] <joeykrim> cant see to find a method to RUU the phone back down ... ive tried all the methods ive seen. any methods i missed?
[22:34] <joshua_> ok, looks like we are hosed then
[22:34] <joshua_> we have a few more tricks up our sleeve sooner or later
Future:
If you have any suggestions/ideas, please post. I might have missed a method.
We will work towards obtaining root for those with new EVOs that have the official OTA applied and those who applied the official OTA.
Details of the tested known root methods:
user debug PC36IMG.zip (toast part 1) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
eng build PC36IMG.zip (toast part 2) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
RUU_Supersonic_1.32.651.6 extracted rom.zip renamed to PC36IMG.zip - bootloader error - main version is older
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
Stock Recovery - Apply update.zip - clockwork recovery update.zip - E:failed to verify whole-file signature E:signature verification failed
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. partition with write access for non-root user and allows executing is /data/local . flash_image can't write to the partitions w/o being run with root permissions. chownto and chown of flash_image to user root - permission denied.
##786# - Reset - doesn't seem to effect much in the way of bootloader version ...
Modifying PC36IMG.zip - using a hex editor to attempt at changing the MainVer stored in the android-info.txt, if any bit changes, it seems to fail the validation by the bootloader.

I tried almost all of these after the OTA hit my wifes phone. No dice. Subscribed to further updates on this thread.

I created a PC36IMG.zip file which contained the .6 releases wimax image and the android-info.txt file from the new update. I was then able to successfully flash it with hboot by placing it in the root of the sdcard and doing a down volume power on boot. It found the pc36img.zip file, verified it, asked me if I wanted to flash it. When I selected yes, proceeded to do so. It then reported the flash as having been successful.
I can't tell if the flash actually worked because I don't know where to check the wimax version info...
I don't know if this worked because the phone doesn't care to check the MainVer when flashing just the wimax image or if it did it because I pulled a fast one with the android-info.txt file swap.
I extracted the wimax image from the RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe file.
I wonder if it would be possible to pull the same trick with the larger subset of images from the rooting pc36img.zip files. i.e. swap out the android-info.txt files...

frankenstein\ said:
I created a PC36IMG.zip file which contained the .6 releases wimax image and the android-info.txt file from the new update. I was then able to successfully flash it with hboot by placing it in the root of the sdcard and doing a down volume power on boot. It found the pc36img.zip file, verified it, asked me if I wanted to flash it. When I selected yes, proceeded to do so. It then reported the flash as having been successful.
I can't tell if the flash actually worked because I don't know where to check the wimax version info...
I don't know if this worked because the phone doesn't care to check the MainVer when flashing just the wimax image or if it did it because I pulled a fast one with the android-info.txt file swap.
I extracted the wimax image from the RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe file.
I wonder if it would be possible to pull the same trick with the larger subset of images from the rooting pc36img.zip files. i.e. swap out the android-info.txt files...
Click to expand...
Click to collapse
im guessing the only reason it allowed you to flash a PC36IMG.zip which wasn't HTC signed is because you're using the hboot from the eng build of the PC36IMG.zip which doesn't check for HTC signatures on the PC36IMG.zip file. Not sure if it looks at the MainVer or not ...
once you're on a stock hboot, the PC36IMG.zip file has to be signed by HTC in order to flash!

I think in order for this to be patched, the bootloader code needs to be disassembled between the two versions to find out what bytes were patched and then either remove the code that checks for HTC signing or find a way to circumvent it.
We had to do things like this when working with mach_kernel when we got ahold of the first developer build of OS X for Intel. It was a pain in the ass and took weeks before we cracked the kernel.
There is even more risk with this though since tampering with the bootloader can definitely permanently brick devices.

joeykrim said:
If you've flashed the official OTA update or your new EVO comes loaded with it, right now it appears there is no way to obtain root...yet!
after going through all these methods with a great helpful member of the unrevoked team, joshua_, this was the final answer:
[22:34] <joeykrim> cant see to find a method to RUU the phone back down ... ive tried all the methods ive seen. any methods i missed?
[22:34] <joshua_> ok, looks like we are hosed then
[22:34] <joshua_> we have a few more tricks up our sleeve sooner or later
If you have any suggestions/ideas, please post. I might have missed a method.
We will work towards obtaining root for those with new EVOs that have the official OTA applied and those who applied the official OTA.
Here are details of the tested methods:
user debug PC36IMG.zip (toast part 1) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
eng build PC36IMG.zip (toast part 2) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
RUU_Supersonic_1.32.651.6 extracted rom.zip renamed to PC36IMG.zip - bootlaoder error - main version is older
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe- Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
Stock Recovery - Apply update.zip - clockwork recovery update.zip - E:failed to verify whole-file signature E:signature verification failed
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. only partition with write access for non-root user and allows executing is /sqlite_stmt_journals . flash_image can't write to the partitions w/o being run with root permissions. another words, need root access to use flash_image
##786# - Reset - doesn't seem to effect much in the way of bootloader version ...
Click to expand...
Click to collapse
since my frien did the OTA update yesterday and "bricked" his phone i have been trying to fix the phone (i have access to bootloader so it seems to me that maybe, just maybe i can save the phone) anyways, i have been getting a lot of the same error messages anytime i try to update/load any stock rom via bootloader.
what my question is, is there a way to take a 1.47.651.1 rom/image and put it into an ruu? i have looked all over htc's website, but they don't even acknowlege the existence of the evo, at least not that i can find.

joeykrim said:
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. only partition with write access for non-root user and allows executing is /sqlite_stmt_journals . flash_image can't write to the partitions w/o being run with root permissions. another words, need root access to use flash_image
...
Click to expand...
Click to collapse
Just curious here, regarding the above step, if you had access to a phone that was already rooted, could you use your sdcard in that phone to copy the files into /data and then transfer the sdcard back to the unrooted phone to flash it then?

Sorry for the long multi quote, there are quite a few good ideas and I wanted to make sure I explored each of them as far as the original poster intended.
EtherealRemnant said:
I think in order for this to be patched, the bootloader code needs to be disassembled between the two versions to find out what bytes were patched and then either remove the code that checks for HTC signing or find a way to circumvent it.
Click to expand...
Click to collapse
interesting ... circumventing the HTC signature check would be perfect and essentially give us an eng build bootloader.
in the RUU.exe rom.zip files, the android-info.txt indicate the MainVer along with a separate hboot.img file. the official OTA didn't have an hboot.img file. It only had a radio.img file which must have updated the MainVer value.
Not sure where on the phone this MainVer value is stored? in the radio?
you're suggesting, compare the bootloader, which is obviously stored somewhere in radio.img as thats the only file being flashed thru the OTA which increments the bootloader version number, against an older radio.img to attempt and find which bytes were changed for the version number?
The radio.img files are all around 22mbs ... ugh
if we're able to find the change in version number on the radio.img, not sure how it would help in flashing over it?
i was kind of thinking down these lines...since the bootloader checks the version number of any file it attempts to flash, the version number is going to be the key.
if we're able to increment (or temp change) the main version number in the file being flashed w/o messing up the htc signature, that could work.
2002wrex said:
what my question is, is there a way to take a 1.47.651.1 rom/image and put it into an ruu?
Click to expand...
Click to collapse
i've heard this was often done back in the WinMo days but i haven't seen anything on this board regarding this approach. if you have any detailed information, we could def look into it!
unknown_owner said:
Just curious here, regarding the above step, if you had access to a phone that was already rooted, could you use your sdcard in that phone to copy the files into /data and then transfer the sdcard back to the unrooted phone to flash it then?
Click to expand...
Click to collapse
very clever concept!
i'm not 100% sure on all the different approaches in the suggestion, but here are the ones it prompted me to explore.
unfortunately, every time the /sdcard is mounted on the phone, its mounted as noexec, meaning no files located on the /sdcard can be executed like programs.
also the /sdcard is mounted with uid=1000 and gid=1015 meaning all files mounted on the /sdcard have their uid/gid overwrote so none of them are allowed root ownership.
without being able to "su" to root access, we aren't able to run any programs with root access.
trying to chownto flash_image to any reference file as root results in:
chownto flash_image /system/bin/chown
Can't change user/group to root!
chown root flash_image
Unable to chmod flash_image: Operation not permitted
if i missed the suggested approach, could you elaborate?

Oh boy...... I thought I was alone in this. I try everything I can and now gave up. Any one can rooted this new OTA please let me know. I really need to downgrade from this.

Made me think of a problem that happened with the Directivo a few years back...
ht t p://dealdatabase.com/forum/showthread.php?t=22154
I was looking around, trying to figure out some way to hack the hdvr2 w/o modifying the prom. I recalled something from the xbox-linux team's presentation for CCC, which was something close to "once you break the chain of trust, the box is forever compromised." I thought to myself: "self, if we can load one kernel via BASH_ENV, why can't we load a second kernel?"
Click to expand...
Click to collapse
So, is there a way we could compromise the kernel? If so, then...

Subscribed...
Not really interested in rooting until froyo is working, and I could really use the wifi fixes this OTA is supposed to offer, but I'll hold off installing it until we know it can eventually be rooted.

Mikesus said:
http://dealdatabase.com/forum/showthread.php?t=22154
So, is there a way we could compromise the kernel? If so, then...
Click to expand...
Click to collapse
i read thru the thread. im not clear on how they used BASH_ENV or any other method to load a 2nd kernel.
unfortunately, i think we have an extra layer of security that they dont. thanks HTC!
without nand unlocked on the kernel partition no data can be stored there including a 2nd kernel.
appreciate the link and info. perhaps the ideas or concepts will spur some innovation!

joeykrim said:
i've heard this was often done back in the WinMo days but i haven't seen anything on this board regarding this approach. if you have any detailed information, we could def look into it!
Click to expand...
Click to collapse
the thing about winmo ruu's (here's a topic i DO know well) is that they are always in a zip. you decompress the zip and have access to all the files. one of them will be the ruu, the rest are all the supporting files/images/rom. all of the android ruu's seem to come as on large exe that doesn't allow access to the files, it merely runs itself. in the winmo days if you got a rom with no ruu, and didn't want to flash from SD, you just took someone elses ruu and dumped the rom image in to the decompressed folder containing the ruu.
i appreciate the help joey, obviously you are busy with your own problems and a lot of people around here just throw you the old "SEARCH BUTTON" response. any help is greatly appreciated!

2002wrex said:
the thing about winmo ruu's (here's a topic i DO know well) is that they are always in a zip. you decompress the zip and have access to all the files. one of them will be the ruu, the rest are all the supporting files/images/rom. all of the android ruu's seem to come as on large exe that doesn't allow access to the files, it merely runs itself. in the winmo days if you got a rom with no ruu, and didn't want to flash from SD, you just took someone elses ruu and dumped the rom image in to the decompressed folder containing the ruu.
Click to expand...
Click to collapse
interesting again .. so the RUU .exe files for android, do have a payload stored in a rom.zip file which is dumped to a temp directory after the RUU .exe starts and before it finishes.
now, the rom.zip files have been pulled and posted in each of the two RUU .exe threads we currently have. these rom.zip files do contain all .img files which are flashed to the phone. the catch is though, just as the PC36IMG.zip files used in root, these rom.zip files seem to have a special HTC signature (checksum?) in their header.
if you open these rom.zip files from the RUU in winzip, it will error out, but using 7zip, they open just fine.
im new to HTC, this is my first HTC android phone and its almost been 4 weeks so this is as much as i know. it seems, if we're able to alter these rom.zip files either used in the RUU .exe or naming them PC36IMG.zip flashed thru the bootloader and the phone excepts them, we would be golden!
to help save you some searching and let you see what im talking about, here is the latest RUU rom.zip file
http://www.joeyconway.me/evo/stock/RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rom.zip

Subscribed, I was able to Order my EVO today so I will be watching for development. I pledge my donations to whoever is able to figure it out. I really appreciate the efforts of this community.

I second that pledge for donations! I, like many others here, updated while knowing that I probably shouldn't have. I knew better...

Subscribed.
Thanks for all the effort and work. I hope ya'll get it figured out.

dang, I just got my evo yesterday and got the update message so I thought it'd be ok to update it as I thought it might have been old.
Came home and was excited to do all my customization and tweaks, but w/ no prevail

So my local best buy will not give the phone to the customer without pushing the new OTA to it :/
Apparently all of the stores will be doing this per Sprint and HTC's request.

EtherealRemnant said:
So my local best buy will not give the phone to the customer without pushing the new OTA to it :/
Apparently all of the stores will be doing this per Sprint and HTC's request.
Click to expand...
Click to collapse
Try calling them ahead of time before picking it up and asking if you can just swing by and pick it up yourself and call Sprint to activate yourself. Tell them you are in a rush, make up a story, and see if they just let you pay for it and run.

Can anyone post a stock recovery img?

Thanks.......

If you have your RUU you can just extract it from that

EddyOS said:
If you have your RUU you can just extract it from that
Click to expand...
Click to collapse
What is RUU? Where do I get it?

http://forum.xda-developers.com/showthread.php?t=1074559

hah2110 said:
What is RUU? Where do I get it?
Click to expand...
Click to collapse
Unfortunately this shows you've done no research before flashing your phone. The RUU (ROM Upgrade Utility) is the stock ROM for your specific device. It's ALWAYS recommended to have it handy in case you ever need to restore your phone back to stock

I have nandroid backups, just never used the RUU. How do I extract from an Exe just an Img file?

1. Start the RUU. When you get to the first main page move it to the bottom of your screen so you can only see the title bar (otherwise it's always in front of everything)
2. Click Start>Run and type %temp%
3. Look for the newest folder in there. Within this is a ZIP file called 'rom' - open this with a decent program like 7-Zip
4. Extract the recovery file from it

Removing revolutionary

Does anyone know how to remove revolutionary and revert back to stock. Im running a HTC Senation xe? I get error code error 155 unknown error. Using the RUU

You mean the hboot? I would try to zip
Code:
hboot_8x60_1.18.0000_20110802_signedbyaa.nb0
android-info.txt
from
Code:
RUU_Pyramid_LE_HTC_Europe_1.73.401.4_Radio_10.58.9035.00U_10.15.9035.02_2_release_220036_signed
Rename the package to
Code:
PG58IMG.zip
and copy it into your storagecard root. Enter the bootloader. Follow the on screen instructions.
In case this won't work, change your CID to SuperCID or edit android-info.txt to allow your CID (but I guess you're on XE so CID shouldn't be a problem)

So what your saying is if the RUU.exe file doesnt work. rename it to PG58IMG.zip and put it on the sd card?

Ach, no, no. You need to extract the exe file.
The easiest method to do this is to run the exe and don't click "next" or whatever the installer is saying. Just keep the installer open and search your C:\ drive for rom.zip.
Extract the file as you would do with a normal archive.
Now you need to zip only this two files:
Code:
hboot_8x60_1.18.0000_20110802_signedbyaa.nb0
android-info.txt
Name the archive PG58IMG.zip

I cant seem to figure out how to do the first bit. Extracting the RUU from the exe archive?

I'll try to be a little more detailed
So when you start the installation RUU the program itself creates temporary files on your computer. One of those files is rom.zip. The problem is that the directory is generated randomly.
It's something like that:
Code:
C:\Users\localhost\AppData\Local\Temp\{88F1C5DF-C107-4939-9651-18615BAD254B}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip
(for Windows 7 and user name "localhost")
The problem is that the installation app removes those temporary files if you successfully flash the firmware, cancel the update or terminate the process. So I suggest that you run the exe and search the whole C:\ drive for a file called rom.zip. It contains the files you need to extract. It's not possible to extract the exe in any other method as far as I know.

maybe Im doing something wrong but I cant find the rom.zip file. Im running windows vista.

Try this:
Start the RUU exe file. When the Update program appears click on "View ReadMe".
If you got Office installed Word should popup.
Click on "File -> Save As" (or something similar on your PC). Check the directory on top. Please find attached the screenshot with shows where to find the path to rom.zip.

blountish said:
maybe Im doing something wrong but I cant find the rom.zip file. Im running windows visya.
Click to expand...
Click to collapse
just go here and follow the guide for s-on
http://forum.xda-developers.com/showthread.php?t=1192300
for you rom http://forum.xda-developers.com/showthread.php?t=1074559
only supercid if you want to unbrand the device. an xe doesnt need it
you can check your cid and chose your correct rom. (in terminal use fastboot getvar cid command).

I look for PG88IMG

Hello look for a link works for PG88IMG_based_on_RUU_Saga_HTC_Europe_1.28.401.1.zi p
Anyone can help me.
i find this but link not work
loveboatcaptain said:
and here it is...
based on the RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release
downloadlink: PG88IMG_based_on_RUU_Saga_HTC_Europe_1.28.401.1.zip
just rename it to "RG88IMG.zip" and put it on the root of your sd card.
then reboot into fastboot mode (bootloader) and the rest will be done automaticly.
you can extract that zip file to modify the system image to get root e.g.
search the forums to get it out how.
kind regards
Click to expand...
Click to collapse

Maybe try this. Not sure if it'll work
http://forum.xda-developers.com/showthread.php?t=1488672
Just scroll down a bit
Edit: forget to mention, maybe your zip-file already contains the pg88.. Thing you need
Sent from my Desire S using XDA App

Thanks for the reply but that's only radio and I need ROM a full install from sdcard And also does not need to do s-off

OP says you need pg88img.
That's not a ROM
Which ROM do you need? didn't searching the forum solve you're problem?
You have to state clearly what you want or need
Edit: Maybe that's what you need
http://forum.xda-developers.com/showthread.php?t=1002506
Sent from my Desire S using XDA App

Whatever may be the reason that you need this (?) here is how to get it yourself:
Download RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release from the sticky Stock ROMs thread.
Run the RUU on your PC.
On the first screen (do not press anything when it starts) open your Windows Explorer, browse to the C: drive and in the search field type rom.zip.
Wait for the search to complete and copy the rom.zip file to another loacation.
Close the RUU setup.
Rename the rom.zip (this is exactly what are you looking for) to PG88IMG.zip and copy to SDCard.

Yeah you are thinking about the rom.zip of the RUU which is renamed to that. So follow what amidabuddha said!

Thank you very much this is exactly what i look for.
thanks for all

[Q] Please help me step by step for a custom ROM?

Hi guys,
I really need help on this, and i am hoping very much someone can be patient with me as i try to install a custom ROM on my HTC Desire S.
The BIGGEST problem i am facing is getting command text correct in the command window, i am using Windows 7 home premium on a laptop, the previous posts i read and followed were all saying put this in the command and put that in the command but none of them were correct and my computer kept saying wrong!
I am currently at the stage where i have visited HTC Dev and i have sucessfully gone through the procedure for unlocking the bootloader, i found this difficult to do, command prompts they gave were wrong i had to change paths, and i was missing certain .dll files on my computer too, which HTC did not mention i would need, but here i am after days of messing about and trying all sorts of commands, with a unlocked bootloader, with S-ON and running a Vodafone stock rom of Gingerbread Android version 2.5.3.
My phone is Vodafone branded i wish to remove all of their branding and apps, and install a plain unbranded ROM.
However, i need step by step instruction, i can not do this from threads that say "follow this here (link to another thread) which then links to another and another, i ended up with i think 15 tabs in the browser open, with conflicting advice, conflicting information, mistakes, and a whole lot of jargon that i did not understand, so what i really am hoping for is firstly links to all the software or downloads that i will need first, direct link to the rom, the backup, and anything else, if anyone needs info from my phone to pinpoint a specific rom i am happy to give it, i do not mind another HTC rom as long as its plain with no carrier apps or branding on it, then once i have got all the downloads sorted out i can start from there.
Please help me out i have been at this for days and getting nothing except confused.
Many thanks! :good:

3324536
I have found this quite up to date guide which is very easy to follow, are the rom and all the downloads OK for a UK phone?
I have hboot 200. 0002 as well as S-ON so i believe its the same, i can follow this one quite easy is it ok to do??
Also, while flashing this rom and recovery image, should i have SDK tools open on my computer??
And another thing, i noticed while extracting the recovery image that it just says recovery, should i rename it to recovery.img or leave it as it is? Because the command prompts are saying "recovery.img" and not just "recovery"?????
Thanks.
http://forum.xda-developers.com/showthread.php?t=1525100

mickmick72 said:
I have found this quite up to date guide which is very easy to follow, are the rom and all the downloads OK for a UK phone?
I have hboot 200. 0002 as well as S-ON so i believe its the same, i can follow this one quite easy is it ok to do??
Also, while flashing this rom and recovery image, should i have SDK tools open on my computer??
And another thing, i noticed while extracting the recovery image that it just says recovery, should i rename it to recovery.img or leave it as it is? Because the command prompts are saying "recovery.img" and not just "recovery"?????
Thanks.
http://forum.xda-developers.com/showthread.php?t=1525100
Click to expand...
Click to collapse
First you need to get in Folder Options in your WIN 7 Control Panel.There's option in View tab called " Hide extension for known file types". Uncheck that option and click ok.Then you will see extensions for all files on you win 7.This will show you extension of recovery.Should be .img.
Then you can follow that guide.I used the same one.
You need to get newest recovery.There are TWRP and 4ext for HTC Desire S.They are up to date.Do a little search and read posts and info.
Check post about panels (Hitachi or Sony)http://forum.xda-developers.com/showthread.php?t=1943524.Again search for that in HTC Desire S forum here.When you check all of that you can try any custom ROM but always backup nandroid.
Little hint : If you want to start CMD window in any folder first open that folder hold SHIFT and right click on empty space.You will get command there named Open command window here.Click on that and you can work.
GL.If you need more help ask here again.

SKENER said:
First you need to get in Folder Options in your WIN 7 Control Panel.There's option in View tab called " Hide extension for known file types". Uncheck that option and click ok.Then you will see extensions for all files on you win 7.This will show you extension of recovery.Should be .img.
Then you can follow that guide.I used the same one.
You need to get newest recovery.There are TWRP and 4ext for HTC Desire S.They are up to date.Do a little search and read posts and info.
Check post about panels (Hitachi or Sony)http://forum.xda-developers.com/showthread.php?t=1943524.Again search for that in HTC Desire S forum here.When you check all of that you can try any custom ROM but always backup nandroid.
Little hint : If you want to start CMD window in any folder first open that folder hold SHIFT and right click on empty space.You will get command there named Open command window here.Click on that and you can work.
GL.If you need more help ask here again.
Click to expand...
Click to collapse
Thanks mate, i will do what you advise, good trick about opening command in a folder
I will ask if i get any questions then cheers

OK i have a question straight away, it says in the tutorial:
Copy the rom onto the SD card, then it says copy the boot.img onto the android C folder - SO -
Do i first extract the boot.img and copy it to the C android folder AND copy the same boot.img onto my SD card, as well as the meta info and other stuff?
OR do i copy the boot.img onto the C drive only, and copy everything else onto the SD card?
A little confused here on what to do.
Thanks for any help.

Copy the rom onto the SD card, then it says copy the boot.img onto the android C folder
Click to expand...
Click to collapse
You do exactly that. You place the rom into the sd card, and you copy the boot.img into the said folder.
This is because you are "unlock s-on", the recovery isn't able to flash the boot.img, so you have to do it manually.
Remember, even after you flash the rom, if you did not flash the boot.img the phone will NOT fully boot.
*also, the guide says to turn the phone off after flashing the rom and boot into the bootloader. I dont think this is necessary, you can just reboot the phone into bootloader from the recovery itself.

98623459
#Fear said:
You do exactly that. You place the rom into the sd card, and you copy the boot.img into the said folder.
This is because you are "unlock s-on", the recovery isn't able to flash the boot.img, so you have to do it manually.
Remember, even after you flash the rom, if you did not flash the boot.img the phone will NOT fully boot.
*also, the guide says to turn the phone off after flashing the rom and boot into the bootloader. I dont think this is necessary, you can just reboot the phone into bootloader from the recovery itself.
Click to expand...
Click to collapse
So, just to clarify, i copy the whole .zip onto the SD card (including boot.img) and then re copy the boot.img into my Android folder on the computer (i will then have boot.img on BOTH the SD card and the C Android folder, this is where i am getting confused, i intend to start flashing today sometime.
OK i am going to flash Reaper V.4 rom and 4EXT as recovery, if anyone has better suggestions on a safe rom please let me know i will flash that instead.
Thanks.

mickmick72 said:
So, just to clarify, i copy the whole .zip onto the SD card (including boot.img) and then re copy the boot.img into my Android folder on the computer (i will then have boot.img on BOTH the SD card and the C Android folder, this is where i am getting confused, i intend to start flashing today sometime.
OK i am going to flash Reaper V.4 rom and 4EXT as recovery, if anyone has better suggestions on a safe rom please let me know i will flash that instead.
Thanks.
Click to expand...
Click to collapse
You can try other roms when you try that.There's a lot of nice and smooth editions. First try reaper you have it now.
With S-ON you have to flash boot.img in fastboot after you install rom from recovery.That's why you need to copy it in android-tools folder.Whole zip goes on sd and you backup old rom from recovery, wipe everything except sd (wipe is recommended) and then install from zip in recovery.After that reboot in bootloader then flash boot.img from fastboot.Reboot and wait.Should be in in few min.No more then 10.Follow the guide.
GL

4325422
SKENER said:
You can try other roms when you try that.There's a lot of nice and smooth editions. First try reaper you have it now.
With S-ON you have to flash boot.img in fastboot after you install rom from recovery.That's why you need to copy it in android-tools folder.Whole zip goes on sd and you backup old rom from recovery, wipe everything except sd (wipe is recommended) and then install from zip in recovery.After that reboot in bootloader then flash boot.img from fastboot.Reboot and wait.Should be in in few min.No more then 10.Follow the guide.
GL
Click to expand...
Click to collapse
Any idea what i am doing wrong here? I do have recovery.img in my Android folder, but its not in the android tools folder, should i be putting it in the adt bundle folder rather than leaving it outside of it?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Michael>cd \Android
C:\Android>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Android>

Yes put the recovery.img inside the fastboot/adb folder

jmcclue said:
Yes put the recovery.img inside the fastboot/adb folder
Click to expand...
Click to collapse
OK going to try again, thanks!

Success!! And all the crap vodafone apps and branding have gone! I did run into problems but i sorted it out. Thanks very much for all the help here i will be installing new roms all the time
On this reaper rom, there is no app for google play store, would anyone know how to install it? Or how do i get to play store from this rom?
And no options for fastboot that i can see, so i may have a few problems installing other roms
Where can i see a list of all the roms i can download for the Desire S??
Thanks!!

mickmick72 said:
Success!! And all the crap vodafone apps and branding have gone! I did run into problems but i sorted it out. Thanks very much for all the help here i will be installing new roms all the time
On this reaper rom, there is no app for google play store, would anyone know how to install it? Or how do i get to play store from this rom?
And no options for fastboot that i can see, so i may have a few problems installing other roms
Where can i see a list of all the roms i can download for the Desire S??
Thanks!!
Click to expand...
Click to collapse
Flash gapps (google apps) in recovery and for everything else ul find below
http://forum.xda-developers.com/showthread.php?t=1146601

jmcclue said:
Flash gapps (google apps) in recovery and for everything else ul find below
http://forum.xda-developers.com/showthread.php?t=1146601
Click to expand...
Click to collapse
jmcclue means you need to download gapps for your android.That will be in zip and you install it through recovery just like rom.Most of custom rom require that step.Copy zip on SD,boot in recovery and flash from zip.Reboot and you will get google apps.
This guide is for HTC Desire S and you can find most of things you need but for roms follow Android Development in HTC Desire S on XDA.
GL

mickmick72 said:
And no options for fastboot that i can see, so i may have a few problems installing other roms
Click to expand...
Click to collapse
fastboot is controlled by the bootloader, the rom can't affect it in any way. The option "fast boot" in HTC Sense roms is something else, that sort of hibernates the phone instead of powering off, so the phone "boots fast".

Thanks guys i will go aheah and do these

SKENER said:
This guide is for HTC Desire S and you can find most of things you need but for roms follow Android Development in HTC Desire S on XDA.
GL
Click to expand...
Click to collapse
That link i posted also has all the roms in it