Hello My Dear Learners & Teachers....:angel:
my question is my At&t HOX is on 4.0.3 ICS Wanted To Install JB i went to htc site and got the RUU Link
(RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial)
The Filename mentioned ... want to know is it correct RUU for my At&t HOX?
My Current Info is
Software Number "1.85.502.3" | Radio 0.17.32.09.12 | Hboot 1.09.0000
That is the right RUU for the AT&T version.
Is your phone stock or modded?
xoreg93 said:
Hello My Dear Learners & Teachers....:angel:
my question is my At&t HOX is on 4.0.3 ICS Wanted To Install JB i went to htc site and got the RUU Link
(RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial)
The Filename mentioned ... want to know is it correct RUU for my At&t HOX?
My Current Info is
Software Number "1.85.502.3" | Radio 0.17.32.09.12 | Hboot 1.09.0000
Click to expand...
Click to collapse
If you have Super CID, do not run the RUU. It will brick your phone.
If you're not sure, type the following command into your command line:
fastboot oem
readcid
redpoint73 said:
That is the right RUU for the AT&T version.
Is your phone stock or modded?
Click to expand...
Click to collapse
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
If you have Super CID, do not run the RUU. It will brick your phone.
Click to expand...
Click to collapse
If the phone is s-on, yes that is right.
First of All Thanksss
yeahhhh its S-on
and please let me know why super cid will brick?? I thought super cid means any ruu will work..lol :silly:
and no mine is not super cid ... so I will upgrade it. :highfive:
SuperCID just means that at&t phones were able to unlock via htcdev because the at&t CID was blocked. SuperCID + s-on + jb RUU = brick. This is because a CID check that occurs halfway through the RUU update doesn't allow the RUU to finish, therefore ending up with a partially completed RUU, which means a bricked phone.
Sent from my Evita
xoreg93 said:
and please let me know why super cid will brick?? I thought super cid means any ruu will work..lol :silly:
Click to expand...
Click to collapse
What timmaaa mentioned is basically a bug. The RUU shoudn't run halfway like that, but for some reason on JB RUUs, it does (past RUUs were fine with SuperCID).
But also, what you said above is not true. SuperCID will not allow "any" RUU to work. It only bypasses CID check. Trying to run a RUU for an older hboot will fail version check. You need s-off to run "any" RUU.
thanksssss ALL Update Successful.....
Related
Hi,
I'm trying to go to the stock rom because I have to return my phone because I have battery problems and dust behind my screen.
But when I try to flash a stock rom it doesn't work. It says that I using the wrong image update.
Current image is 1.11.401.110 and I want to go to the lastest stock rom 3.32.401.105
What do I have to do?
Thanks
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
gol_n_dal said:
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
Click to expand...
Click to collapse
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
OK I don't understand where 1.11.401.110.... figures in the situation. If I understand correctly that is a custom ROM based off a different platform with Sense 4.0. Probably wrong though..
Are you fully S-OFF (clutching at straws here). Assuming you are you should be able to install an RUU easily. I recently went from 3.32.161.... to 3.32.401.. then back to 1.27.161... with no issues at all.
I'm sure someone more able than me can help you here.
GL
tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
ok you are SOFF seeing that you have revolutionary HBOOT ..
so when returning stock ...its better to flash the correct stock...which can be found using CID
but as you have supercid now ...you need to know your original cid or the carrier/country the phone is linked to ..for finding the proper stock RUU
this guide helps you in fiding the proper stock RUU and it has flashing instructions too
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Install "cid getter" from the market.
AFAIK the entry for "ro.cid" should tell you your original CID.
e.g. It says VODAP001 for me while "fastboot getvar cid" gives "11111111".
tommeke19 said:
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Click to expand...
Click to collapse
from which country you bought the phone from and to which carrier it is linked to ?
Thanks everyone for helping me, but after using google I've found a site and found the solution.
Will at&t ruu 2.20.502.7 will work on supercid 1111111 at&t hox to get back to stock?
I am having at&t htc one x bootloader with :
**** tampered ****
**** unlocked ****
evita pvt shp s-on rl
hboot-1.09.0000
radio-0.19as.32.09.09_l
opendsp-v28.1.0.32.0504
emmc-boot
apr 2 2012,21:08:24
installed twrp 2.2.0 recovery and stock rooted rom 2.23707.2 asia generic.
Now the problem is, i am facing the mobile signal(not wifi) dropping issues and i have to revert back to at&t stock rom, i have downloaded the official at&t ruu 2.20.502.2.....exe,
but i am concerned with the doubt that will the ruu will work 100% on supercid 111111 without any problem after relocking the bootloder or do i have to revert back the stock at&t cid, and if yes then what is the procedure to revert back the stock at&t cid???????
If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios
gunnyman said:
If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios
Click to expand...
Click to collapse
thanks for the help,appreciable. But i don't want to flash just the radio, coz i already did that, but it did not solve my problem. So the question still continues..Can i run Ruu with the current supercid 111111 or do i have to revert it back to stock???
SORRY FOR BAD ENGLISH. ITS NOT MY FAMILIAR LANGUAGE.
You don't have to change cid to flash the ruu just relock the bootloader
gunnyman said:
you don't have to change cid to flash the ruu just relock the bootloader
Click to expand...
Click to collapse
thanks for the help,
Are you already on 2.20? If not, why not run 1.85 RUU?
thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
good question.
thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
Doesn't look like the op is on 2.20, the hboot for 2.20 is 1.14.0002.
Absolutely Right, i am not on 2.20,
Sent from my HTC One XL using xda app-developers app
Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app
hemsmaverick said:
Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app
Click to expand...
Click to collapse
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.
gunnyman said:
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.
Click to expand...
Click to collapse
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.
hemsmaverick said:
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.
Click to expand...
Click to collapse
won't work because RUU's include a signature check and if you alter the files in any way, that signature check will fail.
gunnyman said:
won't work because ruu's include a signature check and if you alter the files in any way, that signature check will fail.
Click to expand...
Click to collapse
ok, well as per ur earlier suggestion, i have flash the radio incl ril files from at&t 1.85, asia 2.23, currently on a o2 2.29.
But signal dropping solution has not been resolved.
I have dropped the plan of running ruu and will install custom rom tn special edition 3.6
can u suggest me the best radio for better mobile signals? (i am from india -region asia)
I HAVE MADE A NEW THREAD PLEASE REPLY THERE LINK BELOW
http://forum.xda-developers.com/showthread.php?t=2264388
So long story short -
Basically I deleted my OS and installed a custom until I was able to find a compatible RUU The only probelm is my hboot (Details Below)
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
So can any help me find a RUU. And if you can't will I have to
1)SuperCID
2)S-OFF
Then flash a lower RUU
Im On JellyBean 4.1.1
Running Pacman Rom For Htc One S
Im Branded To THREE UK
Thanks All Help Aprriciated
running S4 processor krait
At the moment, there is no compatible RUU. You might want to S-OFF and run a lower RUU, then update.
usaff22 said:
At the moment, there is no compatible RUU. You might want to S-OFF and run a lower RUU, then update.
Click to expand...
Click to collapse
can this in anyway brick my phone via ota updates etc ...? and will my phone be unbranded
i also have to superCID my phone then do the s off right ? thanks
Zaman-The-Man said:
can this in anyway brick my phone via ota updates etc ...? and will my phone be unbranded
i also have to superCID my phone then do the s off right ? thanks
Click to expand...
Click to collapse
Do NOT run OTA while SuperCID, you may brick it.
Get supercid and then s-off, yes.
But flashing ota With supercid can brick your phone.
Change your cid to e.g. HTC__001 if you are in europe before flashing ota.
Sent from my HTC One S using xda premium
NQNH said:
Get supercid and then s-off, yes.
But flashing ota With supercid can brick your phone.
Change your cid to e.g. HTC__001 if you are in europe before flashing ota.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
so il never be able to update my phone again ? OTA and RUU Updates
i want to go back to stock using ruu as i deleted my OS
after doing supercid then s off i can run a lower ruu but i wont to ota update my phone as i need otg and it doesnt work on ICS so i need jellybean and will my phone be SIM UNLOCKED
Zaman-The-Man said:
i want to go back to stock using ruu as i deleted my OS
after doing supercid then s off i can run a lower ruu but i wont to ota update my phone as i need otg and it doesnt work on ICS so i need jellybean and will my phone be SIM UNLOCKED
Click to expand...
Click to collapse
Just flash the beastmode kernel for otg on ics.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
ryanshew said:
Just flash the beastmode kernel for otg on ics.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Click to expand...
Click to collapse
i want jellybean though and i heard as soon as you s off and do superCID you phone becomes unbranded so couldnt i run a unbranded jelly RUU ?
Zaman-The-Man said:
i want jellybean though and i heard as soon as you s off and do superCID you phone becomes unbranded so couldnt i run a unbranded jelly RUU ?
Click to expand...
Click to collapse
SuperCID allows you to run any RUU. However, there have been reports of devices getting bricked whilst updating to Jelly Bean with SuperCID, so I would recommend setting your CID to HTC__001.
Sent from my HTC One S using Tapatalk 2
usaff22 said:
SuperCID allows you to run any RUU. However, there have been reports of devices getting bricked whilst updating to Jelly Bean with SuperCID, so I would recommend setting your CID to HTC__001.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Isn't there a RUU That Has The Jellybean Software ?
Zaman-The-Man said:
Isn't there a RUU That Has The Jellybean Software ?
Click to expand...
Click to collapse
Yes.
so i am S - OFF and need to run a RUU (long Story)
so when i ran the RUU it said please download the right rom utility update
this is the one i ran http://bugsylawson.com/files/file/3...00528-10275008l-release-301814-signed-2-4exe/
and i changed my CID to HTC__001 and also i can change back to SuperCID 11111111
i heard you have to have a ruu which is lower than your HBOOT my HBOOT:2.13.0000
what shall i do please ould someone help thanks
Zaman-The-Man said:
so i am S - OFF and need to run a RUU (long Story)
so when i ran the RUU it said please download the right rom utility update
this is the one i ran http://bugsylawson.com/files/file/3...00528-10275008l-release-301814-signed-2-4exe/
and i changed my CID to HTC__001 and also i can change back to SuperCID 11111111
i heard you have to have a ruu which is lower than your HBOOT my HBOOT:2.13.0000
what shall i do please ould someone help thanks
Click to expand...
Click to collapse
Since you are Soff I don't think it matters what hboot it is. You just have to run the RUU that matches the CID. May want to double check, but that has been my experience. Once you are Soff it's easy to switch CID.
Sent from my HTC VLE_U using xda app-developers app
npiper05 said:
Since you are Soff I don't think it matters what hboot it is. You just have to run the RUU that matches the CID. May want to double check, but that has been my experience. Once you are Soff it's easy to switch CID.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
my cid is HTC__001 so shall i run the latest unbranded RUU could you link be to the latest unbranded RUU ? i dont trust my self
Zaman-The-Man said:
my cid is HTC__001 so shall i run the latest unbranded RUU could you link be to the latest unbranded RUU ? i dont trust my self
Click to expand...
Click to collapse
Sending you a PM now
I have been trying to run a RUU to unroot the phone before I bring it in for a repair. I keep getting the 155 error and I searched through google for help on the error. I have read a few post about it but nothing works. I tried to run it through fastboot as well and that does not work. My phone information while in bootloader is Evita pvt ship s-on rl hboot 1.09.0000 radio .17.32.09.12 and I am running cleanrom v 6.5 as my rom. Since my rom and boot.img is based of 3.18 I tried to run the ruu on 3.18. Im not sure if its because it is an older verdion of bootloader while im running a rom that is based off the 3.18. So I also tried to flash a older rom and run the ruu for 1.73 but that didnt work either. Im stumped and very frustrated so please I need your help.
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Arrow44 said:
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah for the 3.18 its http://bugsylawson.com/HTCFiles/Evi....24p.32.09.06_10.130.32.34_release_signed.exe
and for the 1.73 its http://www.ponack.net/designgears/b...73.502.2_2FE6772699D8596307CC997452BB8D25.exe
Also I read that in order to use the RUU correct I need to soff the phone, but then I cant upgrade the firmware to jellybean. Do you know if this is correct?
The phone will brick if you try to ruu or update to 3.18 while S-ON and superCID. Your CID right now, no doubt is 11111111. When the RUU runs it checks to see what your CID is, if it's not what it should be, it gives an error. If you change your CID back to CWS__001 you can run the 1.73 RUU but you can never update to 3.18 unless you S-OFF first or you'll brick.
to check your CID fastboot oem readcid.
You can change it once without S-OFF with fastboot oem writecid CWS__001 but you can't change it again with that command unless you're S-OFF
Arrow44 said:
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
exad said:
The phone will brick if you try to ruu or update to 3.18 while S-ON and superCID. Your CID right now, no doubt is 11111111. When the RUU runs it checks to see what your CID is, if it's not what it should be, it gives an error. If you change your CID back to CWS__001 you can run the 1.73 RUU but you can never update to 3.18 unless you S-OFF first or you'll brick.
to check your CID fastboot oem readcid.
You can change it once without S-OFF with fastboot oem writecid CWS__001 but you can't change it again with that command unless you're S-OFF
Click to expand...
Click to collapse
Ok thanks. Im in the process of doing the S-OFF right now. What I want to do is get rid of the red text and make my phone look like the bootloader is locked and never tampered with. I remember doing this with my EVOLTE so it will look like the phone is S-ON and locked. After all that run the RUU for 2.20 so it can get repaired. Now after the repair I can root again and upgrade to the Jellybean firmware right?
cables2590 said:
Ok thanks. Im in the process of doing the S-OFF right now. What I want to do is get rid of the red text and make my phone look like the bootloader is locked and never tampered with. I remember doing this with my EVOLTE so it will look like the phone is S-ON and locked. After all that run the RUU for 2.20 so it can get repaired. Now after the repair I can root again and upgrade to the Jellybean firmware right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2156368