Develop Bugs

Issue with updating to Froyo

I forced my phone to check for an update and it found it and downloaded it. When it reboots to install, I get the following:
Build : RA-eva-v1.7.0.1
Finding update package...
Opening update package...
Verifying update package...
E:No signature (624 files)
E: Verification failed
Installation aborted.
Any ideas what's going on here?

jaihawk8 said:
I forced my phone to check for an update and it found it and downloaded it. When it reboots to install, I get the following:
Build : RA-eva-v1.7.0.1
Finding update package...
Opening update package...
Verifying update package...
E:No signature (624 files)
E: Verification failed
Installation aborted.
Any ideas what's going on here?
Click to expand...
Click to collapse
I get this also. Any help would be much appreciated.

jaihawk8 said:
I forced my phone to check for an update and it found it and downloaded it. When it reboots to install, I get the following:
Build : RA-eva-v1.7.0.1
Finding update package...
Opening update package...
Verifying update package...
E:No signature (624 files)
E: Verification failed
Installation aborted.
Any ideas what's going on here?
Click to expand...
Click to collapse
edrob said:
I get this also. Any help would be much appreciated.
Click to expand...
Click to collapse
Are you rooted? Unroot, then OTA if you are...If not, I'm stumped.

Bang3r said:
Are you rooted? Unroot, then OTA if you are...If not, I'm stumped.
Click to expand...
Click to collapse
im very new. how do i unroot? step by step please! Do I need to just start from scratch? ie. go back to stock? how do I do that? Thank you kind sir.

edrob said:
im very new. how do i unroot? step by step please! Do I need to just start from scratch? ie. go back to stock? how do I do that? Thank you kind sir.
Click to expand...
Click to collapse
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7471721#post7471721
It takes a little adb knowhow...not much...what root method did you use? What rom are you running?

I rooted using simple root steps I did not flash a rom I just did the 4 steps and that's all... I get this same error now when trying to get froyo
Sent from my PC36100 using XDA App

I think the problem is probably related to the unroot method i linked to above. Check your HBOOT version by powering off, and then holding VOL down and power until you're in bootloader mode, and see what version of HBOOT you have. If you have .79, you need to do the unroot method first to get down to .76. Then, from there, I think the OTA update MIGHT work, but you may still have to run an RUU. Not sure about that part..let us know if you get to .76 HBOOT and can do the OTA successfully, but that's where I'd start.

I have .76.2000xxx
Sent from my PC36100 using XDA App

Try using clockwork recovery...version 2.0.2.0 is good with non verification

bump this up,having the same problem... used simpleroot and 1.47 stock rooted rom, and I can't get unrooted... need to return this phone to sprint.

Anyone know how to fix this? I get the same error when trying to do the OTA 2.2.

can't update jb from sdcard/update.zip

Hello.
I m using HOX cid : OPTUS001
I downloaded the ota zip n extracted the firmware.zip (containing hboot , boot , recovery.. ) n flashed it using JBFWFlasher.
my hboot is changed from 1.12.0000. to. 1.36.0000
and RADIO from 2.1204.135.20 to. 5.1204.162.29
but as I install update.zip from sdcard following error occurs..
installing : sdcard/update.zip
finding update paxkage...
opening update package...
installing update...
assert failed: check_cid(getprop("to.cid'): "000
00000", "11111111". "22222222". "33333333"
"4444.... ". "5555555.... till 99999999"
"OPTUS001") =="t"
E error in /sdcard/update.zip
(status 7)
installation aborted.
my phone was bricked (stuck on HTC boot logo) then I flashed boot.IMG from nandroid n restored the backup. now working as before.
what should I do to update JB ??
please help.
thanks in advance

grudboy said:
Hello.
I m using HOX cid : OPTUS001
I downloaded the ota zip n extracted the firmware.zip (containing hboot , boot , recovery.. ) n flashed it using JBFWFlasher.
my hboot is changed from 1.12.0000. to. 1.36.0000
and RADIO from 2.1204.135.20 to. 5.1204.162.29
but as I install update.zip from sdcard following error occurs..
installing : sdcard/update.zip
finding update paxkage...
opening update package...
installing update...
assert failed: check_cid(getprop("to.cid'): "000
00000", "11111111". "22222222". "33333333"
"4444.... ". "5555555.... till 99999999"
"OPTUS001") =="t"
E error in /sdcard/update.zip
(status 7)
installation aborted.
my phone was bricked (stuck on HTC boot logo) then I flashed boot.IMG from nandroid n restored the backup. now working as before.
what should I do to update JB ??
please help.
thanks in advance
Click to expand...
Click to collapse
you need a stock recovery and stock rom,to update the ota.also there are two apk's to install which will make your phone pass the ota check

markb63 said:
you need a stock recovery and stock rom,to update the ota.also there are two apk's to install which will make your phone pass the ota check
Click to expand...
Click to collapse
which apks???
can u name or post the links please??

Dude since you're already on hboot 1.36 just download stock JB nanodroid for Optus from here: http://forum.xda-developers.com/showthread.php?t=1975140
Just restore in recovery and flash boot.img

tomascus said:
Dude since you're already on hboot 1.36 just download stock JB nanodroid for Optus from here: http://forum.xda-developers.com/showthread.php?t=1975140
Just restore in recovery and flash boot.img
Click to expand...
Click to collapse
thanks . I will try that.
but can I update my current ics Rom to JB through the ota file that I downloaded??? (its around 369mb)

[SOLVED] HTC One X cannot update after getting back to Stock ROM

Hey guys,
I have been lurking around the forums for sometime now and I could not find the solution to my problem so I hope someone will be able to help me.
My HTC One X (cid : HTC__203) was rooted and I tried a few ROMS before deciding to sell it before getting the upcoming HTC One.
I used the RUU to flash the original ROM I bought the phone with. I've found the file using this post : http://forum.xda-developers.com/showthread.php?t=1660807
Current phone version is :
Now the phone issue is that Android updates cannot be installed. OTA is working, updates are detected and downloaded :
If I just say Intall now, the phone restarts with CWM (v5.8.4.0) and says it cannot mount the SD card. So I just go to Install zip from sdcard and open the file from the download folder. Then it goes :
Finding update package...
Opening update package...
Verifying update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
So I toggle off both signature verification and get a new error about script asserts :
Finding update package...
Opening update package...
Installing update ...
assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" .... (same pattern to 9 then comes some CID numbers where my phone one is listed)
, "HTC__001" ............... , "HTC__203" , .... , "HTC__016") == "t"
E: Error in /sdcard/Download/OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_and_blablabla.zip
(status 7)
Installation aborted.
From there I don't know what to do. I tried to download and install the last RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed
But it fails as well :
My knowledge of phone tweaking does not go further and I don't know what to do to update my phone and make sure next updates will work.
Thanks for reading and for your help.

Re: HTC One X cannot update after getting back to Stock ROM
You cant update via a custom recovery !
Download this file
http://bugsylawson.com/index.php/fi...-r-radio-5120416229-release-302015-signedexe/
Read carefully :
Put the phone in the bootloader and relock it
Fastboot oem lock
Keep the phone in the bootloader and then click the ruu with the right mouse button and select :
"Run as administrator"
This will bring it back to stock.
What is the outcome of
Fastboot getvar version-main
Edit : i cant see the pictures very well, they are small and get blurry when i zoom them

Mr Hofs said:
You cant update via a custom recovery !
Click to expand...
Click to collapse
Ok well that helps a lot. I'll try and install the stock recovery. So from what I understand, every time I'll want to install OTA updates, I'll just have to switch back to stock recovery, install the update and then reinstall CWM if I need it ?
Thanks for the info

Re: HTC One X cannot update after getting back to Stock ROM
Yeah you need stock rom, kernel and recovery to be able to perform an official htc ota

Mr Hofs said:
Yeah you need stock rom, kernel and recovery to be able to perform an official htc ota
Click to expand...
Click to collapse
Phone is up to date. You're my first man crush, congrats !
:laugh:

Re: HTC One X cannot update after getting back to Stock ROM
Uh ....thanks .....I guess
Good it worked mate.
CASE CLOSED !

[Q] OTA Failed Returned to Stock w/S-off

I've restored my stock nandroid backup and flashed stock recovery, but I can't get the OTA to install. My M9 is from T-Mobile, and it has S-off. Here's what I get.
E:missing bitmap oem_unlock_bg
(Code-1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
E:Find no match PARTITION: for package path @/cache/recover
/block.map
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
L50QCT.01 . 104 . 020
Verifying current system. . .
/dev/block/bootdevice/by-name/system has been remounted R?W
reflash device to reenable OTA updates
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Any help with this?

Another thought, I had problems getting Lollipop OTA with my M8, and I had to run earlier RUU then do OTA's. Is that what I have to do now. It doesn't seem like I should have to go that route. Also I had a completely different error message then.

For you now RUU is a must..
The steps needed as I wrote somewhere there:
http://forum.xda-developers.com/showthread.php?p=60114607
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection

jauhien said:
For you now RUU is a must..
The steps needed as I wrote somewhere there:
http://forum.xda-developers.com/showthread.php?p=60114607
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
Click to expand...
Click to collapse
I was afraid of that. I hate having to redo everything. Thanks for your input.

This is why you need to take a backup of the stock system before rooting... Once system is mounted rw no OTA will be taken naturally...

sgt. slaughter said:
This is why you need to take a backup of the stock system before rooting... Once system is mounted rw no OTA will be taken naturally...
Click to expand...
Click to collapse
I did do a backup before I rooted, but I still have this problem.
Sent using XDA Free Mobile App

Or you could just go to the T-Mobile forum and find my thread and find out what to do to correct this, and maintain your data. ?
Sent From My HTC One (M9)

Rydah805 said:
Or you could just go to the T-Mobile forum and find my thread and find out what to do to correct this, and maintain your data. ?
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Thanks I will go there tonight and check it out, and I will let you know what happens.
Sent using XDA Free Mobile App

Rydah805 said:
Or you could just go to the T-Mobile forum and find my thread and find out what to do to correct this, and maintain your data.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Thank you Rydah805 for your suggestion and work in that Thread. I also want to thank @Captain_Throwback for his work in the thread that you linked to in your thread. I wiped everything except storage, took the nandroid backup I did when I first got my device and restored that. Then I extracted the system.emmc.win from my backup, and after renaming it to system.img I flashed it via fastboot then rebooted the phone. I then rebooted into recovery checked to see if the system option was missing from the mount menu in TWRP, and it was. After that I extracted the recovery.img from the update I had downloaded and flashed it via fastboot. After that it was automatic. I went to software updates, downloaded the update and let it install. Then I did another nandroid backup and rooted the phone again installed Titanium Backup and restored my apps and settings. All good! Thanks again!

[MOD] No Red Text aboot / firmware

I've seen a few people looking for a way to remove the red development text from their aboot, so here's an aboot with the red text removed.
This aboot removes the below development warning that you see on each boot:​ This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.​
If you plan to return to stock and relock your bootloader, first restore the stock aboot (in downloads below).
Requirements:
S-Off
On matching firmware.
adb/fastboot tools installed on your computer
Installation:
Code:
adb reboot download
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip 1.33.605.15_NoRedText_aboot.zip
If you get the warning: 'FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)', repeat step 3:
Code:
fastboot flash zip 1.33.605.15_NoRedText_aboot.zip
Code:
fastboot reboot-bootloader
Disclaimer:​Understand that flashing a modified aboot has the risk of bricking your device. I cannot be held responsible for any damages resulting from flashing this mod.
I have tested this myself, therefore it should be safe, however there are no guarantees.
If you are not willing to accept this risk, PLEASE DO NOT FLASH!​ Downloads:
Downloads removed
Credits/Thanks:
@dottat for pulling 3.10.605.7 OTA package
@allroy75 for testing

Announcements:
-Downloads removed

Works awesome. It asked me to flush, but then again so does my girlfriend. Nice work Ben.

Worked fine flashing from external SD mode also. Thanks !

jtommyj said:
Worked fine flashing from external SD mode also. Thanks !
Click to expand...
Click to collapse
Thanks for confirming. I'll add that to the OP

good golly, its aboot time.....haha, thank you @bschram

Works great. Finally the red text is gone! Woo! If we need to grab a future Ota to update firmware do we need to replace stock aboot first??

magesticschu said:
Works great. Finally the red text is gone! Woo! If we need to grab a future Ota to update firmware do we need to replace stock aboot first??
Click to expand...
Click to collapse
I would definitely recommend going back to stock aboot before grabbing an OTA.
(You'll probably end up RUUing back to stock anyway in order to take the OTA, so that will take care of aboot at the same time)
The best/easiest way to update your firmware will be to wait till the firmware is posted here, instead of reverting to stock and taking the OTA.

bschram said:
I would definitely recommend going back to stock aboot before grabbing an OTA.
(You'll probably end up RUUing back to stock anyway in order to take the OTA, so that will take care of aboot at the same time)
The best/easiest way to update your firmware will be to wait till the firmware is posted here, instead of reverting to stock and taking the OTA.
Click to expand...
Click to collapse
OK cool thanks.

bschram said:
I would definitely recommend going back to stock aboot before grabbing an OTA.
(You'll probably end up RUUing back to stock anyway in order to take the OTA, so that will take care of aboot at the same time)
The best/easiest way to update your firmware will be to wait till the firmware is posted here, instead of reverting to stock and taking the OTA.
Click to expand...
Click to collapse
Have you taken a look at the 5.1 aboot?

aer0zer0 said:
Have you taken a look at the 5.1 aboot?
Click to expand...
Click to collapse
It's already in the OP. The 2.6.605.10 aboot.

bschram said:
It's already in the OP. The 2.6.605.10 aboot.
Click to expand...
Click to collapse
nice, someday i will learn how to read

Every time I reboot and see that text, I just smirk and think to myself, "beat you Verizon" ! :laugh:

works perfectly!
vzw 2.6.605.10
Thanks, Ben!

Just curious...after update firmware from 1.33.605.15 to 2.6.605.10 i got a text in yellow color of a certain HTC Security Warning when i put the phone in download mode. Do u guys have too?

HC4Life said:
Just curious...after update firmware from 1.33.605.15 to 2.6.605.10 i got a text in yellow color of a certain HTC Security Warning when i put the phone in download mode. Do u guys have too?
Click to expand...
Click to collapse
That text is present in the 5.1 firmware for all variants of the m9. I can take a look in a few hours and see if it can be removed.

bschram said:
That text is present in the 5.1 firmware for all variants of the m9. I can take a look in a few hours and see if it can be removed.
Click to expand...
Click to collapse
Thx bro. I thought it was only me...lol
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
Another thing i have a kind of error when i put the phone in FTM mode.
Like:
E:missing bitmap icon_installing01
(Code -1)
E:missing bitmap icon_installing02
(Code -1)
E:missing bitmap icon_installing03
(Code -1)
E:missing bitmap icon_installing04
(Code -1)
E:missing bitmap icon_installing05
(Code -1)
E:missing bitmap icon_installing06
(Code -1)
E:missing bitmap icon_installing07
(Code -1)
Hello FTM UI
Can u confirm that too?

HC4Life said:
Can u confirm that too?
Click to expand...
Click to collapse
Yes
Personally, I wouldn't spend any effort "fixing" it, but that's just my opinion....

jtommyj said:
Worked fine flashing from external SD mode also. Thanks !
Click to expand...
Click to collapse
I tried to do the same, but keeps falling. Did you change anything with the file, or simply go to recovery and install?

sgtslaughter64 said:
I tried to do the same, but keeps falling. Did you change anything with the file, or simply go to recovery and install?
Click to expand...
Click to collapse
You need to rename the file to 0PJAIMG.zip, and it must be a fat32 formatted SD card (32gb or smaller)