Getting CID 0202 - HTC EVO 3D

After turning S-OFF and gettin bootloader unlocked, everythings works perfectly. But know I have problem with cid. I can't change it when i type
Quote:
fastboot oem writecid HTC__001
nothing happens, and I still have cid: 0202. I can't install any firmware and RUU doesn't work. How to fix it, and make cid: HTC__001 again?

Related

[Q] My Flyer is softbricked!

After doing a OTA upgrade from GB to HC my Flyer ended up with an error. It was s-off before this and working fine. I can not run ADB commands, boot up, run revolution, install from sd card, run recovery, htc unlock or fastboot commands. It only boots into fastboot and installing an RUU also ends in an error. Some fastboot commands is working but whatever I do I get Signature error, Bootloader error or FAILED (remote: signature verify fail). My getvar looks like this:
C:\Data\Android\Adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.10.0000
INFOversion-baseband: 3809.05.04.10_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 3.55.1114.31
INFOserialno: HT15SJN00865
INFOimei: 355195000000017
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4140000
INFOcidnum: HTC__Y13
INFObattery-status: good
INFObattery-voltage: 3843mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader:
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.031s
Can someone please give me a hand?
run the hc soff ruu posted in development by globatron. should do the trick .
Already tried that. It starts with: Run revolutionary and I cannot do that. I am at S-ON now. If I try to just run the RUU it fails!
Other things I can try?
if you were s off prior to attempting to upgrade you should not have been able to change the hboot version via standard update and you would be left with a gb s off hboot and a hc system. looking back at your post it appears you have a s on hc hboot but a system that wont boot. When you try to run the globatron soff ruu it would fail becasue you are s on. I am guesing since your system has been updated to hc when you attempt to run your stock ruu you are failing because the misc version is older in the ruu you are attempting.
I am kinda guesing here as to my understanding if you were s off prior you should still be s off, but maybe try to htc dev unlock. then flash recovery to your device. once recovery is installed you should be able to change you misc version following steps listed in globatrons downgrade from hc leak thread. After you change the misc version you would need to relock your hboot then attempt the stock ruu again.
try extracting the zip from the ruu and run these commands:
fastboot oem lock
fastboot erase cache
fastboot rebootruu
fastboot flash zip (filename)
Run the Honeycomb RUU, then proceed with the downgrade instructions.
I have tried all that and none of it is working. Some of it runs, but ends with an error like Signature error, Bootloader error or FAILED (remote: signature verify fail). I guess I'm stuck with a brick?
globatron said:
Run the Honeycomb RUU, then proceed with the downgrade instructions.
Click to expand...
Click to collapse
Finally. I found the correct RUU to download and then the installation finished without errors. Thanx alot !!

cid: 0202 How to fix it?

After turning S-OFF and gettin bootloader unlocked, everythings works perfectly:laugh:. But know I have problem with cid. I can't change it when i type
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
nothing happens, and I still have cid: 0202. I can't install any firmware and RUU doesn't work. How to fix it, and make cid: HTC__001 again?
markk99 said:
How to fix it, and make cid: HTC__001 again?
Click to expand...
Click to collapse
Do u really think that this belongs to development?
There is also one more problem I've had before. I can't turn me WiFi on. When I push button to start it won't, and after moment says ERROR.
fixing cid 0202
Here is the problem hboot. Higher hboot than 1.49.0007 cant change cid. if you downgrade your hboot to 1.49.0007 you can.
I changed it in downgrade procces, my hboot was 1.49.1107.

[Q] Unlockbootloader and s-on???

Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
s-on is required for unlocking bootloader, s-off will go to disclaimer screen but wont respond if yes is selected, it will only say ***unlock*** (which it must, but it wont be truly unlocked, your phone needs to respond when selecting yes and MUST restart, if you need to remove battery, it wont be unlocked.
***Problem***: now I had s-off and ***LOCKED*** so I ran fastboot oem writesecureflag 3 to get s-on, unlocked through htcdev and heres the big problem:
Now:
***UNLOCKED***
HBOOT 1.49.0007 S-ON (RH - i think)
Cant change CID, flash recovery, doesnt read PG86IMG files, cant flash anything through fastboot, cant run RUU because of error 132 (signature error).
After trying to change CID with:
fastboot oem writecid HTC__621
Result =
gave a few errors
cidnum = 0202 ...???
Have hboot 1.49.0007, can unlock relock bootloader, have functioning ICS rom
fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 1.49.0007
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.20.401.2
INFOserialno: HT23NV200556
INFOimei: 352647050653635
INFOproduct: shooter_u
INFOplatform: HBOOT-8260
INFOmodelid: PG863****
INFOcidnum: HTC__621
INFObattery-status: good
INFObattery-voltage: 5785mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: edba812f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.510s
so please help... any1...
cybergurken said:
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
Click to expand...
Click to collapse
You should not have done that.
Also, if you are S-Off that is really all that matters. There is not really any reason to unlock the Bootloader. If you were S-Off and wanted to have an unlocked bootloader you should have just found a hboot like the revolutionary one or engineering and flashed PG86IMG.zip and that would have given you Unlocked and S-Off.
For the most part, you never want to do the fastboot oem writesecureflag 3.
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Thnx 4 responding
mnomaanw said:
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Click to expand...
Click to collapse
Hi, no offence taken...
However, Im still a newbie @ all of this, however, I might be wrong but 3 q's
1. Why would it hang on the "yes" option
2. If I pull out baattery, it says ***unlocked*** but I have no access to recovery, even after custom recovery flash in fastboot, it cant/wont/doesnt boot into recvoery @ all, ref. "my other posts", why would that happen
3. What is the real difference between unlocking bootloader, and s-oof, I have read many posts and I figured getting both would be on the safe side...
and lastly, xd, why would a bootloader not read/detect a PG86IMG file, that is also another problem,
Once again, tnks very much

[Q] Change CID Back to AT&T from DEV EDITION

Is there a way to change my cid back to the att version if I have converted to the stock developer edition and am currently running 4.3? I tried revone s-off but that is a no go... I need to do a warranty exchange through HTC because my mic is busted...
NOFSBIGE said:
Is there a way to change my cid back to the att version if I have converted to the stock developer edition and am currently running 4.3? I tried revone s-off but that is a no go... I need to do a warranty exchange through HTC because my mic is busted...
Click to expand...
Click to collapse
sure it's no problem just run fastboot
reboot your phone to bootloader (Power+Vol Down) / plug in to PC you should be in fastboot usb
from your fastboot location on your PC just open a command window and use these
fastboot oem writecid CWS__001
fastboot erase cache
fastboot reboot
if your returning the phone here's the RUU for AT&T
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
clsA said:
sure it's no problem just run fastboot
reboot your phone to bootloader (Power+Vol Down) / plug in to PC you should be in fastboot usb
from your fastboot location on your PC just open a command window and use these
fastboot oem writecid CWS__001
fastboot erase cache
fastboot reboot
if your returning the phone here's the RUU for AT&T
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
Don't you need to be soff in order to change the cid?
NOFSBIGE said:
Don't you need to be soff in order to change the cid?
Click to expand...
Click to collapse
yes... well maybe not
you can flash the decrypted RUU buy editing the android-info.txt
Here->> http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
then change your android-info.txt to this
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
mainver: 3.17.502.3
btype:0
aareport:1
hbootpreupdate:3
Click to expand...
Click to collapse
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
You have to be s-off to change cid how did you change it to begin with if you are not s-off
Sent from my HTC One using Tapatalk
jerrycoffman45 said:
You have to be s-off to change cid how did you change it to begin with if you are not s-off
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
All I could figure is the Developer RUU must have changed it
Sent from my HTC One using Tapatalk 4
clsA said:
All I could figure is the Developer RUU must have changed it
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
A RUU doesn't change the CID, and you can't flash the developer RUU without changing the CID from CWS__001 because of CID mismatch.
xeni said:
A RUU doesn't change the CID, and you can't flash the developer RUU without changing the CID from CWS__001 because of CID mismatch.
Click to expand...
Click to collapse
lol yeah ..ok then my post #2 stands

[Q] HBOOT-1.57.0000 Relocked

I have HBOOT-1.57.0000 with OS-4.09.605.1. I was trying to get it S-ON and locked so I could get it replaced. I now have S-ON but I forgot to flash lock bootloader zip before running these commands:
Code:
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
It says "Relocked" instead of locked. I have tried moonshine, rumrunner, and every RUU I can find but they all give an error. Could someone please tell me how I can get it to say locked again? I will be charged for the phone soon if it is not returned. Thanks.
yukongt300ex said:
I have HBOOT-1.57.0000 with OS-4.09.605.1. I was trying to get it S-ON and locked so I could get it replaced. I now have S-ON but I forgot to flash lock bootloader zip before running these commands:
Code:
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
It says "Relocked" instead of locked. I have tried moonshine, rumrunner, and every RUU I can find but they all give an error. Could someone please tell me how I can get it to say locked again? I will be charged for the phone soon if it is not returned. Thanks.
Click to expand...
Click to collapse
No ruu will change that. The only think you could do is sunshine s-off it and fix that after rooting it using the adb command to "lock". Then turn s-on. It would cost you $25. If the phone boots, I would personally probably just send it as is. Its s-on and locked and stock. What can they say about that?
This ruu will run but will not change that.
http://forum.xda-developers.com/showthread.php?t=2935556
Official EXE RUU's (s-on)

Categories

Resources