Related
I'm stuck
I got my Sensation back from repairs with 1.18 and pressed on and rooted. I now run rooted stock 2.3 with S-On but unlocked using HTC method (Revolutionary didn't work for some reason) and ClockWorkMod with SuperCID
This is where the problems started
I can't get S-Off
I have tried everything I can find (literally been on this for hours). I've tried:
Revolutionary 0.4pre4 (which fails to gain root - possibly because I've already got root)
HTCSuperTool (v3 of which appears to be broken, btw)
Downloading various firmwares and flashing them (using the PG58img.zip/bootloader method)
I've even tried running the RUU exe and pulling the rom.zip, renaming that and dropping that in the SD card
Running the RUU (both the latest T-Mobile UK and the latest ICS version)
The weird thing is that it reads the PG58img.zip files, loads them, starts to parse them then goes back to bootloader and doesn't read them again unless I reboot the bootloader
Update: Re-locked the bootloader and still can't run the RUU for ICS
Any ideas?
Anyone? Please help!
I've just been through all this after getting my phone back from repair. Mine came back with t-mobile branded rom version 1.50.110.2 and wouldnt s-off with revolutionary. Luckily the phone still had supercid so i flashed RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe and revolutionary finally worked. You can read my thread here http://forum.xda-developers.com/showthread.php?t=1538324
Thank you, I'll try that (if I can ever get a slot on the FileFactory download server...)
I've got a 1.17 hboot.img from Kohr-Ar (used in one of the PG58IMG.zips), could I use fastboot flash hboot hboot.img to flash that or would i be left with a brick?
Ok, got the ROM and tried to flash but I forgot that I put the CID back to the T-Mobile CID. Now, I can't change the CID, I always get:
>fastbooot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.079s]
finished. total time: 1.080s
Any ideas now?
pnlrogue1 said:
Ok, got the ROM and tried to flash but I forgot that I put the CID back to the T-Mobile CID. Now, I can't change the CID, I always get:
>fastbooot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.079s]
finished. total time: 1.080s
Any ideas now?
Click to expand...
Click to collapse
did u find any solution , i am exactly in same situation i also did exactly same thing now stuck
Try to run ruu ???
Sent from my HTC Sensation 4G using xda premium
Afraid not. I tried all sorts of things - best I can say is do NOT try to flash your bootloader using the fastboot method - found that out the hard way...
I think flashing an alternative ROM may help but I'm not sure. Maybe contact the devs of Revolutionary - it just wants a way of skipping the Zerging Root stage in V0.5...
Find my post and do it step by step run ruu then change cid
Sent from my HTC Sensation 4G using xda premium
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 ?
Hi,
Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".
I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.
Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.
With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.
I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)
Could anyone advise if there's a way I can get my phone back?
Bootloader text as folows:
Code:
*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34
Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
But if I choose Recovery, it just reboots to Bootloader.
Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
jezash said:
Hi,
Like, it seems, plenty of others, I messed up my phone by trying a custom ROM and then screwing up the "return-to-stock".
I have a T-Mo UK Sensation which was running GB 2.3.4 until I put Android Revolution HD 6.5.5 XE on it.
Basically I fell into the S-ON trap, and bricked the device. Wouldn't power on at all.
With help from Dexter from the unbrick project, I have managed to get the phone to load into Bootloader, but it won't load the Android OS, nor will it go into recovery.
I think the usual next step is to use latest RUU to flash a new ROM. Thing is, my phone is now S-ON and thinks it's a T-Mo UK phone again (CID T-MOB005, I think). And T-Mo UK's last released upgrade is ancient (RUU_Pyramid_TMO_UK_1.34.110.1). So there isn't a ROM that is new enough AND compatible with my CID number. I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2, but even that sounds like it'll be too old (I'm guessing it probably doesn't have HBOOT 1.27)
Could anyone advise if there's a way I can get my phone back?
Bootloader text as folows:
Code:
*** LOCKED ***
*** Security Warning ***
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17.33.34
Then the usual Vol Up, Vol Down instructions, and
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I go into Bootloader these options change to:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
But if I choose Recovery, it just reboots to Bootloader.
Would be really grateful if anyone can help me. I'm not v popular at home having spent hours trying to fix this mess (and getting pretty stressed about it!)
Click to expand...
Click to collapse
Hi,
I am not sure where exactly you want to end up.
But if you wanted to get an ICS ROM on your phone,try THIS THREAD
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.
Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.
I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.
The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?
Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.
When I tried to flash the 4EXT recovery, I got an error message:
sending 'recovery' (6116 KB)... OKAY [ 1.507s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.298s
Does this mean that the unlock hasn't actually worked then?
jezash said:
thanks for the suggestion. At the moment I just want a working phone. Don't really mind if it's ICS or not.
Just gone through the HTC Dev procedure. Was sceptical as adb devices didn't return any connected devices. But it got the code and I was able to get the token via email.
I sent the command fastboot flash unlocktoken Unlock_code.bin and it appeared to succeed. However, I didn't see the message in Step 13. The phone still shows bootloader and it still says ***Locked***.
The Step 13 message looks like an android OS thing - I wonder if I can't see it unless I can boot to Android?
Anyway, I pressed onto the section about flashing a recovery. Again, no device shows up in adb devices.
When I tried to flash the 4EXT recovery, I got an error message:
sending 'recovery' (6116 KB)... OKAY [ 1.507s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.298s
Does this mean that the unlock hasn't actually worked then?
Click to expand...
Click to collapse
Hi,
Have you got the necessary drivers installed to use ADB.
Try using THIS TOOLKIT
It has the drivers,and an unlock section.
first of all confirm your CID
fastboot getvar cid command will give you cid
if its supercid (unlikely) or any other which has ICS ROM for it ..then you are lucky
other wise try the HTCdev method again...no need to get the unlock_code again
just use the one you got previously ...then reboot and see..hopefully it works
hi, thanks for various suggestions.
have tried the HTCDEV method a couple of times without success. I never see the Confirmation Screen shown in step 13 on the HTCDEV bootloader unlock procedure.
Definitely have the HTC drivers installed, have previously used adb successfully from this PC. Plugged in my old HD2 (running Android) and adb devices finds it ok.
Checked my CID as suggested, it's T-MOB005.
Tried downloading the toolkit suggested by malybru and didn't get any further - I think it just does the same thing (runs the HTCDEV unlock process).
One thing that's odd. I tried flashing 4EXT Recovery from command prompt. A "loading" bar showed up on the right side of the screen of the phone like it was working, but then I get the "signature verify fail" shown above.
I guess I can't use Revolutionary S-OFF as I can't boot to Android.
What can I do? Should I try this: http://forum.xda-developers.com/showthread.php?t=1469296 - Edit - actually it seems like that still needs the HTC DEV unlock to work ... which seems to be my problem :-(
have tried the HTCDEV unlock method quite a few times now. In the command prompt it appears to work successfully, but I never get the Android-like confirmation screen (I think this must be because my phone will not currently boot to Android).
As I think I need to unlock before I can flash anything else, I am stuck. :-(
Does anyone have a suggestion for another way to unlock it?
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
jezash said:
Given that T-Mobile UK have not given any date for releasing ICS, I have no notion of when I can fix my phone. Hence considering sending for repair - presumably replacing CPU or something would fix it? Any idea how much this would cost? (Using my old HD2 running a somewhat unstable version of Android is starting to drive me crazy).
Click to expand...
Click to collapse
Can you pop in the irc? We can do some last tries before you send it for repairs
Sent from my pyramid.. Through blazing fast sonic waves
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.
thanks for your reply.
jezash said:
hi ganesh - am in the IRC now. only for the next 15 minutes or so. if you think there is something remaining that is worth trying i can come back tomorrow.
thanks for your reply.
Click to expand...
Click to collapse
EDIT:based on these values ..seems like something can be done..remember ..this is all to avoid extra money to get it repaired
can you post some more details?
fastboot getvar all (except IMEI and SERIAL NO )
Hi Ganesh,
Thanks for your reply. Here are the details from my phone:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: 11.22.3504.07_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.34.206.1
INFOserialno:
INFOimei:
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: T-MOB005
INFObattery-status: good
INFObattery-voltage: 4032mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.480s
Cheers
now that we know that the stock rom flashed .(before brick)
get the 1.50 RUU and try to RUN it
how you do that
phone in fastboot ...connect it to pc and run the RUU.exe
if it still dint worked
then extract the rom.zip form RUU
http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/
then keep the rom.zip in adb folder and flash it manually
manual flash steps
1.fastboot erase cache (if its failing ...ignore it)
2.fastboot oem rebootRUU (black screen with silver HTC)
3.fastboot flash zip rom.zip (pastebin the output if failed)
4.fastboot reboot-bootloader (check the bootloader there ..changed or not )
hi ganesh,
latest rom available that i can find (for t-mo uk) is 1.34. That ok?
cheers
EDIT: ok, so trying to run the RUU, it looks like it's going ok, starts sending the ROM to the phone, and then aborts with a ERROR [155]: UNKNOWN ERROR.
Will try the manual steps you gave.
jezash said:
hi ganesh,
latest rom available that i can find (for t-mo uk) is 1.34. That ok?
cheers
Click to expand...
Click to collapse
yes try that first if it fails (both ways )
get the updated RUU
I asked Football and he suggested he could get RUU_Pyramid_TMO_UK_1.50.110.2
Click to expand...
Click to collapse
from football ^
and use that and repeat the rom flash again
hi ganesh,
ok, here's what came back when i tried to flash manually.
C:\adb>fastboot flash zip rom.zip
sending 'zip' (381007 KB)... OKAY [ 51.085s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 103.934s
EDIT:
when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!
will contact football again as you suggested.
2nd EDIT:
my bootloader displays HBOOT-1.27.0000 ... isn't the problem still that even 1.50 has an older HBOOT than this, and hence the rom flash fails?
jezash said:
hi ganesh,
ok, here's what came back when i tried to flash manually.
C:\adb>fastboot flash zip rom.zip
sending 'zip' (381007 KB)... OKAY [ 51.085s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 103.934s
EDIT:
when I disconnected USB from phone, it also displayed error message: Hboot version is older / Update fail!
will contact football again as you suggested.
Click to expand...
Click to collapse
yeah thats expected ...can you try one more thing ..can you just remove the hboot.nb0 file from the rom.zip (have a copy of it somewhere safe ..so that you can add later when required)
EDIT: also you need to edit the android-info.txt file ..change the HBOOT inside with te one you have i.e. 1.27.0000 then make the zip again then try flashing it sorry my bad there wont be HBOOT in the android-info.txt ..just cidnum ,modelid etc etc
then do the flash of rom.zip again
weird. I couldn't find that file in the rom.
the contents are as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT - oh, duh, the longer file name that ends as you said. sorry. will try now.
ok, tried this. unzipped, removed the hboot_Pyramid_8x60_1.17.0011_20110602_signedbyaa.nb0 file, rezipped. followed the four manual flash steps that you suggested, and got the following message in cmd:
C:\adb>fastboot flash zip rom.zip
sending 'zip' (375099 KB)... OKAY [ 50.217s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 100.357s
Football can get me a TMO-UK RUU 1.50. There is a cost, apparently. Hence wondering if there's a reason why 1.50 should work when 1.34 doesn't, give - if i understand correctly - that neither is HBOOT 1.27.
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..
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