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>
Related
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
i had the issue with NO SERVICE and WIFI issue and i fixed all of these after changed cid to 11111111 and installed OTA RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5 and everything went perfect no service and wifi fixed!
than when trying to UNLOCK im getting:
fastboot flash recovery Recoveries/TWRP.img
sending 'recovery' (7700 KB)... OKAY [ 1.531s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.078s
im unable to root and install CWM/TWRP
****UPDATE: every time u use RUU update u must generate new token from dev for unlock..
Is your Bootloader unlocked when you try flashing the recovery? Because from what i can understand your bootloader wont unlock and your attempting to flash recovery in fastboot
Also i think recall seeing alot of people getting no service and wifi problems after changing CID and flashing EURO RUU...
I'm supercid'd, just ran 2.21 ruu yesterday with out a issue.
HTC One S™
fmedrano1977 said:
I'm supercid'd, just ran 2.21 ruu yesterday with out a issue.
HTC One S™
Click to expand...
Click to collapse
i did that to but having some problems with calls..
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
Hello,
I get an Error when i try to flash the firmware.zip for MaximusHD
Code:
sending 'zip' (36985 KB)...
OKAY [ 2.699s]
writing 'zip'...
(bootloader) zip header checking.
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.146s
I figured out it may relyto my bootloader.
I'm currently on HBoot 1.14.0002,so i guess its bootloader 2.31
S-ON and unlocked
I read it worked on 2.16, so how do i downgrade.
I really dont want to mess up my bootloader, so i better ask for some advice here
I found this Thread
http://forum.xda-developers.com/showthread.php?t=1990043
But i'm not sure if i took the JB OTA(Had an JB based Rom before)
You gotta be s-off and unlocked and do the commands one by one in command promt. First time it will give u an error...re-do the command right away and it should work.
Also as an advise read the instruction carefully at least 3 times so u undestand what u doing.
So i have to follow this guide
http://forum.xda-developers.com/showthread.php?t=2155135
Read it before, but couldn't figure out if it will help me.
Thanks so far.
Try this one.
http://forum.xda-developers.com/showthread.php?t=2325590
And don't worry about bricking the phone, it's almost imposible. As long as you can go into bootloader you can bring it back to life. I've done it many times.
Also I'm using unknown 2.0 becuase maximus 10 gave me too many problems. I recomend you to use the same as me is basically the same.
Well already got superCID and did everything the guide told me.
Was a bit confused about SuperCID since it didnt sayed CW_001 or something similar.
Could now flash the firmware.zip.
Only messed up my sdcard but i saw that one coming
Thank you very much!
jenenser83 said:
Try this one.
http://forum.xda-developers.com/showthread.php?t=2325590
And don't worry about bricking the phone, it's almost imposible. As long as you can go into bootloader you can bring it back to life. I've done it many times.
Also I'm using unknown 2.0 becuase maximus 10 gave me too many problems. I recomend you to use the same as me is basically the same.
Click to expand...
Click to collapse
Hi Jenenser, I'm on Maximus, Hboot 2.16, s-off, unlocked. I'm trying to get back to Unknown 2.0 because I find Maximus to be too buggy as well. I can't seem to flash anything from fastboot (not recovery, not firmware, can't run RUU, nothing seems to take). How did you get back to Unknown?
Thanks!
Go back to complete stock or RUU than repeat the while unlocking process again.
Unlock bootloader, root the phone, install recovery and then from twrp recover install ROM.
Some info
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot getvar version-main
version-main: 2.20.502.7
finished. total time: 0.026s
And I have HBOOT-1.14.0002
I show
TAMPERED
RELOCKED
I can not seem to flash back to stock using htc_one_x_RUU_2.20.502.7_att_us_08022012.exe, it fails.
So then I get the rom.zip file from htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and run...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.983s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.433s
Im guessing this is because I followed the instructions (to relock the bootloader) before I ran htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
What would you recommend as my next step?
Im following this guide http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
I was able to unlock the bootloader... Now Im stuck here...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.981s]
writing 'boot'...
OKAY [ 1.548s]
finished. total time: 2.531s
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.016s
"Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working due to system.img file being to large."
The error that you are getting seems to be indicative of a known issue. I am sure someone who knows whats up will be along shortly. At least you can take comfort in knowing you are not the only person with this issue. That is when things get scary lol.
Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita
timmaaa said:
Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.
Sent from my Evita
Click to expand...
Click to collapse
I am S-ON and I do not have SuperCID.
LanceM said:
I am S-ON and I do not have SuperCID.
Click to expand...
Click to collapse
fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.010s]
finished. total time: 0.010s
fastboot getvar cid
cid: HTC__621
finished. total time: 0.003s
When I try and flash
1.85 or 1.83
I get this error
<T111504><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
You can't RUU backwards unless you're s-off.
Sent from my Evita
timmaaa said:
You can't RUU backwards unless you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ok Tim... So what do I do to get 2.20 on the phone, stock...
If you're wanting to run the at&t RUU you'll also need the at&t CID. Otherwise you need to run the RUU that corresponds with the HTC__621 CID. Why is it the 2.20 in particular that you want?
Sent from my Evita
Im not stuck on 2.20. I just want the phone back to stock.
Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita
timmaaa said:
Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.
Sent from my Evita
Click to expand...
Click to collapse
Well, that is my question... What RUU is compatible with my CID? And can I change the CID to work for an AT&T RUU, because it seems like 621 is a tawian RUU. If I can, what do I need to change the CID too?
Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita
timmaaa said:
Did you change the CID to HTC__621? It doesn't look like an Evita CID.
Sent from my Evita
Click to expand...
Click to collapse
No, when I got the phone a while ago, I rooted and superCID'ed it. It was changed to 1111111, but now for some reason it has changed to 621, which I dont quite understand and has caused quite an issue for me trying to go back to stock.
The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita
timmaaa said:
The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?
Sent from my Evita
Click to expand...
Click to collapse
I bought the phone in San Antonio at an AT&T store.... Way back when the phone just came out...
At that point, after XDA had root and SuperCID, I did those... And put CM10 on it... Through many upgrades and tinkering, somehow the phone got the CID 621. An Asian CID, I did NOT do this.
Regardless, it is fixed now. I followed the instructions in this thread to change the CID back to 1111111. It worked, then what I did was push the recovery and boot from 2.20 to the phone, then re-locked it.
At this point, I ran the 2.20 RUU and it took... Then I ran the 3.18 phone and now... QHSUSB_DLOAD
Off to http://forum.xda-developers.com/showthread.php?t=1966850
Now downloading linux...
I will fix this damn thing lol!
You pulled a classic megadoug. S on super Cid ruu strikes again. JTAG is the only way to fix it now
Sent from my HTC One XL
Yep. S-on + SuperCID + jb RUU = brick. So you'll need a jtag repair. It's worth tying the unbrick method but nine times out of ten it doesn't work.
Sent from my Evita