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
Related
So, I have done a lot of research and I am hung up on one bit.
I have the stock RUU file on my PC.
I also have superCID . I am rooted with S-OFF
Think i used Revolutionary etc. Currently using ARHD 6.8.0
I want to return to Full Stock with S-ON. I looked at this guide: http://forum.xda-developers.com/showthread.php?t=1192300
But it doesn't say if I need to change my CID back to VODAP001 before or after (Or at all) I flash the Stock RUU. <hope that makes sense?
Could anyone help me?
I basically have the RUU. and need to know about the CID. Does it need to be changed?
Thanks
Just seen this actually
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.
pike0 said:
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.
Click to expand...
Click to collapse
Hi,
If you are returning your phone for warranty purposes,you need to return your SuperCID to normal.
This should be done after running your RUU,but before going back to s-on.
Look HERE for more information.
pike0 said:
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.
Click to expand...
Click to collapse
you can flash any ruu when you have supercid(that means S-OFF also)
this guide will help you more
http://forum.xda-developers.com/showthread.php?t=1672425
but read carefully about returning to S-ON
rzr86 said:
you can flash any ruu when you have supercid(that means S-OFF also)
this guide will help you more
http://forum.xda-developers.com/showthread.php?t=1672425
but read carefully about returning to S-ON
Click to expand...
Click to collapse
Cool, well the RUU I have will need the VODAP001 *** (I think it's that, will check before I attempt lol)
So I flash the RUU then I can use this:
Code:
fastboot oem writecid ******* Replacing the *'s with the CID I need.
Once done, can then return to S-ON
pike0 said:
Cool, well the RUU I have will need the VODAP001 *** (I think it's that, will check before I attempt lol)
So I flash the RUU then I can use this:
Code:
fastboot oem writecid ******* Replacing the *'s with the CID I need.
Once done, can then return to S-ON
Click to expand...
Click to collapse
also about S-ON read carefully what it is saying about bootloader
your bootloader must be LOCKED, RELOCKED or UNLOCKED otherwise don't do S-ON
rzr86 said:
also about S-ON read carefully what it is saying about bootloader
your bootloader must be LOCKED, RELOCKED or UNLOCKED otherwise don't do S-ON
Click to expand...
Click to collapse
Was just about to post. Successfully flashed the RUU and changed CID to VODAP001, phone boots and works fine!!!
But in bootloader it doesn't mention, locked, unlocked or relocked.
Previously to the Update, it said ***LOCKED***
Now I got just this:
Pyramid PVT Ship S-OFF RL
HBOOT-1.17.0006
RADIO-10.11.9007.09_M2
eMMC-boot
What do I need to do to S-ON???
Thanks
pike0 said:
Was just about to post. Successfully flashed the RUU and changed CID to VODAP001, phone boots and works fine!!!
But in bootloader it doesn't mention, locked, unlocked or relocked.
Previously to the Update, it said ***LOCKED***
Now I got just this:
Pyramid PVT Ship S-OFF RL
HBOOT-1.17.0006
RADIO-10.11.9007.09_M2
eMMC-boot
What do I need to do to S-ON???
Thanks
Click to expand...
Click to collapse
if your bootloader says locked now(as you are mentioning) then you can continue with S-ON
edit:what to do for S-ON?
from the same guide it has a tutorial for it
but i think it is a simple command and then you are done
rzr86 said:
if your bootloader says locked now(as you are mentioning) then you can continue with S-ON
edit:what to do for S-ON?
from the same guide it has a tutorial for it
but i think it is a simple command and then you are done
Click to expand...
Click to collapse
Sorry, I actually mean, before I restored the RUU it said locked. Now it doesnt mention anything.
It no longer says that, or unlocked / relocked.
So I haven't proceeded with the S-ON command.
pike0 said:
Sorry, I actually mean, before I restored the RUU it said locked. Now it doesnt mention anything.
It no longer says that, or unlocked / relocked.
So I haven't proceeded with the S-ON command.
Click to expand...
Click to collapse
hmm,
i don't know about that
it is better to ask for that in the ruu thread
someone will know
rzr86 said:
hmm,
i don't know about that
it is better to ask for that in the ruu thread
someone will know
Click to expand...
Click to collapse
Say I still have S-OFF but everything else is back to stock. What steps would I need to take to root, custom recovery & ROM again?
Thanks
pike0 said:
Say I still have S-OFF but everything else is back to stock. What steps would I need to take to root, custom recovery & ROM again?
Thanks
Click to expand...
Click to collapse
Hi,
Flash recovery of choice.
Flash root.
Flash custom ROM.
malybru said:
Hi,
Flash recovery of choice.
Flash root.
Flash custom ROM.
Click to expand...
Click to collapse
Recovery is the PMG...zip is that correct?
Thanks for all the help
pike0 said:
Recovery is the PMG...zip is that correct?
Thanks for all the help
Click to expand...
Click to collapse
Hi,
Look HERE
2. Flashing a recovery
4A. Flashing Root
malybru said:
Hi,
Look HERE
2. Flashing a recovery
4A. Flashing Root
Click to expand...
Click to collapse
Many thanks! Would it make a difference if my phone is already S-OFF??
pike0 said:
Many thanks! Would it make a difference if my phone is already S-OFF??
Click to expand...
Click to collapse
Hi,
No.
If you ran a RUU,then,everything would have returned to stock.
S-off is not affected.
So,to get back up and running,you will need to do all these things again.
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 .
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
I'm not new to the whole android scene since I do all this stuff on my s3, but I've been trying to flash custom roms and what not on my friend's One X and I've been having noo luck at all. Can someone guide me with the whole process?
It seems a bit more complicated cause I have to unlock bootloaders and supercid and s-off etc, and I don't know how to do any of that,
So far, I unlocked the bootloader, rooted, and installed TWRp recovery. But every ROM I try to flash doesn't boot up, or gets stuck at the HTC logo. Help please!
Please provide your bootloader details.
Sent from my Evita
timmaaa said:
Please provide your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Uhh, not sure what you're looking for but..
s-on
hboot 2.14
radio 0.23a. 32.09.29
Well, I think with what I've been reading, I need supercid and s-off. How do I do that? I know s is on but how can I check if I have supercid?
"fastboot oem readcid" is the command to get your CID. What ROMs are you trying to flash?
Sent from my Evita
I was s-off already before and somehow it shows s-on now. I've tried rumrumner, revone, and firewater. They all success but it doesn't show s-off on the bootloader. On firewater it shows there really isn't a helluva lot to do here. bye bye. Which I use google and found that it means I have s-off already. Could it be a bootloader problem? I tried fastboot getvar all and it shows s-on.
It's cos you followed the install guide of insertcoin and flashed the hboot that was suggested.. That boot is a modded one by cmviennau am guessing which hides s-on and removes tampered flag etc
Braddison said:
It's cos you followed the install guide of insertcoin and flashed the hboot that was suggested.. That boot is a modded one by cmviennau am guessing which hides s-on and removes tampered flag etc
Click to expand...
Click to collapse
Sorry for late reply. I tried to flash a fuu to upgrade firmware and it failed. So I took the att ruu and then I took the ota to upgrade to kit kat firmware (hboot 2.22). Are there anything I could do?
It also shows tempered so I don't think it's a hboot that I flashed. Could it be bootloader issue?
Hmm? Well if it's shown as s-on but you are In fact s-off surely that's a bonus?
Try an app that requires s-off to check if you are, or maybe try supercid as you need s-off for that. That's all can suggest.
Braddison said:
Hmm? Well if it's shown as s-on but you are In fact s-off surely that's a bonus?
Try an app that requires s-off to check if you are, or maybe try supercid as you need s-off for that. That's all can suggest.
Click to expand...
Click to collapse
Yup, I have s-off and are there any hboot that will show s-off that I could flash? I know that I got s-off because I was able to change cid.
Edit: It also doesn't show the deveoper purpose thing. I didn't flash any hboot. This is like amazing. I don't know what to say. I didn't flash any different hboot after taking the at&t 4.4.2 ota.