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
Related
After repairing my HTC Sensation, lost the S-OFF and ROOT, SWAP and chage the original IMEI.
Now I have S-ON HBOOT 1.27.000, and through the website HTCDev fails in step 14, is this error:
C: \ Android> fastboot flash unlocktoken
Unlock_code.bin
sending 'unlocktoken' (0 KB) ...
OKAY [0.156s]
writing 'unlocktoken' ...
FAILED (remote: unlock token check
failed)
finished. Total time: 0.172s
How to make S-Off with HBOOT 1.27.000?
From my HTC Sensation Z710e using XDA
bertonegt said:
After repairing my HTC Sensation, lost the S-OFF and ROOT.
Now I have S-ON HBOOT 1.27.000, and through the website HTCDev fails in step 14, is this error:
C: \ Android> fastboot flash unlocktoken
Unlock_code.bin
sending 'unlocktoken' (0 KB) ...
OKAY [0.156s]
writing 'unlocktoken' ...
FAILED (remote: unlock token check
failed)
finished. Total time: 0.172s
How to make S-Off with HBOOT 1.27.000?
From my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
You can't, at least not yet. S-OFF by Revolutionary does NOT support HBOOT 1.27 yet, you just have to wait untill Revolutionary has been updated.
Edit: Just read that you were trying to do S-OFF with HTCdev instead of Revolutionary but i guess it wont work for the same reason.
bertonegt said:
After repairing my HTC Sensation, lost the S-OFF and ROOT.
Now I have S-ON HBOOT 1.27.000, and through the website HTCDev fails in step 14, is this error:
C: \ Android> fastboot flash unlocktoken
Unlock_code.bin
sending 'unlocktoken' (0 KB) ...
OKAY [0.156s]
writing 'unlocktoken' ...
FAILED (remote: unlock token check
failed)
finished. Total time: 0.172s
How to make S-Off with HBOOT 1.27.000?
From my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
You're probably going to have to take it back to 1.17.1111, which is the original Revolutionary firmware.
To do that, flash it from here, then proceed to follow this steps in this guide.
ReeF666 said:
You're probably going to have to take it back to 1.17.1111, which is the original Revolutionary firmware.
To do that, flash it from here, then proceed to follow this steps in this guide.
Click to expand...
Click to collapse
If the OP is S-ON that can't be done as the bootloader isn't unlocked. The official HTC method should work but Revolutionary won't
I heard it's possible to downgrade, get S-OFF, and then do an upgrade, right?
EddyOS said:
If the OP is S-ON that can't be done as the bootloader isn't unlocked. The official HTC method should work but Revolutionary won't
Click to expand...
Click to collapse
Ah, yeah, sorry, I didn't read it properly, cheers.
Thanks, but the official htc metod don't work! I don't understand!
The solution is wait a revolutionary metod?
Sent from my HTC Sensation Z710e using XDA
Flash the old 1.17 firmware from http://forum.xda-developers.com/showthread.php?t=1459767 , then use the revolutionary method to get S-OFF, and then flash the new firmware again?
I've the same poblem, but you can't flash any firmeware with this hboot.
For me, it doesn't work.
yozas said:
Flash the old 1.17 firmware from http://forum.xda-developers.com/showthread.php?t=1459767 , then use the revolutionary method to get S-OFF, and then flash the new firmware again?
Click to expand...
Click to collapse
You can't if you're S-ON as you don't have access to flash the firmware
I don't flash any Firmware with this HBOOT i try all
Sent from my HTC Sensation Z710e using XDA
So, at the moment there isn't any change to downgrade the firmeware and get S-Off?
I'm pretty sure that I flashed ARHD, although having the ICS from HTC installed.
I have a s-ON...
Sent from my HTC Sensation Z710e using XDA
m33-snk said:
So, at the moment there isn't any change to downgrade the firmeware and get S-Off?
I'm pretty sure that I flashed ARHD, although having the ICS from HTC installed.
Click to expand...
Click to collapse
If you were still S-OFF (as an RUU/OTA doesn't change this) then you can do that. If you're S-ON, you're stuck
EddyOS said:
You can't if you're S-ON as you don't have access to flash the firmware
Click to expand...
Click to collapse
What about this thread? http://forum.xda-developers.com/showthread.php?t=1469296
the section "Revolutionary Method ( ICS , General discussion )" has some points to try I think? If not, would flashing an old RUU help?
Can't flash an old RUU either as the HBOOT is lower than 1.27 - you can only go up, not down
Ok thanks! But where is the solution for my problem?
Wait a revolutionaty metod?
Sent from my HTC Sensation Z710e using XDA
bertonegt said:
Ok thanks! But where is the solution for my problem?
Wait a revolutionaty metod?
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
i feel you, bertonegt. im also on a S-ON 1.27.0000 hboot. dont try anything for now, wont work, you risk to have more problems only.
i hate to break it to you like this, but there wont be any update to the Revolutionary method. Another group of people claim they are working on this and they do have a solution, so wait for them. Keep fingers crossed so a "maybe" will become "certainly". When? Never ask an ETA
would I be very wrong if I said that this is very promising?
http://forum.xda-developers.com/showthread.php?t=1573577
http://forum.xda-developers.com/showthread.php?t=1522351
Very much so, if it is true
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..
Hey there,
just today I got my Phone back from HTC for repairing the Display.
On the delivery paper was a notice that the mainboard was replaced and the phone now has a different IMEI.
As I now tried to gain an unlocked bootloader by using the HTCDev Method, I get the same error everytime:
Code:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.164s
I am 100% sure, that I didn't make a mistake while unlocking.
Do you have any suggestions?
Niklas
As far as I know if htc has changed your motherboard, the unlocking method on htcdev website is not going to work. You need to follow Ganeshp's guide to achieve S-OFF. It is in GENERAL section.
Yes after you get your motherboard changed HTC DEV meathod will not work
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
above users are right
motherboard replaced
which means different imei
so htcdev method won't work for you anymore
EDIT: Problem solved
Ok, thanks, finally got S-OFF and root working
I also installed 4ext Recovery, but my last backup was made using TWRP-Touch-Recovery.
When I now try to flash TWRP using Goomanager it doesn*t work, now i tried flashing it via fastboot and i also get an error
Code:
C:\Users\***\Desktop\Sensation\toolkit\Data>fastboot flash recovery recovery.i
mg
sending 'recovery' (5472 KB)...
OKAY [ 1.402s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.721s
Can I either convert my backups to 4ext format, or is there another possibility to flash twrp?
niklas1407 said:
EDIT: Problem solved
Ok, thanks, finally got S-OFF and root working
I also installed 4ext Recovery, but my last backup was made using TWRP-Touch-Recovery.
When I now try to flash TWRP using Goomanager it doesn*t work, now i tried flashing it via fastboot and i also get an error
Code:
C:\Users\***\Desktop\Sensation\toolkit\Data>fastboot flash recovery recovery.i
mg
sending 'recovery' (5472 KB)...
OKAY [ 1.402s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.721s
Can I either convert my backups to 4ext format, or is there another possibility to flash twrp?
Click to expand...
Click to collapse
you have that error because probably you don't have a patched hboot version
that's why the fastboot command fails
actually post the bootloader details to confirm it
rzr86 said:
you have that error because probably you don't have a patched hboot version
that's why the fastboot command fails
actually post the bootloader details to confirm it
Click to expand...
Click to collapse
Code:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012,17:33:34
What do I need to do to solve this issue?
niklas1407 said:
Code:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012,17:33:34
What do I need to do to solve this issue?
Click to expand...
Click to collapse
i dont know why your trying to unlock with HTC DEV your already S-OFF :s Download the Hboot i attatched its from unlimited.io and put it on the root of your sdcard and reboot into bootloader accept the flash and then flash any recovery and your away
do as above user said
that is the patched hboot version
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>
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.