Database Info

CID error after flash generic rom, stuck in boot loader

Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.

What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?

Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described

You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231

How can I run alpharevx when I can only boot into bootloader tho?

Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...

Have you tried to re-setup your phone by executing one of the RUU.exe?

k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.

yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/

What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...

If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App

Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506

Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.

The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!

I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.

Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.

just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)

Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.

Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now

I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.

Can't Apply ICS OTA update

I never rooted my phone, it was done halfway there in procedure (never installed a custom ROM)
I had installed bootloader (4ext) and S-off
As of now on the phone I had a rom backup using 4ext for January (back when I was trying to root)
I waited long and hard for the OTA ICS update, which now I realize is out for Bell.
I tried to apply the update, phone reboots and 4ext tries to perform the update and I get a path error SDCARD\download\ (update file name)
Alternatively I tried booting up 4EXT and using "update from zip", with the OTA update file, and that applies and reboots to a stuck HTC white screen.
I just want to get this OTA update installed, thanks for advice!!!
PS: I don't think a factory reset is possible, I don't know where the factory reset data is stored or if its gone

funkbro2 said:
I never rooted my phone, it was done halfway there in procedure (never installed a custom ROM)
I had installed bootloader (4ext) and S-off
As of now on the phone I had a rom backup using 4ext for January (back when I was trying to root)
I waited long and hard for the OTA ICS update, which now I realize is out for Bell.
I tried to apply the update, phone reboots and 4ext tries to perform the update and I get a path error SDCARD\download\ (update file name)
Alternatively I tried booting up 4EXT and using "update from zip", with the OTA update file, and that applies and reboots to a stuck HTC white screen.
I just want to get this OTA update installed, thanks for advice!!!
PS: I don't think a factory reset is possible, I don't know where the factory reset data is stored or if its gone
Click to expand...
Click to collapse
man, mustn't update with official ota updates when you are rooted or s-off!

How can I s-on?

funkbro2 said:
How can I s-on?
Click to expand...
Click to collapse
Dude for ota soff is fine... Just flash the stock recovery And make sure cid is unchanged.. Then apply the OTA again
(just get the stock recovery.img from any gb RUU and flash it via fastboot
fastboot flash recovery recovery.img)
That's all... Dont lose soff... SOFF is fine For ota
Sent from my pyramid.. Through blazing fast sonic waves

funkbro2 said:
How can I s-on?
Click to expand...
Click to collapse
you can be S=OFF but you must have stock recovery installed not 4ext and with the rooted part you will loose when you update, so just flash the stock recovery back on your phone and you are set to update.

What may work for you is to try to install the stock Gingerbread RUU for your phone first. Since you can't boot into GB, you may have to extract the rom.zip file from the RUU, rename it to PG58IMG.zip and place it in the root folder of your sdcard. Then restart your phone into the Bootloader and Gingerbread should reload. You do not need to be S-ON. If that is successful, your bootloader and recovery will be back to stock and you should still be S-OFF. The OTA should work at that point.

Now why would I need to reflash to a previous rom, if I never rooted?
My phone boots when I reverted to the Jan 5 rom backup (which is still phone original rom)
I can definitely try installing original gingerbread rom and then apply the OTA update as suggested

funkbro2 said:
Now why would I need to reflash to a previous rom, if I never rooted?
My phone boots when I reverted to the Jan 5 rom backup (which is still phone original rom)
I can definitely try installing original gingerbread rom and then apply the OTA update as suggested
Click to expand...
Click to collapse
Didn't know you were able to recover from a backup. Thought you were stuck on the white HTC screen. In that case, go ahead and try to fall back to a stock recovery, then try to do the OTA.

OTA still fails for same reason
After downloading OTA update, clicking apply.. Phone restarts and loads up 4EXT which proceeds to apply update. And then results in the cannot load path error

funkbro2 said:
OTA still fails for same reason
After downloading OTA update, clicking apply.. Phone restarts and loads up 4EXT which proceeds to apply update. And then results in the cannot load path error
Click to expand...
Click to collapse
As long as you don't have the stock recovery the OTA fails.. Read my previous post.. For God sake
Sent from my pyramid.. Through blazing fast sonic waves

Used RUU to flash back to "original"
Then did OTA update and it worked no problems
Now using ICS from OTA
Thank you everyone

ganeshp said:
Dude for ota soff is fine... Just flash the stock recovery And make sure cid is unchanged.. Then apply the OTA again
(just get the stock recovery.img from any gb RUU and flash it via fastboot
fastboot flash recovery recovery.img)
That's all... Dont lose soff... SOFF is fine For ota
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Will this work if I have SuperCID, or do I need to change it back?
Also, once OTA update is done, just reflash 4EXT and then SuperSU?

alza6991 said:
Will this work if I have SuperCID, or do I need to change it back?
Also, once OTA update is done, just reflash 4EXT and then SuperSU?
Click to expand...
Click to collapse
probably you have to change your cid to original
and yes after ota update flash 4ext again

rzr86 said:
probably you have to change your cid to original
and yes after ota update flash 4ext again
Click to expand...
Click to collapse
Posted in help thread, but asking you as well:
My phone is HTC Sensation XE, from Australia on Vodafone network.
I need to change my CID back to original, but I can't remember if it was:
HTC-Australia HTC__023
Hutch-Australia HUTCH001
VODA-Australia VODAP021
In Australia, the network is Vodafone-Hutchinson together, so I don't know which one to take.
Not sure what for, but x.xx.862.x - Voda-Hutch AU (Australia) is my provider/location code.
Any help is much appreciated, thanks in advance.

alza6991 said:
Posted in help thread, but asking you as well:
My phone is HTC Sensation XE, from Australia on Vodafone network.
I need to change my CID back to original, but I can't remember if it was:
HTC-Australia HTC__023
Hutch-Australia HUTCH001
VODA-Australia VODAP021
In Australia, the network is Vodafone-Hutchinson together, so I don't know which one to take.
Not sure what for, but x.xx.862.x - Voda-Hutch AU (Australia) is my provider/location code.
Any help is much appreciated, thanks in advance.
Click to expand...
Click to collapse
install cid getter app from play store
it will show the original cid

Signature verify fail

I need help. I am trying to revert back to stock but when I run RUU for my HTC One S T-Mobile USA it stops every time when trying to verify the signature. I locked my bootloader and tried unlocking it and the same thing happened when verifying my signature it said it failed. I don't know what to do please help me.

Did you flash a signed stock recovery before locking the bootloader?

reverting from a higher firmware version to lower is not possible until the s-off is achieved for htc s

touch of jobo said:
Did you flash a signed stock recovery before locking the bootloader?
Click to expand...
Click to collapse
im not quite sure I'm using a trickdroid rom. Is there anyway that i can still do that?

In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.

touch of jobo said:
In order to run a RUU, your must have a signed stock recovery and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)

bobsie41 said:
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
Click to expand...
Click to collapse
But I have tried to update with a re locked bootloader and every time it fails at the signature verification

touch of jobo said:
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though

milkshakes said:
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
Click to expand...
Click to collapse
Having the same problem. Was able to RELOCK but still won't flash RUU. Would really appreciate any help. Almost as much as I now appreciate a removable SD card.

i have this same problem, orginal bootloader etc boot loader relock and still nothing always finish with error checksum failed
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Any other solution
CID to H3G__001
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Regards

Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium

kylepont said:
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
now i have error 155 it look like wrong bootloader or recovery
i change couple times recovery and boot (taken from OTA update) and still nothing
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Regards

blackangel82 said:
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Click to expand...
Click to collapse
blackangel82 said:
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Click to expand...
Click to collapse
Those RUUs are too old for you. (You can't run a RUU with an older hboot than you have.) If I remember correctly, 1.53.xx comes with hboot-1.06 and the 1.78.xx RUU has hboot-1.13
and you have hboot-2.13. If you are S-Off, you can flash an older stock hboot.
-Jobo

Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.

stoked said:
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
Click to expand...
Click to collapse
Use the Link in my signature.

khan.orak said:
Use the Link in my signature.
Click to expand...
Click to collapse
Thanks. I actually got my phone upgraded by reflashing the stock recovery, locking the bootloader and then running the ota update. Still not sure why I still have a tampered message in the hboot though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Install Failed, Status 1

Ok, i need help here. i'm not sure what is the problem here.
Current Bootloader System
S-Off
hBoot 2.14
Radio 3.18
Super CID - 1111111
Everytime i try to install a ROM, not all of them. i got Install Failed: Status 1. Which i didn't know why.
Previously in previous root i didnt have a problem
Couple days back i decided to tried OTA to 4.1.1 from ATT and this start happening. I relock my bootloader before the OTA and re-unlock before the update following this method. i managed to back to AOSP and some AOKP. but i always had a problem on Viper, very laggy and dialer are almost useless. I cant even flash CleanROM 6.
But, i was thinking. On my bootloader i have Unlocked flag but didnt have Tampered flag, which is i think the issue here. May i get a confirmation on that? and if that the case, may i have the guideline to re-root it this software.
THanks

Try a lower version of twrp if you are using 2.4.3.0

What tez1 said. Though the I believe "failure" is actually just a failure to wipe cache at the end of the flash procedure (at least, that's what it's been for me when I get the error). If you manually wipe cache after install, and then reboot, the flash should have succeeded.

incofstupid said:
But, i was thinking. On my bootloader i have Unlocked flag but didnt have Tampered flag, which is i think the issue here. May i get a confirmation on that?
Click to expand...
Click to collapse
That's not an issue at all. It's what happens when you install new stock system software (like the OTA or a ruu) after you're s-off. S-off stops all security checks, so you don't get that rooted flag anymore.

Problem TWRP... install 2.4.2!

thank you for all the answers i will try it.
EDIT: thanks, you can close this thread. it was the TWRP 2.4.X.X i decided to go back to 2.3.3.1.

Htc a9 at&t

I wanted the newest android Nougat on the phone so i paid for the sunshine s-off and changed the cid and mid. Loaded twrp recovery couldn't get anything to work with that either so i figured it was cause i didn't erase everything the right way and used twrp advanced wipe and now it looks like im really screwed! any help would be appreciated!! Also i tried the RUU from HTC nothing works !!! i want to cuss so bad AAHHHHHH

You're going to have to be more specific about what you did if you want anyone to help you. What did you try to do that didn't work the first time? What all did you wipe? What is your device doing now? How did you try and use the RUU and did it give you any clues when it didn't work? Can you boot into fastboot mode at all?

JohnRogers23 said:
You're going to have to be more specific about what you did if you want anyone to help you. What did you try to do that didn't work the first time? What all did you wipe? What is your device doing now? How did you try and use the RUU and did it give you any clues when it didn't work? Can you boot into fastboot mode at all?
Click to expand...
Click to collapse
Sorry for the rant last night i was extremely frustraded! here is the phones current status
hxxp://imageshack.com/a/img922/7475/b6feFX.jpg
hxxp://imageshack.com/a/img923/192/AA2vGU.jpg
I tried to install the unlocked RUU for nougat and i also tried to use ADB to install the Nougat unlocked zip file
I would like to update to the unlocked version of Nougat
when i try to install the lastest RUU for unlocked it gives me error [132] signature error

i have the same model at&t unlocked and would like to update to the latest nougat, plz if someone can write an easy step by step tutorial
thank you

If converting,soff is needed,and you have to incrementally update device to current ota.. Cannot just change cid and mid and flash the Nougat ruu...

Wonders_Never_Cease said:
If converting,soff is needed,and you have to incrementally update device to current ota.. Cannot just change cid and mid and flash the Nougat ruu...
Click to expand...
Click to collapse
So how would i get my device to the unlocked edition 2.18.617.1 from 1.27.502.5? i realized after doing some research that i can't flash 1.x.x.x.x.x to 2.x.x.x.xx.x and i got flashed back to 1.27.502.5

killerdie14 said:
So how would i get my device to the unlocked edition 2.18.617.1 from 1.27.502.5? i realized after doing some research that i can't flash 1.x.x.x.x.x to 2.x.x.x.xx.x and i got flashed back to 1.27.502.5
Click to expand...
Click to collapse
You will have to take the 1.56.X latest ruu manually (from recovery or SD download mode) and then upgrade using the OTA.
Or PM me for the firmware image for the a9 to get to nougat.