Database Info

Sensation XE stuck at beats logo after update

My phone is not rooted. I tried to update to ICS but after updating process completed it is now stuck at beats logo. Help please

Since this is the official OTA, I don't really know what would have went wrong. I guess all I could think of doing is rebooting the phone and waiting a while. Considering new ROMS take a long time on first boot. If that doesn't work, I guess call your carriers tech support.

You can download and run the 3.32.401.105 RUU to restore it to a factory state with ICS.
Sent from my HTC Sensation 4G

GROGG88 said:
You can download and run the 3.32.401.105 RUU to restore it to a factory state with ICS.
Sent from my HTC Sensation 4G
Click to expand...
Click to collapse
This should be the right solution for you.
And if you want to do this, all required info can be found here.
If you are S Off, I recommend you keep S Off & don't do the last step.

Problem
When i runn RUU on pc it shows error 132 saying signature write error.
If I extract the zip file and run through bootloader the setup aborts after the yellow bars fills up.
When I go to recovery it says cannot open e:cache ........

alirana90 said:
When i runn RUU on pc it shows error 132 saying signature write error.
If I extract the zip file and run through bootloader the setup aborts after the yellow bars fills up.
When I go to recovery it says cannot open e:cache ........
Click to expand...
Click to collapse
Plash the PG58IMG like this: http://forum.xda-developers.com/showpost.php?p=26673647&postcount=12

kgs1992 said:
Plash the PG58IMG like this: http://forum.xda-developers.com/showpost.php?p=26673647&postcount=12
Click to expand...
Click to collapse
again signature error C:\and>fastboot flash zip PG58IMG.zip
sending 'zip' (427312 KB)...
OKAY [ 58.032s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 114.945s

alirana90 said:
again signature error C:\and>fastboot flash zip PG58IMG.zip
sending 'zip' (427312 KB)...
OKAY [ 58.032s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 114.945s
Click to expand...
Click to collapse
dude get the RUU based on your country/carrier
or first get the cid
to get it keep the device in bootloader connect it to pc
and type "fastboot getvar cid" without quotes
that should give you the cid and based on that get the corresponding RUU
repost the cid here..ppl might find it for you

ganeshp said:
dude get the RUU based on your country/carrier
or first get the cid
to get it keep the device in bootloader connect it to pc
and type "fastboot getvar cid" without quotes
that should give you the cid and based on that get the corresponding RUU
repost the cid here..ppl might find it for you
Click to expand...
Click to collapse
HTC__001, he has the right RUU.
Anyway, helping him through it.

kgs1992 said:
HTC__001, he has the right RUU.
Anyway, helping him through it.
Click to expand...
Click to collapse
then the only other thing that can cause signature fail is modelid...
may be he is trying to flash XE RUU on normal one or vice versa

[Q]Fastboot flash radio failed, any solution?

Hello!
I wanted to flash another radio.img onmya HTC Ones C2 (VilleC), and I got this error:
Code:
fastboot flash radio radio.img
sending 'radio' (22541 KB)...
OKAY [ 3.015s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 6.824s
To explain, I have unlocked bootloader and installed custom TWRP recovery. I believe that radio is for this phone cause I have unpack it from official RUU for HTC VilleC. Any ideas?

Ok I've managed to make flashable zip, and i have succesfully flashed it with TWRP. But strange thing happened that Baseband numbers are still the same. So I have deceided to tray manually flash new radio, with "dd" command, again everything went well but still no change in baseband. I have also flash rcdata.img, still no change. Is it possible that on One S radio can't be flashed manully but only with running RUU??

qzem said:
Ok I've managed to make flashable zip, and i have succesfully flashed it with TWRP. But strange thing happened that Baseband numbers are still the same. So I have deceided to tray manually flash new radio, with "dd" command, again everything went well but still no change in baseband. I have also flash rcdata.img, still no change. Is it possible that on One S radio can't be flashed manully but only with running RUU??
Click to expand...
Click to collapse
What is your hboot version? On the s4 if you are on certain hboots you can't flash radios and it does exactly what you are describing.
Sent from my Nexus 7 using xda app-developers app

I have HBOOT version 2.09.0001.
Sent from my HTC One S using xda app-developers app

[Q] How to install latest One X RUU?

Long story short, I'm at the point where I need to use the recovery RUU to make my phone operational again.
All the directions I've found say "just run the exe". However my Rogers One X is at version 3.17.631.2, and I have not been able to find a compatible RUU exe for that. The only download is a .zip file (OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip), and I'm at a loss as to what to do with it. If I try any of the available EXEs it won't restore to the earlier version.
I tried "fastboot flash zip OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j", fails with "remote: verify signature fail".

I believe if you're s-on, you must relock the bootloader to flash ruu's.
Sent from my HTC One XL using xda premium

Tried that both locked and unlocked.
I've since tried two different bootloaders but cannot mount /sdcard/ in addition to my usual troubles. I think I'm borked.

That ruu should match your firmware. Lock boot loader, enter fast boot... And run the ruu program on your computer.. It shouldn't fail.
Take a picture of the error screen and post it here if you can
Sent from my One X using Tapatalk 2

you need s-off to restore to the earlier version
---- Sorry my languege !

MaouLucifer said:
you need s-off to restore to the earlier version
---- Sorry my languege !
Click to expand...
Click to collapse
It's the same version he's currently on. AFAIK, It should work
Are you sure you typed the commands correctly? Should be something like this:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip
Or like inflatedtitan said, keep looking for that ruu program and run it from your computer.

Thanks for the commands.
< waiting for device >
sending 'zip' (650005 KB)...
OKAY [ 29.999s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 100.331s
I'm not sure where else to look for the comparable .exe. Any suggestions?

CaptCanuck said:
Thanks for the commands.
< waiting for device >
sending 'zip' (650005 KB)...
OKAY [ 29.999s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 100.331s
I'm not sure where else to look for the comparable .exe. Any suggestions?
Click to expand...
Click to collapse
Sorry bro, I'm at a complete loss Do you have stock recovery?
Sent from my HTC One XL using xda premium

jacobas92 said:
Sorry bro, I'm at a complete loss Do you have stock recovery?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Nope. Like a complete idiot, I did not back up before flashing. At least I was smart enough to get my photos and videos out.
It's cool though. Got a used Galaxy Nexus last night and am enjoying it so far. The One X was always kinda screwy from the start, which is why I wanted to try CM.
Thanks for your help.

CaptCanuck said:
Nope. Like a complete idiot, I did not back up before flashing. At least I was smart enough to get my photos and videos out.
It's cool though. Got a used Galaxy Nexus last night and am enjoying it so far. The One X was always kinda screwy from the start, which is why I wanted to try CM.
Thanks for your help.
Click to expand...
Click to collapse
Ah. Well, sucks you couldn't fix it but at least your enjoying your nexus.
Sent from my HTC One XL using xda premium

[Firmware Update] For AOSP ROMS-3.4 KERNEL-NEW OFFICIAL CM NIGHTLIES [27June]

When 1st time the new 3.4 kernel released many users had several issues with booting this amazing kernel or had boot loop,
You need this firmware update so you
can install new official CM nightly
so here is what you should do to enjoy it :
I will not be held responsible for your phone do at your own risk
1. First of all backup everything you need .
2. Download This :
2.1 A. For unbranded international devices & full package :
http://www.mediafire.com/?mc1mh05p669hspm
(Include Fastboot , Recovery , ADB , updated Firmware 2.15.0000, everything you'll need)
2.1 B. Here this link contains both firmware for international & T-Mobile devices :
https://www.dropbox.com/sh/ehihpbjf0shqgio/qu3vhYYDWe
2.2 For T-Mobile devices
You have to use T-Mobile firmware.zip from 2nd link replace it with my firmware.zip in the 1st file (A) and continue the steps.
2.3 Then extract it (The A-file) .
Hold Shift then right click on the folder and choose " Open Command Window Here " .
3. Boot into HBoot . Choose fastboot . in command Window type
"fastboot oem lock".
your phone will be locked .
4. Firmware (including HBoot , Boot , Recovery, Radio, every firmware partition needed for this new kernel... ).
Boot into HBoot again . Choose fastboot . in command Window type :
"fastboot oem rebootRUU".
after you are seeing HTC Screen then type :
"fastboot flash zip firmware.zip".
first time it get ERROR .
type again :
"fastboot flash zip firmware.zip".
now it should work and getting installed .
after install it does not reset use this command :
"fastboot reboot"
Or you have to reset by keeping power for some seconds .
5. unlock your phone again via the HTC Unlocking tool (HTC Dev site).
If you have the Unlock_code.bin file you received
originally, copy it into the working directory that you
have been using, return your phone to fastboot, and
issue the following command:
"fastboot flash unlocktoken Unlock_code.bin"
Your will be warned that you are voiding your warranty.
Select Yes or OK and continue. When the phone reboots
to the boatloader, it will announce that it has been
tampered with and is unlocked,
Note : Unlocking your bootloader will wipe your personal which is just data data partition not your internal SD .
6. Open command window again . type :
"fastboot flash recovery recovery.img".
this will install the latest TWRP Recovery .
Some users reported that this recovery.img in my package (A) is some how corrupted so download the latest TWRP RECOVERY and fastboot flash it don't use the one in my zip file
Get the latest TWRP recovery here http://goo.im/devs/OpenRecovery/ville
7. boot in recovery . for the first time it does not boot .
boot another time in recovery . it should work now .
8. Install The NEW CM KERNEL- WITCH IS IN YOUR ROM ZIP - IN FASTBOOT MODE THEN INSTALL The ROM IN TWRP RECOVERY after 3x full wipe .
9. Enjoy your CM 10.1 based ROM -3.4 KERNEL.
Please hit thanks button if this helped you
Hope you all enjoy the new amazing kernel with amazing new ROMS with it,
Thanks to all devs behind this great work
If your device is S-OFF you can just skip the relock & unlock steps And you won't lose any data by this way if you're running stock and just wanna upgrade the firmware but even with this I'd recommend to have backup before
Ps: check 2nd post
Tip: I'd recommend :
1.First if you don't want to risk TRY to run your device official JB RUU if you get errors with that try to get official JB update from the ota then the last way to get firmware update is to use my method here .
2.Get S-OFF and Super-CID if you get errors r with flashing the firmware.zip otherwise no need for that.
People to thank:
HTC
CyanogenMode team
@intervigil
@$droyd$
@BehradGH
@ron_e
@mo976
EVERYONE ELSE I FORGET.

mo976 said:
LIONS1 I hope I'm not stepping on your toes as its based on your Zip's and instructions so big thanks for your hard work.
Here's a little guide FOR S-OFF and SuperCID (111111) only and unlocked bootloader of course.
I TAKE NO RESPONSIBILITY if this messes up your phone. Or if your girlfriend breaks up with you or getting fired by your boss or whatever this is all at your own risk.
That said this is how I flashed and it worked for me!
1: Get the firmware from the opening post I used the T-Mobile firmware.zip https://dl.dropboxusercontent.com/sh...RuMvPhMiA&dl=1 (not the full RUU) but if your phone is not T-Mobile you may need the first download BehradGH_HBoot_2.15.0000_TWRP_Recovery.rar which includes adb and other goodies along with the firmware.zip inside.
2: Download the One S all in one toolkit here http://forum.xda-developers.com/show....php?t=1604677
3: Optional as the lastest is included in the latest version of the toolkit but just in case or if you already have an older version of the toolkit you can get the latest TWRP recovery here http://goo.im/devs/OpenRecovery/ville
My recommendations for file locations are all for making things easier to find
First unzip the toolkit to drive C example c:/one_s in this folder you should see "one s.exe" and a folder called data
Now unzip (or open using 7zip) the firmware and copy the recovery.IMG file inside of firmware.zip (for non T-mobile its inside of BehradGH_HBoot_2.15.0000_TWRP_Recovery.rar) to the recovery folder example c:/one_s/data/recovery (optional if you needed to dowload it copy the TWRP recovery IMG to the same folder).
Last step before beginning the upgrade process copy FIRMWARE.zip into the data folder c:/one_s/data
I recommend using an original USB cable and not some aftermarket or generic POS!
Now the fun begins. Start the all in one toolkit c:/one_s/One_S.exe
And choose reboot to bootloader make sure your phone shows fastboot usb
First we need stock recovery so select flash "your own recovery" in the upper right box and and the click on "flash recovery" when it shows you the file explorer box choose the stock recovery that you extracted before it will do its thing and should show finished okay in the command prompt window after it says done reboot to fastboot.
So far so good you should be back on the bootloader.
From the toolkit main screen in the lower left corner menu select "Flash a factory RUU zip" and click "run"! It will give you some BS message about needing a locked boot loader etc ignore and continue, it will now take you your phone to a black screen with a silver HTC logo and will ask you to locate the "RUU" choose the firmware.zip file and it should start on its own if not open a command prompt from the c:/one_s/data file and type in fastboot flash zip firmware.zip and it should do its thing when it says okay and finishes choose reboot into bootloader if it doesn't work and stays on the HTC screen with the green line hard reboot with power and volume down and go back into the fastboot menu.
Last but not least from the toolkit flash recovery again use the TWRP (S4) or if needed "your own recovery" (select the TWRP IMG that you downloaded) click "flash recovery" and wait for it to say done.
Reboot the bootloader and choose recovery from the menu happy flashing don't forget a full (data/system/cache) wipe might be needed before flashing the ROM.
Sent from my Nexus 7 using XDA Premium HD app
Always read lots post little
Click to expand...
Click to collapse
Hope this will help you guys :thumbup:
Sent from my HTC One S using xda premium

Perfect. Thanks. I was just researching this. I'll need to wait till I get back from vacation to do this though.
Sent.
Oh, wait! Does the hboot matter? I have 1.06...

Guess I can skip relocking it if s-off?
Sent from my HTC One S using Tapatalk 4 Beta

Darknites said:
Guess I can skip relocking it if s-off?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
I skipped it without any trouble
Sent from my One S using xda app-developers app

Bowmanspeer said:
Perfect. Thanks. I was just researching this. I'll need to wait till I get back from vacation to do this though.
Sent.
Oh, wait! Does the hboot matter? I have 1.06...
Click to expand...
Click to collapse
This will uodate all your Firmware including the HBoot to be able to boot the new 3.4 kernel
Sent from my HTC One S using xda premium

Did not work for me.
sending 'zip' (35551 KB)...
OKAY [ 2.461s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 7.148s
I did try flashing the firmware zip twice.
I have not found an RUU that works for me. All give a 155 error. I have flashed stock recovery. I have oem lock.
I am totally stuck. I have tried everything I can find to fix the 155 error and nothing works.
I started down this path because my phone just boot loops after installing this ROM.
I have T-Mobile branded HTC One S. That ran SENSE and CM before the 3.4 kernel OK.

zguithues said:
I skipped it without any trouble
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Cool and thanks.
Sent from my HTC One S using Tapatalk 4 Beta

ron_e said:
Did not work for me.
sending 'zip' (35551 KB)...
OKAY [ 2.461s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 7.148s
I did try flashing the firmware zip twice.
I have not found an RUU that works for me. All give a 155 error. I have flashed stock recovery. I have oem lock.
I am totally stuck. I have tried everything I can find to fix the 155 error and nothing works.
I started down this path because my phone just boot loops after installing this ROM.
I have T-Mobile branded HTC One S. That ran SENSE and CM before the 3.4 kernel OK.
Click to expand...
Click to collapse
Okay bro you have to
1.Try your T-Mobile JB RUU this way you'll update the necessary Firmware
If you still get 155 error
2.Try to extract firmware.zip from the T-Mobile JB ota UPDATE ZIP FILE then replace it with my firmware.zip
I'll try to get you another firmware.zip from T-Mobile JB RUU
Sent from my HTC One S using xda premium

LIONS1 said:
Okay bro you have to
1.Try your T-Mobile JB RUU this way you'll update the necessary Firmware
If you still get 155 error
2.Try to extract firmware.zip from the T-Mobile JB ota UPDATE ZIP FILE then replace it with my firmware.zip
I'll try to get you another firmware.zip from T-Mobile JB RUU
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Where has the one in the op come from?
Sent from my HTC One S using Tapatalk 4 Beta

ron_e said:
Did not work for me.
sending 'zip' (35551 KB)...
OKAY [ 2.461s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 7.148s
I did try flashing the firmware zip twice.
I have not found an RUU that works for me. All give a 155 error. I have flashed stock recovery. I have oem lock.
I am totally stuck. I have tried everything I can find to fix the 155 error and nothing works.
I started down this path because my phone just boot loops after installing this ROM.
I have T-Mobile branded HTC One S. That ran SENSE and CM before the 3.4 kernel OK.
Click to expand...
Click to collapse
What's your cid?
That's probably what it's checking.
I would recommend getting super cid and trying then.
My phone is a Cincinnati Bell phone, and it took the tmo jb ruu no problem.
You might as well get soff while you're at it. Then you don't have to worry about fastbooting kernels.
Sent from my One S using xda app-developers app

Darknites said:
Where has the one in the op come from?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
I updated the Op with two firmware.zip one from international JB ota update and other one from T-Mobile JB ota
Sent from my HTC One S using xda premium

LIONS1 said:
I updated the Op with two firmware.zip one from international JB ota update and other one from T-Mobile JB ota
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
The one from December?
Sent from my HTC One S using Tapatalk 4 Beta

LIONS1 said:
Okay bro you have to
1.Try your T-Mobile JB RUU this way you'll update the necessary Firmware
If you still get 155 error
2.Try to extract firmware.zip from the T-Mobile JB ota UPDATE ZIP FILE then replace it with my firmware.zip
I'll try to get you another firmware.zip from T-Mobile JB RUU
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Thanks,
I still get the 155 error
When I open the RUU file in 7zip I only see a couple of files and none of them are firmware.zip. I do not know how to extract it.

ron_e said:
Did not work for me.
sending 'zip' (35551 KB)...
OKAY [ 2.461s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 7.148s
I did try flashing the firmware zip twice.
I have not found an RUU that works for me. All give a 155 error. I have flashed stock recovery. I have oem lock.
I am totally stuck. I have tried everything I can find to fix the 155 error and nothing works.
I started down this path because my phone just boot loops after installing this ROM.
I have T-Mobile branded HTC One S. That ran SENSE and CM before the 3.4 kernel OK.
Click to expand...
Click to collapse
If you get this error your using the wrong firmware for your phone..
Sent from my One S using xda premium

ron_e said:
Thanks,
I still get the 155 error
When I open the RUU file in 7zip I only see a couple of files and none of them are firmware.zip. I do not know how to extract it.
Click to expand...
Click to collapse
Run ruu and leave it running then go to windows temp folder and dig around in there.
Sent from my HTC One S using Tapatalk 4 Beta

Darknites said:
The one from December?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes the 1st JB ota UPDATE cuz the 2nd one just updated the radio so to have all your Firmware updated you need this one for December
Sent from my HTC One S using xda premium

LIONS1 said:
Yes the 1st JB ota UPDATE cuz the 2nd one just updated the radio so to have all your Firmware updated you need this one for December
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Cool.
Sent from my HTC One S using Tapatalk 4 Beta

ron_e said:
Thanks,
I still get the 155 error
When I open the RUU file in 7zip I only see a couple of files and none of them are firmware.zip. I do not know how to extract it.
Click to expand...
Click to collapse
Check the OP the firmware.zip is in the T-Mobile JB ota UPDATE not in the RUU
Sent from my HTC One S using xda premium

{delete, read PAC thread reply, sorry}

Htc One X Telus bad flash

Hi guys, first off I searched all over to find anyone who had the same problem, alas no luck so I decided to post this up if anyone can help. If my dumb ass missed or searched wrong to find the correct link please post it and remove this post. So I have been hacking and modding video game consoles for 5 years, with no problems whatsoever, until I decided to go to phones XD I wanted to root and flash my htc one x which is:
RE-LOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
originally a telus canadian phone. I flashed the phone to cyanogen and the flash took 3 seconds, as soon as I saw it take 3 seconds I knew what I had just done. I've been searching desperately for a RUU or OTA, called into HTC and Telus and they were of no help of course, HTC helped me clear my cache, restore system settings, and all this other fancy work but without any luck. I have tried going into recovery mode but it does not work from bootloader, my phone turns on, goes past the HTC logo then a phone with a little green arrow pointing at the phone appears for a couple mins before being replaced with a red triangle with an exclamation mark inside of it. I have downloaded the OTA and RUU for my phone, neither come with .exe files when I extract them, only boot.img files which I have tried to flash using a hex downloaded from this website but everything keeps failing. If anyone has any advice or a link to a step by step guide too fixing this it would be greatly appreciated, thanks,
Sam.
Once again if there is already a post like this go ahead and remove this I do not mean to spam the website!

How do you expect to flash anything with a locked bootloader?
Sent from my HTC One X using xda app-developers app

exad said:
How do you expect to flash anything with a locked bootloader?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
As I said its been RELOCKED, I can easily unlock bootloader again, when I flashed it was unlocked, only after messing up I decided to relock it

spikypsn said:
As I said its been RELOCKED, I can easily unlock bootloader again, when I flashed it was unlocked, only after messing up I decided to relock it
Click to expand...
Click to collapse
What you're going to want to do is flash the stock recovery and then run the ruu. Then go through the unlock process. I am not sure what exactly your problem is, but this should fix it.

RollTribe said:
What you're going to want to do is flash the stock recovery and then run the ruu. Then go through the unlock process. I am not sure what exactly your problem is, but this should fix it.
Click to expand...
Click to collapse
I ran the RUU and it comes up with this error XD, would you happen to know what the problem is? I tried reflashing Telus stock RUU and rogers RUU with the same radio, both came up with the same error, I also ran the OTA;S one for telus and one for rogers and they both did not work
sending 'zip' (644729 KB)...
OKAY [ 29.539s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 99.287s
K:\One_X_ATT_All-In-One_Kit_v3.0\data>

spikypsn said:
I ran the RUU and it comes up with this error XD, would you happen to know what the problem is? I tried reflashing Telus stock RUU and rogers RUU with the same radio, both came up with the same error, I also ran the OTA;S one for telus and one for rogers and they both did not work
sending 'zip' (644729 KB)...
OKAY [ 29.539s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 99.287s
K:\One_X_ATT_All-In-One_Kit_v3.0\data>
Click to expand...
Click to collapse
Hmm, while the toolkit should do it for you, that is the error encountered when your bootloader is not unlocked.

RollTribe said:
Hmm, while the toolkit should do it for you, that is the error encountered when your bootloader is not unlocked.
Click to expand...
Click to collapse
Awesome, did exactly that and I got 1 step closer but not exactly there yet =)) it gives me this error when i flashed the .zip file now, I am using the 3.17 telus OTA to flash with, btw I cannot figure out a way to mount my phone to my computer so I cannot install the zip or recovery on the phone, any tips would be great, thanks once again guys
sending 'zip' (644729 KB)...
OKAY [ 29.587s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.802s
C:\Users\Yahya\Downloads\One_X_ATT_All-In-One_Kit_v3.0\data>