Database Info

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english

same problem here, help is needed!

A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM

Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?

I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.

But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?

Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device

Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...

Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.

@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers

Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!

Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

[SOLVED] Restore Stock From Backup on PC/OTA update Error

Hi
The following attachment is what i have backed up on the pc after rooting the desire s originally and before flashing any custom rom.
How do i go about restoring this to the phone.
Is it as simple as wiping the sd card and placing all of it on the root of the sd card or to i have to bundle it into a winrar/7zip file to flash from recovery?
Currently on virtuous affinity, The best imo and have not changed anything else like hboot, still is S-off.
Would just like to keep the backup of basic out of the box stock backup on the phone and whatever custom i use.
Is it possible by the way for any over the air updates from HTC, if i return to stock, that it may remove root access?
Thanks in advance for any replies.

put the folder in sdcard/clockworkmod/backup, and restore the backup from the Backup/Restore menu in recovery. No need to wipe. Also, if yo changed the name of the folder, you'll get an MD5 error. You need to get 4EXT control app, flash 4EXT recovery and disable MD5 check to restore this.

userdesires said:
Is it possible by the way for any over the air updates from HTC, if i return to stock, that it may remove root access?
Click to expand...
Click to collapse
nope, i dont think its possible that OTA update will remove root access

is your phone is still "UNLOCKED"?

Unlocked as in rooted, yes.
HTC Desire S~Tapatalk

shrome99 said:
put the folder in sdcard/clockworkmod/backup, and restore the backup from the Backup/Restore menu in recovery. No need to wipe. Also, if yo changed the name of the folder, you'll get an MD5 error. You need to get 4EXT control app, flash 4EXT recovery and disable MD5 check to restore this.
Click to expand...
Click to collapse
Worked like a charm thank you.
However, after returning to stock i get a message about a system update from HTC but when it reboots to install, 4EXT starts up, tries to install the update and fails. Screenshot provided.
Any way around this?

Any ideas what it could be?
HTC Desire S~Tapatalk

You need stock HTC recovery to flash an update....... You can get it from any RUU, and flash it via fastboot. (I'm pretty this is the correct procedure to flash Stock, but still, wait for someone else to confirm)

shrome99 said:
You need stock HTC recovery to flash an update....... You can get it from any RUU, and flash it via fastboot. (I'm pretty this is the correct procedure to flash Stock, but still, wait for someone else to confirm)
Click to expand...
Click to collapse
So official updates ota are impossible with custom recovery? not sure about it
Sent from my Desire S using XDA App

shrome99 said:
You need stock HTC recovery to flash an update....... You can get it from any RUU, and flash it via fastboot. (I'm pretty this is the correct procedure to flash Stock, but still, wait for someone else to confirm)
Click to expand...
Click to collapse
I'll give it a try cheers.
HTC Desire S~Tapatalk

eyahl said:
So official updates ota are impossible with custom recovery? want sure about it
Sent from my Desire S using XDA App
Click to expand...
Click to collapse
Yup, I'm sure that an official OTA update on stock ROM is not possible to apply without stock HTC recovery. (unless you get it in a custom ROM of course)

Is there anything i can extract from an original stock rom which im looking at here which i found here http://forum.xda-developers.com/showpost.php?p=12269144&postcount=1
in which i can flash the stock recovery without flashing the entire rom?

Ok I flashed that ROM I linked to previously but still had 4ext afterwards. Preformed a full wipe, format sd and all the rest, backed up affinity backup to the PC so I could perform all these wipes and formats so I'm not sure what I did wrong or maybe I used the wrong ROM or method?
HTC Desire S~Tapatalk

Anyone ?
HTC Desire S~Tapatalk

Im stuck on the HTC boot screen after flashing this RUU RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed
The phone runs on meteor
SAGA PVT SHIP S-OFF
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
The RUU flashed successfully, but the hboot didnt change, what can i do from here please?

Flash eng hboot 0.98.2000 using hboot then the RUU. For You I suggest you make a goldcard first though..

Thanks so much for the reply
Ive been trying to flash that version of hboot by putting the zip on the root of the sdcard and booting with vol- and power, it says it performs the action but it doesnt change anything.
Ive tried using the hboot image itself with android flasher, that says this
error: device not found
security: off
finished. total time: 0.010s
sending 'hboot' (1024 KB)...
OKAY [ 0.196s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.028s]
finished. total time: 0.224s
rebooting into bootloader...
OKAY [ 0.200s]
finished. total time: 0.200s
< waiting for device >
rebooting...
finished. total time: 0.187s
But still the same version appears again.
Is there another way?
How can i create the goldcard if i cant boot into the phone?

Are you trying to get your phone back to S-ON, unrooted etc.?
If so, I used this to do it:
http://forum.xda-developers.com/showthread.php?t=1460713

Thanks, after all the guides i looked through i never found that one.
In the end ive used android flasher to flash clockwork recovery back to the phone.
Using a backup i made i tried to use that to restore but didnt work, some error formatting system i think.
Took out the sd card and formatted it, put a custom rom on their and placed it back into the phone.
Ran recovery and flashed the zip file, back up and running for now at least.
Stock can go to hell, im not messing with any RUU from now on.
Thanks to anyone that helped, appreciate it.

Thank god you got this fixed. BTW, if you do want stock ROMs, just wait for devs to optimize them, like lowveld's Hyperion and proxuser's Saga 3D. Both are MUCH faster than stock ROMs and have added tweaks.
I agree with your RUU decision, I myself never mess with such stuff. If i need to return my phone to stock for some reason, I'd restore my backup or use a Stock Pre Rooted ROM (won't really come in handy though, my warranty's gone this month )

Virtuous ROM: SuperCID and Firmware upgrade NOT needed?

The thread [GUIDE] A must read for those noobs who want to enjoy ICS states that ALL ICS roms need a firmware upgrade.
However, the installation instructions for the Virtuous ROM doesn't say anything at all about upgrading the firmware: http://www.virtuousrom.com/p/documentation.html
Which one is right?
Also, just to be on the safe side, is SuperCID needed?

The documentation page you linked is installation instructions for all Virtuous ROMs, so it's pretty generic. If you look at the description page for Virtuous Inquisition, which is ICS-based, the page does mention firmware. That ROM is based on the most recent 3.32 firmware, which is probably what you want to use. AFAIK, all ICS ROMs require firmware version of 3.12 or greater.
As for SuperCID, I think there are firmware downloads on the forums now that don't require it but it's also pretty easy to do.

pyrilium said:
The documentation page you linked is installation instructions for all Virtuous ROMs
Click to expand...
Click to collapse
Ahhh. Ok. That was the missing link. Thanks.
I have a rooted S-OFF Sensation 4G with the stock ROM and ClockWork. So all I need to do is:
Flash the Firmware that doesn't require SuperCID
Nandroid Backup / Wipe
And then I can flash Virtuous.
Is that correct?
Also, does flashing Firmware alone cause a wipe?

That is correct, although I would do your nandroid backup before you flash the firmware. I'm not sure that it will wipe the system partitions, but it might.
The only other thing is that it can be a pain to get back into recovery after you flash the firmware if you're not using adb, since whenever you boot into the boot loader it will detect the firmware (PG58IMG.zip) on your SD card and ask if you want to flash it. One solution is to remove PG58IMG.zip from the SD card using an SD reader after you do the firmware update, but if you have adb installed & working you can also simply issue the command "adb reboot recovery" when the phone is off. This won't work when you're in the bootloader, although there's probably an equivalent fastboot command.

pyrilium said:
That is correct, although I would do your nandroid backup before you flash the firmware. I'm not sure that it will wipe the system partitions, but it might.
The only other thing is that it can be a pain to get back into recovery after you flash the firmware if you're not using adb, since whenever you boot into the boot loader it will detect the firmware (PG58IMG.zip) on your SD card and ask if you want to flash it. One solution is to remove PG58IMG.zip from the SD card using an SD reader after you do the firmware update, but if you have adb installed & working you can also simply issue the command "adb reboot recovery" when the phone is off. This won't work when you're in the bootloader, although there's probably an equivalent fastboot command.
Click to expand...
Click to collapse
Wow, this is extremely helpful, thank you. One other thing: does it matter what version of ClockWork I'm using? (I rooted/did S-Off a loooooong time ago.)

Glad I can help!
I don't know whether the version of CWM matters. I doubt it would, other than maybe making a nandroid backup in a format other than current, but it's not that hard to update the recovery either.
I actually started using 4ext recovery recently, and I like it a fair bit better than CWM. It's something like $2.00 on the market, but includes a userspace application that lets you do things like set up a series of recovery operations (i.e. make backup, wipe, flash a set of zips) and then reboot into recovery to run them.

Perfect, thanks. I'll give this a shot.
Every few weeks I look up how to move to ICS but then lose my enthusiasm once I see all the things I'd have to do to switch haha. But today I noticed that Virtuous doesn't need some of those steps

One more question: SuperWIPE is unnecessary for Virtuous Inquisition correct? I see that it is necessary for Android Revolution, but I just wanted to make sure.

I've always seen superwipe recommended as part of the upgrade process from GB to ICS. It might not be required for Virtuous, but I don't see why you'd want to avoid it. The flashing process *will* wipe your phone - you want to use something like Titanium Backup to backup/restore app states if that's a problem - and performing the superwipe takes almost no time.

Woohoo! Successfully upgraded from stock Gingerbread (rooted & S-Off) to Virtuous Inquisition ICS! I wrote down what I did, so if anyone is interested, below is how I did it. It took about 15 minutes in total (not including the backups). Hopefully it helps someone else out there!
Titanium Backup all apps
Nandroid Backup via ClockWork Recovery (1434 MB)
Get CID Version:
Download ADB/Fastboot files from attachment from Post #1 of the [Firmware][Mar 12] thread
Connect phone to PC -> adb reboot bootloader -> Then in bootloader:
fastboot getvar cid: T-MOB010
fastboot getvar mid: PG5810000
fastboot reboot
Download the appropriate Firmware from above thread (CTRL+F for T-MOB010/PG5810000) and the Virtuous ROM from Virtous Website
Copy both files to sdcard, check md5 on both
Flash Firmware:
Turn phone off -> Hold Volume-Down + Power to enter bootloader
Wait for the firmware package to be found and confirm to update as prompted
Once completed successfully and asks you to reboot, pull the battery out. (Gingerbread & firmware are incompatible, causes bootloops)
With phone off and plugged into PC, do adb reboot recovery (Thanks pyrilium!)
Mount USB storage
Use PC to delete firmware file from sdcard
Wipe all data and cache -> Flash Virtuous -> Reboot
(Note that YES, flashing firmware causes bootloops -- as I found out! So firmware and ROM must both be flashed together.)
And thanks pyrilium for the note about using "adb reboot recovery" while the phone is off! I would have never figured that you could issue adb commands with your phone off. That tip isn't even in any of the guides, so thanks for that! Extremely helpful.
Anyway, hope that helps others out there. And thanks for helping me!

[Q] Splash Screen Freezing on Custom ROMS? (S-ON Unlocked doubleshot)

With the kind assistance of Coug76 (who pointed me to Hasoon's fantastic rooting kit!) I was able to get SuperUser access to my unlocked S-ON Doubleshot. Hooray!
Now I'm trying to install a new ROM. I tried the latest CM9 and I also tried Pyr-o-ice 1.1.1. Both times everything seemed to be going well, but on reboot I just got the splash screen. Most recently I let it sit for 12 minutes (I timed myself, so I wouldn't be tempted to lose patience!) just in case... but it seems to be truly frozen.
The first two times I went through Clockwork, copying the .zip file to the sdcard and then choosing "install from sdcard". The most recent time I went through Recovery, making sure to wipe the data first.
After that didn't work (splash screen for twelve minutes) I vaguely remembered someone saying somewhere (I've read a lot of posts here over the last 48 hours!) that HTC users need to flash the boot image separately. I figured it was worth a try, although I'm not sure if Clockwork does that on its own or not, so after installing from the zip file and trying to boot, I copied the boot.img from the pyr-o-ice .zip file onto the sdcard and then I went into fastboot and typed "fastboot flash boot boot.img".
Same behavior--splash screen still frozen. I also see that the "Read Before Posting" thread says "people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based". I did use HTC's unlock tool, so maybe that's my problem? If so, could someone recommend a good gingerbread ROM for me?
Finally, after restoring from a good nandroid backup (I've used it before, earlier today) the screen is still frozen. Is there any chance that this is because I flashed the other boot.img? I would have thought that the nandroid restore would have fixed that?
Thanks!
-=Benjamin

Oh, I just realized that I wasn't flashing the boot.img on my sdcard, I was flashing whatever random boot.img was sitting in the same folder as fastboot. Ok, fair enough. But the rest is still a mystery, and my nandroid recovery still isn't booting.

silly noob

Oh, no question about it! I'm just glad that I knew enough to get the damn thing working again.
But in the future I do want to try custom ROMs, for sure. So, is it true, then, that before I load a ROM via Clockwork, I need to first flash the boot.img from that particular ROM? If so, it makes Clockwork's ROM Manager seem... not very useful.
Thanks!

whirr said:
Oh, no question about it! I'm just glad that I knew enough to get the damn thing working again.
But in the future I do want to try custom ROMs, for sure. So, is it true, then, that before I load a ROM via Clockwork, I need to first flash the boot.img from that particular ROM? If so, it makes Clockwork's ROM Manager seem... not very useful.
Thanks!
Click to expand...
Click to collapse
Clockwork being on your phone makes it much easier to boot into fastboot and recovery modes instead of using the power and volume down method. It's also good for backup and recovery purposes. I was too much of a chicken to try it but if you're feeling brave, you can use the juniptobear method (hope I spelled that right) to gain S-Off. The link below is for the all in one S-Off kit by Hasoon2000 and will take you where you need to go to do this. If you do this, you won't have to use that extra step (flashing the boot.img file) to load a new ROM.
http://forum.xda-developers.com/showthread.php?t=1696373

eparico said:
Clockwork being on your phone makes it much easier to boot into fastboot and recovery modes instead of using the power and volume down method. It's also good for backup and recovery purposes. I was too much of a chicken to try it but if you're feeling brave, you can use the juniptobear method (hope I spelled that right) to gain S-Off. The link below is for the all in one S-Off kit by Hasoon2000 and will take you where you need to go to do this. If you do this, you won't have to use that extra step (flashing the boot.img file) to load a new ROM.
http://forum.xda-developers.com/showthread.php?t=1696373
Click to expand...
Click to collapse
I have S-Off (as it says in hboot) and I got the splash screen freeze.
I have not yet flashed the boot, maybe it says S-Off even though something reset it to S-On? Anyway I am going to flash the boot.img to see if it fixes the splash screen freeze issue (If it does then maybe my hboot is wrong).
---------- Post added at 04:05 AM ---------- Previous post was at 03:55 AM ----------
UPDATE 1:
Flashing the boot.img did not seem to make a difference it did "Okay" but no difference in the splash freeze.
F:\Android\ROM\Unziped>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (4058 KB)... OKAY [ 0.858s]
writing 'boot'... OKAY [ 7.424s]
finished. total time: 8.283s
I am making a n00b mistake some ware but I can't find it. The boot.img on my F: drive is the correct one, even though I should not need to do that since i have S-Off.
UPDATE 2:
FOUND IT, Ok the noob mistake was that I did the 'wipe' only on the cache and I needed to do the 'wipe' on the factory reset 'and' cache.
Ha ha stupid problems... Feels good though now its running. g-apps.... *worked like a charm! Its all working good now.

[Q] Paranoid noob question regarding S-off and previous Bootloader

I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much

fashofasho said:
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
when you did S-OFF in order to install Cyanogen JB first you had to flash the latest fw version and then the rom
the rom you tried to install requires the latest fw version
now are you still s-off?
what is now your hboot version?
what is your fw version?

I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.

Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
i got confused
.i think your answer is going for fashofasho

Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
Thanks for the reply. Okay so here is where I am currently at. I haven't done anything since I reflashed stock ROM throguh RUU after the fail cyanogen flash. On this stock ROM whenever I load into bootloader it still says s-off 1.17 but I did lose my clockworkmod. So according to your instructions I should either clockworkmod again or 4ext now, that's okay right? If so, going to flash firmware then cyanogen!! Or is there a problem that I have s-off but not recovery.
P.s. there is no point in running revolutionary and have it s-off again when I already have it right, just thought it might be necessary to make things fresh

If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app

Skipjacks said:
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?

fashofasho said:
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?
Click to expand...
Click to collapse
flash su-2.3.6.3-ef-signed.zip first and then install 4ext recovery

You're over engineering this. You don't need to root your current ROM first. That's an extra step since you're s-off.
If you are s-off it's really simple to get 4EXT recovery.
First, download this and put it on the root directory of your SD Card (meaning not in a folder, just on the SD Card. Do not rename it)
http://d-h.st/qnm
I got this download link from here...
http://forum.xda-developers.com/showthread.php?p=21989107
Click Thanks for Joaquinf in that thread. He made the 4EXT zip that's flashable through the bootloader.
That is 4EXT made into a zip file that's flashable via the bootloader, which you can do when you are S-off.
So put that file on the SD card, power the phone off, pull the battery out for a second and put it back in (this stops fastboot so you can get back to the bootloader). Then hold volume down and power at the same time. You have to hit both buttons at the same time. If it goes to the splash screen, pull the battery and try again.
When the bootloader loads up it will immediately find the PM58IMG.zip file. It will ask you if you want to install the update. Say yes by hitting volume up I think (it will tell you how to say yes)
Put the phone down and don't touch it until it tells you it's done. Should just take a second. But seriously don't touch it. Leave it alone.
If that works, you've just flashed 4EXT. You can check it by pulling the SD card out (so it doesn't try to flash the PM58IMG again) and rebooting to the bootloader and selecting 'recovery' from the menu. 4EXT should boot up.
This entire process so far shouldn't take more than 3 minutes total. It just sounds like a lot.
To see this detailed out by someone else in case you want to check what I'm saying, read steps 4 and 5 of the first post in this thread.
http://forum.xda-developers.com/showpost.php?p=21989063&postcount=1
Give the author 'thanks' again because he's awesome and deserves it.
Now you've got 4EXT installed. Great. You're 1/3rd of the way home.
Now you need to update your firmware. Delete the PM58IMG.zip file you used to flash 4EXT off the SD card (use a card reader or boot the phone up and delete it, whatever works. You can also use 4EXT as a card reader now too by choosing USB storage from inside 4EXT. It will give you access toteh SD card on your computer now)
Now get new Firmware from this thread.
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
try the 3.33 firmware universal. First download link in post 2 of the thread above.
CHECK THE MD5 SUM!!!! I'M NOT PLAYING AROUND HERE!!! You are worried about bricking your phone, this is where you can do it if the firmware .zip is bad.
Put that PM58IMG file on your SD and flash it in the bootloader the same way you flashed 4EXT recovery a minute ago. (If you're still in 4EXT recovery you can use it's power menu to reboot into bootloader easily.)
This will take a minute. The phone will shut off and go black in the middle of this process. Your heart will skip a beat. Relax. It'll come back on. Again, put the phone down and walk away while it does it's thing and don't touch it until it says it's done.
Delete the PM58IMG file from your SD card.
You are now 2/3 of the way there. Your phone WILL NOT boot up right now because your ROM is not compatible with your firmware. Relax. That's supposed to happen.
Now you can flash CM10. Make sure you have the CM10.zip file on your SD card nad GApps. (Bruce has Gapps in his downloads page). Delete the PM58IMG firmware file from your SD card (that's important)
Pull the battery again so you can get back into bootloader. Get into bootloader (power + volume down)
Select Recovery
4EXT should boot up.
Go to the Wipe menu. Wipe all partitions except SD card. (Old ROM is now gone)
Go back to the main menu.
Install from SD
Find the CM10.zip file you should have downloaded and put onto the SD card. Flash it.
This will take about 3 minutes. 4EXT will flash it and ask if you want to reboot. You do not yet. Not you need to flash Gapps the same way you flashed the ROM.
When that's done, now you can reboot. You shoudl see the CyanogenMod boot animation after the splash screen. Give it a few minutes to boot up this first time. Once it boots, set it up the way you like it. If you enjoy it, donate a few bucks to the developer, Bruce.
You don't have to root CM10. It's already rooted when you boot it up the first time.