Database Info

[Q] PG58IMG.zip can't be installed

My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Problem is my phone can't boot into system,

pmbldc said:
My hboot version is 1.23, s-on. My phone can't install PG58IMG.zip, bootloader always shows no image or wrong image, i tried different zip file but non of them works. I know this has a close relationship with s on. But what can i do? I would appriciate if you could give me some advice.
Click to expand...
Click to collapse
Hi,
What exactly are you trying to do?

malybru said:
Hi,
What exactly are you trying to do?
Click to expand...
Click to collapse
My phone can't boot into system and now s-on, so i want to do something to make it work

pmbldc said:
My phone can't boot into system and now s-on, so i want to do something to make it work
Click to expand...
Click to collapse
Hi,
Were you s-off before?
What did you flash to make you s-on?

Last night I unlocked the bootloader n been having the same problem but mind say S-on n I don't know what's next
Sent from my HTC Sensation 4G using XDA App

? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it

ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated

malybru said:
Hi,
Were you s-off before?
What did you flash to make you s-on?
Click to expand...
Click to collapse
Sorry to reply so late.
Previously, my phone was eng s-off and got super cid.
After i flash ICS firmware, bootloader was then locked.
After that i did some stupid things, the bootloader turned into "locked", "security warning" and s-on. I succeeded to unlock bootloader by htcdev and get rid of "security warning", at that time i can boot into recovery normally and wipe or flash roms. But it just can't boot into system. I tried fastboot commands to flash but failed just because "it is not allowed in the remote devices".
i tried PG58IMG files but the bootloader shows no image or wrong image.
Can you give me some advice? Thank you very much

ilostchild said:
? im at a lost here little more detail
what did you use to unlock bootloader?
where you ever s-off?
where you rooted?
why did you flash the IMG.zip?
if you unlocked it then go to fastboot and make your CID 11111
and hopefully that will get you back on where you wanted to do?
cant give much help unless you give some details on what was your state of phoen before and what you wanted to do with it
Click to expand...
Click to collapse
My phone had been rooted and end s-off before things happened.
i flash IMG.zip to try to flash a rom( Somebody post that ICS rom can be flash by IMG.zip) or fix the bootloader problem. It's almost the only way to flash a rom for me
I checked the cid and it is still 11111111(Got super cid before) although bootloader is s-on.
Now the state of the bootloader is
1, unlocked
2,s-on
3,cid is 11111111
4,can boot into recovery
5,can't install PG58IMG.zip
6,fastboot command can't write anyting
7,if flash some rom, phone will be stuck at the splash screen which seems splash partition is writable
Thank you!

greenhtc982 said:
I have similar problem, hboot 1.20, was S-OFF, flashed orig RUU ICS,changed CID to HTC___001 than I made stupid mistake and changed back to S-ON (wanted to send my phone to the shop, problems with reception and sound quality) now only ROM that my phone accepts is LeeDroid 5.01, cant change cid to supercid via fastboot some error SMART_IO.CRD not found on sdcard. Tried to flash orig RUU (1.45, 1.29, ICS etc.) error 155 when hboot is locked and error 132 signarure error when relocked. Also tried changing android-info.txt to my cid and mid no luck, tried flashing via RUU and bootloader no luck.
Any help would be appreciated
Click to expand...
Click to collapse
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem

ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?

ilostchild said:
ok find hboot 1.17 PD58IMG.zip, your truly not s-on, format your sdcard, then place the img in sdcard, and boot into bootloader, and you should be able run fastboot commands, you should still have custom recovery right?
Click to expand...
Click to collapse
I format the sdcard in fat32 format and place img that revert to hboot 1.17 in sdcard. Reboot into bootloader, but it shows "no image or wrong image".
I also try fastboot command but i don't know the command format. Would you give me an example please? Just a fastboot command to install img no matter s-on or s-off. Such as "fastboot flash hboot hboot.img".
My device is now s-on.

pmbldc said:
i don't know how to do either, but during solving my problem, i found something may be useful. If you want to unlock bootloader you can try htcdev. This can't s-off but just unlock bootloader.
And since your hboot is 1.20, you can try the zip file attached by this link http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Because my hboot is 1.23 and isn't supported according to the above link, i didn't know whether it will help or not. You can take it into consideration
Hope you can solve your problem
Click to expand...
Click to collapse
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.

greenhtc982 said:
Thanks for the link, but i tried that already, I've read whole bunch of treads and tried everything i can think off but nothing seems to work. Problem is S-on and with hboot 1.20 locked or unlocked i cant flash any rom except leedroid.
Click to expand...
Click to collapse
You mean you can flash leedroid now, don't you?
Can you boot into system？

pmbldc said:
You mean you can flash leedroid now, don't you?
Can you boot into system？
Click to expand...
Click to collapse
Yes its working, but i would like to flash other ROM's

Same Problem
Hi, I can't flash PG85IMG.zip wither except that I have S-Off??

[Q] No Way back - ERROR 155

cheers!
Status of my HTC:
Now it's RELOCKED
It has the original Recovery and Super CID (11111111)
BUT:
I can't flash any Stock rom! I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
but but but! the best thing is , I can't unlock the bootloader now! With the old unlock_boot.bin I will get an error and if I want to get a new Code from HTCDEV.com I also get an Error on the side, and they say, that the code is too long or not right (but I know how to copy and paste the text )
Why I want to go back to Stock?
First of all, I had an Wlan problem, which I solved but after that, i always got the Error (with Custom Roms) that the Android Keyboard (AOSP) will be closed, so I had no keyboard to work with
What can I do?
I only want to go back to my Custom Rom or the Stock ROM!!!!!

thesoldier16 said:
cheers!
Status of my HTC:
Now it's RELOCKED
It has the original Recovery and Super CID (11111111)
BUT:
I can't flash any Stock rom! I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
but but but! the best thing is , I can't unlock the bootloader now! With the old unlock_boot.bin I will get an error and if I want to get a new Code from HTCDEV.com I also get an Error on the side, and they say, that the code is too long or not right (but I know how to copy and paste the text )
Why I want to go back to Stock?
First of all, I had an Wlan problem, which I solved but after that, i always got the Error (with Custom Roms) that the Android Keyboard (AOSP) will be closed, so I had no keyboard to work with
What can I do?
I only want to go back to my Custom Rom or the Stock ROM!!!!!
Click to expand...
Click to collapse
Well, I imagine with the RUU you got back to a stock ROM... At any rate, you could try reflashing the RUU, or attempt to flash a different RUU (since you have SuperCID) and then see if your still having issues with getting a new unlock_boot.bin.
I imagine your 100% sure you know how to cut and paste? LOL I have to ask (even though you said it)... I was able to unlock my bootloader after flashing a newer RUU and didnt have this issue.
AKToronto

Well, I imagine with the RUU you got back to a stock ROM... At any rate, you could try reflashing the RUU, or attempt to flash a different RUU (since you have SuperCID) and then see if your still having issues with getting a new unlock_boot.bin.
Click to expand...
Click to collapse
Good aspect, but (now I love this word ) I tested nearly every Europe RUU and I always get the 155!
Some people said, that one of the latest RUU works with the CID :
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
At tis moment I found this rom, I will test it tomorrow!
I imagine your 100% sure you know how to cut and paste? LOL I have to ask (even though you said it)... I was able to unlock my bootloader after flashing a newer RUU and didnt have this issue.
Click to expand...
Click to collapse
Come on man! I unlocked the bootloader Soooo this is not the problem for me!
I read in some threads, that you can't generate a new .bin file with htcdev when you have on working Rom on your phone haha funny, yeah and I am not able to put a normal stock rom on the phone

This is a long shot, but if you still have a custom recovery, try loading it up and flashing this: http://www.mediafire.com/?l35x37414jhwual
That package will set your mainver to the lowest possible number, which combined with SuperCID will allow flashing of any RUU.
If that doesn't work, you'll have to keep trying the htcdev to get your unlock code. It's possible that the website could be having some temporary problems. If all else fails, shoot an e-mail to HTC Support with screenshots of the errors on the website, the fastboot errors, a picture of your phone's HBOOT, your old unlock_code.bin and your identifier token.
Edit: Oops, just read that you had the original recovery :/ Yeah, try the absolute latest RUU and if that doesn't work, you'll need a new unlock code to have any progress.

what is your hboot version?

thesoldier16 said:
I only want to go back to my Custom Rom or the Stock ROM!!!!!
Click to expand...
Click to collapse
The unlock_code.bin file you get from HTC is generated using fingerprints on your phone. When you changed your CID it's like changing a fingerprint. All you have to do is go through the unlocking process again and get a NEW unlock_code.bin from HTC Dev.
thesoldier16 said:
I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
Click to expand...
Click to collapse
Most likley you are trying to use a RUU that have a lower hboot then yours. You can only use an RUU that has the same version or a higher hboot.
thesoldier16 said:
It has the original Recovery and Super CID (11111111)
I can't flash any Stock rom!
Click to expand...
Click to collapse
If you have the original recovery you need to flash a custom recovery first. Find TWRP and flash that.

what is your hboot version?
Click to expand...
Click to collapse
It's the version 1.14.0002
Ok these roms don'tt work for me:
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe -> I tried this rom with my old CID , it was H3G__106
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
EDIT EDIT EDIT:
I got a new code from htcdev!
my problem was, I paste the text with the "info" . ok it was my fault, but now i have to try, to get my custom Recovery back!
One question, if I replace the SUPER CID with the HTC__001 one, can I flash the HTC Europe ones? (the 1.53 or the 1.78?)
Click to expand...
Click to collapse

thesoldier16 said:
It's the version 1.14.0002
Ok these roms don'tt work for me:
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe -> I tried this rom with my old CID , it was H3G__106
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
EDIT EDIT EDIT:
I got a new code from htcdev!
my problem was, I paste the text with the "info" . ok it was my fault, but now i have to try, to get my custom Recovery back!
One question, if I replace the SUPER CID with the HTC__001 one, can I flash the HTC Europe ones? (the 1.53 or the 1.78?)
Click to expand...
Click to collapse
The problem is that you trying to use RUU's with a lower Hboot then what you got it will never work without a downgrade. Its has to be the same or higher then what you got.

Bell/Virgin HTC Sensation Boot-loop

Hello, I know this may seem like a redundant post but I cannot for the life of me figure out how to un-brick this phone..
Currently the only menu I can get into is the Hboot menu, where it says
RELOCKED
HBoot-1.27.0000
RADIO-11.24.3504.10_M
eMMc-boot
This phone has never been rooted or modified in anyway and just started this bootloop, where I've tried unlocking the bootloader, flashing different recovery's and many RUU files and nothing has worked..
When trying to enter the recovery menu from the HBoot menu it the phone simply resets itself and back to the dreaded HTC bootloop..
The phone is currently on 3.32.666.13 I believe and there is no RUU that I can use to reflash it because the latest RUU for Bell Sensations is
1.45.666.5 and it errors out saying it's the incorrect version.
I've went through many tutorials and searched through many posts trying to get s-off but there is no method that will work because I cannot get into the recovery or the android os or perform a factory reset even..
If anybody has any ideas or can shine some light onto this problem I'd greatly appreciate it

Tom-5- said:
Hello, I know this may seem like a redundant post but I cannot for the life of me figure out how to un-brick this phone..
Currently the only menu I can get into is the Hboot menu, where it says
RELOCKED
HBoot-1.27.0000
RADIO-11.24.3504.10_M
eMMc-boot
This phone has never been rooted or modified in anyway and just started this bootloop, where I've tried unlocking the bootloader, flashing different recovery's and many RUU files and nothing has worked..
When trying to enter the recovery menu from the HBoot menu it the phone simply resets itself and back to the dreaded HTC bootloop..
The phone is currently on 3.32.666.13 I believe and there is no RUU that I can use to reflash it because the latest RUU for Bell Sensations is
1.45.666.5 and it errors out saying it's the incorrect version.
I've went through many tutorials and searched through many posts trying to get s-off but there is no method that will work because I cannot get into the recovery or the android os or perform a factory reset even..
If anybody has any ideas or can shine some light onto this problem I'd greatly appreciate it
Click to expand...
Click to collapse
Hi,
To get into stock recovery,hold volume up and down + power button.

malybru said:
Hi,
To get into stock recovery,hold volume up and down + power button.
Click to expand...
Click to collapse
Hi there, thanks for the suggestion but instead of loading the recovery it just boots to the white htc screen, goes black for about second and reboots.. no matter how long or which button combination I use, besides to get into the Hboot Menu, I haven't seen any recovery menu yet

Tom-5- said:
Hi there, thanks for the suggestion but instead of loading the recovery it just boots to the white htc screen, goes black for about second and reboots.. no matter how long or which button combination I use, besides to get into the Hboot Menu, I haven't seen any recovery menu yet
Click to expand...
Click to collapse
Can you check the cid?
If it's super CID then change it back to original one and then do a reboot and see
Sent from my HTC Sensation using xda premium

ganeshp said:
Can you check the cid?
If it's super CID then change it back to original one and then do a reboot and see
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Hello, Unfortunately the CID hasn't been changed, it's currently BM___001
Is there any RUU's available for this model equal to 3.32.666.13 or higher?

Tom-5- said:
Hello, Unfortunately the CID hasn't been changed, it's currently BM___001
Is there any RUU's available for this model equal to 3.32.666.13 or higher?
Click to expand...
Click to collapse
Hi,
Look HERE or HERE

malybru said:
Hi,
Look HERE or HERE
Click to expand...
Click to collapse
Hello, thanks for the links.
I've tried both the BM RUU's and some of the HTC Europe ones as their firmware versions are higher, but they error out with
<T192024><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
or
<T003702><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
(From RUU Logs)
it was my understanding I need one with 3.32.666.13 or higher retaining the same '666' region type code and a higher or equal firmware to the one already installed, as far as I'm aware no such RUU exists
I've tried taking the rom from either RUU's and flashing the zip manually with fastboot with either a locked or unlocked bootloader using commands like "fastboot -s SH16LV603891 flash zip C:\rom.zip" and it either says something like "remote:signature fail" or "Remote:not allowed" (with unlocked bootloader)

Tom-5- said:
Hello, thanks for the links.
I've tried both the BM RUU's and some of the HTC Europe ones as their firmware versions are higher, but they error out with
<T192024><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
or
<T003702><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
(From RUU Logs)
it was my understanding I need one with 3.32.666.13 or higher retaining the same '666' region type code and a higher or equal firmware to the one already installed, as far as I'm aware no such RUU exists
I've tried taking the rom from either RUU's and flashing the zip manually with fastboot with either a locked or unlocked bootloader using commands like "fastboot -s SH16LV603891 flash zip C:\rom.zip" and it either says something like "remote:signature fail" or "Remote:not allowed" (with unlocked bootloader)
Click to expand...
Click to collapse
Hi,
Relock the bootloader
Code:
fastboot oem lock
Then,try the RUU again.

malybru said:
Hi,
Relock the bootloader
Code:
fastboot oem lock
Then,try the RUU again.
Click to expand...
Click to collapse
Unfortunately no matter which RUU I use or whether the bootloader is locked or unlocked it errors out before it can finish
I appreciate the help though
Is is possible to get supercid without booting into the android operating system or recovery menu? so I could at least flash a custom rom or not be limited with my fastboot commands

Tom-5- said:
Unfortunately no matter which RUU I use or whether the bootloader is locked or unlocked it errors out before it can finish
I appreciate the help though
Is is possible to get supercid without booting into the android operating system or recovery menu? so I could at least flash a custom rom or not be limited with my fastboot commands
Click to expand...
Click to collapse
Hi,
I do not think you can supercid with s-on.
But you can try to follow THIS GUIDE to install a custom ROM.

malybru said:
Hi,
I do not think you can supercid with s-on.
But you can try to follow THIS GUIDE to install a custom ROM.
Click to expand...
Click to collapse
I was able to flash the recovery, but when attempting to boot into the recovery it instantly brings up the white HTC logo on the screen, and stays there until the phone eventually reboots

Tom-5- said:
I was able to flash the recovery, but when attempting to boot into the recovery it instantly brings up the white HTC logo on the screen, and stays there until the phone eventually reboots
Click to expand...
Click to collapse
Hi,
I am running out of things to suggest.
The best thing would obviously be a RUU to reset everything.
Maybe try to re-install the recovery.

malybru said:
Hi,
I am running out of things to suggest.
The best thing would obviously be a RUU to reset everything.
Maybe try to re-install the recovery.
Click to expand...
Click to collapse
It's got me stumped too! I've tried multiple recoveries.. I wonder if it's possible that it could be a hardware-related problem? As I should be able to enter the recovery at this point I think, unless I'm missing something? Would any RUU that is over higher than the current firmware be suitable? for example it currently sits at 3.32.666.13, say I were to use "RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed" The firmware is higher but the region code doesn't match up. If I were to use "RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed" the firmware version is too low, but the region matches up. I figured if I used just an unbranded stock rom.zip based off of 3.32 or 3.33 and flashed it via fastboot with an unlocked/locked bootloader I may have some luck but it was a no-dice situation..
The model of this sensation is a PG58110 with a manufacture date of 2011/06/17
Could these possibly be the wrong RUU's ? I tried ones for the Sensation 4G and regular Sensation
as I wasn't positive which one I have.. No luck either way

Tom-5- said:
It's got me stumped too! I've tried multiple recoveries.. I wonder if it's possible that it could be a hardware-related problem? As I should be able to enter the recovery at this point I think, unless I'm missing something? Would any RUU that is over higher than the current firmware be suitable? for example it currently sits at 3.32.666.13, say I were to use "RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed" The firmware is higher but the region code doesn't match up. If I were to use "RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed" the firmware version is too low, but the region matches up. I figured if I used just an unbranded stock rom.zip based off of 3.32 or 3.33 and flashed it via fastboot with an unlocked/locked bootloader I may have some luck but it was a no-dice situation..
The model of this sensation is a PG58110 with a manufacture date of 2011/06/17
Could these possibly be the wrong RUU's ? I tried ones for the Sensation 4G and regular Sensation
as I wasn't positive which one I have.. No luck either way
Click to expand...
Click to collapse
Hi,
Did you fully read THIS LINK that I gave you?
It shows various alternatives to just running a RUU.
It helps you to determine which of the 3 types of Sensation you have.
Try running all the RUU's that are even reasonably close to your version.
It will only throw up an error if it is no good.
Remember that the phone should be locked or relocked.

ruu stock rom????

my phone run "villec2-jb-4.1.1-deodexed" i down ruu som and run but it faill 155, phone show hboot orlder?????? ruu is ics
who can help me fixx??? thank!!! so much sorry bad english

daothuan said:
my phone run "villec2-jb-4.1.1-deodexed" i down ruu som and run but it faill 155, phone show hboot orlder?????? ruu is ics
who can help me fixx??? thank!!! so much sorry bad english
Click to expand...
Click to collapse
relock your bootloader before you run the RUU

tivofool said:
relock your bootloader before you run the RUU
Click to expand...
Click to collapse
i did, but it faillll have tips ??????

daothuan said:
i did, but it faillll have tips ??????
Click to expand...
Click to collapse
is there a newer RUU that you can run on your device?
http://forum.xda-developers.com/showthread.php?t=2094414
The only tips that I have are
put back stock recovery on your phone if you have changed it. (you will have to unlock bootloader to do this)
relock bootloader.
OH, and one time even though usb debugging was checked on the phone, I had to uncheck it and check it again before the ruu worked.

Will relocking bootloader automatically restore stock recovery? Cause I am trying to return to stock from S-off back to S-on and I am following this guide but in the HTC One S toolkit, the recovery section doesn't have a stock recovery to flash. I can use some help with this also, I want to see if returning phone to stock will fix signal drop issues and if not I will have to return it on insurance. My biggest problems are I do not have an RUU from my carrier so could use some advice as to which one to use? here is the link for RUU's but there isn't one for Cincinnati Bell wireless.

You need S-OFF
Sent from my Nexus 7 using Tapatalk HD

[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?