I want to update my phone to a newer firmware (got 4.1.1 Renovate), and OTA Updater keeps saying I've got an update.
Eventhough it says "Error fetching update info: Invalid ROM (renovate1xjb)...." - How should I proceed to update?
mortenmoulder said:
I want to update my phone to a newer firmware (got 4.1.1 Renovate), and OTA Updater keeps saying I've got an update.
Eventhough it says "Error fetching update info: Invalid ROM (renovate1xjb)...." - How should I proceed to update?
Click to expand...
Click to collapse
Wrong forum, this is for the dual core HTC One X/XL.
Related
Hello,
Today we have a new ota update for HTC One S, but I can't installed it, installation is aborted.
I have downloaded it, then I want to install it, my phone turned off then it turn on with recovery, but I have the message:
Installation aborted.
I have tried to do that manually with recovery, but I have the same message.
Do you have any idea?
Firstly, Is the OTA configured to be flashed via CWM ??
Secondly, Flashing official signed packages require the bootloader to be locked (so ive heard)
Thirdly, Check the MD5 sums match,, Its possible it was a bad download.. This is the most common cause of ''installation aborted'' messages
Here the same
I start the OTA Update for my HTC one S
this error comes on CWM Recovery
ClockworkMod Recovery v5.8.3.1
"Finding update package...
E: CanĀ“t mount INTERNAL SDCARD...
Installation aborted. "
thanks for help
HTC One S only Root and recovery. s-on stock rom
My guess is it's a recovery problem, as the package won't install via manual either.
But I won't dive deeper into the matter now. Just backing up my phone and cleaning it out to be ready for shipping tomorrow. It's going back to retailer because of the MAO chipping issue.
After flashing the Stock Recovery with this wonderful One klick tool the Update is working just fine...
http://forum.xda-developers.com/showthread.php?t=1604677&page=6
I had my Bootloader unlocked via HTCdev... Seems like an unlocked Bootloader has got nothing to do with this issue!
To keep your Phone rooted after the update, use OTA Rootkeeper from the Playstore!
Where did you get the stock recovery? I'm having trouble finding it.. I want to install the OTA update!
eahiv said:
Where did you get the stock recovery? I'm having trouble finding it.. I want to install the OTA update!
Click to expand...
Click to collapse
I follow one of torxx's thread and it took me here, stock recovery available.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always fails with the following details:
CWM-based recovery v5.5.0.4
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
What is this update? Should I just keep trying? Do I need to do something to make it work? Or should I just install the new leaked JB ROM?
MrGibbage said:
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always
Click to expand...
Click to collapse
I believe you can't be on a custom recovery and successfully install an OTA update on its own.
- ooofest
MrGibbage said:
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always fails with the following details:
CWM-based recovery v5.5.0.4
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
What is this update? Should I just keep trying? Do I need to do something to make it work? Or should I just install the new leaked JB ROM?
Click to expand...
Click to collapse
Any OTA update, you need to go back to pure stock rom, meaning no root, no custom rom, no cwm. Sooner or later you need to move on to Jelly Bean, so yeah, prepare yourself, do a full backup of your apps (not system apps), go back to stock then take the OTA. Second option, disabled the OTA notification for now and wait for JB custom rom build for official Jelly Been.
That all makes sense. Thanks, guys!
My oneplus is currently working on android 5.0.2 with cyanogen version
"CM-12.0 YNG1TAS17L" and recently i got a notification form software update that and update to "CM-12.0 YNG1TATAS213"when i clicked at that notification, it dint update and instead it restarted into recovery mode and i found the update file and clicked on it but it gives an error "error executing updater binary " . Please help
Use search.
http://forum.xda-developers.com/showthread.php?t=3150122
kaushik boggarapu said:
My oneplus is currently working on android 5.0.2 with cyanogen version
"CM-12.0 YNG1TAS17L" and recently i got a notification form software update that and update to "CM-12.0 YNG1TATAS213"when i clicked at that notification, it dint update and instead it restarted into recovery mode and i found the update file and clicked on it but it gives an error "error executing updater binary " . Please help
Click to expand...
Click to collapse
Download the full version and flash it manually thru any custom recovery.
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
robert1010 said:
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
Click to expand...
Click to collapse
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Both update methods, as described above, fail. Method 1: using the phone's system updater, method 2: using the official(?) OTA upgrade files provided on this site.
But it looks like the OTA file is of a version I already have. See attachment.
Sorry, I misread your reply. I am looking for the stock recovery now keep you posted.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
robert1010 said:
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
Click to expand...
Click to collapse
Anyone who can help me with this please?
Hi,
I've got TWRP 3.0.2-0 recovery installed with CM12.1.1 YOG7DAS2K1 and am receiving the OTA update for CM13.0 ZNH0EAS2JK Incremental but the installation fails with an error message in recovery saying it's expecting "YOGDAS2K1" level but finds "YOG4PAS1N0". This happens whether I re-enable the CM Recovery update or not.
I found a thread here on XDA linking to all CM official updates. I flashed the recovery from "cm-12.1-YOG7DAS2K1-bacon-signed-fastboot" successfully and then tried the update again but it still failed. Again, happens whether I have CM Recovery update enabled or not.
Verifying current system...
system partition has unexpected contents
E : Failed to install @/cache/recovery/block.map
Click to expand...
Click to collapse
So now I flashed TWRP again. Does someone know what I should do to install the update ? Preferably without returning to stock first.
Solved
Feeling a bit stupid really...
Right under my post in the list was this post which deals with my problem exactly. I just updated my phone using that guide.