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
Related
Hi,
If I check in fastboot I get CID 11111111 which I set myself during the setup of a custom ROM.
If I check with CID Getter application I get HTC__E11 my original CID.
Which one should I trust?
Also, anybody know if having a super CID would void the warranty? have to return my phone for repair so cleaning it up. All is different now is the CID.
Thanks a lot for your help!
saf_ro said:
Hi,
If I check in fastboot I get CID 11111111 which I set myself during the setup of a custom ROM.
If I check with CID Getter application I get HTC__E11 my original CID.
Which one should I trust?
Also, anybody know if having a super CID would void the warranty? have to return my phone for repair so cleaning it up. All is different now is the CID.
Thanks a lot for your help!
Click to expand...
Click to collapse
I would trust the one that you get it fastboot as the one you get from CID getter is the one that is in the build.prop of your ROM.
S-OFFing would void your warranty. You need S-OFF to set SuperCID so there. Connect the dots
thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,
saf_ro said:
thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,
Click to expand...
Click to collapse
YES! I meant S-OFF. That was embarrassing
I think you can just write CID just like how you SuperCID'd but writing proper CID instead of 11111111. I haven't done it myself so I can't help you there.
Just go to viper's thread here. He has instructions for S-ONing
http://forum.xda-developers.com/showthread.php?t=1192300
saf_ro said:
thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,
Click to expand...
Click to collapse
I think what you are searching for is
fastboot oem writecid ............ (Your cid)
Be sure to flash a proper ruu first, or you might end up bricking your device turning s on
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
dgenx210 said:
YES! I meant S-OFF. That was embarrassing
I think you can just write CID just like how you SuperCID'd but writing proper CID instead of 11111111. I haven't done it myself so I can't help you there.
Just go to viper's thread here. He has instructions for S-ONing
http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
yep, already got it working.
I guess in my case the writecid was not working because I was back to S-ON and no root anymore
So, I flashed again the 1.50.401.1 ROM WITHOUT accepting the update, S-off, root, change the CID, flash the 1.50.401.1 again, change back to S-ON with the writesecureflag 3. Device can go now to repair.
Thanks for the help, great forum and info sources!
I cannot boot into ROM, but stuck at Bootloader. And I'm relocked.
The only thing I have is Fastboot USB.
I would like to RUU into a Stock ROM. How to do so?
Well ruu should be pretty self explanatory. If you are in the boot loader just run the ruu. Since you are relocked shouldn't take much work. Are you s-off? Why not just grab an AT&T ROM and flash it over. Sure it will be rooted, but delete the super user app
Sent from my Carbon-ize Evita using xda-developers app
Yeah, I just figured it. RUU was some executable file. I thought it was more complicated. No I'll just leave it like this and not S-Off, thanks. Apparently I'm not more than 30% battery though. But how do I see the battery from the Bootloader screen?
I dont believe you can. Only from recovery. Just let it charge for about 20-30 mins and you should be good
Sent from my Carbon-ize Evita using xda-developers app
If you have supercid and s-on running a ruu will brick your phone just a warning
Sent from my HTC One X using Tapatalk 2
How do I check if I have SuperCID or not?
And apparently the device name is GT-9100 which seems wrong...?
There is command in fastboot I think it is fastboot get cid but not sure do you have a att phone
Sent from my HTC One X using Tapatalk 2
Nope, I do not. I do not need to worry about that then.
No you should be ok att phones are the only ones that had to change there cids to unlock bootloader
Sent from my HTC One X using Tapatalk 2
Fastboot oem readcid
Sent from my One X using xda app-developers app
exad said:
Fastboot oem readcid
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Thanks couldn't remember what it was
Sent from my HTC One X using Tapatalk 2
Oh no! Can anyone please help me?
None of the RUUs work.
I'm Asian and I tried all:
1.88.707.2 ( Error 170, bad USB )
2.23.707.2 ( Error 170 )
This is the only one that I could select ROM and upgrade.
3.17.707.1 ( Less than 30% error is result of previous fail, so reboot. Actual Error 155 )
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Aerodeath said:
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Click to expand...
Click to collapse
I thought if you ran the ruu with s on you could brick...just obtain s off and then run the ruu
Sent from my Carbon-ize Evita using xda-developers app
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Aerodeath said:
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Click to expand...
Click to collapse
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
exad said:
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
Click to expand...
Click to collapse
It's okay, I was running an international One XL, and luckily RUU was smooth, now the problem is solved and my phone has been sold and changed hands .
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
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.....
Ok, guys, i think that i made a big mistake, i was helping to restore to stock the HTC evita of a friend. We download the latest RUU from att, relocked and run. the problem was, that we didnt check it if there was super cid. and it have it. BUT, usually if there is a brick i cant enter to bootloader right? I can enter in bootloader, and show
Relocked
EVITA PVT SHIP S-ON RL
HBOOT- 2.18.0000
RADIO-1.35a.32.45.27
OPENDSP-v33.1.0.45.1127
eMMC-boot
Dec 3 2013,17,10,01:1
The phone has supecid: (bootloader) cid: 11111111
I know that usually is a brick, but i can enter the bootloader (i did a clearstorage but still bootloop) I dont want to make it worse. so any advice to fix it? I was thinking about unlocking again bootloader but probably it cause a brick? I read that the brick is unlocked bootloader + supercid +s-on, but the bootloader was relocket so maybe that save the device?. Any advice would be great
lorddavid said:
Ok, guys, i think that i made a big mistake, i was helping to restore to stock the HTC evita of a friend. We download the latest RUU from att, relocked and run. the problem was, that we didnt check it if there was super cid. and it have it. BUT, usually if there is a brick i cant enter to bootloader right? I can enter in bootloader, and show
Relocked
EVITA PVT SHIP S-ON RL
HBOOT- 2.18.0000
RADIO-1.35a.32.45.27
OPENDSP-v33.1.0.45.1127
eMMC-boot
Dec 3 2013,17,10,01:1
The phone has supecid: (bootloader) cid: 11111111
I know that usually is a brick, but i can enter the bootloader (i did a clearstorage but still bootloop) I dont want to make it worse. so any advice to fix it? I was thinking about unlocking again bootloader but probably it cause a brick? I read that the brick is unlocked bootloader + supercid +s-on, but the bootloader was relocket so maybe that save the device?. Any advice would be great
Click to expand...
Click to collapse
I think you need to unlock your bootloader and get S-off to proceed with RUU because you have superCid.
sathish804 said:
I think you need to unlock your bootloader and get S-off to proceed with RUU because you have superCid.
Click to expand...
Click to collapse
yes, the problem is that i cant load a rom, I mean, its bootloop. If i unlock bootloader and flash a recovery will be ok? I mean, i fear that unlocking bootloader brick my phone because I ran RUU with supercid
Unlock the bootloader again, flash TWRP recovery again, flash a custom ROM, get s-off, then you can run any RUU you want.
Sent from my Evita
ok, i unlock the bootloader, I'm trying to enter hboot again because the volumebutton ihave little damage. thanks If something happen i will report back.
PD: S-off can i do it with an aosp rom? Or need a sense rom?
It shouldn't really matter, I've done it on both.
Facepalm S-off
Sent from my Evita
Doesn't the Evita need to be s off to run a ruu, and with a locked bootloader?
Sent from my One X using Tapatalk
marknoll said:
Doesn't the Evita need to be s off to run a ruu, and with a locked bootloader?
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
No, but running any jb+ RUU with s-on and SuperCID causes a brick. Plus, if you have SuperCID, you need s-off to bypass the CID check that stops the RUU from running.
Sent from my Evita
timmaaa said:
No, but running any jb+ RUU with s-on and SuperCID causes a brick. Plus, if you have SuperCID, you need s-off to bypass the CID check that stops the RUU from running.
Sent from my Evita
Click to expand...
Click to collapse
Uff, finally, but TWPR is weird, flash a lot in splash screen :/ but after a while works. I was thinking that i had a brick because i was s-on and supercid. I had a aosp rom, so right now I will do s off. Thanks so much
PD: Right know is in the boot screen of PAC ROM. The hboot doesnt matter for an aosp rom right?
You probably need to read the Evita FAQ thread in my signature.
Sent from my Evita
timmaaa said:
You probably need to read the Evita FAQ thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
yes i did, is not the first time that i install a custom rom in a htc, i flash the boot.img and everything, but had some weird problems, I will try philz recovery now (TWPR sometimes flash a lot in the splash screen, or freeze or just works normal). and i will download another rom just to be sure.
Ok, its finnish, thanks so much. First the RUU close with an error, but i tried in another account of my pc and works (the same error was before when everything start, is funny, maybe thats save my phone from a brick because I was s-on with supercid :/ )
Thanks so much again for the help