Database Users

Leakers about the OTA

If you are a leaker, please follow this tutorial when updating to the OTA. Get us the url to the OTA zip please.
Code:
If you are interested in looking at the process that HTC/Verizon uses for the OTA updates, you can get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/desirec-ota-104882.7b1e5cca.zip !!!
Then, take the name of the file and paste it on the end of android.clients.google.com/updates/partner, for instance, for the Eris 1.17.605.1 OTA, the complete url is:
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
bftb0

i would, but i have no idea what any of that means :|

Im assuming either Linux or MS Command prompt?
Thats where you would enter the code correct?
Point the code to the device, then begin the update as usual?
EX:
$ cd /path/to/phone/
$ adb logcat > logcat-accept.txt
Or am I off here...
I have no update as of yet, but would love to help.

?
It just says
adb: permission denied
is this for leak or root?

McZimi said:
It just says
adb: permission denied
is this for leak or root?
Click to expand...
Click to collapse
Did you go to your sdk tools dir first? This should be for ANYONE who receives the OTA update.

jearl75 said:
Did you go to your sdk tools dir first? This should be for ANYONE who receives the OTA update.
Click to expand...
Click to collapse
Yeah heres what i did on CMD
cd c:\AndroidSDK\tools\
adb shell
adb logcat > logcat_accept.txt

Did you go to your sdk tools dir first? This should be for ANYONE who receives the OTA update.
Click to expand...
Click to collapse
Yeah heres what i did on CMD
cd c:\AndroidSDK\tools\
adb shell
adb logcat > logcat_accept.txt
Click to expand...
Click to collapse
it may be different for me but my tools dir is at c:\Windows\androidsdk\android-sdk-windows\tools
don't know if its different for you though like I said
Sent from my Eris using the XDA mobile application powered by Tapatalk

WalkingTaco said:
it may be different for me but my tools dir is at c:\Windows\androidsdk\android-sdk-windows\tools
don't know if its different for you though like I said
Sent from my Eris using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
yeah mine is different. When i put the folder in my harddrive i played around with some of the names and what not.
as far as getting URL goes, i think a rooted user might be able to get it no problem.

McZimi said:
Yeah heres what i did on CMD
cd c:\AndroidSDK\tools\
adb shell
adb logcat > logcat_accept.txt
Click to expand...
Click to collapse
If you type adb shell, it will emulate a shell on the phone. Skip that step. Just type
Code:
adb logcat > logcat_accept.txt
and it should start dumping to a file called logcat_accept.txt.

somebody needs to post a step by step how to with complete details so some of us rookies can do this
with what tools and where to get the tools

jdog94 said:
somebody needs to post a step by step how to with complete details so some of us rookies can do this
with what tools and where to get the tools
Click to expand...
Click to collapse
You can find everything he mentioned with a quick google search.

turboguy said:
If you type adb shell, it will emulate a shell on the phone. Skip that step. Just type
Code:
adb logcat > logcat_accept.txt
and it should start dumping to a file called logcat_accept.txt.
Click to expand...
Click to collapse
Thanks for the help. This worked and now im just waiting for it to stop. its been quite a few minutes

LOL too true, OK
Google "android sdk" you should be asked to agree to the licence, then on to dl the installer needed.
And once installed go to the tools folder in your android-sdk folder open a command prompt in the folder. I know Linux enough, Can't remember how to so that in windows sorry.
-------------------------------------
Sent via the XDA Tapatalk App

McZimi said:
Thanks for the help. This worked and now im just waiting for it to stop. its been quite a few minutes
Click to expand...
Click to collapse
It won't stop unless either you stop it, or the phone reboots. If your int the process of getting the OTA, it will reboot when ready

LOL walkingtaco, you beat me there with an even simpler reply.
-------------------------------------
Sent via the XDA Tapatalk App

McZimi said:
yeah mine is different. When i put the folder in my harddrive i played around with some of the names and what not.
as far as getting URL goes, i think a rooted user might be able to get it no problem.
Click to expand...
Click to collapse
I may be way off here but most rooted users won't be able to/won't want to get the update as either a.) The SystemUpdate.apk has been removed from most root roms or b.) they wont want to accept the update as it will remove their root. This should be for leak users only. I think you will need to have gotten the update, run the logcat and then accept the update and capture the update process. Then the devs can use the url to also obtain the update and test it for exploits/vulnerabilities.

jcase said:
It won't stop unless either you stop it, or the phone reboots. If your int the process of getting the OTA, it will reboot when ready
Click to expand...
Click to collapse
So im assuming that i wont get a link unless im actually getting the OTA to begin with?

jcase said:
If you are a leaker, please follow this tutorial when updating to the OTA. Get us the url to the OTA zip please.
Code:
If you are interested in looking at the process that HTC/Verizon uses for the OTA updates, you can get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/desirec-ota-104882.7b1e5cca.zip !!!
Then, take the name of the file and paste it on the end of android.clients.google.com/updates/partner, for instance, for the Eris 1.17.605.1 OTA, the complete url is:
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
bftb0
Click to expand...
Click to collapse
No dice for leak v3 users
I/CheckinService( 85): Sending checkin request (1433 bytes)...
I/CheckinService( 85): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
D/htcCheckinService( 85): Receive cancel Intent, but not by htc
I/CheckinService( 85): Checkin success
W/GoogleHttpClient( 85): Blocked by block_crash_reports: http://android.clients.google.com/crash
I/CheckinService( 85): Crash report blocked
Someone who has 1.5 or 2.1v1 or 2.1v2 please try... now i wish i didn't update to leak 3 last week

nemish13 said:
No dice for leak v3 users
I/CheckinService( 85): Sending checkin request (1433 bytes)...
I/CheckinService( 85): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
D/htcCheckinService( 85): Receive cancel Intent, but not by htc
I/CheckinService( 85): Checkin success
W/GoogleHttpClient( 85): Blocked by block_crash_reports: http://android.clients.google.com/crash
I/CheckinService( 85): Crash report blocked
Someone who has 1.5 or 2.1v1 or 2.1v2 please try... now i wish i didn't update to leak 3 last week
Click to expand...
Click to collapse
You can try downgrading to 2.1v2 (they have the same bootloader, so it might work), but I doubt it's worth it.

hmm
well hopefully the v3 people still receive an update. if not, someone needs to hurry up with a link

If you get an update notification, READ THIS before you do anything

Shamelessly stolen from another forum, editing is mine.
If someone gets the update, can you please do this before you accept it. and post the logcat.txt? Please this may help rooting.
How to get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
Code:
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
Code:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/
You should see a link in the file like
Code:
https://android.clients.google.com/u.../partner/*****
Click to expand...
Click to collapse

indeed, also for a good file manager to pull the zip, use estrongs its free lets you browse / just cant write to it (which isnt what we are looking to do)

great info. I remember seeing this process posted way back when, thanks for the refresher.

What if you have a mac though, w/o any boot camp either?

[Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures

I see so many having problems trying to get S-off on the 1.55 HBoot. Some have had none but I've posted this response so many times I thought I'd make my own post and hopefully people's searches will direct them here and it helps them.
I am no developer or coder or anything but a techno junkie. I have no linux experience except what I've taught myself so be sure if this 47 year old, self taught mother can do this then anyone can.
Just take your time, pay attention to what you're doing, and read everything before you hit go.
I had no luck with rumrunner on Windows 7 or Windows 8/8.1. Drivers were never right. Couldn't get rid of HTC one sync. So I finally got myself
(1) a copy of 32bit Ubuntu. NOT 64!! http://www.ubuntu.com/download/desktop
(2) no need to install-boot into it as if trying it (IMAGE 3)
(3) grab rumrunner for Ubuntu (linux) http://rumrunner.us/
(4) drivers NOT needed
(5) turn off fastboot (IMAGE 2) You should also turn off any lockscreen security....
(6) turn on USB debugging in development settings (IMAGE 1) You should also turn off any lockscreen securtiy
(7) run rumrunner (instructions are on the rumrunner site) paying attention in case extra permissions are required by superuser http://rumrunner.us/instructions/ (See Ubuntu section below)
(8) sat back and watched the magic. Worked the first time.
I know others have had zero issues but some of us have had nothing but nightmares. This is who I'm sharing this for.
I hope it helps... Even just one!
Have fun all!
IF BY CHANCE YOU ARE HAVING ISSUES WITH ADB OR FASTBOOT IN UBUNTU SEEING YOUR DEVICE, TYPE sudo BEFORE YOUR COMMANDS. IT WANTS PERMISSION TO ACCEPT YOUR COMMANDS. WHEN YOU TYPE sudo THEN YOUR PASSWORD YOU ARE GRANTING THOSE PERMISSIONS. SOMETIMES THE ISSUE WON'T APPEAR TIL YOU GET INTO FASTBOOT. SO CHECK FIRST BY TYPING IN adb devices WHEN YOU FIRST OPEN THE TERMINAL. IF YOU GET A SERIAL NUMBER YOU SHOULD BE FINE. AFTER YOU GET INTO BOOTLOADER, TYPE fastboot devices IF YOU GET A "no permission" ERROR THEN YOU NEED TO TYPE sudo BEFORE all INSTRUCTIONS. SOME VERSIONS OF LINUX HAVE AN SU TERMINAL. THAT WOULD BE THE BEST TO USE AS IT REQUIRES ROOT/PERMISSION TO EVEN START AND WILL MAINTAIN THOSE PERMISSIONS THROUGHOUT.​
UBUNTU STEPS.....
Image 3- Boot into Ubuntu
Image 4- Download Linux version of rumrunner
Image 5- Extract Rumrunner (Right click on the zip and select extract here...I left it in the Downloads folder)
Image 6- Inside the extracted Rumrunner file
Image 7- Open Terminal in Ubuntu (Top left gear like symbol, click it and a search bar will appear, start typing terminal, it will appear below the bar, just select it)
Image 8- You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Image 9-12 Shows how the terminal should look as it finds, downloads and install the appropriate files.
Image 13- After the downloads are finish you can check to make sure things were installed correctly. Type “adb” and your screen should look like this
Image 14- Type “fastboot” and this is the information that should appear.
Image 15- To make sure your device is seen type “adb devices” and it should show devices with a serial number.
Image 16- Now make your way in the terminal to your downloads folder and into the rumrunner folder by typing the following BOLDED commands in the terminal
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ cd rumrunner_HTC_0.5.0
[email protected]:~/Downloads/rumrunner_HTC_0.5.0$
(This line simply indicates you are in the rumrunner folder)
Image 17- Now you need to run the command to get the party started...it is in bold
[email protected]:~/Downloads/rumrunner_HTC_0.5.0$ sudo ./soju
Image 18- Confirm you understand what it is you're doing or at the very least you are willing and accept the risks by typing “Yes”. It must be “Yes”. It will not accept yes, y, ok or anything else. The Y must be a captial.
Image 19- After you type Yes the second time things get under way. Be patient. It may take a bit of time. Just pay attention in case you are asked for extra permissions.
Image 20- S-Off verification
After the second Yes rumrunner does it's stuff...it can take a while. Be patient. Pay attention in case you need to give permission. DO NOT DISCONNECT YOUR PHONE until you either get the ok or are told it failed.
This is as clear as I can be and I hope it makes it even easier....
Suggested by @chp , you may need to go into software centre (selected by opening the search bar again and typing software centre), edit tab, software resources and making sure that "Community-maintained free and open-source software (universe)" is selected.
ALSO, PLEASE GIVE CREDIT IF YOU USE THIS. FEEL FREE TO SHARE IT, JUST LET PEOPLE KNOW WHO ACTUALLY TOOK THE TIME TO CREATE IT. UNLIKE THIS PERSON... http://www.usofttech.com/t152630.html , WHO HAS EVEN TURNED OFF REGISTRATION SO I CAN'T EVEN MAKE IT KNOWN THERE.
THANK YOU!! ​

tobesedated said:
I see so many having problems trying to get S-off on the 1.55 HBoot.
Some have had none but I've posted this response so many times I thought I'd make my own post and hopefully people's searches will direct them here and it helps them.
I had no luck with rumrunner on Windows 7 or Windows 8/8.1. Drivers were never right. Couldn't get rid of HTC one sync. So I finally got myself
(1) a copy of 32bit Ubuntu. NOT 64!!
Click to expand...
Click to collapse
I like what your doing here
the instructions on the rumrunner site are very vague and it took me quit sometime just to figure those things out when you know very little about linux.

original post updated with more concise instructions and pictures.....the easiest way to show the steps i took​

Removed an extra picture that may have caused confusion

tobesedated said:
Removed an extra picture that may have caused confusion
Click to expand...
Click to collapse
nice work :good:
just a question, you didnt even need to install adb & fastboot?

nkk71 said:
nice work :good:
just a question, you didnt even need to install adb & fastboot?
Click to expand...
Click to collapse
OMG!! Yes I did...and now I shall update for that as well...Thank you so much for ponting that out

tobesedated said:
OMG!! Yes I did...and now I shall update for that as well...Thank you so much for ponting that out
Click to expand...
Click to collapse
Keep up the good work , and thanks for helping!!!
in case this helps save you some time:
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

nkk71 said:
Keep up the good work , and thanks for helping!!!
in case this helps save you some time:
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Awesome thanks and I just went through a partial run of rumrunner's so I could get the screenshots lol
And it's my pleasure

Op updated!!
Original post has been updated. Added instructions to download and install adb and fastboot in Ubuntu. More pics too LOL YAY!!
Good luck everyone...feel free to hit thanks if you get anything out of this​

[email protected]:~/Downloads/rumrunner_HTC_0.5.0$ sudo ./sujo
Click to expand...
Click to collapse
you have mistyped command, the right is: sudo ./soju

janda said:
you have mistyped command, the right is: sudo ./soju
Click to expand...
Click to collapse
Thank you for pointing that out... Correcting it now
Sent from my LG-D803 using xda app-developers app

Nice work on this guide and thanks for taking the time to write it up
By the way, I've moved this into General as it's more suited there and won't get buried within the forum quite as quickly
Regards,
- KidCarter93
Forum Moderator

KidCarter93 said:
Nice work on this guide and thanks for taking the time to write it up
By the way, I've moved this into General as it's more suited there and won't get buried within the forum quite as quickly
Regards,
- KidCarter93
Forum Moderator
Click to expand...
Click to collapse
Thank you... I wondered where it went lol
Sent from my LG-D803 using xda app-developers app

Fixed the incorrect soju command
Sent from my LG-D803 using xda app-developers app

how is this working on 64b ubuntu as im all ready rocking 13.10 on my laptop and dont want to reinstall just for this

skedone said:
how is this working on 64b ubuntu as im all ready rocking 13.10 on my laptop and dont want to reinstall just for this
Click to expand...
Click to collapse
You don't have to install... You select try from a disc. You can try on 64 but according to rumrunner site it isn't supported. Doesn't mean it won't work just that if it doesn't they can't help you
Sent from my LG-D803 using xda app-developers app

I just ran through this myself, after having no luck in Windows. One thing that's missing... you need to enable 'universe' in Software Center.
Open dash and type software center
On the Edit menu, select Software Sources and enable "Community-maintained free and open-source software (universe)"
Then, you'll be able to install the android tools.

chp said:
I just ran through this myself, after having no luck in Windows. One thing that's missing... you need to enable 'universe' in Software Center.
Open dash and type software center
On the Edit menu, select Software Sources and enable "Community-maintained free and open-source software (universe)"
Then, you'll be able to install the android tools.
Click to expand...
Click to collapse
Thanks for that in case anyone needs to do this... I didn't. I followed exactly as in my OP but this is a good to know in case someone runs into issues.
Sent from my LG-D803 using xda app-developers app

Original Post updated to include a suggestion by @chp ...thank you. And a little rant by me lol
Have a good one all!!​

chp said:
I just ran through this myself, after having no luck in Windows. One thing that's missing... you need to enable 'universe' in Software Center.
Open dash and type software center
On the Edit menu, select Software Sources and enable "Community-maintained free and open-source software (universe)"
Then, you'll be able to install the android tools.
Click to expand...
Click to collapse
tobesedated said:
Original Post updated to include a suggestion by @chp ...thank you. And a little rant by me lol
Have a good one all!!​
Click to expand...
Click to collapse
I think that's needed for 13.10 right? on 12.04 LTS, the other repository should work fine. (at least it does for me)
cheers

[PSA][Tutorial] How to Capture an OTA

You do not need to be rooted! Just have USB debugging enabled in developer options.
Please post the official URL of the OTA that you obtain from following these steps so that everyone can download it safely and securely.
Please do not rehost the OTA zipfile on some ad-laden scammy download hosting website.
Steps shamelessly stolen from http://www.droid-life.com/2014/06/05/download-nexus-ota-url-file/
As soon as you get the OTA notice:
1. When you get prompted to download an update on your phone immediately plug your phone into a computer.
2. From that computer, open a command prompt, type “adb logcat” and hit enter. (On a Mac it’s “./adb logcat”)
3. The command prompt will then begin to spit out information from your phone.
4. Feel free to then tap the “Download” button on the update from your phone.
5. Once the download starts, you will be able to find the URL of the file that is downloading in the logcat.
6. You can do a handful of things now to find it-
a) See if you can spot a URL in the command prompt that starts with “android.clients.google.com” – or -
b) Copy the logcat info, paste into a text editor and then search for that string – or -
C) You could also search for the codename for the device (Ex: Moto G 2014 is “titan”)
Once you have the full URL, post it on the forums!

Nice

Some corrections:
first links for Motorola OTA zips start from storage.googleapis.com. not android.clients like of Nexus
second if you use adb logcat only, there will be a lot of text generated which deletes the logs captured at beginning (in which our url is).
so use abd logcat>filename.txt
so that you can search whole log i.e.filename.txt in text editor
third it's not that simple "post the url in forum"
links of Motoroal OTA get expired immediately (Nexus links don't expire) so you have to download it first and again upload it somewhere.
so please at least try before you post
I know it was not possible to test for you.
Hope you will update OP with corrections.

bhavin192 said:
Some corrections:
first links for Motorola OTA zips start from storage.googleapis.com. not android.clients like of Nexus
second if you use adb logcat only, there will be a lot of text generated which deletes the logs captured at beginning (in which our url is).
so use abd logcat>filename.txt
so that you can search whole log i.e.filename.txt in text editor
third it's not that simple "post the url in forum"
links of Motoroal OTA get expired immediately (Nexus links don't expire) so you have to download it first and again upload it somewhere.
so please at least try before you post
I know it was not possible to test for you.
Hope you will update OP with corrections.
Click to expand...
Click to collapse
What do you mean with "immediately"? If I get the link while my phone is downloading the ota can I use the link to download it on my pc almost at the same time?

Nagass said:
What do you mean with "immediately"? If I get the link while my phone is downloading the ota can I use the link to download it on my pc almost at the same time?
Click to expand...
Click to collapse
Yes you can use it at that time

Great initiative.
A tutorial like that should have been fixed on these forums right from the beggining.
The OTA soak test for xt1069 was lost forever, for instance, because nobody who received the notification knew about this.

On the off-chance that you're using a linux based OS or Mac OS and want to make life even easier, use grep to filter the output and then print to file:
Code:
adb logcat | grep 'storage.googleapis.com' > ota.txt

Just used this method to grab the OTA for 5.0.1 without root! My recommendation is to do this:
adb logcat > log.txt
Search log.txt for handleDownloadServiceRequest:downloadUrl
Copy / Paste URL into browser
Search log.txt for "fileName":"\/cache\/
Rename file downloaded from URL to file name listed in the logcat
Upload to XDA for others to enjoy
---------- Post added at 07:57 AM ---------- Previous post was at 07:54 AM ----------
bhavin192 said:
Some corrections:
first links for Motorola OTA zips start from storage.googleapis.com. not android.clients like of Nexus
second if you use adb logcat only, there will be a lot of text generated which deletes the logs captured at beginning (in which our url is).
so use abd logcat>filename.txt
so that you can search whole log i.e.filename.txt in text editor
third it's not that simple "post the url in forum"
links of Motoroal OTA get expired immediately (Nexus links don't expire) so you have to download it first and again upload it somewhere.
so please at least try before you post
I know it was not possible to test for you.
Hope you will update OP with corrections.
Click to expand...
Click to collapse
BTW, this latest update came from https://dlmgr.gtm.svcmot.com as the root domain. The link did expire as soon as my device finished the update and checked in.

mcnutty said:
BTW, this latest update came from https://dlmgr.gtm.svcmot.com as the root domain. The link did expire as soon as my device finished the update and checked in.
Click to expand...
Click to collapse
Glad to hear you got success
May be different servers are used for different countries.

OTA update internal folder (Pie) and capturing OTA URL

I want to capture OTA update file.
The plan is to power down the device during OTA (when exactly?). Then, boot to TWRP and copy the FW update file. I looked up the OTA update file Blur*.zip , but could not find it
Which folder do look at?
I have also tried to capture OTA URL adb logcat > log.txt , but could not get working URL.
In the log file, I did see something like
Code:
downloadUrl = https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/5a695MmLWnZQIL7IPS5cD4nkj9%2FmlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky%2Fve7SfWcmRdeS8aXEqSgmHrq6dVou%2BSZiZPovBazKrFv%2FJoXkyH7iWsYR8xYS3OnEgEHCmVoZXEBUKY59HhFInaxCzVy0cBpVlJH1nkYcaGn4tEV1OcTQjLUHJm1jGxmqUAatFw%3D%3D
which decodes to
Code:
https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/5a695MmLWnZQIL7IPS5cD4nkj9/mlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN+vGu2j4xooz5Ky/ve7SfWcmRdeS8aXEqSgmHrq6dVou+SZiZPovBazKrFv/JoXkyH7iWsYR8xYS3OnEgEHCmVoZXEBUKY59HhFInaxCzVy0cBpVlJH1nkYcaGn4tEV1OcTQjLUHJm1jGxmqUAatFw==
but still without success
Un-rooted Pie with un-locked BL

You're getting close...
Here are the steps which worked for me:
1. open this file /data/data/com.motorola.ccc.ota/shared_prefs/dl_prefs.xml (it only appears after first update attempt)
2. after a few lines you can find s.th. like this for example:
Code:
<string name="downloadRequest">
{"downloadRequest":
{"contentResource":"
{\"proceed\":true,\"wifiUrl\
":\"https:\\\/\\\/dlmgr.gtm.svcmot
.com\\\/dl\\\/dlws\\\/1\\\
/download\\\/Ig7qWQDh9p68jhxIGs
L7D4nkj9%2FmlRBFuisKgbOUteZFGF0L
VIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky
%2Fve7SfZ5%2F7SIx tZe8aC%2BjQKdzC6g
u%2BSZiZPovBazKrFv%2FJoXktakuX
8J%2FXekJkTtRmbyNA59LsD0cJ%2F
PGoMafEslS1aOcnWbxMUaAS2gAna
GCZgerOcTQjLUHJm1jGxmqUAatFw
%3D%3D\",\&quot
3. copy the URL https://...= and delete all \ between the / before open it in your browser.
ATTENTION:
The URL is only valid while your system is attempting to update your device. If you cancel the (attempt to) update, the URL is not longer valid!

WoKoschekk said:
open this file /data/data/com.motorola.ccc.ota/shared_prefs/dl_prefs.xml
Click to expand...
Click to collapse
I think I will not be able to access this file on un-rooted phone unless I boot to TWRP.
WoKoschekk said:
The URL is only valid while your system is attempting to update your device. If you cancel the (attempt to) update, the URL is not longer valid!
Click to expand...
Click to collapse
if I power off my Wi-Fi router and then power off my phone, will the URL remain valid for a while?
Better yet, if I cancel the download and re-attempt it, say, in 15 min, will the the URL be different or the same?

Why do you need the OTA.zip when unrooted?

Try it this way:
While your device is running and attempting to update connect it to your PC and run following command:
Code:
adb logcat | grep dlmgr > log.txt
copy the URL shown in log.txt in any browser on your PC and download the ota.zip
Don't forget to erase the \ in the shown URL if necessary.

WoKoschekk said:
Code:
adb logcat | grep dlmgr > log.txt
Click to expand...
Click to collapse
Does it have to be a Linux PC?
On Windows PC, I am getting
'grep' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
Regardless, I found a download URL and downloaded "ab_delta-Blur_Version.29.291.8-29.321.13.evert.retail.en.US.zip" ( 148 MB), which updates to 116-11-11
Then, I found another URL and and downloaded "ab_delta-Blur_Version.29.321.13-29.351.21.evert.retail.en.US.zip" (86Mb), which updates to 116-11-13
II was not able to manually install the above Blurs until I re-lock the boot-loader.
So Moto becomes more and more picky and strict and not only root, but also unlocked BL and stock FW for non-matching channels is not tolerated
The download URL is present in both files:
/data/data/com.motorola.ccc.ota/shared_prefs/dl_prefs.xml
/data/data/com.motorola.ccc.ota/shared_prefs/ota_prefs.xml

To make things right:
The ota.zip contains only pieces/updates of your current FW. During the installation process the .zip overwrites targeted files of your significant partitions. If Motorola wouldn't proof these files to be stock, then the installation could lead into a bootloop or hard bricked device. Motorola's developers only know their own filestructure but not custom roms'. To avoid fatal failures of your device they have to check your system before doing any modifications. If it isn't stock then the installation will be cancelled.
BTW: There's no need to relock the bootloader. Running a stock FW meets the criteria to receive and to install a OTA update.