Hello,
Today i was planning to install ARHD 6.0.2 (ICS 4.0.3). I flashed the ROM but i did hang on the bootscreen. It appears that you have to update the bootloader software with the new 3.12.401.102 firmware package. I tried that but the update failed. And now when i enter HBOOT it says that there is a file missing en it gives an update error wich says " wrong model ID" and in the left upper corner there is a pink box with the text "***LOCKED***" in it.
I am able to get in recovery and fastboot. And i flashed back to ARHD 5.0.2 but it still gives an error when i enter HBOOT.
Can anyone help me?
thommio said:
Hello,
Today i was planning to install ARHD 6.0.2 (ICS 4.0.3). I flashed the ROM but i did hang on the bootscreen. It appears that you have to update the bootloader software with the new 3.12.401.102 firmware package. I tried that but the update failed. And now when i enter HBOOT it says that there is a file missing en it gives an update error wich says " wrong model ID" and in the left upper corner there is a pink box with the text "***LOCKED***" in it.
I am able to get in recovery and fastboot. And i flashed back to ARHD 5.0.2 but it still gives an error when i enter HBOOT.
Can anyone help me?
Click to expand...
Click to collapse
Sound like you need to superCID
Follow these instructions
http://forum.xda-developers.com/showthread.php?t=1192300
big_sw2000 said:
Sound like you need to superCID
Follow these instructions
http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
Do you mean only step 4 ?
thommio said:
Do you mean only step 4 ?
Click to expand...
Click to collapse
yep... he does. only step 4 and you're good to go
dexter93 said:
yep... he does. only step 4 and you're good to go
Click to expand...
Click to collapse
I did as you suggested. And i now have the option to update again.
I did that and i said update completed. but when i restart the bootloader it gives the error again!
What error? After the update you should have 1.23 hboot . Remove the IMG.zip from the sd before you boot again to bootloader, otherwise it will ask you to reapply the update
Sent from my HTC Sensation using XDA App
Hello, I just tried to install hd android revolution 6.6.4, got my phone rooted s-off and all that. I didnt update firmware first (which I should have)and i kept gettiing a bootloop. So I tried wiping everything and then updating firmware to no avail, said cid failed. Which that is also my fault because I neglected to do cid prior to any on these other things. So now I cannot update firmware, I cannont install any rom and Im stuck in bootloop no matter what i do. Any help would be greatly appreciated.
jonnyroggles said:
Hello, I just tried to install hd android revolution 6.6.4, got my phone rooted s-off and all that. I didnt update firmware first (which I should have)and i kept gettiing a bootloop. So I tried wiping everything and then updating firmware to no avail, said cid failed. Which that is also my fault because I neglected to do cid prior to any on these other things. So now I cannot update firmware, I cannont install any rom and Im stuck in bootloop no matter what i do. Any help would be greatly appreciated.
Click to expand...
Click to collapse
you are SOFF
so just change the damn cid to supercid
first remove the PG*** file from SDCARD(use a card reader) otherwise you cant get into bootloader properly
i assume you have adb/fastboot setup ...if you dont then follow this guide to set it up
step to supercid
1.keep your phone in fastboot mode and connect it to pc (phone reads fastboot usb)
2.type this command
fastboot oem writecid 11111111 (it should be eight ones)
thats all now you are supercid...
now flash the fw again ..you wont get any error and then flash the rom via recovery again
Thanks man, needed it laid out to me like that. I appreciate it, now to install hd rev
I unlocked my device via the HTC bootloader unlock token, rooted via all in one kit, then I attained s-off using the wire trick. Now upon boot it reads S-off, but it also says locked where it previously read tampered, unlocked. I don't have a recovery to go to to flash anything, so I'm not sure how to proceed now.
After restart, I go into recovery, it then states CID incorrect! Update fail! Press Power to reboot
How can I flash a recovery/rom now?
Profondo_Rosso said:
I unlocked my device via the HTC bootloader unlock token, rooted via all in one kit, then I attained s-off using the wire trick. Now upon boot it reads S-off, but it also says locked where it previously read tampered, unlocked. I don't have a recovery to go to to flash anything, so I'm not sure how to proceed now.
After restart, I go into recovery, it then states CID incorrect! Update fail! Press Power to reboot
How can I flash a recovery/rom now?
Click to expand...
Click to collapse
from this guide do only step 2
http://forum.xda-developers.com/showthread.php?t=1631861
see if you can flash a recovery in that way
Thank you, that worked.
Profondo_Rosso said:
Thank you, that worked.
Click to expand...
Click to collapse
glad for you mate:good:
rzr86 said:
from this guide do only step 2
http://forum.xda-developers.com/showthread.php?t=1631861
see if you can flash a recovery in that way
Click to expand...
Click to collapse
This post saved me alot! I'm trying to install CM 10.2 on my GF's pyramid. Thanks a bunch!
Im trying to install a rom on my sensation with hboot 1.27 so far i have dev unlocked it and rooted it Also a few hours ago i also managed. To complete the Juopunutbear s-off method. with it asking me would i like to installJuopunutbear Hboot to witch i said yes. And that brings us to my current problem, I cant seem to install cwm I put the PG58IMG File on the sd card an booted into hboot but The file loads up and then fails telling me "Model Id Incorrect update fail press power to reboot." Also after using juopunutbear. To s-off my phone the bootloader. Now says Locked instead. Of unlocked is this normal?
THANKS
Lostmymind904 said:
Im trying to install a rom on my sensation with hboot 1.27 so far i have dev unlocked it and rooted it Also a few hours ago i also managed. To complete the Juopunutbear s-off method. with it asking me would i like to installJuopunutbear Hboot to witch i said yes. And that brings us to my current problem, I cant seem to install cwm I put the PG58IMG File on the sd card an booted into hboot but The file loads up and then fails telling me "Model Id Incorrect update fail press power to reboot." Also after using juopunutbear. To s-off my phone the bootloader. Now says Locked instead. Of unlocked is this normal?
THANKS
Click to expand...
Click to collapse
Check the md5 sum of the PG58IMG File.
Lostmymind904 said:
Im trying to install a rom on my sensation with hboot 1.27 so far i have dev unlocked it and rooted it Also a few hours ago i also managed. To complete the Juopunutbear s-off method. with it asking me would i like to installJuopunutbear Hboot to witch i said yes. And that brings us to my current problem, I cant seem to install cwm I put the PG58IMG File on the sd card an booted into hboot but The file loads up and then fails telling me "Model Id Incorrect update fail press power to reboot." Also after using juopunutbear. To s-off my phone the bootloader. Now says Locked instead. Of unlocked is this normal?
THANKS
Click to expand...
Click to collapse
Hi,
Look HERE
2. Flashing a recovery
Flash 4 EXT
The "Locked" just restricts the fastboot commands available to you.
If this is a problem ,look HERE
Second post,and apply this:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
DO NOT GO TO HTC TO UNLOCK YOUR PHONE WHILE YOU ARE S-OFF.
EfrainTrejo said:
Check the md5 sum of the PG58IMG File.
Click to expand...
Click to collapse
malybru said:
Hi,
Look HERE
2. Flashing a recovery
Flash 4 EXT
The "Locked" just restricts the fastboot commands available to you.
If this is a problem ,look HERE
Second post,and apply this:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
DO NOT GO TO HTC TO UNLOCK YOUR PHONE WHILE YOU ARE S-OFF.
Click to expand...
Click to collapse
I tried to flash recovery but it didn't work it tells me " writing recovery FAILED (Remote not allowed)" and the md5 is correct so no problems there
Lostmymind904 said:
I tried to flash recovery but it didn't work it tells me " writing recovery FAILED (Remote not allowed)" and the md5 is correct so no problems there
Click to expand...
Click to collapse
You have to flash the patched hboot first add suggested by @malybru . after that then you won't have a problem flashing a recovery.
Sent from my Ouya
AndroidSupporter318 said:
You have to flash the patched hboot first add suggested by @malybru . after that then you won't have a problem flashing a recovery.
Sent from my Ouya
Click to expand...
Click to collapse
I was unable to flash the hboot i would just get an error. I fixed my problem about 30 seconds ago by supercid the phone which allowed me to flash Juopunutbear Hboot and then recovery took me 8 hours to figure it out but i was determined.
For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys
BrandonBaskin said:
For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys
Click to expand...
Click to collapse
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.
salvy' said:
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.
Click to expand...
Click to collapse
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again
BrandonBaskin said:
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again
Click to expand...
Click to collapse
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)
MGfusion said:
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)
Click to expand...
Click to collapse
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks
BrandonBaskin said:
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks
Click to expand...
Click to collapse
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified
MGfusion said:
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified
Click to expand...
Click to collapse
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?
BrandonBaskin said:
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?
Click to expand...
Click to collapse
I'm not sure, I don't understand what could still be "modified"
MGfusion said:
I'm not sure, I don't understand what could still be "modified"
Click to expand...
Click to collapse
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)
MGfusion said:
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)
Click to expand...
Click to collapse
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?
BrandonBaskin said:
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?
Click to expand...
Click to collapse
Can't remember if it said modified or not, but I am definitely s-off.
MGfusion said:
Can't remember if it said modified or not, but I am definitely s-off.
Click to expand...
Click to collapse
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.
BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing the OTA, then flashing ruu. Thats how I did I it.
BrandonBaskin said:
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.
Click to expand...
Click to collapse
Oh, you are s-on? I would definitely try sunshine and then install ota or ruu then
The_scam said:
Try installing the OTA, then flashing ruin. Thats how I did I it.
Click to expand...
Click to collapse
Hey, thanks for the response. What is Ruin?
I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...
kommoncents said:
I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...
Click to expand...
Click to collapse
download the zip file I had given a link to above and try installing it with the stock system recovery
BrandonBaskin said:
Hey, thanks for the response. What is Ruin?
Click to expand...
Click to collapse
Lol sorry, meant to type ruu. Using my phone and autocorrect ?
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
MGfusion said:
download the zip file I had given a link to above and try installing it with the stock system recovery
Click to expand...
Click to collapse
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer
The_scam said:
Lol sorry, meant to type ruu. Using my phone and autocorrect
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer
Click to expand...
Click to collapse
lol ohh! ok...I thought it was something like Odin haha
so just so I'm clear:
Flash OTA (in Recovery)?
Then immediately start the RUU?