Hi everybody,
This morning I received the notification about the OTA update on my phone (new build: NPW26.7, software channel reteu), that is unlocked and rooted.
The problem is that the update fails everytime, even after I flashed the stock system image.
I tried also installing the OTA with adb-sideload, but it fails and the output is:
Code:
Opening update package...
Verifying update package...
Installing update...
Step 1/2Error applying update: 20 (ErrorCorde::kDownloadStateInitializationError)
E:Error in /sideload/package.zip
(Status 1)
I was wondering: is it possible that the update fails even if the system is stock, just because the bootloader is unlocked? Basing on my past experience, it should work anyway.
Or maybe I'm just receiving the wrong package? The OTA filename is Blur_Version.26.51.2.payton.retail.en.US.
Any ideas?
Ok, the issue was that, having rooted the phone, all the partitions - somehow - changed. In fact, taking a look at the logcat, it gave that "kDownloadStateInitializationError" after comparing the hash for the actual and expected partitions.
So I had to reflash all of them (partition, bootloader, modem, bluetooth, dsp, logo, boot, system, system_b and oem) to get it working.
Related
Got the OTA notification yesterday. Decided to install it.
The problem is is that I have a custom recovery image. Android system recovery or something like that. When the OTA update put the phone in recovery mode, the instillation failed because the packet was not signed (assuming this recovery can't read official signed zips)
I also downloaded it from google and the same thing happened. I clicked "flash zip from sdcard" under the recovery and it gave me the same error.
Also, this won't unroot me right? If it does can I just adb root it again?
Also I've heard alternative keyboards have issues, but I also heard if you uninstall and reinstall them it fixes the issue.
So how can I install 2.2.1? I don't really want to reset the phone to factory. Any other options?
Also, the OTA notification is gone, so I have to flash the zip most likely.
And... I rooted using adb. Will this unroot it (I know it breaks one-click root)
Bump
Sent from my Nexus One using XDA App
Use Amon RA 1.8.0.x or ClockworkMod, they will both flash anything, signed (release or test) or not.
This will unroot you, but the rageagainstthecage exploit still works.
I tried both amon ra and clockwork. Amon ra gave me this
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (188 files)
E:Verification failed
Installation aborted.
Click to expand...
Click to collapse
clockwork gave me something similar. I believe it just failed.
This is where I'm getting the update from
http://android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
I mean it looks entirely legit. I renamed it to update.zip.
Edit: I tried Amon Ra 1.8.0 (as it is supposed to allow singed and unsigned packages) and it still failed, I got this one this time...
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:boot:2392064more text):unknown command [(more text)]
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
XSafire said:
I tried both amon ra and clockwork. Amon ra gave me this
clockwork gave me something similar. I believe it just failed.
This is where I'm getting the update from
http://android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
I mean it looks entirely legit. I renamed it to update.zip.
Edit: I tried Amon Ra 1.8.0 (as it is supposed to allow singed and unsigned packages) and it still failed, I got this one this time...
Click to expand...
Click to collapse
The Status 7 error was a similar error i got when I tried to flash KoR 2.2 (no cyanogen). I believe it meant your boot or kernel sector has bad areas or something. The rom dev released a fix with a new rom with smaller kernel.
I have a Consumer Cellular XT1064 running 21.11.17.titan_retuaws.retuaws.en.US.na with an unlocked bootloader and am having trouble applying the lollipop ota upgrade patch. When I attempt to apply the patch in stock recovery, I get an error durning "Patching system files". The error reads "assert failed: apply_patch(*/system/framework/framework-res.apk" followed by a series of letters and numbers, and ultimately ending with "installation aborted".
I previously successfully applied the ota and was running Lollipop using this guide. While attempting to root, I couldn't get twrp to persist after a full boot nor could I successfully install supersu, so I decided to start from scratch (probably a bad move) and followed those same steps again, but this time ran into the assert failed error described above. I tried re-locking the bootloader, thinking that may help, but got error messages during the process, so that's a no-go. I've scoured the forums and web for another solution, but haven't come up with anything so far.
Maybe there are some files/settings that aren't being completely restored to 4.4.4 stock through the manual flashing process? I can't get RSD Lite to recognize this phone (even though it recognizes my Droid Maxx just fine).
Any other thoughts or suggestions would be much appreciated.
Solution for XT1064 assert failed errors when applying Lollipop ota
After much trial and error, I successfully found a way to get rid of the assert failed errors and get back to Lollipop. Thanks to diamondjoker5, I obtained the original retail firmware 21.11.23 and used fastboot commands to flash it over the 21.11.17 firmware. I then let the phone fully boot into 21.11.23, powered off, then followed the original ota update procedure once again, without any errors.
Hi all, new to the forums here. Sorry if this is in the wrong section. So I was trying to update my nexus 6 to 6.0.1 from 6.0 and I got this error
supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing Update...
Source: google/shamu/shamu:6.0/MRA58K/2256973:user/release-keys
Target: google/shamu/shamu:6.0.1/MMB29K/2419427:user/release-keys
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8393958:28495c2ab9b8a2210fc396d8af35c29bc885fce9:8398054:bb5e73e0be23e9709b0acfd83db5c62140" has unexpected contents
E: Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Now I looked up status 7 errors and how to fix, but none had pertained to my particular issue, so I figured I'd check before doing anything drastic. For some info, I have rooted, unlocked bootloader, flashed a custom recovery and rom, but when Marshmallow came out, I flashed stock image for 6.0 to my phone through nexus root toolkit, which removed custom recovery, flashed to stock, but kept bootloader unlocked. So now I'm on clean stock 6.0 and I received the OTA and I tried to install it and this is the message I get. Any ideas on how to get my phone to update? Oh, and BTW if it matters, I'm on T-Mobile. Thanks in advanced!
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
istperson said:
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
Click to expand...
Click to collapse
Hey, that would be great! The only problem is I'm not particularly skilled in that field lol. Does the boot.img, system.img and radio come from the stock factory image, or do I have to download those separately? And would I install those with a particular program? Thanks, sorry for being such a noob
It's in the factory package mmb29k. Download it, and extract it, you'll have the bootloader, the radio, and a zip file with all the rest. You don't need the bootloader, it hasn't changed since the marshamllow preview. Extract the files from the zip file, then flash radio, boot.img and system.img.
For flashing you need fastboot, but the toolkit already installed it, it just calls it when you push buttons.
As for the flashing, everything is explained in the pinned post.
My phone is Moto G 2014 XT1068 Dual SIM with 5.02 Lollipop. The phone is unlocked but unrooted. I received the OTA notification for upgrading to MM. The process failed. Recovery mode was "no command available" (in Italian). So I installed TWRP recovery instead. The OTA prompt aimed at updating to MM reappared. After have Launched the updating process, the phone entered in TWRP recovery displaying the following error message:
"Package expects build fingerptint of motorola/titan_retaildsds/titan_umtsds:5.0.2/LXB22.99-16.3/5:user/release-keys or motorola/titan_retaildsds/titan_umtsds:6.0/MPB24.65-34/31:user/release-keys; this device has Motorola/omni_titan/titan:5.1.1/LYZ28J/2:eng/test-keys.
Updater process ended with ERROR: 7
Error installing zip file '/cache/Blur_Version.22.56.3.titan_retaildsds_retaildsdsall.en.03.zip
Done processing script file
MTP Enabled".
Any suggestion to allow OTA update to work properly?
Thank in advance.
---------------------------
I have solved the problem reinstalling Stock Lollipop 5.0.2. I now guess that the problem derived from the fact that I had changed the logo to avoid the annoying warning about the risks of having the phone unlocked.
Hope this may be helpful for those that have done a similar change in their phone.
Greetings,
in a last month or so, im trying to revive this tablet, mostly because of the dual boot posibilities, but that can be done only with lollipop uefi bios.
My device is currently running 4.4 .201 OTA and im unable to update to 5.0 with whatever step i do.
First of all, i hard bricked my first device of this model myself completely, so i decided to replace my motherboard, somehow i lost the side buttons aswell, so i did order a "non-working" device from e-bay. I made it working by just flashing the .182 firmware.
I wasnt able to apply OTAs to the device, always got Status 7 Error in recovery, i did fix that by using a modified update script that i had to apply to every single OTA i flashed.
Finally got to 201, now its time to go to Lollipop.
I tried
- flashing LP firmware through temporary recovery (CWM/TWRP)
- flashing every single firmware thats available - .17; .24; .33; .36 - every single one with the KK "prefix"
- flashing every single firmware with the official firmware update method aswell (putting the update file to root of internal/sd memory and applying it within the tablets system
- flashing the official OTA updates that arrived as dlpkgfile
- flashing the firmware with the command file (putting renamed firmware to update.zip, to /data/ + command file to /cache/recovery/
- flashing service firmware with Intel Phone Flash Tool (KK/LP)
- reseting data/factory reset before and after the update, with cache included
- restoring both backups of KK/LP
- flashing boot.img extracted from the ROM after applying the update
Maybe im missing something, but in every single case, the update went through (some maybe had error in TWRP, but were fine in CWM/stock), but the system doesnt upgrade itself.
The update completes, then after a system reboot the device just goes to the ASUS logo (first one), gets stuck for roughly 30 seconds and bootloops. The droidboot/bootloader is not changing after update.
Any ideas on how to proceed now? I believe i tried every single method of updating, could not suceed unfortunately.
Thanks!
FIXED
The original system update process (putting update file in the root of sdcard,blablabla) always ended up on like 70% and rebooted, with no bootloader upgrade.
So the system didnt boot up, had to revert back to kitkat.
I found OTA Verifier app, that verifies the update script and selects the error in it.
I saw, its saying my device model number is K013_1, but thats not true! For some reason i had 2 build.props in my system files, so i rooted, deleted build.prop_K013_1 (or some name like this) and kept the original one.
! The update itself didnt give any kind of error, it went through without saying anything, thats why i didnt think the updater script would be the problem!
I believe, just deleting the first 2 lines in the update script would help aswell.
After that, i applied the update and waited for it to finish, at 70% once again it rebooted, but this time it started upgrading the bootloader. Lollipop installation finished and im finally at 5.0