Related
So I want to update to 4.2.2 using the Nexus Toolkit (I have the latest one) but have been running into problems. Every time I try to update it fails: assert failed: apply_patch_check ("/system/lib/libSR_AudioIn.so", bcc09f67f497c66aedece202942bc4c45f712f62", "85eeeb97d102a3f6656e58cb25ad97bbe29ec613")
After reading around I found out that the Beats Audio drivers I had installed (and thought I removed) modified that .so file. I'd like to be able to just replace that single file with the stock version to save me the hassle of flashing the whole stock image.
Does anyone know where I can find a copy of that file, or a work around that I can use?
Thanks!
http://forum.xda-developers.com/showthread.php?t=2144330
use 'search thread', people have similar issues, you'll find a solution there.
Yeah, I read through about 10 different threads about this but none of them actually had a solution... Just a bunch of "This is happening UPDATE: Fixed it" type posts. No one has actually posted their solution in any of the threads I've looked through (including the one you linked). Thanks for the link though.
issak42 said:
http://forum.xda-developers.com/showthread.php?t=2144330
use 'search thread', people have similar issues, you'll find a solution there.
Click to expand...
Click to collapse
i am also looking for SiMILAR Method like how we installed BEATS AUDIO so the method should be the same if someone can provide stock audio driver ZIP so we can reflash it back to get old drivers
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Thanks. That's exactly what I did... I decided to use the Nexus 7 Toolkit to just restore to stock (I was getting frustrated so I didn't care if it removed all my apps, etc). It turns out the toolkit lets you restore the stock image without wiping all of your apps/sd data so I was able to update and everything was great. Not rooted anymore, but I'll deal with that later .
nextelbuddy said:
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Click to expand...
Click to collapse
i had the same deal. flashed system.img, updated, flashed su. i didn't flash boot though
?need to flash boot.img
Thanks for above. I have solved the beats audio problem as per above. I only flashed the system.img and not the boot.img. Does this matter? Or should I do so to get the latest kernel? or is my kernel 3.1.10-g05b777c the latest?
Cheers,
Sam
yuo need to be on stock everything so to be safe and retain all user data and apps, just flash system.img and boot.img
it wont hurt anything and saves you headaches
I am currently in the same boat. I can't seem to find the stock image for 4.2.1. On Google's site they only have 4.1.2 and 4.2.2. Does any one know where I can get it or at least the system.img and boot.img from it?? Thanks for the help.
Leif
Leifrn said:
I am currently in the same boat. I can't seem to find the stock image for 4.2.1. On Google's site they only have 4.1.2 and 4.2.2. Does any one know where I can get it or at least the system.img and boot.img from it?? Thanks for the help.
Leif
Click to expand...
Click to collapse
http://goo.im/devs/WugFresh/stock/nakasi
burnitdown said:
i had the same deal. flashed system.img, updated, flashed su. i didn't flash boot though
Click to expand...
Click to collapse
same here. Now on 4.2.2 rooted.
I tried flashing boot.img but I cant seem to fastboot to device because of an unknown partition error. What to do??
swidnik0
You sir, are a gentleman. Thanks for you help.
Leif
Try this command to resolve partition issue
Leonhan said:
I tried flashing boot.img but I cant seem to fastboot to device because of an unknown partition error. What to do??
Click to expand...
Click to collapse
> fastboot flash system system.img
[email protected] said:
> fastboot flash system system.img
Click to expand...
Click to collapse
Oh there, spot on! Thanks man!
nextelbuddy said:
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Click to expand...
Click to collapse
Sorry for noon question
Any link for the guide ?
For flashing boot.IMG system.IMG
Sorry I have never done these things before
Sent from my Nexus 7 using Tapatalk HD
How/where to extract system.img and boot.img ??
rm79 said:
Thanks. That's exactly what I did... I decided to use the Nexus 7 Toolkit to just restore to stock (I was getting frustrated so I didn't care if it removed all my apps, etc). It turns out the toolkit lets you restore the stock image without wiping all of your apps/sd data so I was able to update and everything was great. Not rooted anymore, but I'll deal with that later .
Click to expand...
Click to collapse
How/where to extract system.img and boot.img ??
after I flashed 4.2.1 system and boot images
so after flashed system.img and boot.img i was able to upgrage 4.2.2 OTA but now my nexus is not rooted. so if im gonna root it again will i lose all my data and apps?
ashok_jeev said:
so after flashed system.img and boot.img i was able to upgrage 4.2.2 OTA but now my nexus is not rooted. so if im gonna root it again will i lose all my data and apps?
Click to expand...
Click to collapse
If your bootloader is already unlocked, then rooting it won't wipe your data.
DISCLAIMER:
What you do with Your Device is Your Responsibility!
I am not responsible for anything that happens to your device.
I'll try to help you solve the problem, if I can!
I wanted to change my XT1033 into GPe, and well procedure isn't that hard, but it required installing two firmwares one over the other that is
GB first and then selective flashing of GPe. And as i frequently change between GPE, GB, AsiaRetail. I made custom scripts for each one of them. I also Mixed the firmware of GPe and GB to make one single firmware which can be directly flashed over XT1033 using one single bat to convert GPe.
I am lending the major part of work from @ffosilva who in turn gives credit to @oldblue910 on thread
[FASTBOOT] Google Play Edition images (semi-official)
I know similar threads already exist, I am starting a new one with the aim of keeping the thread Noob-Friendly, And provide a single download to convert into GPe. I am also adding the package to change the Unlocked bootloader logo to GPe version. and providing a bat script to make it easier for newbies!Downloads
You can download the Mixed-Firmware From:
1.Here (GDrive)
2.Here (progammingnerds.com) by @tanmay190
Mirrors Needed!
Pre-Requisite: Installed Motorola Drivers.
Instructions:
Download the Package and Extract it to a folder
Reboot the phone into Bootloader (Power+VolumeDown).
Double Click XT1033_to_GPe.bat to begin
OR
Run Following commands from the Command Prompt after cd-ing to the folder, one by one
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg_intl.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot erase cache
mfastboot erase userdata
Reboot into system to be booted into GPe version.
And there you have it the XT1033 converted to Moto G GPe.
Quick Useful Links/Tips:
CWM for GPe
Philz Recovery for GPe
Command to flash a recovery "fastboot flash recovery filename.img" (without quotes) where filename.img is the filename (It has to be in the same folder) of the recovery image that you are flashing. To go back to stock recovery you can find the recovery.img from the download package above and flash using the same command!
If you use CWM/Philz, when you exit the recovery while phone is unrooted, It will ask you that your phone is not rooted, Install su? You c5. an select yes to root your phone. and later install SuperSU from Play Store.
SuperSU flashable zip if you Think flashing SuperSU directly is better! I find the above method a lot faster!
If anything goes wrong, Use This Guide to Get Back to Stock
[Stock][Firmware Package][XT1033] Asia Retail - Alt. Link [4.4.2][Lock Bootloader]
Any Mirrors to Download Links are welcome.
Hit Thanks if it helps!
Thanks. What is the purpose of fsg partition?
Sent from my XT1033 using Tapatalk
Dual SIM?
Sent from my Moto G using XDA Free mobile app
I dont know, do you know if it is related to dualsim? Lets say we converted a xt1033 into gpe with this and get one sim working. Can we flash stock based xt1032 custom roms on this gpe rom ? Gpe roms use ext4 filesystem whereas motorola roms use f2fs.
Lets say I want to keep f2fs file system and get one sim working with stock based xt1032 custom roms. What should i do ?
Sent from my XT1033 using Tapatalk
Convert it to GB
Semseddin said:
I dont know, do you know if it is related to dualsim? Lets say we converted a xt1033 into gpe with this and get one sim working. Can we flash stock based xt1032 custom roms on this gpe rom ? Gpe roms use ext4 filesystem whereas motorola roms use f2fs.
Lets say I want to keep f2fs file system and get one sim working with stock based xt1032 custom roms. What should i do ?
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Flash a full GB firmware, you will get a single sim working! and you will also have a f2fs!
I could install this rom but recovery does not recognize the sd card.
I can't install any thing.
How can I fix this problem?
i don't know if it's just my mobile , but when i use single sim rom ( i mean xt1032/gpe rom ) audio in real racing 3 and nfs most wanted gets laggy , and sometimes audio repeat itself for every 3-4 seconds . gameloft games are fine tho . i tried replacing xt1032's "audio.primary.msm8226.so"
file with xt1032's "audio.primary.msm8226.so" but i lost sound completely .
Well
mobilephone01 said:
I could install this rom but recovery does not recognize the sd card.
I can't install any thing.
How can I fix this problem?
Click to expand...
Click to collapse
flash latest philz recovery or flash gpe specific recovery,anyway you'll get encryption error on custom roms
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe
rr46000 said:
flash latest philz recovery or flash gpe specific recovery,anyway you'll get encryption error on custom roms
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe
Click to expand...
Click to collapse
I'm using latest philz recover.
If the same thing happen when I install the custom rom. I'll wait till you fix this problem.
Thank you.
Changed the method, Foolproof this time!
mobilephone01 said:
I'm using latest philz recover.
If the same thing happen when I install the custom rom. I'll wait till you fix this problem.
Thank you.
Click to expand...
Click to collapse
Changed the method, Foolproof this time!
Sorry had to change the files in downloads as well!
I found another thread with a similar concept but a better implementation, I am borrowing the files from them and just adding a couple things!
But it should work now!
And again, I already did this here.
thelegendofzeth said:
And again, I already did this here.
Click to expand...
Click to collapse
And again two people said they didnt understand!
I wrote in description the aim is to make it noob friendly!
And its not like your original work! I'd probably take that comment from @ffosilva
mfastboot.exe crash and can't install. Please fix it.
mobilephone01 said:
mfastboot.exe crash and can't install. Please fix it.
Click to expand...
Click to collapse
Right on it!
EDIT: Crash fixed, it was a command issued when bootloader was offline, ideally it should've waited, but i dont know whats wrong. I paused the script for a while It is working fine now!
Download the mfastboot+logo_bin.zip again!
mfastboot does not crash but still does not work.
Maybe not install all GPe file? Finishes very quick and still remain previous rom.
Do I have to download GPe file?
mobilephone01 said:
mfastboot does not crash but still does not work.
Maybe not install all GPe file? Finishes very quick and still remain previous rom.
Do I have to download GPe file?
Click to expand...
Click to collapse
You have to download two files! 1. Mixed-Firmware 2.mfastboot+logo_bin.zip
deej_roamer said:
You have to download two files! 1. Mixed-Firmware 2.mfastboot+logo_bin.zip
Click to expand...
Click to collapse
You changed the both files?
mobilephone01 said:
You changed the both files?
Click to expand...
Click to collapse
The first file was fine! There was no fault with the firmware. It was a scripting problem on my side, I've changed only the script
deej_roamer said:
Right on it!
EDIT: Crash fixed, it was a command issued when bootloader was offline, ideally it should've waited, but i dont know whats wrong. I paused the script for a while It is working fine now!
Download the mfastboot+logo_bin.zip again!
Click to expand...
Click to collapse
On some systems mfastboot crashes after the reboot command The best work around is to add "mfastboot continue" after the reboot command in the bat script
deej_roamer said:
The first file was fine! There was no fault with the firmware. It was a scripting problem on my side, I've changed only the script
Click to expand...
Click to collapse
I could not install. It was finished 1 second for install after click XT1033_to_GPe.bat. Is it normal?
Booting previous rom. Nothing changed.
Hi i just received the announcement that 22.26.1.en.de is ready to install.
I´m currently on official 21.11.14 ret.de
So, check your phones, should be availabale for all now !
:good:
Here is a link to OTA file.
http://www.filefactory.com/file/4ky9luc6apeb/ota.zip
Update with unlocked Bootloader
Hi everybody,
I've got an error message. How do i update with an unlocked and rooted Phone?
dpdp73 said:
Here is a link to OTA file.
http://www.filefactory.com/file/4ky9luc6apeb/ota.zip
Click to expand...
Click to collapse
retde 5.0.2 ota.zipmirror of 385mb OTA retde zip
Same here. 21.11.14 retde. Can't wait to get home to update. Finally!
Sent from my XT1068 using XDA Free mobile app
minifamilie said:
Hi everybody,
I've got an error message. How do i update with an unlocked and rooted Phone?
Click to expand...
Click to collapse
You have to restore any changes to /system, use unroot option in SuperSU and reflash stock recovery.
dpdp73 said:
You have to restore any changes to /system, use unroot option in SuperSU and reflash stock recovery.
Click to expand...
Click to collapse
I'm in the same boat. I can restore a backup to revert my /system (mostly, I think I only have to remove su afterwards), but could you link the stock recovery?
TheCreat said:
I'm in the same boat. I can restore a backup to revert my /system (mostly, I think I only have to remove su afterwards), but could you link the stock recovery?
Click to expand...
Click to collapse
Recovery depends on your system, search for your specific firmware and there will be file recovery.img inside, then just "fastboot flash recovery recovery.img".
TheCreat said:
I'm in the same boat. I can restore a backup to revert my /system (mostly, I think I only have to remove su afterwards), but could you link the stock recovery?
Click to expand...
Click to collapse
stock DE 4.4.4 in my signature
reefuge said:
stock DE 4.4.4 in my signature
Click to expand...
Click to collapse
Well, thank you (both) very much. Downloading/installing now...
TheCreat said:
Well, thank you (both) very much. Downloading/installing now...
Click to expand...
Click to collapse
Were you successful???
minifamilie said:
Were you successful???
Click to expand...
Click to collapse
Unfortunately, no. While the update seemed to complete, the system wouldn't boot afterwards: I got a "No Command" error whenevery I tried to boot. This was shown on a recovery-screen with the android bot in the middle (similar to the screen you see while the update is applied).
I'm now trying to reflash most things (but not wiping my data just yet), including /system, but unfortunately the update has to be downloaded again and it's rather slow...
If that doesn't work either, I'll have to do a full return-to-stock with a complete wipe, but I'd rather not...
With the second attempt the update finally worked fine. Booting obviously takes ages the first time, but afterwards it was fine.
I can recommend to just re-flash the important partitions instead of manually trying to restore the stock state. What I did and what worked was the following (using files for RETDEALL_XT1068_4.4.4_KXB21.85-14_Easy_Installer, linked in the signature of reefuge on the first page of this thread):
Code:
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe erase cache
Notably, I didn't wipe (except cache of course), flash the partitions or the modem
TheCreat said:
With the second attempt the update finally worked fine. Booting obviously takes ages the first time, but afterwards it was fine.
I can recommend to just re-flash the important partitions instead of manually trying to restore the stock state. What I did and what worked was the following (using files for RETDEALL_XT1068_4.4.4_KXB21.85-14_Easy_Installer, linked in the signature of reefuge on the first page of this thread):
Code:
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe erase cache
Notably, I didn't wipe (except cache of course), flash the partitions or the modem
Click to expand...
Click to collapse
If i understood right, your data wasn't wiped, right?!
minifamilie said:
If i understood right, your data wasn't wiped, right?!
Click to expand...
Click to collapse
Yes exactly.
Unrelated: I don't know to what exactly this is related (Rom? version?), but it seems the lollipop version of XPosed doesn't work on this ROM, it bootloops when installed...
Xposed for lolipoop is in alpha, it still doesn't work on many roms and devices.
But your bootloop rescued me from trying
Sent from my XT1068 using XDA Free mobile app
Change from global Version to retde?
Has anyone tried to change from the global version (Indian rom) to the German version?
I had mine bought on kitkat as German retail and then changed to global rom from India to go to Lollipop.
Any way to change back to German retde?
MrIngenieur said:
Has anyone tried to change from the global version (Indian rom) to the German version?
I had mine bought on kitkat as German retail and then changed to global rom from India to go to Lollipop.
Any way to change back to German retde?
Click to expand...
Click to collapse
Yes in my signature use the DE version (4.4.4) then OTA update to DE lollipop
But im already on lollipop not 4.4.4..
So change should be from 5.02 global india to 5.02 retde german... Any idea?
Sent from my XT1068 using XDA Free mobile app
MrIngenieur said:
But im already on lollipop not 4.4.4..
So change should be from 5.02 global india to 5.02 retde german... Any idea?
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
NO Full german (DE) 5.0.2 firmware available yet , so must downgrade to 4.4.4 de and then ota to 5.0.2 DE lollipop
DO NOT RESTORE BACK TO 4.4. THIS WILL BRICK YOUR PHONE.
--UPDATE--
JUST FLASH THIS! (In stock recovery) https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view
--
(if the above doesn't work, or if you are not on totally stock, use the following method)
Here is how to upgrade from 23.11.14 to 23.16.3
What you need: https://yadi.sk/d/cBaKACE7hQH9Y (upgrade from stock 5.0 to 23.16.3)
http://www.graffixnyc.com/motox.php (stock 5.0 image. You need to use this one. The one found in Motorola's site WILL NOT WORK WITH THIS METHOD)
Unzip the stock 5.0 image
Boot into fastboot
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Boot into recovery
adb sideload Blur_Version.22.21.11.victara_tmo.tmo.en.US.zip
reboot!
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Grzesiek1010 said:
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Click to expand...
Click to collapse
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
bongostl said:
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
Click to expand...
Click to collapse
ok but what with all apps data setting ?
Grzesiek1010 said:
ok but what with all apps data setting ?
Click to expand...
Click to collapse
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
bongostl said:
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
Click to expand...
Click to collapse
better wait for official update too much risk lost data ...
I successfully downgraded to 5.0, and I've attempted the sideload method twice and failed. Each time it says there is an error in the package, status 7. I get the same result when I apply update from sd card. Any ideas?
---------- Post added at 12:25 PM ---------- Previous post was at 11:43 AM ----------
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Use the files I posted.... That's what I used
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
leffer said:
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
Click to expand...
Click to collapse
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
sivarticus85 said:
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
Click to expand...
Click to collapse
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
leffer said:
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
Click to expand...
Click to collapse
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Success!
Stanleywinthrop said:
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Click to expand...
Click to collapse
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
thenestor said:
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
thanks for your help. I tried to download from your link and for some reason the file will not extract. However, I noticed that your image file is named exactly as the image file linked in the OP to this thread. Are they one in the same?
sivarticus85 said:
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Click to expand...
Click to collapse
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
thenestor said:
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
Good catch! I have fixed the original post
Stanleywinthrop said:
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
Click to expand...
Click to collapse
I've updated the original post to make this clearer.
anyone able to root this new OTA?
CF auto root was working on every previous OTA from 4.4 to 5.0 and 5.1 but now causes boot loops. I am able to TWRP back to the unrooted build to get me out of the bootloops.
leffer said:
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
Click to expand...
Click to collapse
Thanks! And no, the name is normal. The OTA filename always states the version you need to be on to install it, not the version that it contains.
I just recieved my Moto X pure/style today in the mail and opened the box and let the update install. After the installation I then unlocked the bootloader, flashed the correct logo.bin so I wouldn't have the unlocked bootloader crap, flashed twrp 2.8.7.0. Once I installed twrp I used the option to stay read only so I could get a backup with an unmodified system partion. I did the backup and then rebooted and downloaded the correct supersu by chainfire thanks by the way chain-fire! Then went on to root my device so I did that and then rebooted again. I downloaded a aosp 5.1.1 custom rom keep in mind I changed twrp from read only so I could modify the system. Rebooted and flashed the rom and everything seemed fine but when I rebooted it kept rebooting the the Motorola emblem. I thought maybe it was the rom but I downloaded one more and the same thing. So can you not install a 5.1.1 rom after you do the official 6.0 update? I guess the system partitions are not the same? It would be nice if someone can help me succeed doing this if there is a way. Thanks!
I miss the part where you whipe? And.....Shouldn't this be in Q&A?
ibila said:
I miss the part where you whipe? And.....Shouldn't this be in Q&A?
Click to expand...
Click to collapse
Of course I did the wipe. I did the advanced wipe and wiped the cache, dalvic cache, system, and data and it has been moved. Sorry about that. So do you know what the problem could be
jlbuck6212 said:
Of course I did the wipe. I did the advanced wipe and wiped the cache, dalvic cache, system, and data and it has been moved. Sorry about that. So do you know what the problem could be
Click to expand...
Click to collapse
You have to flash the Lollipop modem (NON-HLOS.bin) from the Lollipop SBF. Make sure you have the lollipop modem and kernel. If in doubt, use the return to stock tool and manually flash the LP modem. This should do the trick.
The lollipop modem isn't compatible with MM, and the MM modem isn't compatible with LP.
jlbuck6212 said:
Then went on to root my device so I did that and then rebooted again. I downloaded a aosp 5.1.1 custom rom keep in mind I changed twrp from read only so I could modify the system.
Click to expand...
Click to collapse
How did you go about making TWRP read write again? I chose to make it read only so I could go the systemless root method and TWRP does not give me the window to allow /system modifications, no matter whether I reflash or just boot it up.
Also, won't mounting TWRP the way you did create a bootloop because the stock recovery fights with TWRP when flashing?
EVR_PR said:
How did you go about making TWRP read write again? I chose to make it read only so I could go the systemless root method and TWRP does not give me the window to allow /system modifications, no matter whether I reflash or just boot it up.
Also, won't mounting TWRP the way you did create a bootloop because the stock recovery fights with TWRP when flashing?
Click to expand...
Click to collapse
Go into the mount tab and at the bottom uncheck where it says read only
samwathegreat said:
You have to flash the Lollipop modem (NON-HLOS.bin) from the Lollipop SBF. Make sure you have the lollipop modem and kernel. If in doubt, use the return to stock tool and manually flash the LP modem. This should do the trick.
The lollipop modem isn't compatible with MM, and the MM modem isn't compatible with LP.
Click to expand...
Click to collapse
Awesome I appreciate that. I figured it had something to do with that but what do you mean by flash it through lollipop sbf? Also you say make sure i have the stock kernel for lollipop. Why when I'm flashing a custom rom?
jlbuck6212 said:
Awesome I appreciate that. I figured it had something to do with that but what do you mean by flash it through lollipop sbf? Also you say make sure i have the stock kernel for lollipop. Why when I'm flashing a custom rom?
Click to expand...
Click to collapse
Perhaps I should have been more clear. You can find the lollipop SBF (full return to stock file) here: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view?usp=sharing
You can use RSD Lite, Return to Stock tool, or manual method to flash back to stock 5.1.1
Once flashed back to full stock, flash TWRP and install your custom ROM. It should work properly after this.
Since your custom ROM already includes /system, probably the easiest/fastest way assuming you have the SDK platform-tools installed is:
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash recovery TWRPfilename.bin
fastboot reboot-bootloader
boot into TWRP recovery. Flash your custom ROM. Reboot. Enjoy.
samwathegreat said:
Perhaps I should have been more clear. You can find the lollipop SBF (full return to stock file) here: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view?usp=sharing
You can use RSD Lite, Return to Stock tool, or manual method to flash back to stock 5.1.1
Once flashed back to full stock, flash TWRP and install your custom ROM. It should work properly after this.
Since your custom ROM already includes /system, probably the easiest/fastest way assuming you have the SDK platform-tools installed is:
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash recovery TWRPfilename.bin
fastboot reboot-bootloader
boot into TWRP recovery. Flash your custom ROM. Reboot. Enjoy.
Click to expand...
Click to collapse
I really appreciate that! Thank you! It's been driving me crazy lol. I'll make it happen