Database Info

[GUIDE]Updating to 4.22.651.2 OTA WITHOUT flashing a new ROM or wiping your Phone

This assumes you:
- Have the latest FROYO OTA installed 3.70.651.1
- Have some experience working with flashing things in recovery
- Have NOT deleted/uninstalled ANYTHING in /system
- Have defrosted any bloat you froze with Bloat Freezer or Ti Backup Pro
- Have S-OFF (Used Unrevoked Forever or a version of Unrevoked3 that includes Forever)
OK now let us get to it.
1. Go ahead and download the OTA like normal on your phone, but DO NOT install it.
2. Using a file manager copy the OTA zip file from /cache to /sdcard
3. Using Rom Manager, flash Amon RA Recovery 2.3 (Down at the bottom)
4. In Rom Manager, click the Reboot into Recovery button.
5. Select apply zip from SD Card and flash the OTA zip file that you put in /sdcard
--10 Minutes later.....you now have the UNROOTED OTA installed just as if you installed it normally--
6. Download the 2.6.0.1 ClockWorkMod Recovery zip from here and place it in the root of your SD card
7. Under settings > applications > disable FastBoot (re-enable this when you are done with the whole process)
8. Power off and reboot holding Volume down. The bootloader will scan and then will and ask you to press Volume up to install. Reboot.
9. Delete the PC36IMG.zip file from your SD card and place the attachment below in the root of the SD card.
10. Power off and reboot holding Volume down and then select recovery to start CWM recovery.
11. Choose apply zip from sd card. Choose select zip on sd card. You will see the SU file on the list, flash it to root your phone. Reboot.
You should now be rooted and can upgrade the recovery now to whatever style and version you want!
Enjoy! Please click the THANKS button if it worked for you!
----------------------------------------
Developer of Bloat Freezer - Freeze Your Pre Installed System Apps in One Click
Bloat Freezer - Android Market Link

Very cool!!

Great info ..hey if I follow these steps and skip the last part will my phone be stock / uprooted and good to go.for a trade in or repair? I've been trying to figure out the best way to unrest when.e3d comes out

I never updated to 3.70. I'm assuming I can do that the same way, root again, download the gingerbread, and root again?
I'm thinking it might just be easier to flash the rooted ROM and radios, but I'm not sure what's best.

if you have amon ra recovery (and a stock rom), you can simply download and click install.
I clicked install, amonra booted up, detected and ran update, click reboot, then the stock recovery will be active and updates the radios, once back in to sense, you can reinstall amonra or clockwork, then SU
worked for me.
http://forum.xda-developers.com/showthread.php?t=1109230

im curious why the title says "WITHOUT flashing a new ROM" yet you are clearly flashing the rom in amon ra. sorry just got to nit pick

what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?

JMQUINT00 said:
what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?
Click to expand...
Click to collapse
Well I wouldn't want to try it unless your prepared to do a full ruu reset if it fails.
the OTA is like a patcher, it deletes unneeded files, adds new files, and updates existing files... if its not completely stock it may (or may not) cause an error which the updater can't handle, and then you may be left with a half upgraded system.
if you nandroid *before* downloading the ota, you should always be able to go back, assuming you have perm soff from unrevoked forever.

it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.

cant I reinstall the apps and put the apks in their original system folder?

DomSim said:
it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.
Click to expand...
Click to collapse
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty

JMQUINT00 said:
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty
Click to expand...
Click to collapse
shouldn't be any worry about bricking but make 100% sure you are s-off from unrevoked forever and you should be able to re-root pretty much how the op outlined.

im currently running cm7. if i go back to a rooted stock froyo rom, will this work???

confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.

DaEXfactoR said:
im currently running cm7. if i go back to a rooted stock froyo rom, will this work???
Click to expand...
Click to collapse
Just download the update from here http://forum.xda-developers.com/showthread.php?t=1038701
Do a full wipe and flash like any other rom you've ever flashed before. You'll then be on the latest and greatest . (you'll probably be going right back to CM)
EDIT: and to the OP, sorry that I don't agree with you. I just find it more confusing that way, and I guess that whatever the point of doing it that way is, is sailing miles above my head.

k2buckley said:
confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.
Click to expand...
Click to collapse
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks

DaEXfactoR said:
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks
Click to expand...
Click to collapse
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."

k2buckley said:
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."
Click to expand...
Click to collapse
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!

rileyd5 said:
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!
Click to expand...
Click to collapse
I was a little curious about why those kernels were linked there too. I honestly haven't really kept up with thread, because I don't have an interest in flashing the update to begin with. I noticed those kernels are from May 4th, so it doesn't seem like they'd be the most current one. Without reading that thread, I first would've presumed that the kernel that comes with the rom would be the one to use. So, you've read through the thread and you're seeing that people are having trouble with the kernel that the rom comes with?? I'll take a gander over in the thread in a few minutes and see what I make out of it.

Well I f'd up and installed the latest update straight from sprint, instead of waiting for the rooted version to come out. I guess I thought I would find something exciting, but now I would realize it was kind of worthless and want to go back to a different rom like miui or vaelpak. I am s-off with unrevoked. Is there some combination of the steps listed I can use to back out of this?
Let me take a guess...did this update my radios and hboot to a version that would be incompatible with these roms?

[Q] ICS ota with half root?

I want to be sure my DS can receive and install the imminent (?) ota ICS from HTC. Still a bit of a noob so read a lot of stuff on here and other forums (mainly non DS) but haven't really found definitive answers for the 'half rooted' device i.e. bootloader unlocked via htcdev, cwm flashed, s-on.
Main concerns are:
losing root
ota will not install because of /system/app and framework mismatch (after a few UOT mods) - boot animation and sound have also been changed in /system/customise/resource, also bloatware removed
ota issues with cwm installed
Originally first thing I did immediately after flashing cwm was a nandroid backup so that's available to me, which really only leaves the cwm and ota compatability question.
Is Rootkeeper an option or should I root from scratch again after ota?
If I receive notification of the ota availability, then restore from original backup (and maybe relock bootloader with htcdev?) will I then have lost the chance to install the ota?
A lot of questions and ifs, I know, I just don't want to screw up the chance to try the official ICS before going for a custom rom. Thanks in advance.
Hboot 2.00.0002
Android 2.3.5
Sense 3.0
Stock rom/kernel/radio

Sorry, I'm pretty sure HTC Dev unlocked devices can't get OTA updates. I'm completely sure devices with CWM can't (you need stock HTC recovery). Since you already have a custom recovery, it would be better to get a custom ROM, much fastr and tweaked

As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.

foX2delta said:
As shrome99 said..
To get the OTA update you will need to have STOCK recovery, and a relocked bootloader to get the OTA.
__________________
This assumes you are 100% stock on the operating side.
Click to expand...
Click to collapse
I got OTA updates with both an unlocked bootloader and custom recovery. It's true the update won't install till you're back on stock recovery but the locked bootloader isn't necessary. I was however updating from Stock Sense 2.1

Warning: do not install it if you get a OTA message if rooted!
It will lead to the dreaded red triangle screen. Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.
Sent from my HTC Desire S using xda premium

The "dreaded" triangle screen is just the stock recovery.

Jack_R1 said:
The "dreaded" triangle screen is just the stock recovery.
Click to expand...
Click to collapse
That won't boot back to your ROM therefore you are stuck.
No root/s-off, therefore you can't do much about it. (Unless you get the RUU to run)
And for the average user, this is difficult for them to understand. Hence it has picked up its name as the 'dreaded triangle screen' over several different HTC device threads.
Sent from my HTC Desire S using xda premium

Cheers for the input.. did a bit more snooping and (if and when I get the ota shout).. I think I can go back with original nandroid to pre-root, before superuser went in. Then I'll give Android Recovery Manager (Sensation Android Development forum) a lash, just to see if I can flash back the stock recovery img.
If any nice ota comes my way which won't take then I'll try htcdev to relock the bootloader and give it another lash!
Think (hope) it'll work.. couldn't find a stock img anywhere yet so I'm hoping it's included in the above manager.. was going to try tonight but, typical, my connection went..
'Your best bet is to just install CWM/4EXT then when the new update comes, install the ICS prerooted ROM by Adidas.'
I have cwm, not sure why I would wait for the update then install a custom ics rom..

You must install stock recovery to install OTA update.OTA won't install, if you have custom recovery or S-off.But I recommend to install ROM, using zip or RUU.

From htcdev:
(after unlocking bootloader) Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable.
That answers the question re the bootloader but I'm struggling to find the stock recovery img to flash.
I suppose I can extract and then flash it, possibly from this: RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.exe, even though my device is 2.10.161.3 (161 is Vodafone). The radio is the same as mine which is irrelevant anyway, right?
I know it would be easier to install the RUU but after hours of research I would really like to be able to nail this so I have the option of reverting back to VF stock, as I still have 18 months warranty left.
Can anyone can confirm if I'm on the right track pls?

I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.

scandron said:
I suppose, if you haven't GoldCard or SuperCID recovery won't flash(signature verify failed).Download Zip/exe of your ROM , and flash that recovery.After that you might be able to install FOTA.No guarantee it will work.
Click to expand...
Click to collapse
It will flash, because his bootloader is unlocked.
He won't need a goldcard cause he is flashing a voda RUU recover, future I don't think it will even come into play when using fastboot to flash it.
However I suggest EVERYONE who is a little unsure make a goldcard.

Thanks all, trying to get a gold card now just to be sure.. however just intend to extract and flash the recovery img from the ruu, once I can be sure I have the right one.. the stock recovery in HTC devices is generic, no?

i also have a doubt.
what i wanted to know is that will i still be able to update my device OTA if i have unlocked the bootloader, rooted my device but havent installed a custom recovery?my device is rooted nothing more than that. and after relocking my bootloader (i dont mind loosing root) will i be able to update OTA?
sorry for being irrelevant but i didnt want to start a new thread for a doubt of this magnitude.

See post #10

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

[Q] Htc One X Unique problem

So as a n00b, I posted in the wrong forum earlier, lol
Anyways , long story short, htc one x evita, unlocked bootloader, tampered, rooted, will not flash past htc splash screen, when I try to restore, it does nothing, when going into folders there is NOTHING there, so random, I did clear my caches as instructed, maybe I am n00bish and deleted the wrong things, I can read the phone in adb, will go into teamwin screen,
REgardless, If I can get this fixed, I will not be messing with it again, lol(as all noobs say)
IS there anything I can do at this point before I throw my hands in the air and throw my phone at a wall?

Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita

timmaaa said:
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
Click to expand...
Click to collapse
HI, I may have wiped the sd, let's say sure to this..lol..
I have tried to copy a rom, I had Viper somewhat load, then it flashes back to htc splash, then to twrp,
Any insite to one that may possibly work?(the others will not load at all, they all fail install)

I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita

timmaaa said:
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you for your prompt replies
Venom loaded splash screen, then reboot to htc splash with the red developer on the bottom
twrp is the newest one
first 5 lines are you meaning?
*** TAMPERED ****
*** UNLOCKED ****
Evita put ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
??
Well I tried to load the stock RUU from rogers, (ota one)
then after rooting,unlocking bootloader, I tried to load a custom rom(slimkat IIRC)
then IT shut down, I left it for the night, and then nothing, so I tried to install slimkat again, nothing, so I tried venom, and I had the splash screen for the rom, now I am basically back at square one, nothing lol

Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita

timmaaa said:
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so very much, once again with the quick replies and the "dumming" it down for me,
I will try in a little bit, to be honest, im not sure what twrp it is, I know its 2.3.6.0, it was the newest one,
in your instructions is there a way to boot just back to stock rom as well?(my pc is horrible, if I load more then one page it dies off lol) I will try this when I get home in a little bit herre.

I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita

timmaaa said:
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
Click to expand...
Click to collapse
Yes I have a basic Adb/fastboot setup already, is there a particular rom you recommend?(I will trust your best judgement here) I am home now, I will try and let you know
Thank you again

Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita

timmaaa said:
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
Click to expand...
Click to collapse
I understand and apologize, Never thought of it that way,
Anyways an update, I followed your tutorial, and I am not having much luck here, It still maintains to say NO OS installed (through twrp when rebooting after I do adb and such)
maybe I am missing something ?

Adb or fastboot?
Sent from my Evita

timmaaa said:
Adb or fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Fastboot,
Small update I did manage to get a rootbox rom to load, but its not stable by anymeans...Ugh super frustrated with it

Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita

timmaaa said:
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
Click to expand...
Click to collapse
Yes to wiping before flashing in TWRP just those ones mentioned, (if you do sd you loose your flash right?), anyways the rom I flashed yesterday was super unstable, just trying a few diff. ones out and trying to find one that will continue to stay working lol!! Your tutorial in your signature is very helpful
thank you so much for all your help,and patience

Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita

timmaaa said:
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
Click to expand...
Click to collapse
Oh this is a clean phone, I already backed up on pc Before lol
Question though, I installed Viper again(just to try it) and it loads a menu showing ram, one of the memory sections shows -1? is this correct?

On a side note, I got Venom up and running and WOW!!!
once again, a super thank you for your patience and help all along Timmaaa,

I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita

timmaaa said:
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
Click to expand...
Click to collapse
it was while I was installing, everything seems fine, still no wifi(original issue)
im thinking the logic board may be buggered...sad day...lol
But, it is fast as heck now, running venom rom, I will try to get S-off and then maybe try to get it so I can load up the 4.4X roms
Thanks for all the help

[Q] Stock Recovery

Hi all,
I apologize if this has been answered before, but I had trouble finding it here. I am currently rooted on a stock backup, but I am running a custom recovery. I am not sure where to find the stock recovery image for my device. I am using the HTC One M8 through Verizon, and I know that the new firmware update is coming out soon, and I'd like to be able to just OTA update my phone so that I can reflash a custom recovery and install the newest VenomROM. I have flashed a custom recovery before (obviously), but I didn't know if it mattered which firmware base you are running. I read somewhere that the recovery is totally separate from the OS, and it is meant to be an alternative to booting into the OS in case of a problem, but I want to be sure. If there is a specific recovery I need to use and someone here knows where I can find it, that'd be great. I found the collection of stock recoveries, but I'm having trouble figuring out which one I need to use. Any and all help is appreciated, thanks.
EDIT: My CID is VZW__001
My VERSION-MAIN is nothing. There's is just nothing next to this label.
I tried locating it on the collection of stock recoveries, but couldn't find it. I'm not sure why this is.

It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....

hgoldner said:
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Hi there,
I actually just used the psuedo RUU tool (I assume this is the one you are talking about? http://forum.xda-developers.com/showthread.php?t=2727831)
I just finished using this tool, but when I went to check the recovery, all I get is a big red triangle with an exclamation point in the middle. Nothing else. So, I'm guessing that recovery didn't flash properly? But I'm honestly not completely sure. I would screenshot it, but I can't do that. Any help is appreciated.
EDIT: I found out that pressing volume up and power gives more options. I assume I am all good to go now? I am still rooted, and I'm not sure if that is a problem. I am stock, s-off and rooted, but I don't have any mods installed.

You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....

hgoldner said:
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.

ChuckFinley1992 said:
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
Click to expand...
Click to collapse
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.

hgoldner said:
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?

ChuckFinley1992 said:
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
Click to expand...
Click to collapse
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.

hgoldner said:
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
Click to expand...
Click to collapse
Okay, I may look into that. I've only seen an RUU flashed via hboot, so I'd have to look into it. At the very least though, I'd imagine someone will post the instructions on how to flash the firmware when it comes out.
Thanks so much for your help!

hgoldner said:
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
+100 for this!
I am reading dozens of posts in all kinds of threads of people just dying to take that OTA...
Why???
I would not touch that new firmware with a 100 foot pole until the devs have figured out what it breaks!!!
I predict a flood of posts in the line of:
"I flashed back to stock to take the OTA and now weaksauce is not working - how do I get root back?"
What's the hurry?????