[Q] Stuck downgrading from Super CID

Bizwax · Aug 1, 2012 at 3:19 AM

I have a Sensation I need to get back to stock. I ran an RUU and everything seems fine, but when I perform the steps in fastboot to change my CID back to HTC__001 it refuses to stick. It always comes back with 11111111.

Here's the log:

Code:

C:\Android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXX    device


C:\Android>adb reboot bootloader

C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.550s

C:\Android>fastboot oem writecid HTC__001
...
(bootloader) Start Verify: -1
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [  0.050s]
finished. total time: 0.050s

C:\Android>fastboot reboot
rebooting...

finished. total time: 1.738s

C:\Android>adb reboot bootloader

C:\Android>fastboot getvar cid
cid: 11111111
finished. total time: 0.003s

Sorry if this has been answered before. I searched but all I found was questions about achieving Super CID.

Cheers
-Bizwax

ganeshp · Aug 1, 2012 at 6:31 AM

Run the RUU again.. Then try the cid change.

And use fastboot reboot-bootloader

After cid change to verify it.. Instead of fastboot reboot

Sent from my pyramid.. Through blazing fast sonic waves

Bizwax · Aug 1, 2012

Thanks ganeshp. Here's the new log. Fresh RUU install as instructed.

Code:

C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXX    device


C:\adb>adb reboot bootloader

C:\adb>fastboot getvar cid
cid: 11111111
finished. total time: 0.003s

C:\adb>fastboot oem writecid HTC__001
                              ... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
OKAY [  1.542s]
finished. total time: 1.542s

C:\adb>fastboot reboot-bootloader
     rebooting into bootloader... OKAY [  0.285s]
finished. total time: 0.286s

C:\adb>fastboot getvar cid
cid: 11111111
finished. total time: 0.004s

I've also tried using a different RUU but get the same result.

gol_n_dal · Aug 1, 2012 at 9:38 AM

Hmm, just tried it myself, I'm on HBOOT 1.27.1100 if that make a difference and it seemed to work fine.

ganeshp · Aug 1, 2012 at 11:37 AM

Bizwax said:

Thanks ganeshp. Here's the new log. Fresh RUU install as instructed.

Code:

C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXX    device


C:\adb>adb reboot bootloader

C:\adb>fastboot getvar cid
cid: 11111111
finished. total time: 0.003s

C:\adb>fastboot oem writecid HTC__001
                              ... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
OKAY [  1.542s]
finished. total time: 1.542s

C:\adb>fastboot reboot-bootloader
     rebooting into bootloader... OKAY [  0.285s]
finished. total time: 0.286s

C:\adb>fastboot getvar cid
cid: 11111111
finished. total time: 0.004s

I've also tried using a different RUU but get the same result.

cid will be stored at 3 partitions afaik ..and somehow one partition is not letting it changed ...
the error " ... INFOStart Verify: -1" kind of says that

there is some high level solution (dd and dumping images ) ..let me check on that first and then Ill let you know ..the method

ganeshp · Aug 3, 2012 at 12:21 PM

hey

i need some info
first you need to root your device (you can reflash the RUU after cid change ..that will remove the root)

to root your device ..try my one click root tool (soff guide link in my signature) ...

then i want the output of these commands

from adb folder

adb shell
su (make sure the prompt is # not $)
strings -n 8 /dev/block/mmcblk0p4 (paste the output of this command)
strings -n 8 /dev/block/mmcblk0p5 (paste the output of this command too)

then based on this output i will give you further instructions

Bizwax · Aug 4, 2012 at 1:34 AM

Just to confirm, you want me to follow the rooting procedure from scratch even though I'm already rooted and currently running Elegancia?

ganeshp · Aug 4, 2012 at 4:47 AM

Bizwax said:
Just to confirm, you want me to follow the rooting procedure from scratch even though I'm already rooted and currently running Elegancia?

No no not required if you are already rooted.. Just give me that information from Elegance itself

Sent from my HTC Sensation 4G using xda premium

Subin khan · Aug 4, 2012 at 7:14 AM

I have the same problem. That is not able to downgrade from Super CID. I have tried to run the command as per your suggestion and found “HTC__044” for both commands. But when I type “fastboot getvar cid” it is showing my CID is 11111111. Pls suggest on this.

ganeshp · Aug 4, 2012 at 7:26 AM

Subin khan said:
I have the same problem. That is not able to downgrade from Super CID. I have tried to run the command as per your suggestion and found “HTC__044” for both commands. But when I type “fastboot getvar cid” it is showing my CID is 11111111. Pls suggest on this.

Then mostly it got changed but it's not being reflected from bootloader correctly

Post the output of this command

fastboot oem readcid

Also try an older RUU like that of GB one and then check the cid again..

Sent from my HTC Sensation 4G using xda premium

Subin khan · Aug 4, 2012

Actually, this problem is starting after I have applied below command by a mistake:
fastboot oem writePid HTC__044
that is instead of CID I typed pid
and I think some info are overwritten.

---------- Post added at 12:42 PM ---------- Previous post was at 12:37 PM ----------

Subin khan said:
Actually, this problem is starting after I have applied below command by a mistake:
fastboot oem writePid HTC__044
that is instead of CID I typed pid
and I think some info are overwritten.

BTW, fastboot oem readcid command showing below:

D:\My Mobile\Android\Tools\ADB_Fastboot_Windows>fastboot oem readcid
... INFOfake cid: 11111111
INFOcid: 11111111
OKAY [ 0.000s]
finished. total time: 0.000s

ganeshp · Aug 4, 2012 at 12:49 PM

Subin khan said:
Actually, this problem is starting after I have applied below command by a mistake:
fastboot oem writePid HTC__044
that is instead of CID I typed pid
and I think some info are overwritten.

---------- Post added at 12:42 PM ---------- Previous post was at 12:37 PM ----------

BTW, fastboot oem readcid command showing below:

D:\My Mobile\Android\Tools\ADB_Fastboot_Windows>fastboot oem readcid
... INFOfake cid: 11111111
INFOcid: 11111111
OKAY [ 0.000s]
finished. total time: 0.000s

One more partition where cid is stored is missing then.. I'll dig into that.. Might take some time.. May be in few hours I can come to conclusion

Sent from my HTC Sensation 4G using xda premium

Subin khan · Aug 4, 2012 at 1:28 PM

ganeshp said:
One more partition where cid is stored is missing then.. I'll dig into that.. Might take some time.. May be in few hours I can come to conclusion

Sent from my HTC Sensation 4G using xda premium

Ok then pls help me to restore my missing partition's CID..

Bizwax · Aug 5, 2012 at 1:00 AM

ganeshp said:
adb shell
su (make sure the prompt is # not $)
strings -n 8 /dev/block/mmcblk0p4 (paste the output of this command)
strings -n 8 /dev/block/mmcblk0p5 (paste the output of this command too)

then based on this output i will give you further instructions

I don't get any output from those commands. I switched from Elegancia to Insertcoin to double check and still the same.

Code:

C:\adb>adb shell
[email protected]/# su
su
[email protected]/# strings -n 8 /dev/block/mmcblk0p4
strings -n 8 /dev/block/mmcblk0p4
[email protected]/# strings -n 8 /dev/block/mmcblk0p5
strings -n 8 /dev/block/mmcblk0p5
[email protected]/#

I'll try reflashing the RUU first instead.

Subin khan · Aug 5, 2012 at 5:51 AM

Bizwax said:
I don't get any output from those commands. I switched from Elegancia to Insertcoin to double check and still the same.

Code:

C:\adb>adb shell [email protected]/# su su [email protected]/# strings -n 8 /dev/block/mmcblk0p4 strings -n 8 /dev/block/mmcblk0p4 [email protected]/# strings -n 8 /dev/block/mmcblk0p5 strings -n 8 /dev/block/mmcblk0p5 [email protected]/#

I'll try reflashing the RUU first instead.

Pls use GB base ROM and unlocked bootloader.

Subin khan · Aug 13, 2012 at 11:17 PM

any help regarding this issue?

Bizwax · Aug 14, 2012 at 8:59 AM

Subin khan said:
any help regarding this issue?

Likewise

ganeshp · Aug 14, 2012 at 9:22 AM

Subin khan said:
any help regarding this issue?

Bizwax said:
Likewise

i PM'd one dev for some help ..no reply from him yet ..will try talking to him again today (fingers crossed)

Bizwax · Aug 18, 2012 at 3:18 PM

Well it looks like this one is going nowhere fast. ganeshp, I believe we have you stumped, my good man

So anyways, I've been playing around in the meantime and I got those adb shell commands working. I flashed the RUU, then flashed 4extRecovery via PG58IMG, then installed superuser using 4ext...and now I can actually get outputs for the commands you mentioned earlier:

adb shell
su (make sure the prompt is # not $)
strings -n 8 /dev/block/mmcblk0p4 (paste the output of this command)
strings -n 8 /dev/block/mmcblk0p5 (paste the output of this command too)

then based on this output i will give you further instructions

Here's the bad news, I get strings: not found for both of them. Not much of an improvement, eh?

Code:

C:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p4
strings -n 8 /dev/block/mmcblk0p4
sh: strings: not found
127|[email protected]:/ # strings -n 8 /dev/block/mmcblk0p5
strings -n 8 /dev/block/mmcblk0p5
sh: strings: not found

gol_n_dal · Aug 18, 2012 at 3:46 PM

Did the RUU install OK ? Did you also install Superuser/SuperSU ?

If so install a Terminal Emulator from Play Store (the one I use is from Jack Palevich). Then install BusyBox. Then try directly on the phone in the Terminal Emulator.

When that works try the ADB method again.

[Q] Stuck downgrading from Super CID

Member

Senior Member

Member

Senior Member

Attachments

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member