Database Info

[Q] My CID is 11111111 and my HBOOT is 1.14.0002

What am I able to do with those in terms of roms and kernels?

doesn't matter for ROMs, but kernels and radios can't be flashed through recovery on that hboot.

Cid just means you're rooted. Your hboot means you can flash kernels and ROMs with an extra step. You'll have to fastboot flash the boot.img then install the .zip from twrp.
To save you from doing that, you can downgrade your hboot and then RUU downgrade to 1.85 so you can flash a radio. Go to the eMMC JET tool in the android dev forum if you want to downgrade your hboot.
Sent from my One X using xda app-developers app

Myrder said:
Cid just means you're rooted. Your hboot means you can flash kernels and ROMs with an extra step. You'll have to fastboot flash the boot.img then install the .zip from twrp.
Click to expand...
Click to collapse
I've had a good amount of luck with Aroma installers taking care of the boot.img flashing for me. Between CleanRom and BeastKernel, I only had to flash the zips from twrp.

Instead of creating a new thread, I thought I'd just bump this one.
Anyway, just bought a used AT&T HTC One XL and it has CID: 11111111 and S-ON. I need to update my HBOOT so I can run CM10. I just want to know what exact firmware/HBOOT to use so I can use the phone.
Thanks in advance!

The easiest thing to do would be to s-off. Then you can flash whatever you want.
Sent from my HTC One X using xda premium

You shouldn't need to update your hboot to run cm10 but I'd be lying if I said I hadn't encountered people with phones that wouldn't boot cm10 unless they updated to the 2.14 HBOOT.
Bear in mind on the 1.14 hboot, you need to extract the boot.img from the rom and flash it using fastboot before most roms will boot. If it still doesn't boot or you don't like the idea of flashing boot.img separately every time you flash a rom then yes I would agree to S-OFF and use the 3.18 ruu.
Sent from my One X using xda app-developers app

ratsack said:
Instead of creating a new thread, I thought I'd just bump this one.
Anyway, just bought a used AT&T HTC One XL and it has CID: 11111111 and S-ON. I need to update my HBOOT so I can run CM10. I just want to know what exact firmware/HBOOT to use so I can use the phone.
Thanks in advance!
Click to expand...
Click to collapse
Thank you for not creating a new thread. Let everyone else said, it would be wise to do s off while you are this far.
Sent from my Carbon-ize Evita using xda-developers app

I think it is my old HBoot as it's doing the same thing my wife's HTC One X did the other day when I tried to put CM10 on it. Updating HBoot fixed that.
I can't boot into Android as it isn't working. Is there a way to S-Off (that's easy) where I don't need to boot into Android? All I really want is to update HBoot and I'll be happy.
---------- Post added at 01:44 AM ---------- Previous post was at 12:48 AM ----------
Well, I think the issue was I that I wasn't using the correct recovery to flash the CM10 & GApps. Was using the recovery for a One X, not XL. Put the correct recovery on and now I'm typing this message on my phone. Yay!
Thanks for the help peoples! Now to find out how to remove the red text on start-up!
Sent from my One X using Tapatalk 2

Help with RUU'ing to 2.20

I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.

You need to S-off first.
Sent from my HTC One X using xda premium

tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?

Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium

Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/

Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium

Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?

Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium

Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error

dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium

31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....

dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium

Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?

For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.

knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita

Softbricked(?) Rogers

I recently tried to flash CM10 onto my Rogers One X through TWRP 2.3.3.1 but it's been stuck on the bootloader so now I don't have a working OS. I've been trying to figure out how to either fix that or go back to stock through RUU I can't find the correct RUU for that.
**Relocked**
Evita PVT SHIP S-ON RL
Hboot -2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26
So far I've tried
Flashing TWRP 2.6 on, clearing cache/devlek/system then flashing CM10

Every phone is different. You should always read the stickies prior to doing anything even if you think you know what you're doing.
With 2.14 hboot and s-on you need to fastboot flash boot boot.img where the boot.IMG is extracted from the rom. This phone has a few quirks so I suggest reading more or you may find out the hard way.
Typically I ignore these questions but I was feeling nice today. Please also remember that the rules on xda are to search before asking so you are also in violation of xda rules.
Good luck.
Sent from my One X using xda app-developers app

I'll assume the attempted flash of TWRP 2.6 failed, since your bootloader is relocked.

redpoint73 said:
I'll assume the attempted flash of TWRP 2.6 failed, since your bootloader is relocked.
Click to expand...
Click to collapse
His last line shows that he flashed cm 10 in twrp 2.6 he relocked to try ruuing but there is no rogers ruu for that fw
Sent from my One X using xda app-developers app

[Q] cant ruu 3.18 or s-off my phone

first thing, sorry for my bad english
I have my att hox from an order version from 1.17 or something like that. i tried to upgrade my hboot by ruu but i got an error 158 image error right at the process of updating signature (relocked my bootloader). Then i tried to s-off by using the facepalm method but no luck.
I'm trying to install android revolution hd 31.0 but i got stuck at 30% or the older 22.0 at 30% as well and viperxl 3.8.0 final so im using 3.28 viperxl and cyn 10.1
I downloaded the RUU 3.18(cingular) directly from htc webside
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v31.1.0.45.0815
eMMC-boot
cid is 11111111
any help will be greatly appreciated!!!

Flash twrp 2.6 (make sure for evita)
Wipe everything except SD card
Flash any sense rom for evita
Soff
Ruu
Sent from my One X using xda app-developers app

thanks for fast reply!!!
Im gonna try it now

You mentioned trying to install Android Revolution, don't do that, it's not for our phone. You need to stay in this device forum that you're posting in or you'll flash something that'll brick your phone.
Sent from my Evita

oh i didnt know that
Somehow i cant use adb on sense rom, only with cyn
i tried a few times already but still s-on no matter what.

What happens?
Sent from my One X using xda app-developers app

I installed the twrp 2.6.0 then tried to install cleanrom and viperxl to s-off but still s-on
I followed the steps n got the same 92 error but still s-on after bott my phone into boot loader

OK.. Paste your cmd so I can see
Sent from my One X using xda app-developers app

Im on viperxl now and i stuck at the adb device offline thing again
tried adb kill/start-server but no luck

phongduong93 said:
Im on viperxl now and i stuck at the adb device offline thing again
tried adb kill/start-server but no luck
Click to expand...
Click to collapse
press and hold power until the phone shuts off then turn it back on and try again.

exad said:
press and hold power until the phone shuts off then turn it back on and try again.
Click to expand...
Click to collapse
still the same, i also tried that with adb kill/start-server
it was working fine with cleanrom after adb kill/start-server

Is HTC sync running? If so make sure it isn't. I remember I had this issue too once.. I can't remember how I fixed it now...
I think I just changed usb ports rebooted the pic and phone etc.
Sent from my One X using xda app-developers app

thanks for the helps i really appreciated but i no longer own the device.

Wrong posts -

quentin2260 said:
Hi !
Your wifi fix (Tesco ION 3.2.0) in the first page doesn't work with my phone because it's S-ON.
How can I flash this fix with my S-ON (its difficult to flash kernel with S-ON) ?
Click to expand...
Click to collapse
Why don't you just get s-off? And what fix are you talking about? Are you posting in the right thread?
Sent from my Evita.

[Q] T-mobile got bootloop after s-off

Greetings all. Please help.
S4, T-mobile (TMOUS)
What i have done:
+ debranding PJ4011000->PJ4010000
+ SuperCID 11111111
+ S-OFF by facepalm, moonshine, rumrunner
I try every kind of s-off and as a result: Bootlooping phone (black desktop, and in a minute - system restart)
Checked on RUU 2.31,2.35, 3.14, ViperOneS, CM10.
If i get S-ON, RUU firmware works fine
Please help, how can i get everything works?

NewbieFound said:
Greetings all. Please help.
S4, T-mobile (TMOUS)
What i have done:
+ debranding PJ4011000->PJ4010000
+ SuperCID 11111111
+ S-OFF by facepalm, moonshine, rumrunner
I try every kind of s-off and as a result: Bootlooping phone (black desktop, and in a minute - system restart)
Checked on RUU 2.31,2.35, 3.14, ViperOneS, CM10.
Please help, how can i get everything works?
Click to expand...
Click to collapse
Are you s-off or not?
Sent from my Nexus 4 using Tapatalk

nicknc said:
Are you s-off or not?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Forget to mention one thing, while system boot, there is no sim card datection (sim insert) and no sim card logo, if sim is out)
At this moment i have:
Unlocked
S-OFF
CID-11111111
Hboot 2.15
Radio 1.11
OpenDSP-v.31-1.0
eMMC-boot

NewbieFound said:
Forget to mention one thing, while system boot, there is no sim card datection (sim insert) and no sim card logo, if sim is out)
At this moment i have:
Unlocked
S-OFF
CID-11111111
Hboot 2.15
Radio 1.11
OpenDSP-v.31-1.0
eMMC-boot
Click to expand...
Click to collapse
Lock your boot loader and RUU to RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2
I know it's a TMOUS ruu, but it is reliable and you won't be keeping it.
After that, you should still be s-off, so unlock bootloader again, fastboot TWRP 7.0.0.8, root and then press forward with whatever ROM you want to use.
Sent from my Nexus 4 using Tapatalk

nicknc said:
Lock your boot loader and RUU to RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2
I know it's a TMOUS ruu, but it is reliable and you won't be keeping it.
After that, you should still be s-off, so unlock bootloader again, fastboot TWRP 7.0.0.8, root and then press forward with whatever ROM you want to use.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for help.
I've installed RUU_Ville_U_JB_45_S_TMOUS_3.14 - still black desktop and reboot after 30 seconds Should RUU work fine on S-OFF?

NewbieFound said:
Thank you for help.
I've installed RUU_Ville_U_JB_45_S_TMOUS_3.14 - still black desktop and reboot after 30 seconds Should RUU work fine on S-OFF?
Click to expand...
Click to collapse
Yes, RUU works fine on s-off
What do you mean by "black desktop"?
Sent from my Nexus 4 using Tapatalk

nicknc said:
Yes, RUU works fine on s-off
What do you mean by "black desktop"?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Photo of my phone after RUU:
http://imgur.com/PWtgmA9
Bootloader:
relocked
s-off
cid-11111111
hboot 2.15
radio 1.13
Same result i get after installing ViperOneS or CM10, or any other RUU

NewbieFound said:
Photo of my phone after RUU:
http://imgur.com/PWtgmA9
Bootloader:
relocked
s-off
cid-11111111
hboot 2.15
radio 1.13
Same result i get after installing ViperOneS or CM10, or any other RUU
Click to expand...
Click to collapse
But recovery works, right?
Sent from my Nexus 4 using Tapatalk

nicknc said:
But recovery works, right?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
What do you mean by "recovery works"?
I can install any RUU (tmous/europe) or custom (viperones) - no errors. But nothing phone doesn't work after install.

NewbieFound said:
What do you mean by "recovery works"?
I can install any RUU (tmous/europe) or custom (viperones) - no errors. But nothing phone doesn't work after install.
Click to expand...
Click to collapse
So with s-on, your phone works normally, right?
How are you achieving s-off?
NewbieFound said:
What do you mean by "recovery works"?
I can install any RUU (tmous/europe) or custom (viperones) - no errors. But nothing phone doesn't work after install.
Click to expand...
Click to collapse
Sent from my Nexus 4 using Tapatalk

nicknc said:
So with s-on, your phone works normally, right?
How are you achieving s-off?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
1. With S_ON RUU works fine, i haven't checked it on viperones or cm modes
2. In past week i try:
- moonshine
- rumrunner
- facepalm
each of them get me S-OFF, and bootloop

NewbieFound said:
1. With S_ON RUU works fine, i haven't checked it on viperones or cm modes
2. In past week i try:
- moonshine
- rumrunner
- facepalm
each of them get me S-OFF, and bootloop
Click to expand...
Click to collapse
Some phones can't seem to s-off. Maybe you're in that group.
Sent from my Nexus 4 using Tapatalk

nicknc said:
Some phones can't seem to s-off. Maybe you're in that group.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for help!
Okay, if my phone can't be s-off, can i install viperones, then retrun S-ON, and if i don't like viper install RUU again? (in other words, can i install RUU on custom roms while S-ON?)

NewbieFound said:
Thank you for help!
Okay, if my phone can't be s-off, can i install viperones, then retrun S-ON, and if i don't like viper install RUU again? (in other words, can i install RUU on custom roms while S-ON?)
Click to expand...
Click to collapse
You're welcome, feel free to hit the thanks button.
As for flashing ruu's while s-on, the short answer is yes. However, you don't need to flash a RUU every time you want to change Roms. You can just wipe between and flash away.
Lastly, be sure to update your radio before going back to s-on. It makes it much easier.
Sent from my Nexus 4 using Tapatalk

nicknc said:
Lastly, be sure to update your radio before going back to s-on. It makes it much easier.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Well I installed ViperOneS and go S-ON, and only then read FAQ and remembered about radio 1.20
Right now i'm s-ON on radio 1.13
Where can i found some info about 1.35 and 1.20 radio's?

NewbieFound said:
Well I installed ViperOneS and go S-ON, and only then read FAQ and remembered about radio 1.20
Right now i'm s-ON on radio 1.13
Where can i found some info about 1.35 and 1.20 radio's?
Click to expand...
Click to collapse
Start in the radio thread.
Sent from my Nexus 4 using Tapatalk

nicknc said:
Start in the radio thread.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Could you be so kind and share a link. I found only guides/how to, but couldn''t find thread where there is comparison between 1.20 and 1.35 radio

http://forum.xda-developers.com/showthread.php?t=2709164 is the link for the 1.35 radio. This supposedly only works for non-us markets
For 1.20, which works for all, search the android development forum. I believe it is in there.
Sent from my Nexus 4 using Tapatalk