[Q] [HTC One SV] SuperCID problem - cannot receive OTA - HTC One SV

I have the HTC One SV LTE phone, CID=HTC__622 (Asia) with ICS.
I did the unlock, root, SuperCID, S-OFF and changed MID to 8010000 - all without any problems.
The only thing is - while the phone reports CID 11111111 in fastboot oem readcid, the CID Getter still see the original HTC__622 one and I cannot receive OTA for JB update.
Just to make sure it's the CID, I used the sniffer to check the update request and here is what I have found:
the request:
{"zip":"******","adminArea":"Moscow","ApHRAddr":"NA","timeStamp":1369935905158,"imei":"***************", "locale":"ru_BG","timeZone":"GMT+04:00","digest":"*****************************","country":"RU","SID":"********************************","statusCode":7,"checkin":{"mcc_mnc":"25099","mid":"PL8010000","checkin_type":"Manual","build": {"product":"k2_ul","id":"htc_europe\/k2ul\/k2ul:4.0.4\/IMM76I\/137060.5:user\/release-keys","revision":"129","firmware_version":"1.17.401.5 CL137060 release-keys","radio":"0.12.40.00.14_2_10.49.40.11L","carrier":"htc_europe","bootloader":"u1.01.0000","build_type":"user","changelist":"137060","serialno":"************"},"cid":"HTC__622","connection_media":"IPT","client_version":"A4.0(GB)"},"model_number":"HTC One SV","last_checkin_msec":"1369935769127","locality":"Moscow"}
Click to expand...
Click to collapse
and the answer:
{"time_msec":"1369935906393","stats_ok":true,"reason":"FOTACANCEL_NO_MATCH_RULE_FOR_CID","digest":"*******************************","intent":[{"action":"android.server.checkin.FOTA_CANCEL"}], "setting":[{"name":"upload_crash","value":"crash block"}, {"name":"checkin_interval","value":"86400"},{"name":"upload_event","value":"false"},{"name":"update_stats","value":"false"}]}
0000
Click to expand...
Click to collapse
I can see in adb getprop that ro.cid is still HTC__622 and I cannot do anything to change it. I relocked the boot and flash the RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5 successfully, but still cannot receive OTA!
I also followed the guide here to no avail.
Any advice?

Aord said:
Any advice?
Click to expand...
Click to collapse
I'm not sure if this can help but did you try to flash an european RUU?

old.splatterhand said:
I'm not sure if this can help but did you try to flash an european RUU?
Click to expand...
Click to collapse
That's what I did at the beginning - in fact, I was referring to that in my first message.
Actually, I was able to overcome this problem myself - I used fastboot oem writecid HTC__001 then after a reboot ro.cid became also HTC__001 and I was able to receive the update.
For some reason when you set SuperCID it didn't get reflected in ro.cid and that's what the phone is reporting when you initialize OTA update check.

Aord said:
That's what I did at the beginning - in fact, I was referring to that in my first message.
Actually, I was able to overcome this problem myself - I used fastboot oem writecid HTC__001 then after a reboot ro.cid became also HTC__001 and I was able to receive the update.
For some reason when you set SuperCID it didn't get reflected in ro.cid and that's what the phone is reporting when you initialize OTA update check.
Click to expand...
Click to collapse
Ok, glad you got it sorted out.

Related

CID change with S-ON!

UPDATE: Apparently it is only possible to change the CID with S-ON if your current CID is SuperCID.
*issue closed*
I had used Revolutionary to de-brand my phone. First S-OFF, then SuperCID, then a stock unbranded ROM, then back to S-ON.
I wasn't getting the OTA to 2.3.4 here in The Netherlands, so I changed my CID to HTC__E11, which is the CID for an unbranded Sensation in The Netherlands. Lo and behold, I got the OTA immediately.
Interesting to note, I was able to change the CID using "fastboot oem writecid HTC__E11" with S-ON. Someone else was able to do exactly the same thing so it's confirmed to work.
Now that I have upgraded to 2.3.4 and have my CID set to HTC__E11, this no longer works for me. However I'm wondering if it *does* work for people still on 2.3.3, or if it only worked for me because I was already SuperCID. I wonder if others who are still on 2.3.3 are able to use "fastboot oem writecid 11111111" with S-ON (i.e. without using Revolutionary).
So, using adb tools on a stock ROM:
NOTE: If you test this you do so at your own risk.
0. download and unzip adb tools to a folder. make sure HTC Sync is not running (uninstall, or just exit/kill the application).
1. open command prompt and "cd" your adb folder
2. ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (ensure usb debugging is on settings).
3. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
4. enter the command "adb reboot-bootloader". (nothing further required device WILL reboot in bootloader)
5. enter the command "fastboot oem writecid 11111111"
6. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
7. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
8. enter the command "fastboot reboot"
9. you should now be able to flash any stock ROM you like.
NOTE: Please DO NOT change your CID to HTC__E11 unless you are in The Netherlands. HTC__E11 is the CID for an unbranded Sensation in The Netherlands. If you are in a different country, check for the appropriate CID here: http://forum.xda-developers.com/showthread.php?t=1195475&page=3.
I've already de-branded my phone, but I wonder if others are able to using "fastboot oem writecid 11111111" without using Revolutionary.
Click to expand...
Click to collapse
Yes, I have. In fact I believe that method is in one of the tutorials here.
Here is a link that describes it: http://forum.xda-developers.com/showthread.php?t=1192300
kmdub said:
Yes, I have. In fact I believe that method is in one of the tutorials here.
Here is a link that describes it: http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
No, that tutorial uses Revolutionary first to go from S-ON to S-OFF before changing the CID. I was able to change my CID with S-ON.
so I'm changing my cid to 11111111?
not HTC__E11?
zahashingo123 said:
so I'm changing my cid to 11111111?
not HTC__E11?
Click to expand...
Click to collapse
11111111 is the SuperCID. HTC__E11 is the CID for unbranded Sensations in The Netherlands. If you don't use the SuperCID, you may want to refer to http://forum.xda-developers.com/showthread.php?t=1195475&page=3 for a list of CIDs.
I changed to the SuperCID using Revolutionary to first get S-OFF. Then I set S-ON. But even with S-ON, I was still able to change my CID (I changed it to HTC__E11 in order to receive the OTA to 2.3.4.).
So what I'm wondering is if people with 2.3.3 and S-ON are able to change their CID to the SuperCID 11111111, without first using Revolutionary to change to S-OFF.
Ok, I must have misunderstood your question. It seems as if you have clarified your question since your original post. I just thought you were asking if one could write the CID without Revolutionary. My bad. FYI, I have not tried what you are asking.
I changed to the SuperCID using Revolutionary to first get S-OFF. Then I set S-ON.
Click to expand...
Click to collapse
A statement like this, though, I don't really understand. Two questions come to mind: 1) How did you set S-ON? and 2) Were you able to confirm that you wrote a new CID with S-ON, or did you just not get an error message?
kmdub said:
Ok, I must have misunderstood your question. It seems as if you have clarified your question since your original post. I just thought you were asking if one could write the CID without Revolutionary. My bad. FYI, I have not tried what you are asking.
A statement like this, though, I don't really understand. Two questions come to mind: 1) How did you set S-ON? and 2) Were you able to confirm that you wrote a new CID with S-ON, or did you just not get an error message?
Click to expand...
Click to collapse
I set S-ON using the instructions on how to set S-ON here http://forum.xda-developers.com/showthread.php?t=1192300 and I confirmed it during reboot, the text "S-ON" was back on the boot screen.
I wrote the new CID with S-ON, then confirmed it by rebooting and running the command "fastboot getvar cid", which gave me the phone's CID, which indeed was the new CID I'd written. In addition, with the new CID (unbranded Dutch, instead of SuperCID), I immediately got the OTA to 2.3.4.
Someone need to test this with a stock phone!
Or try to set secureflag to 1 maybe its not really changed ...
xtcislove said:
Someone need to test this with a stock phone!
Click to expand...
Click to collapse
That's exactly what I'm asking people to do.
xtcislove said:
Or try to set secureflag to 1 maybe its not really changed ...
Click to expand...
Click to collapse
What's your problem, can't you read? I wrote already, the phone reports "S-ON" in the boot screen, and after a reboot, it still reports the new CID, and after setting the new CID, I got the Netherlands OTA immediately.
I tried it with stock s-on phone and it doesn't work.
Code:
C:\AndroidSDK\tools>fastboot oem writecid 11111111
...
(bootloader) pyramid_init_sd, SD card already power on
(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 [ 0.172s]
finished. total time: 0.172s
It still reports same cid.
supendal said:
I tried it with stock s-on phone and it doesn't work.
It still reports same cid.
Click to expand...
Click to collapse
Thanks for testing this - just to confirm, you tested with 2.3.3 and not 2.3.4, right?
If so, then it seems to imply that you can change the CID even with S-ON but only if you currently have SuperCID.
Then I have no idea. I would not think one could write a new CID with S-ON, regardless of the ROM. However, you have tried it and claim it works, so someone with more knowledge will have to explain why...lol
I notice in the tutorial it says "secureflag 3," which at least gives you S-ON displayed, and perhaps does set the security back on. I wonder what 0,1,and 2 do, though. Is it 0,1,2, or 3 on stock phone with S-ON?
sowen222 said:
Thanks for testing this - just to confirm, you tested with 2.3.3 and not 2.3.4, right?
Click to expand...
Click to collapse
Yes, tested on stock s-on phone and stock 2.3.3 rom. 2.3.4 Ota update is still not available here.
well i do also have s-on and managed to change cid to HTC__E11 with adb and also like the OP can't seem to change it back to what it was (stock sensation with 1.50...rom) does the cid mathers in terms of warranty and ota updates??? (i'm in the netherlands)
regards
edit:well OTA updates do work on my side but still no luck changing the CID again.
nobody here that can decifer this one??
I have a sendation xe with hboot 1.18 and s-on.
I used the commands to change CID from HTC__038 to HTC__001.
I still don't receive the OTA update on my phone though.
The phone was bought from Hong Kong but from using the CID Getter app it shows CID at the top as HTC__001 now but when you scroll through the data there are still reference to it being an indian phone.
I am looking to change it to stock Euro gingerbread with CID 001 so that I can receive the OTA ICS update.
I can't use revolutionary to change to S-OFF as always fails. I can't install the RUU for euro GB as it gives an error when I try to run it.
Not having any joy asking people for help so far either.

Can't run RUU on Sensation - "Customer ID Error"

Hi all - yet more problems, so few answers..
I was on ARHD but it sucked for me. So I wanted to revert to stock. But the RUU wouldn't run, so on another member's advice, I flashed InsertCoin and have just tried to run the RUU again.
And it ran, but then stopped saying it couldn't update and I've got a "Customer ID Error". I've no idea what this means or what I can do.
Please? Anyone?
s
schnidex said:
Hi all - yet more problems, so few answers..
I was on ARHD but it sucked for me. So I wanted to revert to stock. But the RUU wouldn't run, so on another member's advice, I flashed InsertCoin and have just tried to run the RUU again.
And it ran, but then stopped saying it couldn't update and I've got a "Customer ID Error". I've no idea what this means or what I can do.
Please? Anyone?
s
Click to expand...
Click to collapse
Appreciate to post the picture when your phone at Hboot or Fastboot state (?) is phone s-off and what you are doing to phone before running RUU.
Is your unit Super CID? You need this to flash RUU
paulmor said:
Is your unit Super CID? You need this to flash RUU
Click to expand...
Click to collapse
I don't know - can you tell me how to find out? Honestly, I've really had enough of how complicated this has to get - I just want to restore root and sell the thing. Any help would be much, much appreciated.
Are you using the correct RUU for your device, eg. Asian RUU for Asian device etc?
I doubt that your device is on SuperCID as having that will negate the Customer ID errors
Blodia said:
Are you using the correct RUU for your device, eg. Asian RUU for Asian device etc?
I doubt that your device is on SuperCID as having that will negate the Customer ID errors
Click to expand...
Click to collapse
Reboot into the Bootloader and then select Fastboot-USB. Run the RUU again and it will work with no issues.
Blodia said:
Are you using the correct RUU for your device, eg. Asian RUU for Asian device etc?
I doubt that your device is on SuperCID as having that will negate the Customer ID errors
Click to expand...
Click to collapse
Definitely - but I will try the dr's solution and get back to you guys if I have any more problems.
Thanks for your help.
schnidex said:
I don't know - can you tell me how to find out? Honestly, I've really had enough of how complicated this has to get - I just want to restore root and sell the thing. Any help would be much, much appreciated.
Click to expand...
Click to collapse
It's not complicated, just that you need to do the things in order.
If you want to check the CID, look at: http://forum.xda-developers.com/showthread.php?t=1192300
Note though that you'll need ADB installed and working.
Step 4. is about the CID, there are steps to check it and write a different one.
9. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
10. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
dr9722 said:
Reboot into the Bootloader and then select Fastboot-USB. Run the RUU again and it will work with no issues.
Click to expand...
Click to collapse
Thanks again for this, but it didn't work unfortunately..
However..
gol_n_dal said:
It's not complicated, just that you need to do the things in order.
If you want to check the CID, look at: http://forum.xda-developers.com/showthread.php?t=1192300
Note though that you'll need ADB installed and working.
Step 4. is about the CID, there are steps to check it and write a different one.
9. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
10. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
..this did! Thank you for this - the RUU is installing now!

[Q] How to reset CID back to tmobile USA

OK So I SuperCID my phone to find out that I didn't need to do it I have tried running the RUU install to go completely back to stock so I can reset it Is there another way to reset the CID back to tmobile
fastboot OEM writecid T-MOB010 this should write your cid back to stock cid
ThaPirato said:
fastboot OEM writecid T-MOB010 this should write your cid back to stock cid
Click to expand...
Click to collapse
That worked thanks ^_^
Sinistra425 said:
That worked thanks ^_^
Click to expand...
Click to collapse
Anytime,Glad i could help out.
that works for sensation 4G?
Jayisaiah said:
that works for sensation 4G?
Click to expand...
Click to collapse
Yes
Sent from my Kindle Fire using Tapatalk
Jayisaiah said:
that works for sensation 4G?
Click to expand...
Click to collapse
I dont get what you mean by that? if it worked to get cid 111111
then yes it will work to go back to stock CID
you just need to know your orginal CID, you can go into terminal and type
su enter
getprop ro.cid
enter
and it should out put your original CID even if you SUPERCID, reasons why i have no clue, i think its reading off your carrier signal cause when you do that in fastboot after you supercid
"getvar CID"
it will give you 111111
ThaPirato said:
fastboot OEM writecid T-MOB010 this should write your cid back to stock cid
Click to expand...
Click to collapse
That worked for me, except for it all had to be lowercase except "T-MOB010" part... When I copied and pasted it as you have it, it answered with the list of proper usages of fastboot command. But it worked. ThaPirato properly thanked.

Problem with two CID's

I have a sensation thats giving me two CID numbers.
If i use fastboot commands i get 11111111.
If i use CID getter i get VODAP001.
Phone is s-off, rooted and unlocked.
How can i get these the same?
The phone is downloading an ICS update but not installing it.
I've seen the same thing, your correct CID is the one you got through adb. CID getter for some reason throws up CID information stored elsewhere so you generally end up getting the CID the phone came with.
Given that you are SuperCID, why won't ICS install? What error(s) are you seeing?
goatee84 said:
I've seen the same thing, your correct CID is the one you got through adb. CID getter for some reason throws up CID information stored elsewhere so you generally end up getting the CID the phone came with.
Given that you are SuperCID, why won't ICS install? What error(s) are you seeing?
Click to expand...
Click to collapse
More accurately... Your correct CID is the one you get through:
Code:
fastboot getvar cid
If I use adb shell command:
Code:
getprop ro.cid
Then I get my original CID "T-MOB010"...
To the OP:
Go to your directory where adb and fastboot are, and type the following:
Code:
adb reboot bootloader
wait for bootloader to boot
Code:
fastboot oem writecid VODAP001
wait for it to flash
Code:
fastboot reboot-bootloader
wait for bootloader to boot
Code:
fastboot getvar cid
verify that the output is "VODAP001"
Code:
fastboot reboot
wait for device to reboot and you should be able to install your update if you're on an unaltered stock ROM...
Thanks for the replies.
It is the rom that came on the phone but i have removed some of the app's that Vodaphone pre-install, will this affect the up date?
Part of the error message was a problem with flickr which i did remove.
I would like a T-mobile ICS stock rom that is rooted as that is my provider, any suggestions?
I tried updating to 3.32 firmware but was getting boot loops, so downgraded again.
If you apply SuperCID, your phone has 2 CIDs:
the actual CID, which is 11111111
and the backup CID, which is a backup of the
cid the phone was before(shipped).
The backup CID is stored in the misc partition,
and i havent tried yet, but there are following fastboot cmds:
fastboot oem erasebcid
fastboot oem readbcid
fastboot oem writebcid
I think theyre the appropriate cmds for handling the bcid.
After deleting the backup CID the only CID left is the (main) CID.
BTT: If you want to apply a ICS RUU, I think you have to change your CID back
to stock, because the RUU checks for a T-Mob phone, which your phone isnt if
you have SuperCID ;D
After the RUU, you can SuperCID again.
Edit:
Have not read the first time:
If you want to install a T-Mobile RUU on a Vodaphone Device,
you have to set one of the following CIDs, matching the RUU best:
TMA: T-MOB102
TMCZ: T-MOB004
TMD: T-MOB101
TMH: T-MOB007
TMHR: T-MOB006
TMMK: T-MOBL11
TMNL: T-MOB003
TMSK: T-MOB008
TMUK: T-MOB005
TMUS: T-MOB010
Greetz
criestr
ann-dr01d said:
Thanks for the replies.
It is the rom that came on the phone but i have removed some of the app's that Vodaphone pre-install, will this affect the up date?
Part of the error message was a problem with flickr which i did remove.
I would like a T-mobile ICS stock rom that is rooted as that is my provider, any suggestions?
I tried updating to 3.32 firmware but was getting boot loops, so downgraded again.
Click to expand...
Click to collapse
Your stock ROM must be unaltered... Restore those apps if you still have them.

No Updates after Unroot

Ok, so I had my Sensation rooted with a custom ROM but decided to put it back to stock (mainly to be able to use Sky Player). It has been 3 weeks since I did it and I've not had an update. It's stuck with Android 2.3.3. When I try to manually update It tells me that no updates are available.
Any Ideas?
neoduder said:
Ok, so I had my Sensation rooted with a custom ROM but decided to put it back to stock (mainly to be able to use Sky Player). It has been 3 weeks since I did it and I've not had an update. It's stuck with Android 2.3.3. When I try to manually update It tells me that no updates are available.
Any Ideas?
Click to expand...
Click to collapse
for you to recieve OTA ..the CID must match
check the CID using
this command
fastboot getvar cid
if its not matching
change it to your region CID using this command
fastboot oem writecid <your cid>
eg: fastboot oem writecid HTC__001
check/get your original cid from here
Thanks for the reply.
I just checked. My CID is set as VODAP001, which should be correct for Vodafone UK.
Any other ideas?
Thanks in advance.
anybody???
Would having S-OFF have any effect?
neoduder said:
anybody???
Would having S-OFF have any effect?
Click to expand...
Click to collapse
nope it doesnt change anything
can you post the RUU name ..is it perfectly matching ?
The RUU I used was called...
RUU_Pyramid_Vodafone_UK_1.24.161.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190798_signed
neoduder said:
The RUU I used was called...
RUU_Pyramid_Vodafone_UK_1.24.161.1_Radio_10.39.9007.00P_10.11.9007.09_M2_release_190798_signed
Click to expand...
Click to collapse
that seems too old
there is an updated version of RUU try this
http://goo.im/stock/pyramid/ruu/PG58IMG_Pyramid_Vodafone_UK_1.27.161.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191974_signed.zip
even after that if it didnt worked still..then
directly try the ICS RUU of vodafone
ICS VODAFONE UK RUU
Thanks buddy. I'll give them a try and report back
Excellent. The updated RUU did the trick. Thanks again dude :good:

Categories

Resources