Database Info

[Q] System update 1.45.162.1

So I got the notification that there's a Software update for my HTC Sensation; 1.45.162.1 (41.09MB) - Android 2.3.
I'm rooted via Revolutionary and still on original Vodafone (NL) stock ROM... However the update doesn't work for me. All I see is the green Android with a Triangle and an exclamation mark in it....
So after some search it seems that some other people have this issue, but that was in the tread for the 1.45.401.2 update....
Now what I would like to know now is this; Do I really need to go back to S-ON or is there any other way to get this update?
I'm asking this as going back to S-ON might brick the phone and also as I don't seem to find the original ROM in this thread.
Also, this as the instruction on this page clearly says:
Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
Click to expand...
Click to collapse
So..... I'm kinda lost now and I'm wondering how to proceed?? Would someone enlighten me?
THANKS!

as far as the US TMO update..you just had to be on the stock rom. You'll still keep S=OFF. And I'm still S=OFF after the update.

jmcghee1973 said:
as far as the US TMO update..you just had to be on the stock rom. You'll still keep S=OFF. And I'm still S=OFF after the update.
Click to expand...
Click to collapse
Ok... Strange... Any idea why I got stock on the green Android with a Triangle and an exclamation mark in it? The only way I can use my phone is to remove the battery and then it starts again, but it seems that it hasn't been updated.

If you backed up your original stock ROM w/ CWR, then restore in recovery.
Then run the update.

Gunkk said:
If you backed up your original stock ROM w/ CWR, then restore in recovery.
Then run the update.
Click to expand...
Click to collapse
But I'm already running stock rom... All I've done is rooted my phone and removed some bloatware such as The Sims, Soundhound etc. But that wouldn't be the problem would it?
Sent from my HTC Sensation Z710e using XDA App

Did you change your CID ?
Sent from my HTC Sensation Z710e using XDA App

Unroot & make sure you have your stock recovery...not cwm recovery. You'll lose root regardless when you update but you can re-root afterward.

m0rgul said:
Did you change your CID ?
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Yes, I did. However I'm not sure if that's still the case as I've used CWM to put back the original stock rom after I didn't like a custom ROM.
How can I check if I still have Super CID?
EDIT: I can confirm that my CID is 11111111. After exploring the forums I also have tried to install the updates with the following CID's as well;
HTC__E11 + VODAPE17.
However without any luck!
jmcghee1973 said:
Unroot & make sure you have your stock recovery...not cwm recovery. You'll lose root regardless when you update but you can re-root afterward.
Click to expand...
Click to collapse
EDIT: I do have the first backup (made using CWM) which I made before I rooted and changed my CID. But that's not what you mean? This as this is the first backup I made from my device.
Ok... I'm fine with that BUT:
I don't seem to find the original ROM in this thread.
I do see Vodafone's UK, France and 3 HTC Europe Roms... So not quite sure what to choose?
This as the instruction on this page clearly says:
Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
Click to expand...
Click to collapse
Is there any other way I can install the updates?
And will I have the same problem in the future as well, with other upcoming updates?
THANKS!

I think it's strange that OTA vodaphone 1.45.162.1 gets pushed to your phone if you have set Super CID, because OTA is based on CID. I had to change CID after I unbranded my phone(installing stock RUU HTC EUR), to get OTA 1.45.401.2.
It should work when you set CID to 'VODAPE17', or maybe the problem is the phone being unlocked, you should have chec.ked before using revolutionary that an RUU was available to restore your original rom..
At last try to restore your first backup, and set CID to 'VODAPE17'.
Also try to download the OTA file on your phone and copy it to your computer.

m0rgul said:
I think it's strange that OTA vodaphone 1.45.162.1 gets pushed to your phone if you have set Super CID, because OTA is based on CID. I had to change CID after I unbranded my phone(installing stock RUU HTC EUR), to get OTA 1.45.401.2.
Click to expand...
Click to collapse
Ok.. Didn't knew that.
It should work when you set CID to 'VODAPE17', or maybe the problem is the phone being unlocked, you should have chec.ked before using revolutionary that an RUU was available to restore your original rom..
Click to expand...
Click to collapse
As far as I know I haven't unlocked my phone... All I have done is the following:
- Rooted via Revolutionary
- Installed CWM
- Made a backup
- Made sure I had Perm root access
- Set the super CID.
Yeah... I know.. I should have done so, but I was too excited I guess...
At last try to restore your first backup, and set CID to 'VODAPE17'.
Also try to download the OTA file on your phone and copy it to your computer.
Click to expand...
Click to collapse
That I can try! Thanks.
So I've downloaded the OTA file and I think I understand why the VODAPE17 doens't work. The update is called: "OTA_Pyramid_Vodafone_DE_1.45.162.1-1.35.162.1_release_208996.zip".
So I'm going to try with Vodafone DE CID and see if I can update!
Will keep you updated!
UPDATE: No, even with CID set to VODAP102 I can't get the update installed.
So I extracted the zip file and went through the files and saw a file called: updater-script.
I opened this file and saw the following lines:
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "VODAP102" , "VODAPE17" ,
"VODAP304") == "t");
Click to expand...
Click to collapse
Now... I already have tried all the 3 Vodafone CID and the super cid is 11111111. Should I check the rest as well or what can I do?

This worked for me.....
BioTecK said:
Ok.. Didn't knew that.
As far as I know I haven't unlocked my phone... All I have done is the following:
- Rooted via Revolutionary
- Installed CWM
- Made a backup
- Made sure I had Perm root access
- Set the super CID.
Yeah... I know.. I should have done so, but I was too excited I guess...
That I can try! Thanks.
So I've downloaded the OTA file and I think I understand why the VODAPE17 doens't work. The update is called: "OTA_Pyramid_Vodafone_DE_1.45.162.1-1.35.162.1_release_208996.zip".
So I'm going to try with Vodafone DE CID and see if I can update!
Will keep you updated!
UPDATE: No, even with CID set to VODAP102 I can't get the update installed.
So I extracted the zip file and went through the files and saw a file called: updater-script.
I opened this file and saw the following lines:
Now... I already have tried all the 3 Vodafone CID and the super cid is 11111111. Should I check the rest as well or what can I do?
Click to expand...
Click to collapse
Hi - I had exactly the same issue as you - it turned out that the OTA will not run if you are S-OFF, I had to go back to S-ON and then install the OTA, then go back to S-OFF.
Worked a treat - then I decided that I didn't like stock and installed a ROM - lol

iftikar666 said:
Hi - I had exactly the same issue as you - it turned out that the OTA will not run if you are S-OFF, I had to go back to S-ON and then install the OTA, then go back to S-OFF.
Worked a treat - then I decided that I didn't like stock and installed a ROM - lol
Click to expand...
Click to collapse
Hmm... I see... So there's no chance that I can install this while having S-Off? Even not with CWM?
Also, would restore to factory setting do the trick as well? (Instead of using RUU?)

ok don't worry abt the S=OFF .. its ok.. You need to find the RUU of the rom that originally shipped on your phone. Run it via your pc with your phone connected and then do the update.
You may have to set your CID back to the original... I did but I didn't test it with 11111111 first.

jmcghee1973 said:
ok don't worry abt the S=OFF .. its ok.. You need to find the RUU of the rom that originally shipped on your phone. Run it via your pc with your phone connected and then do the update.
You may have to set your CID back to the original... I did but I didn't test it with 11111111 first.
Click to expand...
Click to collapse
Is there any way to figure out which rom was originally shipped and the CID on my phone?
Running the RUU shouldn't be a problem as I've done that a couple of time when I wanted to install EnergyROM on my old TP2.
Thanks.

so where is asian update ? i'm stell waiting but it didnt come
one question, my device is rooted now, can i update ?

BioTecK said:
Is there any way to figure out which rom was originally shipped and the CID on my phone?
Running the RUU shouldn't be a problem as I've done that a couple of time when I wanted to install EnergyROM on my old TP2.
Thanks.
Click to expand...
Click to collapse
You say your on a stock "backed up " rom... go to Settings > About Phone> Software Information & look at the Software Number

jmcghee1973 said:
You say your on a stock "backed up " rom... go to Settings > About Phone> Software Information & look at the Software Number
Click to expand...
Click to collapse
That's what I did and I was running 1.35.162.1.
While searching the forum and Google and checking the OTA update I noticed that I needed to have RUU of Vodafone DE (Hence the 162 code in my software information).
At some point I came across a website which had posted the "latest" RUU for Vodafone De; RUU_Pyramid_Vodafone_DE_1.27.162.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191975_signed.
So I downloaded the file and ran it. After this I searched for any OTA updates and I could download 1.35.162.1. I was able to download and install this without any problems.
After a restart I searched again for any other updates and I could download the latest version which is 1.45.162.1! Again, I was able to download and install this update without any problems! =)
So I guess everything is just working right! Luckily I'm still S-OFF and some how the phone seems to be MUCH faster then it used to be!! So I'm all happy again!
THANKS again for your help and everyone else!!

So wait...you were able to install it with all the custom mods like clockwork recovery s-off and root?? I tried installing the update but it wouldn't install assuming because I had the custom recovery not stock. Can someone clarify? I have a t Mobile branded sensation also. Thanks
Sent from my HTC Sensation 4G using XDA App

nexicon said:
So wait...you were able to install it with all the custom mods like clockwork recovery s-off and root?? I tried installing the update but it wouldn't install assuming because I had the custom recovery not stock. Can someone clarify? I have a t Mobile branded sensation also. Thanks
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Not quite...
I was only able to install the OTA updates after I run the original RUU... Without it I wasn't able to install as well.
A lesson which I learned today is that you need to flash to the original RUU before you can install the OTA's.
Hope this helps.

Glad to see you managed to sort it out, just curious, what is your hboot version now ?

[HOWTO] [HTC One SV] Unbrand your phone to get the OTA updates

Bonjour everyone, here's a little guide on how to unbrand your phone in order to get the OTA updates notifications directly and be able to install them.
If you want to get S-OFF one day on your One SV, read this first. You need to change CID to SuperCID to do so, and it's not possible (for the moment) if you upgrade to JB
Basically this works as long as your phone model is sold unbranded somewhere in the world and that the people having such a phone got an OTA update.
For now, ther's no way to change CID if you're running JB and are S-ON. That means that this only work for One SV's running ICS who want to get the OTA updates.
As far as I know, it works on K2_U and K2_UL, since they both got an OTA update to JB.
The trick is simple, I didn't invent it and haven't been able to find its original founder, but thanks a lot to her or him !
I'm basically just a messenger here since I only tried out some stuff that worked with other phones, so thanks a lot to bkcokota, old.splatterhand and jmztaylor
Don't try it if you're worried, bricks happen, you'd be the only one responsible !
Here we go :
1. First you need to root your phone, here's how.
2. Change you CID using the same method than for the One S.
Personnaly, I changed it to "HTC__203", which is the CID unbranded HTC phones have in France (HTC-FRA).
For example, "HTC__001" is HTC-WWE, which stands for World Wide English.
You can change it to whatever CID you like : choose it well. I can only recommend to use HTC__203 since it's the only one I tried and that it worked, but do as you please !
3. Flash stock recovery back. You'll find it here or here. Flash it like you flashed CWM recovery (into fastboot, using fastboot flash recovery xxxxxx.img).
4. Relock your bootloader. It's possible that it's not necessary, but it can't hurt ("fastboot oem lock", when in fastboot usb)
5. Run a RUU that matches you unbranded CID to get an "unbranded" rom.
You'll find them here, for example. The "RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5_R....exe" one will work with HTC__203 and HTC__001 CIDs.
6. Go ask your phone if he can find any updates
WARNING : for the moment there's no way to change CID if you upgrade to JB since the newer HBOOT (v2.00) don't let you do it. That means that for now you won't be able to S-OFF if you upgrate to JB using this method. For now...

Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).

old.splatterhand said:
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
Click to expand...
Click to collapse
Done, sir.
It was only said at the bottom of the message at first, but now I put it at the beginning as well.
There's one thing that I'm trying to get though : according to a lot of people and forums, you don't get OTA when you have SuperCID... but some poeple say they do.
It probably changes depending on the type of HTC phone, but also depending on the OTA (some got the first ones, but not the latest...).

I got the ota notification with SuperCID, i think it depends on more things.
But there i'm not far enough into it.

I have had no success at all. My story:
Updated a branded phone to JB, rooted. Then I did a moonshine S-off and changed CID to HTC__001 (even tried 11111111).
I have downloaded a ICS RUU (couldn't find stock K2_UL so I thought that I would download ICS first and then do OTA to JB) but I am getting error 158. I have checked md5 sum and it matches (http://androidfiles.org/ruu/getdown...0.14_2_10.49.40.11L_release_301902_signed.exe). Any ideas?

If you're on jb and hboot 2.00, that's normal... and written in the first post.

There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?

Is there any chance to make this for the k2cl ( boost mobile ) version?

idr666 said:
Is there any chance to make this for the k2cl ( boost mobile ) version?
Click to expand...
Click to collapse
Can you be more specific, what you mean with "this".

old.splatterhand said:
Can you be more specific, what you mean with "this".
Click to expand...
Click to collapse
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB

idr666 said:
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
Click to expand...
Click to collapse
Boost has no official jb, but i know that there is work for an custom jb rom for boost.

Oh, thank you for the info. Is there any link about this work in progress?

idr666 said:
Oh, thank you for the info. Is there any link about this work in progress?
Click to expand...
Click to collapse
Look here

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot,...
Click to expand...
Click to collapse
This was before moonshine was available. With S-Off i think it should be possible.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
I think so.
szympro said:
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
Click to expand...
Click to collapse
To get it a bit clearer.
At this point i'm not very up to date, thats why i didn't answer til now.
I think (but i'm not sure) you can flash the ruu, if you are on hboot 1.0.
And as you are S-Off you should be able to downgrade hboot. But this is a very risky point, you can easily brick your device. Here is, how you have to do:
rollon76 said:
To change hboot you will need a PL80IMG.zip on sdcard with android-info.txt and hboot.img inside it.
reboot to bootloader and flash.
Click to expand...
Click to collapse
The thing what makes it difficult, is to get the hboot.img (its inside ics ruu), cause the htc ruu's encrypted and i only have heard about tools for linux which can decrypt it.

Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!

szympro said:
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
Click to expand...
Click to collapse
Glad, it worked for you.
Yes, of course, everything is appreciated! You can use this thread, please post ruu name too. You can look at my posts there. Hboot, boot.img, recovery, radio, would be fine.

HERE have other ruu
https://www.dropbox.com/sh/1t2zswod7tc97az/5hbzEgTv80

szympro said:
I have downgraded hboot first (by extracting and encrypting ICS RUU using linux)
Click to expand...
Click to collapse
Wow, that's cool !
Did you use rollon's method and flashed PL80IMG.zip in bootloader mode ?
If yes, which android-info.txt did you use ?
If not, how did you do it ?
szympro said:
then I could run RUU and now I am stock ICS with S-off and superCID
Click to expand...
Click to collapse
Even cooler for you.
Did you get the ota update notification for JB then ?
Did you manage to apply it ?
Thanks and congratulations !

Hi everyone.
Just a quick message to confirm that rollon's method works.
To downgrade you need to be S-OFF, extract and decrypt (with ruuveal, using linux or a linux virtualbox runned in windows) hboot and androidinfo from ICS RUU, put them in a zip named PL80IMG.zip, put it on your sd card and boot into bootloader. Then you can run the ICS RUU normally and you'll be back to stock ICS, with a "*** LOCKED ***" bootloader (not relocked !), will be able to go back to S-ON using "fastboot oem writesecureflag 3" (thanks to JMZ)...
You'll then have a locked S-ON out of box phone running 100% stock ICS with original boot, recovery and all that... who'll get the 2 JB OTA's...
In case anyone's interested

Fido/Rogers Stock RUU

Hello
I am officially getting crazy over the fact that my phone is broken
I tried everything and nothing works
now I want to flash a stock RUU
I tried both :
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed
but they gave me error 155
here is the info I have :
VLE PVT SHIP S-On RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OPENDSP-V31.1.0.45.0815
eMMC-boot
Cid : ROGER001
I really appreciate any help
this has been a problem for 7 days now and I cant figure it out

jimlee2 said:
Hello
I am officially getting crazy over the fact that my phone is broken
I tried everything and nothing works
now I want to flash a stock RUU
I tried both :
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed
but they gave me error 155
here is the info I have :
VLE PVT SHIP S-On RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OPENDSP-V31.1.0.45.0815
eMMC-boot
Cid : ROGER001
I really appreciate any help
this has been a problem for 7 days now and I cant figure it out
Click to expand...
Click to collapse
Iam also having the same problem did you found any solution for that dude

jimlee2 said:
Hello
I am officially getting crazy over the fact that my phone is broken
I tried everything and nothing works
now I want to flash a stock RUU
I tried both :
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed
but they gave me error 155
here is the info I have :
VLE PVT SHIP S-On RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OPENDSP-V31.1.0.45.0815
eMMC-boot
Cid : ROGER001
I really appreciate any help
this has been a problem for 7 days now and I cant figure it out
Click to expand...
Click to collapse
From the looks of it, seems like Those are ICS RUUs so that won't work. (Downgrade isn't possible without S-OFF which seriously I won't recommend)
Either:
- Find a JellyBean RUU.
OR
- Find a JellyBean OTA. (Though for OTA you will have to be on Stock ROM and Stock Recovery)

khan.orak said:
From the looks of it, seems like Those are ICS RUUs so that won't work. (Downgrade isn't possible without S-OFF which seriously I won't recommend)
Either:
- Find a JellyBean RUU.
OR
- Find a JellyBean OTA. (Though for OTA you will have to be on Stock ROM and Stock Recovery)
Click to expand...
Click to collapse
I tried to manually install the second RUU but it said HBOOT fails so when I researched it appeared that mine is HBOOT-2.15.0000 and the RUU is older version,
what do you mean find a JellyBean RUU ? another Rogers RUU ?

jimlee2 said:
I tried to manually install the second RUU but it said HBOOT fails so when I researched it appeared that mine is HBOOT-2.15.0000 and the RUU is older version,
what do you mean find a JellyBean RUU ? another Rogers RUU ?
Click to expand...
Click to collapse
I meant to say that these RUUs hold ICS stuff in it. Which is why it won't work since your phone is on JellyBean.
You need to find and Run a JellyBean RUU for Rogers.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
I meant to say that these RUUs hold ICS stuff in it. Which is why it won't work since your phone is on JellyBean.
You need to find and Run a JellyBean RUU for Rogers.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
oh, I did not know they are ICS ,
the problem is I can not find any other Rogers RUU, can you please help me find the correct one ?
I am new to this and in the past few days I tried almost anything, but still not working

jimlee2 said:
oh, I did not know they are ICS ,
the problem is I can not find any other Rogers RUU, can you please help me find the correct one ?
I am new to this and in the past few days I tried almost anything, but still not working
Click to expand...
Click to collapse
Okay, I couldn't find a JB RUU for Rogers. But I found an OTA.
You can find all the RUUs/OTAs Here.
OTA specific to your phone is in above link or Here Directly.
When you download it, be sure to match the MD5 checksums of the downloaded file to that of the file on server. MD5 hashes are given on the website. Long bizarre number.
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
For further material on how to flash an OTA (Since it won't work normally by flashing it over anything via custom recovery), follow This Guide.
Though it is for VilleC2 or the S3 variant, the rule is the same for S4.
I know it's a bit unusual process, but it's the only way to avoid doing the S-OFF which poses numerous problems afterwards.

khan.orak said:
Okay, I couldn't find a JB RUU for Rogers. But I found an OTA.
You can find all the RUUs/OTAs Here.
OTA specific to your phone is in above link or Here Directly.
When you download it, be sure to match the MD5 checksums of the downloaded file to that of the file on server. MD5 hashes are given on the website. Long bizarre number.
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
For further material on how to flash an OTA (Since it won't work normally by flashing it over anything via custom recovery), follow This Guide.
Though it is for VilleC2 or the S3 variant, the rule is the same for S4.
I know it's a bit unusual process, but it's the only way to avoid doing the S-OFF which poses numerous problems afterwards.
Click to expand...
Click to collapse
thank you so much for the help
you said :
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
since I dont have the stock ROM , is it possible to fix this?
I heard OTA is different from RUU, will that cause more problems ?
thank you again

jimlee2 said:
thank you so much for the help
you said :
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
since I dont have the stock ROM , is it possible to fix this?
I heard OTA is different from RUU, will that cause more problems ?
thank you again
Click to expand...
Click to collapse
Doesn't cause problems but won't let you update if anything other than stock. That's how it is different.
You can avoid using Stock Recovery, by editing updater script. That is explained in the afore mentioned thread.
And to get stock ROM you an use a nandroid backup of stock ROM and then flash this OTA.
Sent from my HTC One S using Tapatalk 4 Beta

Stuck at the same situation
jimlee2 said:
thank you so much for the help
you said :
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
since I dont have the stock ROM , is it possible to fix this?
I heard OTA is different from RUU, will that cause more problems ?
thank you again
Click to expand...
Click to collapse
Hey
Did you ever manage to get your phone back to the stock ROM? I am stuck exactly at the same place as you. All numbers about my phone are the same too.
I cannot find any suitable RUU or nandroid online. Could you please point me to one?
Best,
Vic

veemon said:
Hey
Did you ever manage to get your phone back to the stock ROM? I am stuck exactly at the same place as you. All numbers about my phone are the same too.
I cannot find any suitable RUU or nandroid online. Could you please point me to one?
Best,
Vic
Click to expand...
Click to collapse
Here's your OTA.zip. Flash it using the method in my signature.
Sent from my Nexus 7 using Tapatalk HD

[Q] Android 4.2.2 odexed problem, noisly from speaker

Hi.
I have problem when I flash odexed 4.2.2 with sense 5.0 it's work perfectly, but when I want answer the phone speaker is stranger noisly :/
On 4.1.2 is worked fine.
I tired to flash different boot but this same result or will be stuck on bootloader (HTC)
Please help, any idea?
And second my question is: How to get superCID or changed actually on JB?
I think I need diffrent bootloader maybe.
Phone:
K2_UL: Branding Vodafone DE (but firmware odexed 4.1.2) without brand
S-ON
Recovery: TWRP
Bootloader: unlocked

You guys should read a bit more, because the last days the same questions poping up day for day and the answers are already given!
Noisy sound comes from missing firmware files, like already said in the rom thread.
And for SuperCid, follow the guide i wrote. You will find it in my Index thread (look at the link in my signature).

old.splatterhand said:
You guys should read a bit more, because the last days the same questions poping up day for day and the answers are already given!
Noisy sound comes from missing firmware files, like already said in the rom thread.
And for SuperCid, follow the guide i wrote. You will find it in my Index thread (look at the link in my signature).
Click to expand...
Click to collapse
I've downloaded full OTA for SV, and I got frimewere frome here, how could I flash it with s-on?
Maybe it must be flashed before flashing the room?

old.splatterhand said:
You guys should read a bit more, because the last days the same questions poping up day for day and the answers are already given!
Noisy sound comes from missing firmware files, like already said in the rom thread.
And for SuperCid, follow the guide i wrote. You will find it in my Index thread (look at the link in my signature).
Click to expand...
Click to collapse
SuperCID don't work on JB..
In the topic with odexed 4.2.2 the problem with missing firmware file have bluetooth.
When I restore 4.1.2 I have the same problem with noisly. When I flash boot from 4.1.2 the problem will be gone.

Damian0429 said:
SuperCID don't work on JB..
Click to expand...
Click to collapse
That's not true. Yesterday evening a guy changed cid on JB. You must be S-off, then it works also on JB.
In the topic with odexed 4.2.2 the problem with missing firmware file have bluetooth.
When I restore 4.1.2 I have the same problem with noisly. When I flash boot from 4.1.2 the problem will be gone.
Click to expand...
Click to collapse
Bluetooth is already fixed in v2 like i said in the rom thread.
And if firmware files are not causing the problem with sound, then i can not do anything. It can always give problems, if firmware files are missing, htc don't release them for fun.
The whole rom is for playing around until official update is here for all. Nothing more. Maybe as backup for k2ul devices, which have done the OTA update already.

old.splatterhand said:
You guys should read a bit more, because the last days the same questions poping up day for day and the answers are already given!
Noisy sound comes from missing firmware files, like already said in the rom thread.
And for SuperCid, follow the guide i wrote. You will find it in my Index thread (look at the link in my signature).
Click to expand...
Click to collapse
old.splatterhand said:
That's not true. Yesterday evening a guy changed cid on JB. You must be S-off, then it works also on JB.
Bluetooth is already fixed in v2 like i said in the rom thread.
And if firmware files are not causing the problem with sound, then i can not do anything. It can always give problems, if firmware files are missing, htc don't release them for fun.
The whole rom is for playing around until official update is here for all. Nothing more. Maybe as backup for k2ul devices, which have done the OTA update already.
Click to expand...
Click to collapse
Thanks, so we must waiting for other release.
I have swap internal memory and root 4.2 thats will be great the phone work faster. But when I answer the phone is strange noisly from speaker, ringtone sound great. This is great update This is awesome stuff So I must wait for fix this bug.
Maybe any instuction how to change CID, have ota update and flash TWRP so:
First I must S-OFF moonshine
next change cid to HTC__032
In next step I must flash original boot, orginal recovery, relock bootloader
Next flash ruu with 4.1.2
Next OTA to 4.2.2
Next unlock bootloader
flash twrp
next I wonna to swap memory and root.
This is a good plan or not?

old.splatterhand said:
Bluetooth is already fixed in v2 like i said in the rom thread.
Click to expand...
Click to collapse
I have fixed BT problem, so, I'm waiting for the speaker-sound fix.
Now, I've returned back to 4.1.2, I hope, that thiese bag will be fixed soon, as I liked sense50
Damian0429 said:
First I must S-OFF moonshine
next change cid to HTC__032
In next step I must flash original boot, orginal recovery, relock bootloader
Next flash ruu with 4.1.2
Next OTA to 4.2.2
Next unlock bootloader
flash twrp
next I wonna to swap memory and root.
This is a good plan or not?
Click to expand...
Click to collapse
I think, that swapping will not work, as 4.2 rom is't the same as 4.1.2

a4necromant said:
I have fixed BT problem, so, I'm waiting for the speaker-sound fix.
Now, I've returned back to 4.1.2, I hope, that thiese bag will be fixed soon, as I liked sense50
I think, that swapping will not work, as 4.2 rom is't the same as 4.1.2
Click to expand...
Click to collapse
I use patch from 4.1.2 to 4.2 work perfectly

Damian0429 said:
First I must S-OFF moonshine
next change cid to HTC__032
In next step I must flash original boot, orginal recovery, relock bootloader
Next flash ruu with 4.1.2
Next OTA to 4.2.2
Next unlock bootloader
flash twrp
next I wonna to swap memory and root.
This is a good plan or not?
Click to expand...
Click to collapse
There is no 4.1.2 RUU, only ICS RUU. But basicly this should be the way to get the update. Can't say anything about swap.
a4necromant said:
I have fixed BT problem, so, I'm waiting for the speaker-sound fix.
Now, I've returned back to 4.1.2, I hope, that thiese bag will be fixed soon, as I liked sense50
Click to expand...
Click to collapse
As i said many times now: i don't think, this will be fixed until everybody has done the OTA update.

old.splatterhand said:
There is no 4.1.2 RUU, only ICS RUU. But basicly this should be the way to get the update. Can't say anything about swap.
As i said many times now: i don't think, this will be fixed until everybody has done the OTA update.
Click to expand...
Click to collapse
Yes! My CID was changed when I do moonshine s-off i use comand:
fastboot oem writecid 11111111
And work on JB
Now I will downgrade to ICS nice
Now the phone updating to JB next to JB 4.2

Damian0429 said:
Yes! My CID was changed when I do moonshine s-off i use comand:
fastboot oem writecid 11111111
And work on JB
Now I will downgrade to ICS nice
Now the phone updating to JB next to JB 4.2
Click to expand...
Click to collapse
Somobody knows, does it works with k2_u (non LTE) too?

a4necromant said:
Somobody knows, does it works with k2_u (non LTE) too?
Click to expand...
Click to collapse
This is moonshie for K2_U:
http://moonshine.io/download/okdtbhjccvwn.html
Instructions working in 100%

a4necromant said:
Somobody knows, does it works with k2_u (non LTE) too?
Click to expand...
Click to collapse
I have ben trying just for fun. Seems to work, i encountered The same bugs reported here

gibihr said:
I have ben trying just for fun. Seems to work, i encountered The same bugs reported here
Click to expand...
Click to collapse
When I done I will write in this thread instrucions for everyone who would have ota update.
Instructions:
First we must S-OFF moonshine
next change cid to HTC__032 <-- in my phone (fastboot oem writecid HTC__032)
Next back to ICS http://forum.xda-developers.com/showthread.php?t=2386426
Now we must do S-ON fastboot oem writesecureflag 3
Next update from OTA to 4.2.2
Next unlock bootloader htcdev.com
flash twrp http://forum.xda-developers.com/showthread.php?t=2280241
next I wonna to swap memory and root.

S-On is not needed!

old.splatterhand said:
S-On is not needed!
Click to expand...
Click to collapse
When I have S-OFF OTA stuck in red triangle
S-ON For sefty

Damian0429 said:
Instructions:
First we must S-OFF moonshine
next change cid to HTC__032 <-- in my phone (fastboot oem writecid HTC__032)
Click to expand...
Click to collapse
Flash this command:
fastboot oem writecid HTC__032
via adb can change CID ?

rJiLz said:
Flash this command:
fastboot oem writecid HTC__032
via adb can change CID ?
Click to expand...
Click to collapse
flashboot no adb

Damian0429 said:
When I have S-OFF OTA stuck in red triangle
S-ON For sefty
Click to expand...
Click to collapse
Not true! OTA also work when the phone is S-off.

old.splatterhand said:
Not true! OTA also work when the phone is S-off.
Click to expand...
Click to collapse
That's right.
I recieve jb OTA with unlock and S-OFF.

Help to revert to stock

Hi, u'm on Newroot 4.1 rom.
I need to return to android 4.3 sense 5 stock rom. How do I do that? Last time i tried and gave up but I need to try it again. Can someone please guide me?

Hi Guys,
i'm have flashed the rom from here (http://forum.xda-developers.com/showpost.php?p=43816453&postcount=2) and revert to stock boot and recovery.
But now when I try to get OTA update, there is a message saying "Variant system version"
Any idea?

Guys, help please! I can't update from OTA!

The link you stated is for TW version (.709) which your CID should be HTC_621.

xunus said:
The link you stated is for TW version (.709) which your CID should be HTC_621.
Click to expand...
Click to collapse
thanks. My CID is 044.
I just SOFF and tried to flash this RUU but keep failing.
I have tried two method putting it on my external SD. Downloaded the file, renamed it and put it as PL99IMG.zip but it doesn't work.
Also tried to flash using fastboot but get a failed message too. Is the RUU compatible with my phone? I used it long time ago and it is all right it don't seems to work now.

finally got it. These are the steps if anyone is interested for CID044 devices.
1) Upgrade Hboot to using the files here
2) S-off using rumrunner.
3) downgrade to 1.41 hboot
4) download RUU from http://forum.xda-developers.com/showthread.php?t=2157029
5) Follow these instructions to update