Related
I've got a little problem with update from HTC. I've downloaded update package and said to install it. Phone reboots to CWM and shows:
"E: failed to verify whole-file signature
E: signature verification failed
Installation aborted"
What should I do to install this update?
parkourz said:
I've got a little problem with update from HTC. I've downloaded update package and said to install it. Phone reboots to CWM and shows:
"E: failed to verify whole-file signature
E: signature verification failed
Installation aborted"
What should I do to install this update?
Click to expand...
Click to collapse
A bit more information?
Like cwm what version, what update etc?
Phone with unlocked bootloader and rooted, Titanium kernel build 3, CWM version: 5.8.3.1, Update: OTA_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2-1.56.401.2_release_263407fhrx3c7ruhhci3bi.zip
parkourz said:
Phone with unlocked bootloader and rooted, Titanium kernel build 3, CWM version: 5.8.3.1, Update: OTA_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2-1.56.401.2_release_263407fhrx3c7ruhhci3bi.zip
Click to expand...
Click to collapse
now that is a problem,
You can't update an OTA with CWM.
If I'm correct you want to go back to stock. If yes than follow these instructions (or if you have nandroid, backup at cwm)
http://forum.xda-developers.com/showthread.php?t=1705484
eee... I only have unlocked bootloader and root, no custom ROMs
parkourz said:
eee... I only have unlocked bootloader and root, no custom ROMs
Click to expand...
Click to collapse
but you have cwm, which is not the stock recovery, so OTA will not update. But if you are on stock, you need just to fastboot flash recovery recovery_signed.img from the same post. You will not be able to update from that zip, but RUU will update your device. use OTA rootkeeper to maintain root after ota.
---------------------------
Just to be 100% clear:
OTA updates are only installable by your device, if You have the stock recovery. CWM or touch recovery is not the stock version, so the phone cannot write partitions that is must, and stock recoveries often uses non-edified file verification, so the non-stock recoveries will see them as defected.
So if You want to update by that zip you just need to do the following:
fastboot flash recovery recovery_signed.img
fastboot oem lock (not sure if it is necessery, but it works for sure)
If you don't want to reroot your device after OTA, download OTA rootkeeper (voodoo) from market, and push protect root BEFORE update.
so you have the stock recovery, the zip which contains the OTA upgrade will install.
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Sgtpanda said:
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Click to expand...
Click to collapse
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
dnlsmy said:
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
Click to expand...
Click to collapse
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Sgtpanda said:
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy Nexus using xda app-developers app
wilsonlam97 said:
Yes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Sgtpanda said:
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Click to expand...
Click to collapse
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Any ideas or am I screwed and should go ahead and try flash stock rom and unroot? Will that even help?
Sgtpanda said:
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
efrant said:
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
Click to expand...
Click to collapse
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Sgtpanda said:
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
efrant said:
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
Click to expand...
Click to collapse
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Sgtpanda said:
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Click to expand...
Click to collapse
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
efrant said:
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
Click to expand...
Click to collapse
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Sgtpanda said:
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Click to expand...
Click to collapse
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
efrant said:
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
Click to expand...
Click to collapse
I'll try it, thanks for the help.
EDIT: It worked! Did it without wiping and it accepted the OTA without needing to do it manually, once again thanks so much for helping!
I am a complete newbie to modding my phone. I have an AT&T HTC One X with 2.2 build. I was able to successfully root the phone and install TWRP v2.8.1.0. I have downloaded CM10.2.1 and attempted to flash using the TWRP recovery but I get the following error E: Error executing updater binary in zip '/sdcard/cm-10-2-1-endeavoru.zip'. Any help would be greatly appreciated. Keep in mind I am a newbie so I may need dumbed down instructions.
Try CM11...
Regnas, I tried CM11 and still got the same error.
zx2max said:
I am a complete newbie to modding my phone. I have an AT&T HTC One X with 2.2 build. I was able to successfully root the phone and install TWRP v2.8.1.0. I have downloaded CM10.2.1 and attempted to flash using the TWRP recovery but I get the following error E: Error executing updater binary in zip '/sdcard/cm-10-2-1-endeavoru.zip'. Any help would be greatly appreciated. Keep in mind I am a newbie so I may need dumbed down instructions.
Click to expand...
Click to collapse
Man you are in the wrong section go in AT&T forum one x and try some rom from there dont floash anything from here. Here is international ONE X not AT&T
I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
Verifying update package...
Installing update...
M60QCT.02.003.021
Verifying current system...
Package expects build fingerprint of htc/pmewl_00617/htcpmewl:6.0.1/MMB29M/761759.1:user/release-keys or htc/pmewl_00617/htc_pmewl:6.0.1/MMB29M/787791.1:user/release-keys; this device has htc/pmewl_00617/htcpmewl:6.0.1/MMB29M/748430.5:user/release-keys.
E:Error in /sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???
nullo said:
I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???
Click to expand...
Click to collapse
Alrighty seems like I fixed it! I ended up flashing the EraseDevInfo zip in http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
Not sure how I did the first update without flashing it that file last time?
nullo said:
Alrighty seems like I fixed it! I ended up flashing the EraseDevInfo zip in http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
Not sure how I did the first update without flashing it that file last time?
Click to expand...
Click to collapse
Glad that worked for you. You don't always trip the verity mode check when you modify system. It seems to only occur when you modify system AND use a 100% stock kernel. So it makes sense that ota will work sometimes and not others.
Edit: wrong thread
nullo said:
I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???
Click to expand...
Click to collapse
Do you mind me asking how I can manually flash 1.82.605.6 to my device? I'm s-off/rooted, bootloader locked, flashed stock recovery (thinking I could get OTA, I was wrong). Ideally I'd like to not lose data, but all I'm really worried about is not losing s-off or bricking my phone. It seems like this must be common knowledge, because any time firmware is posted or linked with a ROM there are no instructions on how to actually install it. I would really appreciate some help, I'm stuck on 1.19.605.22!
Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?
I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.
droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.
charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.
How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx
sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs