Database Info

[Q] Upgrade hboot to stop navigation from crashing...

I've heard that people on hboot 1.14 aren't having problems with the navigation... For me, this has always been a problem from day one... How can I upgrade my hboot? Probably this is a noob question, but I couldn't find any tutorial... Thanks

I doubt that is causing the problem. HBOOT has nothing to do with software running on the phone.
Sent from my HTC One S using Tapatalk 2

usaff22 said:
I doubt that is causing the problem. HBOOT has nothing to do with software running on the phone.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
That's not exactly true. We've seen it happen in the CM10 thread where there were different behaviors with different hboots.

dc211 said:
That's not exactly true. We've seen it happen in the CM10 thread where there were different behaviors with different hboots.
Click to expand...
Click to collapse
HBOOT may not be causing the problem, could be anything from SBL1,2 and 3 to adsp. New software versions have different radios, HBOOTs, etc.

Already tried different radios, I'm on CM10. This has been a issue for many people... Check out this
http://code.google.com/p/cyanogenmod/issues/detail?id=6611
and read comment 3 by intervigil... he says " For what it's worth, I and others on HBOOT/firmware 1.14 do not have this issue. "
That's why I want to try hboot 1.14...

HBOOT gets upgraded by running a newer RUU than installed.
Which version are you on? Which HBOOT do you currently use?
By the way, found out something funny:
I was on 1.14.0001 and 2.31 HTC ROM .. I downgraded HBOOT to 1.06 (tried something), then flashed 2.31 RUU again, it upgraded HBOOT to 1.14.0002.

andryyyy said:
HBOOT gets upgraded by running a newer RUU than installed.
Which version are you on? Which HBOOT do you currently use?
By the way, found out something funny:
I was on 1.14.0001 and 2.31 HTC ROM .. I downgraded HBOOT to 1.06 (tried something), then flashed 2.31 RUU again, it upgraded HBOOT to 1.14.0002.
Click to expand...
Click to collapse
I'm on hboot 1.13... but what is the RUU? It's like making the phone factory default correct? Where I can find it? Sorry for the noob questions...:laugh:

No problem
Use this app to tell us your CID. It is written at the top.
RUU files are official HTC firmware tools, which reset your phone and update your Android.
And please tell us which version you are using: Go to Settings, Info, Software-Information, write down "Software-Number"... Should be something like 2.31.xxx.x

andryyyy said:
No problem
Use this app to tell us your CID. It is written at the top.
RUU files are official HTC firmware tools, which reset your phone and update your Android.
And please tell us which version you are using: Go to Settings, Info, Software-Information, write down "Software-Number"... Should be something like 2.31.xxx.x
Click to expand...
Click to collapse
Take a look at this screen captures... I got an ad in the way... lol. I purchased the phone locked from Vodafone Portugal, but I've unlocked the bootloader and rooted it...

labroste said:
Take a look at this screen captures... I got an ad in the way... lol. I purchased the phone locked from Vodafone Portugal, but I've unlocked the bootloader and rooted it...
Click to expand...
Click to collapse
Find the line in the CID Getter app starting with ro.aa.maincid

usaff22 said:
Find the line in the CID Getter app starting with ro.aa.maincid
Click to expand...
Click to collapse
I could not find the ro.aa.maincid... it doens't appear on my device...

labroste said:
I could not find the ro.aa.maincid... it doens't appear on my device...
Click to expand...
Click to collapse
In that case, go to HBOOT and type fastboot getvar cid or fastboot oem readcid into an adb window.
I don't think it is in alphabetical order. Or you can open your build.prop in system, transfer it to a computer, and search using notepad++ or similar.

Hey,
sorry, my girlfriend came here, had no time.
And yes, get into bootloader > fastboot, type "fastboot getvar cid"

andryyyy said:
Hey,
sorry, my girlfriend came here, had no time.
And yes, get into bootloader > fastboot, type "fastboot getvar cid"
Click to expand...
Click to collapse
The result is VODAP304

Is it true that if I run the RUU I have to root and unlock all over again my phone?

labroste said:
Is it true that if I run the RUU I have to root and unlock all over again my phone?
Click to expand...
Click to collapse
You will have to root, but you will remain unlocked. You will need to flash a SuperUser zip.
Boot into FASTBOOT USB mode.
Since your CID is VODAP304, type fastboot oem writecid HTC__001 (with two underscores). Then download this file, and place it in your adb folder. Then type fastboot flash hboot ville114.nb0 (make sure it is nb0, not nbO). Reboot into the bootloader again, and you should have HBOOT 1.14.
Or alternatively, after writing CID, just run the HTC WWE 2.31 RUU. That will also work.

As an FYI, RUUs for many phones can be found at http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
and a discussion can be found at http://forum.xda-developers.com/showthread.php?t=1543588
To flash an RUU, you can only flash one that has an equal or greater bootloader version (ie you cant downgrade). RUUs will upgrade your bootloader if you flash a version that is greater.
You also need to flash an RUU that corresponds to your CID. The RUU wont flash if the CID doesnt correspond. However, you can also turn your CID into a SuperCID to flash any other RUU. There is DEV thread on this as well.
Oh and you need to relock your bootloader before starting the RUU.
Cheers,
AKToronto

Thanks anyway, but I've upgraded to hboot 1.14 and the navigation keeps crashing.... I thing it's a bug from CM10...

labroste said:
Thanks anyway, but I've upgraded to hboot 1.14 and the navigation keeps crashing.... I thing it's a bug from CM10...
Click to expand...
Click to collapse
I thought so. Are you using the default Google Maps Navigation?
Sent from my HTC One S using Tapatalk 2

usaff22 said:
I thought so. Are you using the default Google Maps Navigation?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Yes, i'll try waze and other nav apps, but i prefer navigation from google by far...

[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

[Q] Revert back to stock

I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.

Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/
I would just prefer a nandroid backup of the stock image that I can just flash with CWM.
I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
Sent from my One S using xda premium

I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414

Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium

OccupyDemonoid said:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
Click to expand...
Click to collapse
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.
You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
Sent from my Nexus 7 using Tapatalk HD

I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium

OccupyDemonoid said:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.
You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)
OR
you can find it in the forums.

Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium

OccupyDemonoid said:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.

tivofool said:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)

DroidLuvver said:
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
Click to expand...
Click to collapse
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.

tivofool said:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
Click to expand...
Click to collapse
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13

DroidLuvver said:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
Click to expand...
Click to collapse
It will install the newer hboot to 2.15

tivofool said:
It will install the newer hboot to 2.15
Click to expand...
Click to collapse
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -
Is it true that with 2.15 hboot, modifying the CID is not allowed ?
Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?

Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.
But there is a guide to run a ota.zip for those people, so it isn't hopeless.
So not too many disadvantages.
In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.
And the gossip is that update will be officially put out by HTC in a few weeks.
Sent from my HTC One S using Tapatalk 2

Remember this.
if you want to go stock again in future (warranty purpose)
some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard
It's not that easy to flash an ota as is a ruu.
If your s-off downgrading is no issue.
Verstuurd van mijn HTC One S met Tapatalk

[Q] Upgrade HBOOT - Roger001 CID

Hi everyone,
This is my very first post and I'll admit I am a NOOB.
As I've searched XDA and Google for my questions, I am really at a loss and thought I would pose my question(s) to the community.
I have a Rogers HTC One X(Evita) running CM 10.0, I am currently S-ON, with TWERP 2.3.1
I would like to install the latest CM but it would seem my HBOOT (1.11) needs to be upgraded.
My first question is if my CID is Roger001 is this similar to being SuperCID?
If so, which firmware is recommended? Which is the latest HBOOT I should upgrade to?
I guess this brings me to my next question, what exactly do I need to be able to upgrade my HBOOT?
I've seen a few walkthroughs but none mention Roger001 as CID and I'd rather not risk bricking my phone.
If you need any other information, please let me know.
Any assistance is greatly appreciated.

You definitely need to update your phone in order to flash the latest cm ROM. But, with your phone in its current state you'll brick it. You don't have SuperCID (11111111), you'll definitely need to get that first, then get s-off, then you can RUU up to the latest. Links to everything you need are in this thread.
Sent from my Evita

Thanks Tim.
I'll give that a whirl and let you know how it turns out.
Another silly question, what exactly is RUU?
Sent from my One X using xda app-developers app

RUU stands for ROM Update Utility. It basically takes your phone back to being completely stock, including recovery. The beauty of being s-off when you run an RUU is the s-off status survives the process, and so will your unlocked bootloader. So all you need to do when it's finished is flash TWRP again via fastboot, then flash your ROM via TWRP.
Sent from my Evita

Ahh
That makes perfect sense!
If I wanted to stay stock, I could?
Sent from my One X using xda app-developers app

Yeah there's nothing stopping you. Then if you change your mind it's as simple as following the steps I mentioned before.
Sent from my Evita

I haven't had a chance to try anything as of yet but I've been doing some reading, could I use the One X Att all-in-one kit 3.0.1 to obtain SuperCID as well S-Off?
I tried another apparently popular program yesterday but it didn't work, as my CID is still Roger001.
Thanks!
Sent from my One X using xda app-developers app

Yeah you might as well try anything you can to get it done.
Sent from my Evita

Yes!
timmaaa said:
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:

Spoke too soon.. :S
asarrecchia said:
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Click to expand...
Click to collapse
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?

asarrecchia said:
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
Click to expand...
Click to collapse
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita

timmaaa said:
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps from the link you gave me, under the RUU section, as there was a guide on how to install an RUU for Rogers HTC One X.
It said to relock the phone, so, I did.
ARWizard was part of the guide.
The weird thing is, I didn't flash CM, I flashed the Rogers RUU, so, I'm not even sure how CM10 is even on my phone.
I can get to the Bootloader but I can't launch TWERP and my windows PC now doesn't recognize my phone, it says installing drivers but never does. I had HTC Sync installed in hopes that it would help, it didn't.
Is my only option to do a Factory Reset in Hboot? I've read ill lose all my info on the SD card.
Thanks

Which RUU did you run? Something has gone wrong.
Sent from my Evita

timmaaa said:
Which RUU did you run? Something has gone wrong.
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps in the below thread to help me flash the RUU
http://forum.xda-developers.com/showthread.php?t=1658929&nocache=1
I went to this site to get the Stock image:
http://forum.xda-developers.com/showthread.php?p=37227608
It's 3.17.631.2
OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip
I really do appreciate the help, by the way.

I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita

timmaaa said:
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
I am 2.14 HBOOT and S-off.
The problem is that while my Windows PC recognizes my phone, it doesnt load the drivers and therefore, I cant send any ADB commands.
I am not even able to go into TWERP.
How will I be able to run the AT&T if I cant push any ADB commands from my PC?

You don't need any adb commands to run an RUU, but you do need the pc to recognize the phone. I'd try uninstalling all drivers, then installing them again to see if it helps.
Sent from my Evita

Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files, evita ones get the name pj83img.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
If you follow the "or" method for flashing the zip it actually should work. The better correct answer is once s-off to download/install the latest ruu available that you want and ota up from there.

twistedddx said:
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
Click to expand...
Click to collapse
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita

timmaaa said:
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys.
I'll try uninstalling the phone drivers and reinstall them, hopefully, it'll allow my PC to see my phone.
Worse case scenario, if my computer doesn't load the drivers for my phone, what are my options?
What if I select factory reset from HBOOT?

Upgrading my hboot???

Hello all, here is my situation.
I recently purchased two used HTC One X phones. After a bit of research, I found out that they are actually the international version, the XL or Evita as they also go by. This is not a problem to me. I struggled getting them to take custom ROMs and I was finally able to get Cyanogenmod 10.0 installed. They are working great as is, however I would like to be able to update further, as there are a couple very minor bugs. Whenever I try to install an update through clockwordmod recovery, I always get a bootloader error. The number is spits out is 2.14, which I know is a never version of hboot. So, my question is, should I update my hboot (currently in 1.14.0002) to 2.14 in order to install newer versions of Cyanogenmod? If so, can you please provide detailed step by step instructions, or link me to a forum that does? Thank you.
Other potentially relevant information:
-EVITA PVT SHIP S-ON RL
bootloader unlocked via HTCdev

Ok, firstly it isn't the hboot you need to update, it's the firmware. It just happens that the firmware contains the hboot, and the hboot version is what's used by the ROM installer to tell whether you've updated or not. First thing you'll need to do is get s-off, that's required for flashing the firmware.
Facepalm S-off
Rumrunner S-off Thread
Once you've done that just head to the How-To Guide For Beginners thread in my signature and follow the directions there to update your firmware.
It might be a good idea to bookmark that thread, and also the Evita FAQ thread. The answer to your question is contained within the FAQ thread, which is actually stickied at the top of the section you've just posted in.
Sent from my Evita

timmaaa said:
Ok, firstly it isn't the hboot you need to update, it's the firmware. It just happens that the firmware contains the hboot, and the hboot version is what's used by the ROM installer to tell whether you've updated or not. First thing you'll need to do is get s-off, that's required for flashing the firmware.
Facepalm S-off
Rumrunner S-off Thread
Once you've done that just head to the How-To Guide For Beginners thread in my signature and follow the directions there to update your firmware.
It might be a good idea to bookmark that thread, and also the Evita FAQ thread. The answer to your question is contained within the FAQ thread, which is actually stickied at the top of the section you've just posted in.
Sent from my Evita
Click to expand...
Click to collapse
Okay, thanks. Yeah I'm aware you can't get boot without a firmware update. Will 2.14 allow me to update to cyanogenmod 11?

Yes it will but getting that firmware requires you to run an RUU, which also requires s-off, and is a lot harder than just flashing the firmware package.
Sent from my Evita

timmaaa said:
Yes it will but getting that firmware requires you to run an RUU, which also requires s-off, and is a lot harder than just flashing the firmware package.
Sent from my Evita
Click to expand...
Click to collapse
Major problems. I now have s-off but my phone refuses to boot. It was in a boot loop, tried flashing boot.img again and now it tries to start then fails, black screen until I how the volume and power button to get back into bootloader. Any suggestions on that?

asilaydyingdl said:
Major problems. I now have s-off but my phone refuses to boot. It was in a boot loop, tried flashing boot.img again and now it tries to start then fails, black screen until I how the volume and power button to get back into bootloader. Any suggestions on that?
Click to expand...
Click to collapse
Flash a ROM, not really a major problem.
Sent from my Evita

timmaaa said:
Flash a ROM, not really a major problem.
Sent from my Evita
Click to expand...
Click to collapse
Tried it, still fails. Installed the ROM, gapps, and flashboot flash boot boot.img

timmaaa said:
Flash a ROM, not really a major problem.
Sent from my Evita
Click to expand...
Click to collapse
Flashed the right boot.img (somehow had the wrong one) now back in boot loop again. Any ideas? I did have to change my CID because I did not turn on debugging for ADB. Would that have something to do with it?

What are your bootloader details now? What did you change your CID to? And what did that have to do with debugging? What ROM did you flash?
Sent from my Evita

timmaaa said:
What are your bootloader details now? What did you change your CID to? And what did that have to do with debugging? What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT 1.14.0002
Flashed Cyanogenmod 10.0.0. I was unable to use the last command successfully on facepalm's tutorial without allow ADB in android debugging.

Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita

timmaaa said:
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ummm... how do I transfer the new files to my phone if I can't get it to boot in the first place? I will need to transfer the files for the new ROM.

timmaaa said:
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
IM BACK IN!!! Updating the firmware did it! THANKS FOR YOUR HELP!!! KITKAT HERE I COME!