Related
i have go to S-On whit this tutorial
http://forum.xda-developers.com/showthread.php?t=1187231
after i reboot i can only in the bootloader an its say Security warning.
I can not flash a RUU .
The VF Ruu say bootloader version error, and the HTC Ruu say User ID Wrong.
wat can i do?? My device is a VF devices..
or iss the device absolutly Bricket?!
Bootloader Shows:
****Security Warning****
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
Radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
edit: i think i need a RUU_Saga_Vodafone_UK_1.47. ROM
****....
Try again and again with that RUU.
It didn't worked first time for me either.
Or try other RUU.
I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release
You should go to fastboot and try RUU
thanks for your answers.
i try it again and again (in fastboot)
it say update from 1.47.161.2
to 1.32.161.1 than it stop into 104 Bootloader Version Error.
I use the VF UK 1.32.161.1
all HTC Europe RUU`s says USER ID Error
before i would go to stock i have installed de Virtuos unity 1.31.
and befor this the VF German 1.47...
Try other RUU's...It has to work, anyway the phone is not bricked....maybe you should try revolutionary to get it S-off again. Don't know if it works if you are in fastboot, but you can try.
I try all the RUU`s and all give me (Device ID ERROR, USER ID ERROR) the Vodafone RUU alone give me the Bootloader Version ERROR...
I Try this again and again and ever it give me this errors.
Can not understand that is not worked...
i think i must really wait for a Vodafone RUU Leak that have the version 1.47.
Revolutionary say ever "waiting for Device" i think it will not work into the Fastboot Mode
I am very happy wen any can help me to make the system run.
i found the debug files of the RUUs and cane see wat he do..
i check and can make Fastboot commands over cmd
like this : fastboot devices
than it give an output like:
SH16KTJ01149 fastboot
wen i use any adb commands it never found the device....
can we any make over the Fastboot commands for fixing my problem?!
Or can we any moddifing the RUUs that this accept my device?!
i have copy two debug messages of the Vodafone RUU and a other:
Code:
<T011153><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{95567211-FFFE-46A1-B012-975D1FD8FE2D}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T011153>
<T011237><DEBUG><OUT>sending 'zip' (268758 KB)... OKAY</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011237>
<T011318><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
</DEBUG></T011318>
or debug messages like this:
Code:
<T230252><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{FB1AC174-A654-4612-B610-902E97243E0E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T230252>
<T230335><DEBUG><OUT>sending 'zip' (254595 KB)... OKAY</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T230335>
<T230414><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
</DEBUG></T230414>
HTML:
<T011638><DEBUG><OUT>sending 'zip' (254865 KB)... OKAY</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011638>
<T011717><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T011717>
Stuck in bootloader after use the S-off to S-on tutorial
no one can help???
edit: i see that is the exact same problem in this treath : http://forum.xda-developers.com/showthread.php?t=1190050
should i extract the boot.img and recovery.img from the rom.zip (VF Ruu) and install it over Fastboot commands??
i see a topic about this, but it was another htc phone
http://forum.xda-developers.com/showthread.php?t=1168081
can this work ?!
or should iflash CWM over fastboot ?? can i acces than CWM on s-on hboot??
i have backups from my stock rom.
should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.
Silverbullet09 said:
should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.
Click to expand...
Click to collapse
I'm afraid that I don't really know what is the best step for you to do next, so aren't going to offer any advice in case it's incorrect.
Don't buy an xtc either look into the pay as you go xtc option or find someone who owns one near where you live, and pay to use it, should be about a tenth the cost.
See a very old thread that I created regarding the xtc clip http://forum.xda-developers.com/showthread.php?t=1076937
Swyped from HTC Desire S using XDA Premium
Try to use steps 1 - 10 from this guide : http://forum.xda-developers.com/showthread.php?t=1190992
If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.
globatron said:
If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.
Click to expand...
Click to collapse
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
Very glad to hear it
Swyped from HTC Desire S using XDA Premium
Nomader0 said:
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded
Click to expand...
Click to collapse
do not use this procedure to s-on your Phone wen it iss branded, and you never have a 1.47 RUU from your Provider.
Your Phone is not Bricked but it will Stock on the bootloader,
i think wen you make a GoldCard before you S-on with this methode you are able to install a 1.47 RUU wen this is avaibled for you.
(I am not Sure, i think this only)
The know way to fixed this Problem wen you will not have a GoldCard will tell you another. Thats not my Fame
I think the best iss all have to wait off a SAFE S-ON methode.
We have not the Vodafone UK RUU can install than its not leaked with Version 1.47.
We have install the HTC Europe RUU with this Versions number on my Phone.
A Super CID let you install all RUU Updates with Version 1.47.Never need a GoldCard for this, wen you have Super CID.
I Know the workaround for this but i will tested this before i post this thing her.
@ben_pyett
so if my phone is not branded=i am super CID?
and it is safe to s-on with this method?
no you must enter the super cid wen you are s-off ...
i think you can go with the tutorial but all HTC RUU Europe for unbranded Phones avaibled.
Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
How to you fixed it ?
my DS work only fastboot cmd
help me, plzz...
poppy8x:
In order to bypass CID errors while flashing a RUU you can try one of two methods:
- If you're still S-OFF, you can change your CID to a SuperCID using fastboot (many guides are available at the HTC Sensation forums). Remember to write down your original CID.
- If you're S-ON already, you can create a goldcard using this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ You can get the SD's CID from another Android phone, doesn't have to be yours. Insert the goldcard before flashing the RUU (and keep it in until the process ends), and you should be good to go.
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
hello everybody
I send my sensation back for waranty and now i have it back completely stock.
Is it possible to unlock the sensation without using the htcdev's method?? and if this isn't possible can somebody help me with using the htcdev's method because when i presse the begin to unlock button on there site nothing happened.
S-on
hboot: 1.27.0000
Latest stock rom (4.0.3)
I cant start on the htcdev.com/bootloader page the 'begin unlock bootloader button' when i press this button nothing happened
can somebody help me!! :'(
darretje said:
hello everybody
I send my sensation back for waranty and now i have it back completely stock.
Is it possible to unlock the sensation without using the htcdev's method?? and if this isn't possible can somebody help me with using the htcdev's method because when i presse the begin to unlock button on there site nothing happened.
S-on
hboot: 1.27.0000
Latest stock rom (4.0.3)
I cant start on the htcdev.com/bootloader page the 'begin unlock bootloader button' when i press this button nothing happened
can somebody help me!! :'(
Click to expand...
Click to collapse
Hi,
Have a go with THIS TOOLKIT
You can't unlock your Sensation "hboot: 1.27.0000" by HTC Dev method, nor by Revolutionary. Still no working solution. Same happened to me, nothing useful found till now.
freec1 said:
You can't unlock your Sensation "hboot: 1.27.0000" by HTC Dev method, nor by Revolutionary. Still no working solution. Same happened to me, nothing useful found till now.
Click to expand...
Click to collapse
Hi,
Check the post above yours.
The toolkit will allow this ,if you want.
malybru:
"Check the post above yours.
The toolkit will allow this ,if you want."
Revolutionary Does not support HBOOT 1.27.0000, so the toolkit won't help.
I have 1.27.0000 s-on.
I'm stucked at first step of S-OFF: HTCdev does not work, tried many times. Ends with failure message:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.141
So I can't unlock bootloader with JuopunutBear. First requirement is to unlock with HTCDev. So I think it won't work for me.
Idk if unrevoked works whit this device??
Sent From My Sexy Sensation.
shahkam said:
Idk if unrevoked works whit this device??
Sent From My Sexy Sensation.
Click to expand...
Click to collapse
Unrevoked does not support Sensation. Tried.
I found this in Android Development section, maybe helps someone to root HBOOT 1.27.0000 device:
[Guide] Root Official ICS ROM HBoot 1.27.000 Easely without S-Off
---------- Post added at 03:48 PM ---------- Previous post was at 03:37 PM ----------
In that section guys wrote that it worked for them.
I tried this method, but failed at first step again: HTC DEV onlock bootloader does not work!
C:\TEMP\a\HTC S\OneX root\One_X_All-In-One_Kit_v1.0\data>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.157s
I was told just keep trying, but no luck.
Anyway tried to flash recovery:
C:\TEMP\a\HTC S\OneX root\One_X_All-In-One_Kit_v1.0\data>fastboot flash recovery Recoveries/CWM5827.img
sending 'recovery' (4876 KB)... OKAY [ 1.195s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.826s
Will Revolutionary support HBOOT versions over 1.18.0000 ?
ive been reading but cant find a definate answer so forgive me if i missed it but can my rogers with 3.16 ota with hboot 2.14 (rooted with venom 3.2.6)be s-off'd
it doesnt show cid 11111111 but when i fastboot read cid it states it does have cid 11111111
thanks
I don't think anyone has successfully done it yet. I've got a member I've helped get unlocked and root permissions for the rogers jb ota. I'd like to have kamillo try it and see if we can get it to take.
Sent from my HOX w/CM10.1 4.2.2 s-off
ok thanks for the info subarudroid appreciate that
hopefully something comes of this
keep up the great work devs
babarnard said:
ive been reading but cant find a definate answer so forgive me if i missed it but can my rogers with 3.16 ota with hboot 2.14 (rooted with venom 3.2.6)be s-off'd
it doesnt show cid 11111111 but when i fastboot read cid it states it does have cid 11111111
thanks
Click to expand...
Click to collapse
Ya just use one of the guides around the forums to change CID. Then s-off.
RollTribe said:
Ya just use one of the guides around the forums to change CID. Then s-off.
Click to expand...
Click to collapse
I was thinking that was the way to go. Fastboot oem writecid 11111111
Sent from my HOX w/CM10.1 4.2.2 s-off
C:\Users\BRUCE BARNARD\Downloads\adb-fastboot\untitled folder>Fastboot oem write
cid 11111111
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 1.074s
this is what i get when i try to write cid as you specified
im pretty new to this so no im lost
C:\Users\BRUCE BARNARD\Downloads\adb-fastboot\untitled folder>fastboot getvar ci
d
cid: 11111111
finished. total time: 0.002s
this is what i get when i check the cid
thanks guys
You gonna try it? Need help pm me?
Sent from my HOX w/CM10.1 4.2.2 s-off
thanks for the help guys
goes to show if you read read read then follow directions to a t you will get what you want and what they say it will do
achieved s-off
thanks again and keep up the GREAT WORK devs
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