Database Info

[Q] stock rom with s-off ? what i need to do?

hello and sorry for the same questions asked over the same issue...
its my first time and im afraid to brick my phone
anyway now im with custom rom and want to go back to stock to receive ota updates.
my phone is rooted and s-off i want to stay s-off with stock rom.
1. is it possible ?
2. will i need to wipe data before the flash?
3. backup needed ?
4. will i get ota updates with stock rom s-off?
5. the ruu is europe 1.47 do i need it to match to my software/radio/hboot?
my phone:
SAGA PVT SHIP S-off RL
HBOOT -0.98.0002
RADIO-3805.06.02.03_M
EMMC-boot

@yonigo870
Since you want to stay s-off and a stock rom then....
1) Yes if you don't want need OTA. No if you want ota
2) Yes
3) If you want to restore your apps/data yes, google SHOULD be okay with contacts/calendar
4) Dont be silly, really, DONT TRY STOCK THINGS ON ALTERED PHONES, thats common sense (at least it should be)
5) You will not use a RUU, you wil use a pre rooted stock rom from the development forum
However, if you want to get ota updates you will need to go s-on and use a RUU, I suggest just getting the latest RUU
My suggesttion, rather leave your phone as is and install a stock pre rooted rom, you can always install the latest stock rom when the OTA is released and its made into a prerooted rom.

foX2delta said:
@yonigo870
Since you want to stay s-off and a stock rom then....
1) Yes if you don't want need OTA. No if you want ota
2) Yes
3) If you want to restore your apps/data yes, google SHOULD be okay with contacts/calendar
4) Dont be silly, really, DONT TRY STOCK THINGS ON ALTERED PHONES, thats common sense (at least it should be)
5) You will not use a RUU, you wil use a pre rooted stock rom from the development forum
However, if you want to get ota updates you will need to go s-on and use a RUU, I suggest just getting the latest RUU
My suggesttion, rather leave your phone as is and install a stock pre rooted rom, you can always install the latest stock rom when the OTA is released and its made into a prerooted rom.
Click to expand...
Click to collapse
@foX2delta i agree with you
@yonigo870 flashing a ruu can actually force you into a bootloop if you flash the wrong RUU the best wasy to get to stock is to flash a pre-rooted stock ROM
heres both links to the RUU and pre-rooted stock ROMs
RUU http://forum.xda-developers.com/showthread.php?t=1002506
pre-rooted http://forum.xda-developers.com/showthread.php?t=1183684
i hope i have helped

thanks
thanks for the help !
how do i flash pre rooted roms?
and witch one i need???
and the other thing is, if i want to flash one of the custom roms via rom manager how do i flash the updates ? will it be the same way? do i need to change anything else or i can just backup and flash rom?!

yonigo870 said:
thanks for the help !
how do i flash pre rooted roms?
and witch one i need???
and the other thing is, if i want to flash one of the custom roms via rom manager how do i flash the updates ? will it be the same way? do i need to change anything else or i can just backup and flash rom?!
Click to expand...
Click to collapse
here is a few guides to help with that question i don't know anything about rom manager sorry i use 4ext touch recovery
Custom ROMS:
Custom roms can be found in this thread: http://forum.xda-developers.com/show....php?t=1146601 or head to the development section.
(Most of these ROMs are pre-rooted, which means that you don't need to root your phone after flashing one of the custom ROM.)
How To: Flash Custom ROMs using Recovery (Method 1)
(You can use your default recovery from Revolutionary tool but I recommend using 4EXTRecovery)
1. Copy your custom ROM "zip" file to your SD card (Root directory).
2. Turn off your phone.
3. Turn on your phone by holding the power button and the volume down button together.
4. Once you see the white screen, choose "Recovery"
5. Make a full wipe/format and clear all cache.
6. Choose "install from sdcard/zip file" and then choose your Custom ROM zip file from your SD card to flash your Custom ROM.
Optional: If you want to use 4EXTRecovery, just flash it like you are flashing your custom ROM(Step 6). Just do it before you flash your new ROM.
How To: Flash Custom ROMs using ROM Manager (Method 2)
(This method might be easier for flashing ROM updates or add-ons)
1. Go to ROM Manager (You can install this software from the Android Market.)
2. If you want to use 4EXTRecovery, please follow steps below, and if you're not using 4EXTRecovery, please skip to step 6)
3. Press your phone's option's button and choose Manual Flash Override.
4. Press OK and choose your phone model.
5. Choose ClockworkMod 3.x (After these steps, your ROM Manager won't ask you to flash new recovery again when flashing new a ROM)
6. Reboot into Recovery and make a full wipe/format and clear all cache then reboot.
7. Now, from your ROM Manager, choose Install ROM from SD Card.
Note: Flashing ROMs can be vary, some custom ROMs may require you to flash some of their own file first. Eg, The LBC Mod ROM requires you to flash "WIPE zip file" before flashing the ROM. Read their instructions carefully to know more.
NOTE: I am not responsible for any faulty or bricked devices after S-OFF or flashing new ROMs. Do it at your own risk.
How To: Flash a ROM in a "Perfect" Way (Method 3 - Recommended)
A great guide from vampire36 for people who encounter the following problems:
1. The ROM you flashed gets stuck on HTC screen (bootloop) while the same ROM works right for others
2. You get the same kernel and radio yet you find your cell to have more battery drain than others
3. Finally some strange force closes and restarts but works perfect for others
So this is basically one of the most perfect way to flash a custom ROM and is a way to help people who face such issues.
Please head to : http://forum.xda-developers.com/show....php?t=1257731 to see full instructions and discussions.

Blush91 said:
@foX2delta i agree with you
@yonigo870 flashing a ruu can actually force you into a bootloop if you flash the wrong RUU the best wasy to get to stock is to flash a pre-rooted stock ROM
heres both links to the RUU and pre-rooted stock ROMs
RUU http://forum.xda-developers.com/showthread.php?t=1002506
pre-rooted http://forum.xda-developers.com/showthread.php?t=1183684
i hope i have helped
Click to expand...
Click to collapse
You can enter a boot-loop but I've flashed ROMs too many times to remember (stock & MOD) and never truly boot-looped. You may soft-brick your phone however, but with remedy. Rooting phones & flashing ROMs isn't for the faint-hearted. My phone was dead for almost 48 hours (within 24 hours of purchase). That's how I joined XDA.
Scary. Turned out it wasn't hopeless. Within an hour of Temp Root, I had self-styled flashed CWM Recovery (haven't run into the gung-ho method I crafted yet, at least on these forums), proceeded to acquire Permanent Root afterwards and within the week had flashed 4 ROMs. Invented a few tricks myself .
Point is you have to get your hands dirty. That's why you bought the darn phone in the first place! Pull your gloves & get those hands dirty!

Saipro said:
You can enter a boot-loop but I've flashed ROMs too many times to remember (stock & MOD) and never truly boot-looped. You may soft-brick your phone however, but with remedy. Rooting phones & flashing ROMs isn't for the faint-hearted. My phone was dead for almost 48 hours (within 24 hours of purchase). That's how I joined XDA.
Scary. Turned out it wasn't hopeless. Within an hour of Temp Root, I had self-styled flashed CWM Recovery (haven't run into the gung-ho method I crafted yet, at least on these forums), proceeded to acquire Permanent Root and within the week had flashed 4 ROMs. Invented a few tricks myself .
Point is you have to get your hands dirty. That's why you bought the darn phone in the first place! Pull your gloves & get those hands dirty!
Click to expand...
Click to collapse
yes i've flashed many roms also and have never encountered a boot-loop the only time i got a boot-loop was when i flashed the wrong RUU in the past 48 hours i've changed roms about 20 times

flashing pre rooted stock rom
in progress...
hope i wont fu*k my phone at the very first time im doing this
btw im doing that with rom manager

yonigo870 said:
in progress...
hope i wont fu*k my phone at the very first time im doing this
btw im doing that with rom manager
Click to expand...
Click to collapse
Loooool don't worry that's what's xda is for were all here to help
Sent from my HTC Desire S using XDA

no wifi
flashed Saga_Europe_2.10.401.8_heb made by dmatik
and no wifi !!! how to fix it ?
the other thing is that i cant connect to market ...
and how do i restore titanium backup if i cant find the program on my apps ?
the phone updates himself ??? i see it updates programs from the market without me doing anything
* do i need to reboot the phone after flashing rom ??? and how ?

yonigo870 said:
flashed Saga_Europe_2.10.401.8_heb made by dmatik
and no wifi !!! how to fix it ?
the other thing is that i cant connect to market ...
and how do i restore titanium backup if i cant find the program on my apps ?
Click to expand...
Click to collapse
I don't know much about titanium I use app extractor try this ROM http://db.tt/Wnl7ZrKa
App extractor restores your apps contacts wifi settings SMS from your nandroid(backup)
Sent from my HTC Desire S using XDA

many thanks for the help !!!!
do i need to reboot after flashing ?

Yeah reboot I hope you made a full wipe before flashing sorry should have told you earlier
Sent from my HTC Desire S using XDA

yeah i did full wipe
after flashing rom the phone made updates from the market by himself, and now im restoring via titanium and seems like everything is ok...
after that titanium asked me to reboot, and so i did.
again thanks a lot for the support and for the help !!!!!!!!

problem !!! the rosie utility stopped unexpectedly...
htc widgets (like clock and weather) not working after restoring with titanium!
maybe its since the backup was on sense 2.1 and now its 3.0
how can make the htc widgets work ???

reboot back into recovery and fix permissions i dont know if you can do that in titanium

solved !!!
all was needed is to clear data from the htc sense

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] problem flashing ICS roms

I'm having problems flashing my Desire S with ICS based roms. GB roms work fine, but any ICS rom I flash gets stuck on boot on a lit up black screen. I have tried a variety of roms, flashed both on CWM and 4EXT but the issue persists. Is there some kind of special procedure for ICS roms ?

Did you
1. Wipe all partitions except SD
2. Wipe dalvik + cache
Edit : And the procedures same for flashing ics and gb roms, unless the OP specifically tells you to do otherwise

I did all possible wipes and It's still the same. Any more ideas ?

tomkow4 said:
I did all possible wipes and It's still the same. Any more ideas ?
Click to expand...
Click to collapse
did u u unlock with HTCDEV.com ? if u did just flash the boot.img inside the rom you want if u never then either the rom takes a long time to boot or your not doing the wipe properly
give me some specs of your phone

Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.

tomkow4 said:
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
Click to expand...
Click to collapse
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.

He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something

Vodka69er said:
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Click to expand...
Click to collapse
This. Exactly. I mean I have a MIUI GB rom so, I guess it's not about flashing a rom but trouble with ICS ones. So I figured that those must have something different about them or have a specific prerequisite. Others have flashed their D S's, so I'm kind of lost.

Can you post what you see on your bootloader
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!

*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
Radio - 3822.10.08.04_M
eMMC - boot
Aug 22 2011, 15:22:13

@op
I know that this is covering old ground, but I've not seen an actual answer
Have you ever used 'fastboot flash boot NAME.IMG' command?
Swyped from my DesireS

http://www.androidauthority.com/desire-s-root-s-off-hboot-2-00-0002-superoneclick-74470/ - this is the guide I followed.
On a side note, I did a full wipe of everything I could and still no luck with ICS roms. I think I'll leave it alone.

You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS

ben_pyett said:
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
Click to expand...
Click to collapse
To answer directly - I don't remeber/don't think so. But honestly didn't care much since my roms ran. Right now I'm on MIUI.
But the remark on the kernel got me thinking - I don't really know how to approach this, should I find some kernel and flash it?

On your pc you need to open the ICS ROM zip file and take out a file called boot.img
After flashing the Rom you must then use the fastboot command from your PC, as you did when you flashed your recovery.
You must then issue the command 'fastboot flash boot boot.img'
see below for the full instructions
HappyEmu said:
If you unzip your ROM's Zip-file (the one you want to flash, you'll find a file called "boot.img". Move it into the same folder as your adb and fastboot executables (Android SDK) and flash it using fastboot.
To be a little more specific:
1. Extract boot.img from ICS rom zip file and move it in the same folder as your fastboot.exe (Android SDK) on your PC
2. Flash the ICS Rom as usual from recovery (don't forget to first perform the full wipe/format including the boot partition)
3. Boot into fastboot mode, connect your phone to your PC and flash boot.img using fastboot
Code:
fastboot flash boot $pathToYourBootIMG\boot.img
4. Reboot
Click to expand...
Click to collapse
Swyped from my DesireS

Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!

eyahl said:
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
Click to expand...
Click to collapse
*Bump*
Sent by my fingers to your head.

suku_patel_22 said:
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Click to expand...
Click to collapse
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?

tomkow4 said:
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
Click to expand...
Click to collapse
I suspect that you're suffering the problem on other ROMS now as you're wiping the boot partition and therefore have no kernel.
[Q] How long do you wait on boot? you must be patient as first boot can take a while (although not longer than 10minutes).
A video would be a great way of showing the problem...Try to capture everything....
Your bootloader screen....
All the partition wipes
The Rom flash
The fastboot boot.img flash
and then what happens after...

Kind of noobish on my end, but as I was making the video - and did everything according to protocol just as earlier - it worked . I flashed BlackICE 5.5. Christ. Thanks anyway for the patience guys (I assume )

[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.

Useless HTC Sensation

HI! Today I got an HTC Sensation from a friend and it was laggy due to it's stock rom with preinstalled apps and stuff, so I decided to move to a custom ROM, the first one which caught my eye was 5.0 CM12 from the development section, so I copied it to sdcard.
I have managed to unlock the bootloader through the htcdev site and then flashed the lasted CWM Recovery available, 5.8.0 and then formatted cache, data, system, dalvik, because that's what I've always been doing on my Galaxy S2, it was very straight forward.
But now, I can't install a custom rom, tried that one and the slim pyramid one, even a cyanogenmod rom but still no luck. It would abort the installation and output an error about filesystems which can't be found or it woudn't say nothing but will restart the phone straight to recovery mode.
Also, tried 4ext recovery and still no luck. At this point I started panicking and tried to resolve this by installing the stock rom, RUU.
Downloaded RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed , which is the perfect match for my phone but also fails to finish installation, telling me something about failed/unknown mounts/filesystem... If it will help, I will tell you exactly what the error is.
At this moment I have S-On in bootloader, and can't see any radio serial metioned at the top. Tried some instructions flashing PG58IMG.zip , but it doesn't seem to do anything.
Please, help me out because at this point my phone won't go anywhere but bootloader and recovery.

AKAndrew41 said:
HI! Today I got an HTC Sensation from a friend and it was laggy due to it's stock rom with preinstalled apps and stuff, so I decided to move to a custom ROM, the first one which caught my eye was 5.0 CM12 from the development section, so I copied it to sdcard.
I have managed to unlock the bootloader through the htcdev site and then flashed the lasted CWM Recovery available, 5.8.0 and then formatted cache, data, system, dalvik, because that's what I've always been doing on my Galaxy S2, it was very straight forward.
But now, I can't install a custom rom, tried that one and the slim pyramid one, even a cyanogenmod rom but still no luck. It would abort the installation and output an error about filesystems which can't be found or it woudn't say nothing but will restart the phone straight to recovery mode.
Also, tried 4ext recovery and still no luck. At this point I started panicking and tried to resolve this by installing the stock rom, RUU.
Downloaded RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed , which is the perfect match for my phone but also fails to finish installation, telling me something about failed/unknown mounts/filesystem... If it will help, I will tell you exactly what the error is.
At this moment I have S-On in bootloader, and can't see any radio serial metioned at the top. Tried some instructions flashing PG58IMG.zip , but it doesn't seem to do anything.
Please, help me out because at this point my phone won't go anywhere but bootloader and recovery.
Click to expand...
Click to collapse
install latest 4ext from here
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
the command is fastboot flash recovery recovery.img
then from 4ext format all partitions except sdcard
enable smartflash( because you are on S-ON)
flash the custom rom
note: enable smartflash exactly before flashing the rom

Thank you very much! I've managed to install SKimKAT now. But how can I get S-Off permanent? Also, I can't install the stock RUU firmware.
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed
It freezes on the "sending" stage for hours.

AKAndrew41 said:
Thank you very much! I've managed to install SKimKAT now. But how can I get S-Off permanent? Also, I can't install the stock RUU firmware.
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed
It freezes on the "sending" stage for hours.
Click to expand...
Click to collapse
see this guide
http://forum.xda-developers.com/showthread.php?t=2751187