Database Info

How to re-flash stock JB rom with OTA (custom recovery)

Hi,
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
Or, can I flash OTA update as update.zip in TWRP recovery?
sorry, for my bad english.

Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S

JohnKoeMan said:
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
Click to expand...
Click to collapse
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.

Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
Haha no problems friend!
I've found a link to a custom ROM using JB 4.1.1, you can look into that?
http://forum.xda-developers.com/showthread.php?t=1871866
Also you can instead remove TWRP (if you know how) and instead install CWM (clockworkmod).
I found CWM to work better than TWRP.
I myself am using CyanogenMod 10.1, very nice and clean, works perfectly ad has Android 4.2.1
That might also be an option if you want a clean ROM. ^^

I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.

orenfl said:
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
Click to expand...
Click to collapse
Since I'm facing the same problem, and there is no RUU for now, how and where to get a JB OTA nandroid... Haven't seen any around.

Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app

tominozh said:
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?

bo6o said:
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
Click to expand...
Click to collapse
Yes, you should be. Download zenrom, reboot recovery, wipe everything a few times, flash zenrom, set it up, then recovery, flash STOCK RECOVERY ( very important), prompt for update, download, install, set up, ( you may get a few errors here and there so just do factory reset in setting-->factory reset). Then flash twrp, flash superuser, backup.
Sent from my HTC One S using xda app-developers app

[SOLVED] Need To Fuly Revert To Stock

Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
I no longer need to downgrade to get the WiFi thanks to this great post here: WiFi Fix
I hope this helps people in the future.

All roms wifi works fine for me on hboot 1.14...

Vuciz said:
Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
i regret rooting my phone.. i cant sell it because they dont want a rooted phone

Re: Need To Fuly Revert To Stock
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app

zaak00 said:
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
so let me post it the fourth time ..
http://forum.xda-developers.com/showpost.php?p=37942416&postcount=2

Usually you'll find answers to your problems in the according rom section as you're not the only one with it.
But as you are pretty new here:
1. You can use Linux livecd for downgrading. More here. The process isn't that easy so and you'll need to be patient and careful. (I did that couple of times on my device. The first time it was really worse also I was/am not new to Linux).
2. 1.14 means you have been on ICS only so far. So any ICS rom should work for you. If there is still trouble with wifi, search for answers in that rom section. I remember some guys editing a file for enabling/boosting wifi. As I'm not concerned by this, I have no links.
3. If you'd like to move to JB roms search for 'flashing wifi partitions' as long as you want to keep 1.14. If flashing the OTA update for JB your bootloader version will be 2.15 and the according wifi partitions will be working as well. For both, ICS and JB.
Substantially there will be no real differences for you between 1.14 and 2.15 as only with 1.06 and 1.09 you don't need to flash kernels via fastboot mode.
Hope you got the point as my answer is very short.

What went wrong?

I was pulling my hair out for a few hours last night trying to get my phone back to a functional state. Fortunately I was able to do so, but I have no idea what caused all of my problems. Here's what happened:
I was running CM10 on my HOX (from this thread) for awhile now. I was having a few issues with it that were annoying but I didn't want to change the ROM and have to restore everything. I then got a notification for an update to CM10.1 so I downloaded that and installed it. During this process I decided to do a Factory Reset in TWRP.
Once I was booted back into CM10.1 I was having all sorts of strange issues, but the biggest one was that I was unable to connect to my cell network and it kept prompting me to restart. I decided I would just install another ROM so I downloaded CleanROM JL Beta 1 (here) and the Bulletproof-1.0 kernel (here).
I booted into TWPR and proceeded to wipe everything (i.e. clicked all of the buttons under the 'Wipe' menu). I've done this before and haven't had any problems. I then proceeded to install the kernel. It went through the installer fine without any issues. When I tried to install CleanROM JL Beta 1 in TWRP it just kept giving me an error and wouldn't bring up the installer.
I went back and forth trying to install multiple ROMs and every single one would give me an error. I thought I was screwed because I couldn't install an OS on the phone. I also went ahead and installed the stock kernel hoping that would fix the problem but it didn't. I eventually decided on finding the RUU to get me back to bone stock.
I downloaded the 2.20 RUU and relocked my bootloader. I went through the RUU process and everything is fine now, except the fact that I have a stock, bloated phone again.
Was it the kernel that messed me up? I installed it after I wiped everything and I'm not sure if I was supposed to do it that way. I'd like to get back to something stable again but I am not sure if I am able to since I relocked my bootloader and installed the 2.20 RUU. Any help is much appreciated, thanks!
NEW ISSUE #1: I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?
NEW ISSUE #2: I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...

If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?

redpoint73 said:
If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?
Click to expand...
Click to collapse
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.

afrat said:
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.
Click to expand...
Click to collapse
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.

redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine. I then tried installing CleanROM JL Beta immediately after and it would just give me the zip error.
What I mean by "after the ROM wouldn't install" was after it wouldn't install via TWRP. I then went back and extracted the boot.img, flashed it with fastboot, then went back into TWRP to try and install it again. That didn't work.

redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.

eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.
Click to expand...
Click to collapse
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.

afrat said:
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine.
Click to expand...
Click to collapse
If you keep reading on the Bulletproof instructions, you will see:
hboot 1.14+ and S-ON:
The installer includes a method to flash the boot.img for S-ON devices using hboot 1.14 or higher;
however, some people still have difficulties. If it doesn't work:
1. extract boot.img from the zip, reboot to bootloader and do:
fastboot flash boot boot.img​
---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------
eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have?
Click to expand...
Click to collapse
With hboot<1.14, or with S-on yes. But in his case no. For hboot 1.14 and higher and S-on, you can flash the kernel before or after the ROM, it doesn't matter since the kernel can't be flashed from recovery.
---------- Post added at 04:29 PM ---------- Previous post was at 04:26 PM ----------
afrat said:
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.
Click to expand...
Click to collapse
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.

redpoint73 said:
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.
Click to expand...
Click to collapse
I'm not sure. If I did the RUU, does that mean I lost the custom recovery (TWRP) that I've installed as well?

I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?

I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...

afrat said:
I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...
Click to expand...
Click to collapse
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw

eraste said:
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw
Click to expand...
Click to collapse
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!

afrat said:
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!
Click to expand...
Click to collapse
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?

eraste said:
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?
Click to expand...
Click to collapse
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.

afrat said:
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.
Click to expand...
Click to collapse
Strange. Really strange.

eraste said:
Strange. Really strange.
Click to expand...
Click to collapse
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.

I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.

afrat said:
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.
Click to expand...
Click to collapse
Yes ruu would have put you back to stock with the exception of supercid that would have stayed.
iElvis said:
I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.
Click to expand...
Click to collapse
Me to this was my initial thought super cid was the culprit!

eraste said:
Me too this was my initial thought super cid was the culprit!
Click to expand...
Click to collapse
But some others insisted that it couldn't have been the issue. SuperCID is supposed to allow flashing of any updates regardless of CID restrictions.

Proper way to Flash Jelly Bean ROMs?

Trying to solve a lag/crash issue with any ROM I install on my or my wifes phone. Reading the forums I've seen references to needing to install the official Jelly Bean RUU before flashing a Jelly Bean ROM like Viper XL, etc.
To do this, do I need to be S-OFF first?
Both our phones are already rooted (never took the 2.20? update, so never any issues with root).
Would it be something like this?
S-OFF the phone.
Install Jelly Bean RUU
Re-root
Install Jelly Bean ROM
Thanks!

that would work fine, you would need to s-off to run the jb update. as far as lag from jb sense roms, are you doing a full wipe before flashing?

Instead of "re-root", just push twrp 3.xxx to the phone. Then you can flash whatever rooted Rom you want. Has to be v3 or higher since the touchscreen drivers were updated. Personally I downgraded my touchscreen drivers to use 2.2.2.0 instead cause I'm partial to that version.
Sent from my HTC One X

ECEXCURSION said:
Instead of "re-root", just push twrp 3.xxx to the phone. Then you can flash whatever rooted Rom you want. Has to be v3 or higher since the touchscreen drivers were updated. Personally I downgraded my touchscreen drivers to use 2.2.2.0 instead cause I'm partial to that version.
Sent from my HTC One X
Click to expand...
Click to collapse
cwm ftw!!!
do the touchscreen driver downgrade like ECEXCURSION said though.

DvineLord said:
that would work fine, you would need to s-off to run the jb update. as far as lag from jb sense roms, are you doing a full wipe before flashing?
Click to expand...
Click to collapse
Yeah I completely wipe everything including storage. Still get lag after a while, still get freezes and reboots.
Just trying to figure out the best way to do this, step by step.

jburkco said:
Yeah I completely wipe everything including storage. Still get lag after a while, still get freezes and reboots.
Just trying to figure out the best way to do this, step by step.
Click to expand...
Click to collapse
You'll want to:
s-off
run ruu
update if your ruu doesnt include the latest update.
ruu will not relock your bootloader nor do you need to relock so no need to unlock or reroot.
fastboot flash recovery. i suggest twrp 2.3.x
then you can downgrade your touchscreen if you intend to use an older recovery or an aosp rom but i like to think the updates made improve things so i wouldnt downgrade unless you need to for an aosp rom or older twrp version.
flash whatever rom you like! if you just want stock rooted boot to recovery after flashing and it will prompt to root your rom when you go to reboot from within recovery.
good luck and have fun!

Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0

jburkco said:
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
Click to expand...
Click to collapse
-JB touchscreen firmware does not work with AOSP roms. Your touchscreen won't function.
-TWRP 2.4.x seems to cause problems with flashing for a lot of people.

jburkco said:
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
Click to expand...
Click to collapse
you need to downgrade touchscreen driver so you can use non-jb sense roms such as aosp roms and ics sense roms. he meant to say twrp 2.3 vs 2.4, twrp 2.4 can give many users random issues. i personally haven't had a single issue with official cwm.

Okay but since I'll be using ViperXL, the touchscreen wont be an issue. Thanks for all the help everyone.

2.4 doesnt properly wipe partitions and remnants are left behind causing issues.

[Q] problem flashing ruu jb 3.16

Hi guys
I want to revert my one s to stock rom through RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.
befor doing this I had supercid and s-off
After launching ruu ,the process stopped by error 159.
I tried other RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed
this flashed fine and worked good.
but i wanted JB so i downloaded OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96
and flashed it by CWM
but in the cwm enviroment , process stopped saying cid check failed....(and a couple of cid es)
So I changed my CID to stock (HTC_203) and I went through all above steps againe but same errors......
I don't know where the problem is??

salar_bigharar2009 said:
Hi guys
I want to revert my one s to stock rom through RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.
befor doing this I had supercid and s-off
After launching ruu ,the process stopped by error 159.
I tried other RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed
this flashed fine and worked good.
but i wanted JB so i downloaded OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96
and flashed it by CWM
but in the cwm enviroment , process stopped saying cid check failed....(and a couple of cid es)
So I changed my CID to stock (HTC_203) and I went through all above steps againe but same errors......
I don't know where the problem is??
Click to expand...
Click to collapse
hm.. which hboot do you have?
try to run the ics ruu again, after this you have stock ics rom right? do a factory reset and be sure that you have flashed the stock recovery.
then apply the ota update and install it the normal way.
I'm not sure if the ota updates are flashable so easily with custom recovery.

NQNH said:
hm.. which hboot do you have?
try to run the ics ruu again, after this you have stock ics rom right? do a factory reset and be sure that you have flashed the stock recovery.
then apply the ota update and install it the normal way.
I'm not sure if the ota updates are flashable so easily with custom recovery.
Click to expand...
Click to collapse
Yes ...I have ICS now....
sorry but what do you mean by normal way....
shoud I flash stock recovery separately?
what is the normal way of installing ota?
I thought that the usual way is using CWM.

salar_bigharar2009 said:
Yes ...I have ICS now....
sorry but what do you mean by normal way....
shoud I flash stock recovery separately?
what is the normal way of installing ota?
I thought that the usual way is using CWM.
Click to expand...
Click to collapse
hm..
the normal would be (if everything is stock)
boot your phone, search for updates, download update, apply update and the rest is an automatically process.
as far as I know you only have to be on stock recovery to be able to install the ota.
so, flash the stock recovery
https://www.dropbox.com/s/btmsslfgbwegu2k/ville_recovery_signed.img
look for updates again, and after download, tap on "install update" or sth like that.
your phone should restart in recovery mode and install the update.
but you have to be on stock recovery.
give it a try and let me know if this way worked
it should
aaaand I recommend you to do a factory reset after the JB update.
boot your phone after the update to your bootloader and select factory reset.
after this procedure you can flash back your favourite custom recovery and do whatever you want

ojoydro occasions
salar_bigharar2009 said:
Yes ...I have ICS now....
sorry but what do you mean by normal way....
shoud I flash stock recovery separately?
what is the normal way of installing ota?
I thought that the usual way is using CWM.
Click to expand...
Click to collapse
And i forgot my hboot is1.14.0002

salar_bigharar2009 said:
And i forgot my hboot is1.14.0002
Click to expand...
Click to collapse
oh I forgot.
change your cid to HTC__001
its the regionfree one for EU
should work with the ota

Thank you man .....after running Ics ruu ,i flashed stock recovery and installed ota jb zip from recovery ....(After entering to recovery, holded volum up and power button and the menu displayed)
During this my cid was stock:htc_203
Sent from my HTC One S using xda premium