Database Develop

How do I remove the leaked update to get the "Official OTA"?

Im just wondering if the official update will work better than the leaked version.
My problems are BSOD issues. Still getting them about once every 3 days.

chay03 said:
Im just wondering if the official update will work better than the leaked version.
My problems are BSOD issues. Still getting them about once every 3 days.
Click to expand...
Click to collapse
I'm reading more and more that the leaked updates are really the OTA Updates. They will start soon rolling out the 5.5.893 OTA and then progress through the others and you must be bone stock for the update to install. But the 5.8.894 will install on everyone's phone without regard to kernel/radio versions.

Geezer Squid said:
But the 5.8.894 will install on everyone's phone without regard to kernel/radio versions.
Click to expand...
Click to collapse
This is 180 degrees contrary to what we found trying to flash the leaked 5.8.894.
So maybe moto/vzw will alter the flash procedure to install this over everything else that was leaked?
RMD

In another forum, a user stated he had talked to a supervisor of Motorola's Technical help dept. and was told that the official update path is going via 5.5.886 --> 5.7.893 --> 5.8.894 --> ICS, and that the incremental updates released OTA through VZW will not have the pre-qual checks like the latest 5.8.894 does.
Take that with a grain of salt, though. If you read his posts, you'll understand.

Geezer Squid said:
I'm reading more and more that the leaked updates are really the OTA Updates. They will start soon rolling out the 5.5.893 OTA and then progress through the others and you must be bone stock for the update to install. But the 5.8.894 will install on everyone's phone without regard to kernel/radio versions.
Click to expand...
Click to collapse
Nobody has actually checked the MD5 sums yet (to my knowledge) so there is no way of knowing if the leaks are indeed the same. They are the same download size, but that does not mean that the OTA doesn't have edits not found in the leak.
The only way to know is to compare the MD5 sums.

Umm, I have checked the MD5 sums. The OTA that is already rolling out to people as of yesterday is the same 5.5.893 that we got from cheesecake back in the end of Sept or early October, whenever it was. According to another poster (see my reply 2 posts above) the upgrade path is 5.5.886 (stock) --> 5.5.893 --> 5.7.893 --> 5.8.894 --> ICS.
The hashes for both files are:
CRC32: 0EF1BF2A
MD5: 066E3C2393AEECB963FC950013E42A76
SHA-1: 304A2B479C80DB56DCA1A0D1E906511914D89100
I was not the first to check, another user here already posted that the MD5 sums matched, so I checked the old file versus the new one that just got pushed and all three match.

johnlgalt said:
Umm, I have checked the MD5 sums. The OTA that is already rolling out to people as of yesterday is the same 5.5.893 that we got from cheesecake back in the end of Sept or early October, whenever it was. According to another poster (see my reply 2 posts above) the upgrade path is 5.5.886 (stock) --> 5.5.893 --> 5.7.893 --> 5.8.894 --> ICS.
The hashes for both files are:
CRC32: 0EF1BF2A
MD5: 066E3C2393AEECB963FC950013E42A76
SHA-1: 304A2B479C80DB56DCA1A0D1E906511914D89100
I was not the first to check, another user here already posted that the MD5 sums matched, so I checked the old file versus the new one that just got pushed and all three match.
Click to expand...
Click to collapse
Okay cool, as I said, TO MY KNOWLEDGE, no one had checked the MD5 sums yet.
So thats cool that they are indeed the same thing. Concerning what the other poster is saying about the upgrade path, I'd take that with a huge grain of salt. Remember the source of the information, a moto rep. Who aren't really any better than VZW reps when it comes to actually knowing what's going on.
Plus it's already been said by a moto rep that the next update we'll be seeing is the ICS upgrade. See what I mean?

So has anyone actually been able to go from the 5.7.893 leak to 5.8.894? I can't get any info on this....

rduckwor said:
This is 180 degrees contrary to what we found trying to flash the leaked 5.8.894.
So maybe moto/vzw will alter the flash procedure to install this over everything else that was leaked?
RMD
Click to expand...
Click to collapse
I would say not that the 5.5.893 OTA is out, the leaked 5.8.894 can't be the final OTA. Since it only installs over stock 5.5.886 (kernel/radio/system) it will not install over the "new" stock of 5.5.893 since kernel and radio were updated. So who knows what that 5.8.894 leak really was, maybe it was an alternative to the 5.5.893?

Character Zero said:
I would say not that the 5.5.893 OTA is out, the leaked 5.8.894 can't be the final OTA. Since it only installs over stock 5.5.886 (kernel/radio/system) it will not install over the "new" stock of 5.5.893 since kernel and radio were updated. So who knows what that 5.8.894 leak really was, maybe it was an alternative to the 5.5.893?
Click to expand...
Click to collapse
Over at rootzwiki DroidTh3ory says the MD5 for the 5.5 is the same as 5.8.894. I'd link it but I'm in my phone. It's post number 481 in his Kin3tx thread.
Sent from my DROID BIONIC using Tapatalk

I think he might have meant that the 5.5.893 OTA had the same MD5 as the 5.5.893 leak because the 8.894 has a different radio (.03) than the OTA (.01).

I just updated my phone from the official update. I was running the leaked version of 5.5.893. So I unrooted yesterday with f4rever root and now to day I got the update. Everything when fine

Character Zero said:
I think he might have meant that the 5.5.893 OTA had the same MD5 as the 5.5.893 leak because the 8.894 has a different radio (.03) than the OTA (.01).
Click to expand...
Click to collapse
yeah, I think you are right. I've read over and over that the MD5 of the official OTA was the same as the leak 5.5.893. I actually hope that is the case.

It is.
Hashes for both files (I still have the one I downloaded as a leak at the end of October) and I compared it with the file that someone on here (user Terri, from her son's phone, IIRC) posted in one of these threads.
CRC32: 0EF1BF2A
MD5: 066E3C2393AEECB963FC950013E42A76
SHA-1: 304A2B479C80DB56DCA1A0D1E906511914D89100
Screenshot to prove it (Yes, I know someone out there can say "It could be doctored, the file could be the same one and I just renamed it, changed the date, blah blah blah" - well, these are the hashes from the original leaked file, easily verified from posts made around the net when the file was first found and posted from cheesecake, and anyone who *has* gotten the update but not yet applied it can manually DL their file and compare the hashes).

anyone know why dhackers released method doesn't restore ZUmocast with a stock 2.1 version ?

ZumoCast is actually in a different tree from the system tree. The R3L34S3D does not do the preinstall tree. Is that actually causing issues for people if ZumoCast is not there??
From the Updater script in the OTA update:
assert(apply_patch_check("/preinstall/app/com.motorola.zumocast", "27c7d3ba9de38230042dbc000b7cccb59c2aafaa", "73415ce67779b079ad83942f417992b02fbf31b8"));
Click to expand...
Click to collapse
Everything else prior to that is actually checking in /system not in /preinstall.
IIRC, when all is said and done, ZumoCast is not considered a system app (at least no on my TiBu). Yeah, just checked, and ZumoCast is not in read, so it is not indicated at a System app, per se.

2nd OTA lollipop update failing

I recieved the first OTA update for lollipop and it installed correctly. Now I went to download the large 700+mb 2nd OTA update and after the download completes my phone resets. It goes into installing the update, however about 1/4 of the way through the update, i get the dead droid screen flash on my screen and then my phone reboots back to 4.4.4 and tells me that the updated was unsuccessful. I have a moto x XT1060 dev ed, build KXA21.12-L1.26-4 on system version 212.166.4.
I'm stumped on what to try next. I have already returned everything back to stock and downloaded all updates and I get to the same point and get the same results. I've wiped all data, system, cache, and davlik, installed stock recovery and still get the same results. i've removed super user rights to see if that would work but it did not. I'm at a lose at what to try next. Anyone have any other ideas?

[email protected] said:
I recieved the first OTA update for lollipop and it installed correctly. Now I went to download the large 700+mb 2nd OTA update and after the download completes my phone resets. It goes into installing the update, however about 1/4 of the way through the update, i get the dead droid screen flash on my screen and then my phone reboots back to 4.4.4 and tells me that the updated was unsuccessful. I have a moto x XT1060 dev ed, build KXA21.12-L1.26-4 on system version 212.166.4.
I'm stumped on what to try next. I have already returned everything back to stock and downloaded all updates and I get to the same point and get the same results. I've wiped all data, system, cache, and davlik, installed stock recovery and still get the same results. i've removed super user rights to see if that would work but it did not. I'm at a lose at what to try next. Anyone have any other ideas?
Click to expand...
Click to collapse
I was having this same problem, but here is the process I went through to get through the full update to 5.1:
I saw this post this morning and started with it: http://forum.xda-developers.com/moto-x/general/help-lollipop-update-unlocked-bootloader-t3201426 I had previously downloaded the version of 4.4.4 referenced in it.
I don't have RDSLite installed so I moved on to this post: http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and used Option #5 since I already the Android SDK tools on my computer. After going through all the steps I have successfully stepped through all three updates, rebooting the phone after each whether it helps or not. My phone is currently optimizing apps after the second 5.1 update.
For reference I was on the most current version of 4.4.4, rooted with TWRP with no modifications to any system/bloatware apps. I originally tried Option #6 in the above thread which allowed me to take the first 5.1 update but the second update failed in the same way you described.
Hope this helps, and good luck!

Thanks for the post. I was reading through that post late last night and I was going through option #2. I didn't read further down to option #5, but that worked perfectly. My phone is optimizing apps as we speak.

How to switch to correct update tree (to get OTA updates)?

(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.

lgmayka said:
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
Click to expand...
Click to collapse
Any reason not to use a Google Factory image? It looks like MMB29V is the most recent.

According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer. As I mentioned, joining the Android Beta program actually seems to be the easiest solution, if the current beta (NPD30G) is stable enough.
Frankly, I am surprised that Google/Motorola/AT&T (or any cell phone designer/manufacturer/carrier) allows a working cell phone to get into this state where the phone refuses to accept security updates.

For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.

That's half the fun of owning a Nexus, not waiting for updates. Dl the factory image, unzip it and the zip file inside and flash the system. IMG only and you'll lose nothing but root. If, of course, you are rooted.

http://forum.xda-developers.com/showthread.php?p=59561445/ You may give it a try..... prerooted lite stock rom.

lgmayka said:
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer.
Click to expand...
Click to collapse
As already suggested, just install the system image. The simplest way to do that is via fastboot. Nothing gets erased unless you flash the userdata.img. Using Google's script to flash everything would overwrite the userdata partition.
The version you are on (MMB) is released to provide updates without updating the radio. The MOB release is the same as the equivalent MMB plus the package includes the updated radio. This is a requirement of the carriers who want to approve the radio before it's released.
You will be unable to take any *incremental* OTA if there is any differential between what's on your system partition and what the OTA is expecting. You can not hop over incremental OTA updates. They must be sequentially applied. Therefore, the safest way to get to a known state is with a factory image.
If fastbooting a factory image is unacceptably risky, then maybe an eBay phone wasn't a great choice.
Or, as you say, you go straight to N. If the beta program is still available now that N is released.

stevemw said:
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
Click to expand...
Click to collapse
I decided to do this. NPD90G is running well enough for me, and before long Google will release Android 7.0 Final.

[HOW TO] Return to stock

Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips

Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.

If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.

Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy

Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!

full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!

esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.

NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE

WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.

Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP

when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?

cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.

moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from

irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip

So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?

How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.

Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.

robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.

A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.

hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this

CC /w GTV (Sabrina) NEW OTA & Factory Image Dump

Previous version: https://forum.xda-developers.com/t/chromecast-with-googletv-sabrina-ota-dump.4178163/
This time when I went to pull the new OTA, I also discovered what I believe is the full factory image too
New OTA: https://drive.google.com/file/d/1zAAPbymAO1Mxb_g0w8YMfDo240ROdxgG/view?usp=sharing
Full Factory: https://drive.google.com/file/d/1ZSoR7U9gjJW8yFlh_Fxv0kZs6BUe9olX/view?usp=sharing
Kernel Version: 4.9.180
Anroid TV OS Build: QTS2.200918.015.6966301

great find, how do you usually pull the images?

micallan_17 said:
great find, how do you usually pull the images?
Click to expand...
Click to collapse
I just look at the logs while I'm updating. There's an ota url that gets set right before an update happens, and then right after it happens it gets nulled during the first boot.
Usually it's just an ota with a partial update. Around 60MB or so. For whatever reason I looked at the logs before I went to update this time and noticed the url was set - so I downloaded it and discovered it was much much larger so I grabbed it. When I went to go do a system update though it changed to a smaller ota, and I grabbed that one too.

thank you very much for the explanation, definitely very helpful info.

I don't think it's useful right now, but i've successful dumped the full factory image thar you sent
Here the link of the dump
Files · sabrina_prod_stable-user-10-QTS2.200918.015-6966301-release-keys · Giovanni Ricca / dumpyara
git.rip
git.rip

oh wow awesome find, i am going to try and get this to boot on my s905x device a port should be possible as i have done on s905x, s905w and s912 and the mi box s firmware

Hello guys.
Another user and I are experiencing issues updating our brand new Chromecast with GTV as seen in this thread: https://forum.xda-developers.com/t/chromecast-with-gtv-update-recovery-error.4274509/
My device comes with build QTS1.200625.002.A5.6686931
I guess the OTA that it is downloading is having a hard time updating from a build that is so old?
Do you think there's a way I can flash the full factory image posted by OP?
I think, by doing that, the device could then update to latest (April 2021) version.
Could that be a solution?
Do you have any other ideas?