Hello everybody! I need help urgent! I have my AT&T HTC One X (XL according to my "Settings" "Model Number" and I need to restore back to stock. I'll list everything that is wrong, I need help with, and more settings on my device. MAINLY, IF ANYBODY CAN AT LEAST HELP ME TO FIND MY CID AS SOON AS POSSIBLE, THAT'S ALL I NEED AS FAR AS I KNOW RIGHT NOW.
My Device Settings:
1. Android Version: 4.1.1
2. I did successfully flash to "MIUI-3.8.9" using "Hasoon2000's HTC One X (Evita) All-In-One Toolkit" for most of this.
3. HBOOT/Bootloader:
*** TAMPERED ***
***RELOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
4. RECOVERY:
ClockworkMod Recovery v6.0.3.1
Notes:
1. I looked at the video on youtube, "TUTORIAL: HTC One X stock ROM update: 4.1.1 to 4.2.2 (via CWM)" using CWM (same version) but kept getting status error 0 no matter whether odexed or deodexed.
2. I tried using fastboot options I saw on other posts on this website to find your stock CID, but it still showed 11111111.
3. I used "Hasoons200's Toolkit" to SuperCID to 11111111.
4. "Xfactor" on the toolkit to exploit the device's CID.
Help With:
1. To at least get/find out a way to find out my TRUE STOCK CID as quick as possible.
2. To find the RUU used for this device.
I truly thank all of you for your help!
If your phone is an at&t model the original CID is CWS__001. Your CID doesn't actually matter anyway because you're s-off, you can run any Evita RUU without any problems regardless of your CID. The reason fastboot commands were showing your CID as 11111111 is because your CID is 11111111, that's because SuperCID overwrites the original CID.
There's nothing at all "wrong" with your device. I think you're extremely confused. I'm not sure why you've been trying all those toolkits, those give you SuperCID, they don't reverse it. You seem to lack a basic understanding of this device, modifying it, and what you can and can't do with it. Why exactly do you want to return to stock? I can tell you exactly how to do it but I'd like to know why first.
Sent from my Evita
timmaaa said:
If your phone is an at&t model the original CID is CWS__001. Your CID doesn't actually matter anyway because you're s-off, you can run any Evita RUU without any problems regardless of your CID. The reason fastboot commands were showing your CID as 11111111 is because your CID is 11111111, that's because SuperCID overwrites the original CID.
There's nothing at all "wrong" with your device. I think you're extremely confused. I'm not sure why you've been trying all those toolkits, those give you SuperCID, they don't reverse it. You seem to lack a basic understanding of this device, modifying it, and what you can and can't do with it. Why exactly do you want to return to stock? I can tell you exactly how to do it but I'd like to know why first.
Sent from my Evita
Click to expand...
Click to collapse
Yeah I do have AT&T. Also, yes, I'm pretty new at rooting and such, but I am still learning
I forgot to add this in the post, will edit it in, that I am using "MIUI" like said, and I decided I wanted to get another rom. I tried to get "Paranoid Android", latest version, boot-loader both unlocked and locked, and TWRP and CWM recovery. It came up with status 0 (having to do with the update-binary) but luckily I made a nandroid backup. The device is still working from the nandroid backup, but I will probably use the CID (CWS__001) to get the stock RUU endeavor, then flash.
Eh.. You have an evita, not endeavor. If you flash endeavor stuff you will likely brick.
Sent from my HTC One XL using xda app-developers app
exad said:
Eh.. You have an evita, not endeavor. If you flash endeavor stuff you will likely brick.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok. IS there anyway to know which RUU I would need to get stock without CID? If you need any information to help me with this (such as rom version I'm currently using and such) I'll let you know.
Antm50jr said:
Yeah I do have AT&T. Also, yes, I'm pretty new at rooting and such, but I am still learning
I forgot to add this in the post, will edit it in, that I am using "MIUI" like said, and I decided I wanted to get another rom. I tried to get "Paranoid Android", latest version, boot-loader both unlocked and locked, and TWRP and CWM recovery. It came up with status 0 (having to do with the update-binary) but luckily I made a nandroid backup. The device is still working from the nandroid backup, but I will probably use the CID (CWS__001) to get the stock RUU endeavor, then flash.
Click to expand...
Click to collapse
The installer for Paranoid Android probably failed because the ROM wasn't meant for this phone, you got lucky it didn't brick you. You have the Evita, not the Endeavoru, I'm not sure where you're downloading your ROMs from but it's the wrong place. Only ever download ROMs from within this device forum you're posting in now, NEVER anywhere else.
Sent from my Evita
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
Antm50jr said:
Ok. IS there anyway to know which RUU I would need to get stock without CID? If you need any information to help me with this (such as rom version I'm currently using and such) I'll let you know.
Click to expand...
Click to collapse
You have s-off so you can run any Evita RUU that you want, your CID doesn't matter when you have s-off. Go to androidruu.com and get one from there, just make sure it's from the Evita section. I still have no idea why you want to RUU though, you said you just want to change ROMs, an RUU will return your phone to being completely stock.
Sent from my Evita
timmaaa said:
The installer for Paranoid Android probably failed because the ROM wasn't meant for this phone, you got lucky it didn't brick you. You have the Evita, not the Endeavoru, I'm not sure where you're downloading your ROMs from but it's the wrong place. Only ever download ROMs from within this device forum you're posting in now, NEVER anywhere else.
Sent from my Evita
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
You have s-off so you can run any Evita RUU that you want, your CID doesn't matter when you have s-off. Go to androidruu.com and get one from there, just make sure it's from the Evita section. I still have no idea why you want to RUU though, you said you just want to change ROMs, an RUU will return your phone to being completely stock.
Sent from my Evita
Click to expand...
Click to collapse
I can't believe this! It turns out, it's bricked I think! I tried to restore from a nandroid backup I got off the internet, not sure whether it was evita or not, WAS ON THIS WEBSITE (XDA), and not it won't boot. The screen is on, but it shows the white screen HTC logo with red letters under it, and made a low buh-buh sound when in USB. I cant find a way to enter boot-loader or recovery (computer cant detect it) but it does show the solid red light at the top. Please, even if it involves downloading a ton of computer applications, I'm willing to.
I can believe it. Why the hell did you restore a nandroid if you're not even sure if it was for Evita? Have you not listened to a word we've been saying to you? I'm not sure why I bothered trying to help you if you're ignoring the advice I'm giving. Your phone isn't bricked, if it turns on it isn't bricked. Do some research and figure out how to recover.
Sent from my Evita
timmaaa said:
I can believe it. Why the hell did you restore a nandroid if you're not even sure if it was for Evita? Have you not listened to a word we've been saying to you? I'm not sure why I bothered trying to help you if you're ignoring the advice I'm giving. Your phone isn't bricked, if it turns on it isn't bricked. Do some research and figure out how to recover.
Sent from my Evita
Click to expand...
Click to collapse
I just wanted to say that I am sorry, and I did fix the problem. Thank you for your support! You are right: I should have listened and pay more attention. Thank you though! I'll always check to see whether a rom is Evita or Endeavor.
Related
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
splayer7 said:
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
Click to expand...
Click to collapse
Exactly what has been said. There is no unrooting or S-On restoring at this time. I would just wait if you haven't already. HTC Released their source codes today. Its only a matter of time before an easier root is available with unroot, and S-on.
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
kevinliu2336 said:
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
Click to expand...
Click to collapse
do we have any confirmation on this working correctly
Tried it, resets your ROM but doesn't reset s-off
Guys.. There is about a 25% chance at best that HTC will actually check the boot loader status before providing warranty service. Even if you are unlucky and they do, if you make enough noise they might make an exception and let you off the hook. I think that as long as the issue that you are trying to resolve isn't a direct result of s-off or root, it should be fine.
splayer7 said:
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
Click to expand...
Click to collapse
Flash an official RUU, and the device will be S-ON! TESTED!
lge73 said:
Flash an official RUU, and the device will be S-ON! TESTED!
Click to expand...
Click to collapse
Are you sure man? Somebody else above tested and found the opposite..
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
smoochiezz24 said:
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
Click to expand...
Click to collapse
I used the rom.zip file included in an untouched RUU, and I checked it includes HBOOT, also saw version change when I went into HBOOT.
It does NOT reset S-OFF back to S-ON.
I dont know if when you flash it reads S-OFF so keeps it, for users who genuinely had S-OFF?
I have personally tested this, and can confirm that using HTC's stock RUU does not return the phone to S-ON. However, it did remove the top area that says revolutionary, so now it appears as though I have a factory S-OFF device
Sent from my HTC Sensation 4G using XDA App
bummer.. I really hope there is a way to reverse s-off, just in case. but then again, I do have insurance so I guess I could say it was 'stolen' if I really need to get it replaced
prank1 said:
For those worrying about warranty issues..
You can try flashing the correct RUU for your phone.
IF that doesn't get rid of -revolutionary- s-off, then you can flash the ENG HBOOT (which gets rid of -revolutionary- but gives you ENG S-OFF) then you can flash the correct RUU for your region (which will definitely get rid of ENG S-OFF, and make you official stock HBOOT S-ON)
Click to expand...
Click to collapse
Try flashing ENG HBOOT, then the RUU afterwards.
I am going to try to get my phone back to S-ON now, just to test everything
EDIT
Hmm, very odd indeed, after flashing the RUU I have 'stock' Radio S-OFF (no -Revolutionary-) , I tried fastboot oem write secuflag 1 and fastboot oem writecid HTC__001 but I am still Radio S-OFF.
Just so people know, flashing full RUUs, even HBOOTs do NOT get rid of Radio S-OFF. Thats why it is favored by people, it can only be turned S-ON specifically by tools which may be released for the Sensation in the near future. I thought these tools only sent the commands that I tried to change the Radio security status. It would appear not.
However
There is no need to worry, Radio S-OFF probably won't void your warranty (if you sent it to a HTC repair center), as long as you have the correct CID and ROM installed you should be fine.
If I remember correctly, with the past Android phones, some people randomly got S-OFF (like sensation users did) out of the box. The HTC repair center didn't care. They don't like custom ROMs, custom HBOOTs, rooted ROMs, etc
so i unlocked my device via HTCDev.com thinking since its htc device and all they said was i had to unlock bootloader to flash custon OS's i already knew about S-OFF but being the site didn't talk about it(why would it) i went and flash virtouous ROM and got stuck at the HTC screen. i wasnt thinking so i never backed up the stock HTC Rom!!
now i tried 2 of those RUU's in the shipped rom thread the tmous ones with 29 and 50 both saying wrong version.
my question here is there anyway to get at least one RUU to work or get s-off from HBOOT?
my reason of doing this after going back to completely stock is i cant wait any longer for HTC/Tmobile to get us ICS so i tried the custom way and failed lol
I am sure unless you super SID you will have to find ROMs specific for the country the phone came from.
Eg my phone was from Asia region and I could not flash Euro ROMs
ok from the Shipped rom thread in the dev section for the sensation i was trying to go back to stock to gain s-off but the tmous(USA) which is where i am from said wrong version.
futty said:
ok from the Shipped rom thread in the dev section for the sensation i was trying to go back to stock to gain s-off but the tmous(USA) which is where i am from said wrong version.
Click to expand...
Click to collapse
What h boot version do you have?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Hboot: 1.18.0000
Check your CID using fastboot getvar cid to see if these still match the ROM you were trying to flash.
says for cid is t-mob010
i guess out of the 2 stock ruu"s from the post doesnt match that?
edit: ok from what i learned in another post i opened up the rom.zip file and looked at android-info.txt both the cid and mid matched my phones from the RUU file "RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed" buuuuttttt it tried to update it but fails saying i need to correct version :\
futty said:
Hboot: 1.18.0000
Click to expand...
Click to collapse
Are you on t mous us?
Also you can s off and super cid and flash any ruu.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Yes i am. the 2 Ruu's i am using seem to have matching info to my phone when i went to get the rom.zip it uses to send to my phone and looked in the android-info.txt but tell me to get the correct RUU and try again. i got the from here:http://forum.xda-developers.com/showthread.php?t=1074559 under the tmous RUU one with 29 and the other 50.
so i am just stuck at the white screen with the word HTC. if i could get s-off and SuperCID through fastboot that would be awesome but googling it shows up that i cant s-off via fastboot ughhh
still no luck cant seem to flash anything without s-off or supercid
so looks like i am jumping the boat going to sprint this thursday and geting the iphone 4s...byebye android
If you can get into fastboot you should be able to flash RUU from there. Just download the RUU.exe and run it as administrator. Follow the prompts in the exe program while your phone is in fastboot mode.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
futty said:
still no luck cant seem to flash anything without s-off or supercid
so looks like i am jumping the boat going to sprint this thursday and geting the iphone 4s...byebye android
Click to expand...
Click to collapse
Maybe iCrap is better for you. When you use Android phones and want to complete unlock them for flashing customroms aso you shoud realy learn to read before you do something. I hate it when people are not able to read about the stuff they want to do and when something goes wrong they blaim Android for it.
To get s-off, super CID and root on a HTC Android device is realy easy if you read the how-to threads and normaly takes about 15 minutes.
Have fun with your iCrap 4S and please don't try to jailbreak it before you read some stuff.
Sent from my Revolver powered ICS Asus Transformer TF101
first off let me say i have rooted and flashed roms on my sensation before just fine. i was unlocking via htcdev.com and figured their method didnt require s-off since it didnt say anything about it. it just talked about unlocking it to put customs os's on it. 2nd i always had a love hate thing for IOS since i had the 3G and ipod touch.
far as using the RUU'ss it tells me i need the correct Ruu version or something like that. maybe because i didnt run as admin but i have all that stuff turned off due to the theme i used for windows 7 required it off.
If I were you I would Super CID your device. That is what I had to do. A great guide that I used was http://forum.xda-developers.com/showthread.php?t=1472298
i tried and i get this error
vreg_set: request is duplicated id 14
pyramid_init_sd, SD card power on ok
sdcc_init_memory_device done
[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
[JAVACARD_ERR] SMART_IO.CRD cann't find
Click to expand...
Click to collapse
and my cid remains the same as t-mb010
how can i fix it? would love to get mt device back up and running
You can recover this. Firstly read this guide, regarding downgrading hboot and getting s-off.
http://forum.xda-developers.com/showthread.php?p=23222794
The problems are due to HTC.dev not unlocking all parts of the boot loader - you can't flash radio.img or boot.img so nothing is working.
Sent from my Pyramid-T
stringer7 said:
You can recover this. Firstly read this guide, regarding downgrading hboot and getting s-off.
http://forum.xda-developers.com/showthread.php?p=23222794
The problems are due to HTC.dev not unlocking all parts of the boot loader - you can't flash radio.img or boot.img so nothing is working.
Sent from my Pyramid-T
Click to expand...
Click to collapse
thanks for your help. i went to your link and i flashed a stock tmobile rom as suggested and before i could take out boot.img and send it over fastboot my sensation booted to the home screen. i went ahead and s-off'd and SuperCID. just need to create a backup before i screw up again.
again thanks for the help everyone.
Hi all,
I've got a HTC ONE S that has Vodafone (UK) branding on it but the phone is unlocked so it takes my Orange sim card. What's the best method to remove the Vodafone branding? I just want a generic handset.
Thanks in advanced.
Are you talking about the actual physical branding or the software branding?. A simple flash to a 3rd party Rom would "debrand" your device.
Sent from my HTC One S using xda app-developers app
DxTcmix said:
Are you talking about the actual physical branding or the software branding?. A simple flash to a 3rd party Rom would "debrand" your device.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Software unbranding mate. It has Vodafone crap on it. Just want it generic.
bouncyball said:
Software unbranding mate. It has Vodafone crap on it. Just want it generic.
Click to expand...
Click to collapse
Just flash a debranded rom, any here exept tmobile roms would do it.
Oh and WRONG SECTION. Read the rules before posting... sheesh.....
masterkamon842 said:
Just flash a debranded rom, any here exept tmobile roms would do it.
Oh and WRONG SECTION. Read the rules before posting... sheesh.....
Click to expand...
Click to collapse
tryout trickdroid's latest version
Apologies for the wrong forum, I realised that afterwards.
Right, I've now rooted my device so could someone recommend me a STOCK rom to clear out the Vodafone crap?
Thank you
EDIT - I have the S4 ONE S (1.5Ghz version)
bouncyball said:
Apologies for the wrong forum, I realised that afterwards.
Right, I've now rooted my device so could someone recommend me a STOCK rom to clear out the Vodafone crap?
Thank you
EDIT - I have the S4 ONE S (1.5Ghz version)
Click to expand...
Click to collapse
Choose wise, choose carefully:
http://www.shipped-roms.com/index.php?category=android&model=Ville
Eu 1.78 is pretty good actually
Sent from my One S using xda app-developers app
JohnKoeMan said:
Choose wise, choose carefully:
http://www.shipped-roms.com/index.php?category=android&model=Ville
Eu 1.78 is pretty good actually
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for that. I updated the phone to JB the other night so will these be compatible?
Also - I tried a ROM last night and it wasn't the right file type but I wiped my old OS. But as a guide told me to make a backup, I did and restored without any problems but lost SuperSU - Is this normal? Shall I just re-install?
Downloaded one but unsure how to install them as they're EXE files. What state does my phone need to be in? It also says
From:
Image Version
3.16.161.9
To:
Image Version:
1.78.401.2
Error [155]: UNKNOWN ERROR
I've tried locking my bootloader again it says 'RELOCKED' but still says TAMPERED
EDIT - In recovery screen also, it says at the top
***TAMPERED***
***UNLOCKED***
Is this normal?
I am getting no where with this and it's becoming very annoying!
I've tried reading through forum and forum, YouTube videos and various different methods!
All I want is my phone to be STOCK and it's taking me over 4 hours this morning to get no where!
bouncyball said:
I am getting no where with this and it's becoming very annoying!
I've tried reading through forum and forum, YouTube videos and various different methods!
All I want is my phone to be STOCK and it's taking me over 4 hours this morning to get no where!
Click to expand...
Click to collapse
Really strange that it says relocked/tampered and tampered/unlocked in recovery...
You might've gone wrong with the relocking of your phone, undoubtedly have you checked this out.
Can you tell me what you've ben trying so far?
And another thing: if you updated to JB, these RUUs might not work any longer since they are ICS mostly.
The best thing for you is to go by a custom ROM, it is at least the easiest thing to do now.
You can always fiddle around to restore to STOCK but as you've experienced yourself already, it isn't easy.
Here's a link to what I used when I bricked my phone, it might be of some help.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
JohnKoeMan said:
Really strange that it says relocked/tampered and tampered/unlocked in recovery...
You might've gone wrong with the relocking of your phone, undoubtedly have you checked this out.
Can you tell me what you've ben trying so far?
And another thing: if you updated to JB, these RUUs might not work any longer since they are ICS mostly.
The best thing for you is to go by a custom ROM, it is at least the easiest thing to do now.
You can always fiddle around to restore to STOCK but as you've experienced yourself already, it isn't easy.
Here's a link to what I used when I bricked my phone, it might be of some help.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Click to expand...
Click to collapse
Thanks for the reply.
EDIT - Locking my handset I'm doing the following ;
Placing my Unlock_code.bin in the DATA folder on the toolkit and pressing RELOCK BOOTLOADER
I've tried the following ;
Running RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.EXE while the phone is on the HOME SCREEN and BOOTLOADER
Running OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.ZIP using Hasoon's Toolkit.
I'm getting ERROR messages 151 when installing from the phones HOME SCREEN and ERROR 131 when installing from Bootloader.
I've tried both methods while the phone is LOCKED and UNLOCKED
Currently my phone is displaying the following in the bootloader menu ;
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11-50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57-1
My goal is put have a stock or stock looking ROM with the Vodafone software removed.
Thanks for reading.
Double post
bouncyball said:
Thanks for the reply.
EDIT - Locking my handset I'm doing the following ;
Placing my Unlock_code.bin in the DATA folder on the toolkit and pressing RELOCK BOOTLOADER
I've tried the following ;
Running RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.EXE while the phone is on the HOME SCREEN and BOOTLOADER
Running OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.ZIP using Hasoon's Toolkit.
I'm getting ERROR messages 151 when installing from the phones HOME SCREEN and ERROR 131 when installing from Bootloader.
I've tried both methods while the phone is LOCKED and UNLOCKED
Currently my phone is displaying the following in the bootloader menu ;
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11-50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57-1
My goal is put have a stock or stock looking ROM with the Vodafone software removed.
Thanks for reading.
Click to expand...
Click to collapse
Error 131 means the RUU is incompatible with your CID. Do you know it? Not sure where to find cid specific RUU but searching XDA will always yield answers.
Lock phone, fastboot usb connect phone, find right RUU and open the .exe
Btw you htc drivers installed on you're pc right?
Sent from my One S using xda app-developers app
JohnKoeMan said:
Error 131 means the RUU is incompatible with your CID. Do you know it? Not sure where to find cid specific RUU but searching XDA will always yield answers.
Lock phone, fastboot usb connect phone, find right RUU and open the .exe
Btw you htc drivers installed on you're pc right?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001
bouncyball said:
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001
Click to expand...
Click to collapse
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
JohnKoeMan said:
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
Click to expand...
Click to collapse
Ignore that, was for htc one X XD
---------- Post added at 03:24 PM ---------- Previous post was at 03:11 PM ----------
bouncyball said:
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001
Click to expand...
Click to collapse
Read this article carefully. It will give you an insight in how difficult the process we're doing is:
http://www.xda-developers.com/android/facepalm-s-off-for-htc-one-s-one-xl-and-droid-dna/
You said you downloaded the latest OTA right? This article states that with the latest OTA update we are no longer able to SUPERCID the phone, meaning only CID-specific RUUs can be applied. I can't find any RUUs for your CID, so this might just be the end of the road for this plan.
So maybe installing a ROM similar to stock might be the only good solution for you.
JohnKoeMan said:
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
Ignore that, was for htc one X XD
---------- Post added at 03:24 PM ---------- Previous post was at 03:11 PM ----------
Read this article carefully. It will give you an insight in how difficult the process we're doing is:
http://www.xda-developers.com/android/facepalm-s-off-for-htc-one-s-one-xl-and-droid-dna/
You said you downloaded the latest OTA right? This article states that with the latest OTA update we are no longer able to SUPERCID the phone, meaning only CID-specific RUUs can be applied. I can't find any RUUs for your CID, so this might just be the end of the road for this plan.
So maybe installing a ROM similar to stock might be the only good solution for you.
Click to expand...
Click to collapse
Thanks for the information - I'll give this a read in a while. I've also looked into changing the CID of my phone, followed a couple of guides but they don't seem to work, they just crash my phone.
EDIT - So, basically I have to stick with the Vodafone branding on my ONE S unless I flash to a custom ROM?
bouncyball said:
Thanks for the information - I'll give this a read in a while. I've also looked into changing the CID of my phone, followed a couple of guides but they don't seem to work, they just crash my phone.
EDIT - So, basically I have to stick with the Vodafone branding on my ONE S unless I flash to a custom ROM?
Click to expand...
Click to collapse
Yeah, its the only way I guess...
Nothing wrong with custom ROMs, they're the best, trust me! :good:
JohnKoeMan said:
Yeah, its the only way I guess...
Nothing wrong with custom ROMs, they're the best, trust me! :good:
Click to expand...
Click to collapse
Can you recommend me a good one to try? One that's as close to stock as possible that doesn't have any problems. This is my 3rd HTC device and the last 2 devices always had problems, hence why I wanted stock.
EDIT - Also, what steps do I need to take to get it back to before I rooted it? Completely factory before I installed anything.
Still getting nowhere.
I've even managed to change my CID to 11111111 from the Vodafone branded one using HEX editor. Still getting the same error's when I'm trying to install .ZIP and .EXE's when the bootloader is RELOCKED.
Could no one else shed some light on this for me please?
CID is now HTC__001 and still get the same error messages!
How hard can it be to remove a service providers software from a phone?
I would really appreciate someones help - I've tried pretty much all I can try!
Could I install an Android version lower than what I've got? I don't mind it not being JB as it's pretty much the same as ICS!
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
theonetruewill said:
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
Click to expand...
Click to collapse
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
AndroidSupporter318 said:
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
astar26 said:
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
I have put card in-between this to keep it secure before on a trial and error when it was having connection issues. It is not this that is the problem. Thank you for your input though.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
How do I do this. Please bear in mind I have not rooted etc before. I performed Step 4 of this guide before and that is why I believed I had done this. http://forum.xda-developers.com/showthread.php?t=1192300
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
This is where I got confused and started to seek assistance. I have no idea what my CID is or really how to use an RUU or what one to pick. It was a UK Vodafone handset but I don't know how this corresponds to anything or what to do about it.
AndroidSupporter318 said:
...If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
When I do (and did before) step 3 I just get a list of commands and no current software version showing. This was exactly when I came here. I thus went no further as what I had did not correspond.
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
astar26 said:
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
Click to expand...
Click to collapse
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
in the sensation forums no one reported that he had supercid while on S-ON
theonetruewill said:
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
Click to expand...
Click to collapse
open the cmd window in the folder where you have adb and fastboot files and perform there the command
also make sure that in hboot screen it shows fastboot usb
rzr86 said:
in the sensation forums no one reported that he had supercid while on S-ON
Click to expand...
Click to collapse
Hi. Maybe no one has reported it but u can have supercid with s-on, and i dont mean by going s-off first. It is very rare tho, like if u work for lets say vodafone then u can get a stock s-on phone with supercid. For development r something i think. But like i said, its very rare that us general public get our hands on them. But it is possible
Got it to show my cid. Error when flashing the rom using the executable file. Will try again when back from work
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
maybe you used an RUU of SE when you are not (or otherwise, regular for XE). beside CID, there is MID. the procedure of adding your MID and checking the MID is similiar to the CID.
MID indicates your model - in this case mainly three are possible: one for regular sensation, one for XE, and one for 4G.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
rzr86 said:
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
Click to expand...
Click to collapse
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Managed to get a RUUto flash to it - http://freakshare.com/files/gt7345y....23.3504.07_M2_release_251541_signed.exe.html
Unfortunately this has not fixed the problem. I suspect this may be terminal. Any suggestions?
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
theonetruewill said:
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Click to expand...
Click to collapse
with that hboot version you can only use juopunutbear method to S-OFF the device
try to unlock the bootloader via htcdev site
flash a custom recovery(i suggest 4ext)
flash a custom rom from recovery(before flashing enable smartflash from 4ext)
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
TotallydubbedHD said:
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
Click to expand...
Click to collapse
post your bootloader details and what exactly did you do ?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
theonetruewill said:
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
Click to expand...
Click to collapse
do it with notepad++
Okay so my friend asked me to fix a phone that he says one day it got stuck in boot splash screen. He claims he did not try to flash a custom Rom or something but he said he hadn't.here's some of the phones info
HTC one x
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Can anyone sheed some light on the subject.
I don't know how to use adb and fastboot
And I have Windows xp and Mac 10.6 and lynx
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Mr Hofs said:
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Click to expand...
Click to collapse
As if by magic, it appears in the One XL forum.
I think your friend is telling fibs, phones don't just magically stop booting for no reason. Please tell him to own up to whatever activities lead to this situation, as embarrassing as it might be, I need to know how this happened in order to help properly.
Now, just to be clear, the phone is actually the HTC One XL, not the HTC One X. They look similar but are actually very different. What recovery is installed on the device?
Another question for you, why isn't your friend posting here and attempting to fix this problem himself? If he can't recover from a simple problem like this (or can't be bothered learning/trying) he honestly has no place having a modified phone. That might sound harsh but it's the truth, this is very basic knowledge, it's flashing 101. Knowing how to recover from something like this is an essential skill for anyone who owns a modified phone. If your friend isn't interested in being honest about what lead to this situation, or interested in learning how to recover from this situation, my only advice is to return to the device to stock and leave it that way. I'd strongly urge him to get on here and post himself, and do some reading to educate himself on the ins and outs of modified devices.
Sent from my Evita
sorry for being so vauge
My friend is a lady friend who had no idea how the phone could have become modified. The phone is a HTC one X and my lady friend said she would love nothing more then to have a stock phone. My friend has no intrest in leaning how the in's and out's of HTC but, I on the other hand would love to learn about HTC and Android. I come from a n Apple community and have a little knowledge but not a lot.
Anything you can tell me would help greatly, and I would be indeed greatful.
Sincerely Nanamkin
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Thank you so much
timmaaa said:
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Click to expand...
Click to collapse
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Nanamkin said:
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Click to expand...
Click to collapse
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Man your GOOD
timmaaa said:
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Click to expand...
Click to collapse
I am sooo sorry. you are absulotly right, and you are good! how did you know that? lol
here is the right info.
TWRP 2.3.1.0
im sorry i cant boot into the phone to check the setting/about phone for a software version. do you know any other way?
and while i was messing around i figured out how to install ADB and FASTBOOT and use it.
I'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the CID for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita
got it
timmaaa said:
i'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the cid for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
sent from my evita
Click to expand...
Click to collapse
cid:11111111
Ok. To get the phone back to stock you Erik need to run an RUU, but in order to do that safely you'll first need to get s-off. To get s-off you're gonna need a booting ROM on the device. Purely for this exercise I think Kickdroid would be your best option, head to our Android Development section and find the Kickdroid thread, download it, and use TWRP recovery to install it. Look in the How-To Guide For Beginners thread in my signature for full instructions on how to flash the ROM. Please note, you'll also need to flash the boot.img from the ROM zip via fastboot after flashing the ROM.
Sent from my Evita
got it
Okay I have the Rom on my phone now what?
Nanamkin said:
Okay I have the Rom on my phone now what?
Click to expand...
Click to collapse
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
your awesome
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
oh yeah i was over there just a little awhile ago. i een your name so i tiend to fallow it but couldnt get the rom. thank you sooo much
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Nanamkin said:
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Click to expand...
Click to collapse
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
I got the rom to work
timmaaa said:
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
Click to expand...
Click to collapse
I got the rom to boot after fallowing your directions(like you said)lol. but when i do steps 7 the 3 codes it says there are no directory. I got the first one to go but the other 2 would not work
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
got the os to boot
timmaaa said:
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
Click to expand...
Click to collapse
okay so i have the rom on the phone (kickdroid) and now i cant run the last 3 codes on step 7. any clue. I have soffbin zip unzipped in the directory but where exactly do i put it? i have it in the same folder as adb and fastboot is that right?