Hi, it initially rooted my XT1068 and a day before I received the notification for software update to Lollipop, I opted in for the update, but when I started the update the Recovery mode booted by and when I tried to install from the Recovery by selecting the downloaded file "Blur_Version.21.11.23.titan_retaildsds.retaildsds all.en.03" it gave me error saying:
"Package expects build fingerprint of motorola/titan_retaildsds/titan_umtsds:4.4.4/KXB21.85-23/19:user/release-keys."
Your device has "motorola/titan_retbr_dstv/titan_udstv:4.44/KXB21.85-18/24:user/release-keys".
I got the above message after trying to restore to the stock version from the files in this post :http://forum.xda-developers.com/mot...windows-tool-moto-g-2014-xt1068-dual-t2983295
Prior to the restore which is when I rooted the device, I got the error as "Your device has "motorola/titan_retaildsds/titan_umtsds:4.4.4/KXB21.85-14/9:user/release-keys"
Can someone help me how can I restore the exact firmware?
Related
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.
Good day
I was trying to update my 2014 Moto G XT1068 from (Kitkat) 4.4.4 to 5.0.2 (Lollipop)
from following this link
http://forum.xda-developers.com/moto-g-2014/general/official-lollipop-indian-ota-captured-t3002674
Now forgive cause I am new to rooting etc, when I did try and root the phone using the global firmware, my sim was disable. So I decided to use differnet firmware with resulted in sim card not getting signal. So I end up using the Brazilian update for the firmware, and ended up having the phone in AP Fastboot Flash Mode with the error is " Error Failed to Validate System Image"
I have tried using different firmware to get back the phone to work, but to no luck, I am asking what steps can I take now to try and fix my problem.
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.
I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
mnaceem said:
I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
Click to expand...
Click to collapse
maybe a bad/corrupted download
Same issue here, I am unable to update my phone
Sent from my [device_name] using XDA-Developers Legacy app
I just got the same error too.
I also got a warning while i boot back to the old version.
System update failed
Update failed, tap to enter repair mode to try again.
guys, i had the same issue too.
Download the full rom via xda link, installation failed. Same goes for the OTA.
However, I managed to update to stock PIE.
My bootloader was unlocked when using stock OREO.
So what I did was, I RE-LOCKED the bootloader, and reboot the OP3T. (BE WARNED,IT RESET THE WHOLE PHONE)
After fresh installation, i was able to update to PIE via OTA. (Should work with local upgrade too)
So for my case, that helps.
vinoxflame said:
maybe a bad/corrupted download
Click to expand...
Click to collapse
NOPE no bad/corrupted download...
---------- Post added at 09:01 AM ---------- Previous post was at 08:52 AM ----------
Well I was upgraded to the pie with locked bootloader and after that, I had flashed official twrp and magisk but I flashed oreo rom to check if this problem is there when the bootloader is unlocked well yes the one plus detects that your bootloader is unlocked and doesn't deliver the ota so what you can do is click on download upgrade read carefully bro DOWNLOAD not INSTALL just DOWNLOAD it and then you will find it in .ota directory in File Manager now what you have to do is backup your all data via your prefered backup method from which you can restore things after the update I am going to give you a spoiler all data will be corrupted when you will flash the update file via twrp that's why the one plus package updater doesn't update and says installation failed... The pie update will be successfully installed but you have to factory reset your phone to use it that's why I told You to take a backup and after this restore your data...
***I have experienced all this by downgrading and then again upgrading with an unlocked bootloader so I would be honored if you thank me***
I was on stock Pie. I was facing some battery drain issue so I decided to install Oreo official stock which was already downloaded last month. I installed it through local upgrade and rom is still in internal memory. Now I am stuck in Recovery. It tries to boot but every time after few minutes it comes back to recovery. Please help me. It installs Oreo through recovery but unable to boot.
I think Pie can be installed through sideload but I could not find exact links for installation through sideload. Or if there is any option to copy Pie Rom in my internal memory to try installing back latest rom.
If anyone could help me It will be highly appreciated. My bootloader is still locked.
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