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

Marshmallow here for xt1095

I just got a notification for the update an hour ago. Installed it and seems to be fine
Sent from my XT1095 using Tapatalk

Are you on the soak test?

I just got it, downloading...

[Checks updates]... "crap, no update!" [repeat x100]

I signed up for the soak test. Maybe that's why. but I figured I would get an email telling me it is officially starting and I didn't get anything like that
Sent from my XT1095 using Tapatalk

Nothing yet
Sent from my XT1095 using Tapatalk

Download in Progress...
Where is the file I should capture so I can sideload this OTA again?
(I have two Moto X 2014 (2nd gen) and one is downloading the upgrade right now. I'd like to save the file(s) in case my second phone is delayed in getting the upgrade.)
Thanks

wpscully said:
Where is the file I should capture so I can sideload this OTA again?
(I have two Moto X 2014 (2nd gen) and one is downloading the upgrade right now. I'd like to save the file(s) in case my second phone is delayed in getting the upgrade.)
Thanks
Click to expand...
Click to collapse
http://www.droid-life.com/2014/06/05/download-nexus-ota-url-file/
works for moto ..
http://forum.xda-developers.com/moto-g/general/to-released-android-5-0-lollipop-t2930936

The Droid-Life article seems to discuss how to capture the URL of the server for the OTA file. I'm more interested in finding the file on my devices internal disk space after the download is complete.
I see in the logcat that the download completes and the OTA file is valid.
D/OtaApp ( 2784): [debug] > Notifying Updater to update progress
D/OtaApp ( 2784): [debug] > Receive intent: com.motorola.blur.service.blur.Actions.UPGRADE_DOWNLOAD_STATUS
I/OtaApp ( 2784): [info] > BotaDownloadHandler.finished: I appear to have read the entire file 927390521/0
I'm just not sure where the file is located on my phone disk space. Ideas?

wpscully said:
The Droid-Life article seems to discuss how to capture the URL of the server for the OTA file. I'm more interested in finding the file on my devices internal disk space after the download is complete.
I see in the logcat that the download completes and the OTA file is valid.
D/OtaApp ( 2784): [debug] > Notifying Updater to update progress
D/OtaApp ( 2784): [debug] > Receive intent: com.motorola.blur.service.blur.Actions.UPGRADE_DOWNLOAD_STATUS
I/OtaApp ( 2784): [info] > BotaDownloadHandler.finished: I appear to have read the entire file 927390521/0
I'm just not sure where the file is located on my phone disk space. Ideas?
Click to expand...
Click to collapse
It's in the cache folder.
Sent from my XT1095 using Tapatalk

Has anyone been able to grab the url for the ota upgrade? Or is there a uploaded zip somewhere? Thanks for sharing!

Is this officiall, or a soak test?

Hopefully someone captures it. I haven't got it yet, bah humbug to Motorola's fast update promise.

Got it a few hours ago for US. Was unable to capture OTA as I do not have root.

We're you entered into the soak test, or is it the official bump up.

I was definitely not part of the soak test.

Fr0stbyteX said:
I was definitely not part of the soak test.
Click to expand...
Click to collapse
did you grab the zip file from cache folder?

munchy_cool said:
did you grab the zip file from cache folder?
Click to expand...
Click to collapse
No, I do not have root so could not access /cache

I have root but unfortunately I have not yet received the OTA

Oh come on...

Kiw l21 middle eastern MM released...

The official huawei page of our region has stated that it has released the MM update for kiw l21 and it should reach us in 2-3 working days...
There will be an OTA and a link on their website... I want to mirror the link on sites like mega etc for people who don't get the update right away.... But don't kniw how to, can someone please explain the procedure so middle eastern people don't have to wait any longer...
Sent from my KIW-L21 using Tapatalk

hi.can send me rom link?

Faheemarif252 said:
The official huawei page of our region has stated that it has released the MM update for kiw l21 and it should reach us in 2-3 working days...
There will be an OTA and a link on their website... I want to mirror the link on sites like mega etc for people who don't get the update right away.... But don't kniw how to, can someone please explain the procedure so middle eastern people don't have to wait any longer...
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
where is the link??? Please share with us

Faheemarif252
What is the web address of the official Huawei page thats states this ?
Please provide a link so that we can read this.
Thank you

If you read the original post correctly... Huawei said that the OTA will reach in 2-3 working days... That means monday or tuesday (at least where i live).... Some people have got the ota but i still haven't... And there is no update available till now on their website...
One of my friends recieved the update so i should be soon too.... I will mirror the OTA and share the link asap
Sent from my KIW-L21 using Tapatalk

It should be in XDA's Honor's 5x repository

Faheemarif252 said:
The official huawei page of our region has stated that it has released the MM update for kiw l21 and it should reach us in 2-3 working days...
There will be an OTA and a link on their website... I want to mirror the link on sites like mega etc for people who don't get the update right away.... But don't kniw how to, can someone please explain the procedure so middle eastern people don't have to wait any longer...
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
I simply use the logcat feature of android to get the URL of an OTA update
Open a command prompt and use these two commands to clear the log and then dump the log to your PC and simply look (search) for any http:// in the log
I simply use.
adb logcat -c
followed by
adb logcat -d > logcat.txt
to learn more read below
1. When you get prompted to download an update on your Android device, 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-
Click to expand...
Click to collapse
To better use the "adb logcat" command, we need to look at its options:
"adb logcat -b <buffer>" - Loads an alternate log buffer for viewing, such as event or radio. The main buffer is used by default. There are log buffers on the Android system: "main", "events", and "radio". The default buffer is "main".
"adb logcat -c" - Clears (flushes) the entire log and exits.
"adb logcat -d" - Dumps the log to the screen and exits.
"adb logcat -f <filename>" - Writes log message output to a file. The default is the "stdout - Standard Output".
"adb logcat -g" - Prints the size of the specified log buffer and exits.
"adb logcat -n <count>" - Sets the maximum number of rotated logs to <count>. The default value is 4. Requires the -r option.
"adb logcat -r <kbytes>" - Rotates the log file every <kbytes> of output. The default value is 16. Requires the -f option.
"adb logcat -s" - Sets the default filter spec to silent.
"adb logcat -v <format>" - Sets the output format for log messages. The default is brief format.
Click to expand...
Click to collapse

clsA said:
I simply use the logcat feature of android to get the URL of an OTA update
Open a command prompt and use these two commands to clear the log and then dump the log to your PC and simply look (search) for any http:// in the log
I simply use.
adb logcat -c
followed by
adb logcat -d > logcat.txt
to learn more read below
1. When you get prompted to download an update on your Android device, 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-
To better use the "adb logcat" command, we need to look at its options:
"adb logcat -b <buffer>" - Loads an alternate log buffer for viewing, such as event or radio. The main buffer is used by default. There are log buffers on the Android system: "main", "events", and "radio". The default buffer is "main".
"adb logcat -c" - Clears (flushes) the entire log and exits.
"adb logcat -d" - Dumps the log to the screen and exits.
"adb logcat -f <filename>" - Writes log message output to a file. The default is the "stdout - Standard Output".
"adb logcat -g" - Prints the size of the specified log buffer and exits.
"adb logcat -n <count>" - Sets the maximum number of rotated logs to <count>. The default value is 4. Requires the -r option.
"adb logcat -r <kbytes>" - Rotates the log file every <kbytes> of output. The default value is 16. Requires the -f option.
"adb logcat -s" - Sets the default filter spec to silent.
"adb logcat -v <format>" - Sets the output format for log messages. The default is brief format.
Click to expand...
Click to collapse
Nice trick, thanks

clsA said:
I simply use the logcat feature of android to get the URL of an OTA update
Open a command prompt and use these two commands to clear the log and then dump the log to your PC and simply look (search) for any http:// in the log
I simply use.
adb logcat -c
followed by
adb logcat -d > logcat.txt
to learn more read below
Click to expand...
Click to collapse
Thnx a lot bro... I'll try the same as soon as i get the ota...
Sent from my KIW-L21 using Tapatalk

Faheemarif252 said:
Thnx a lot bro... I'll try the same as soon as i get the ota...
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
yep no problem another tip the file is normally named update.zip
and can be found in internal storage HwOUC folder with a folder inside with 5 digit number containing update.zip file

Nahid s said:
where is the link??? Please share with us
Click to expand...
Click to collapse
mammadpsy said:
hi.can send me rom link?
Click to expand...
Click to collapse
Tasha T said:
Faheemarif252
What is the web address of the official Huawei page thats states this ?
Please provide a link so that we can read this.
Thank you
Click to expand...
Click to collapse
Hey guys, Here is the link for Official MM update for ME - http://download-c.huawei.com/download/downloadCenter?downloadId=90103&version=351925&siteCode=pk

vsriram92 said:
Hey guys, Here is the link for Official MM update for ME - http://download-c.huawei.com/download/downloadCenter?downloadId=90103&version=351925&siteCode=pk
Click to expand...
Click to collapse
i have a bug in my phone in this update
when i receive new notification ex.whatsapp not show whatsapp icon in statusbar
show me pic who send me a message in statusbar
plz help me this bug

Amr fego said:
i have a bug in my phone in this update
when i receive new notification ex.whatsapp not show whatsapp icon in statusbar
show me pic who send me a message in statusbar
plz help me this bug
Click to expand...
Click to collapse
It's due to EMUI I guess

PalakMi said:
It's due to EMUI I guess
Click to expand...
Click to collapse
how can i fix this bug !!!!
i tired to found solution

Amr fego said:
how can i fix this bug !!!!
i tired to found solution
Click to expand...
Click to collapse
Try uninstalling and reinstall whatsapp

PalakMi said:
Try uninstalling and reinstall whatsapp
Click to expand...
Click to collapse
this problem in all application in my phone after i install this update

Amr fego said:
this problem in all application in my phone after i install this update
Click to expand...
Click to collapse
It's because the update, just go with a custom ROM that's better

how i return to custom rom !?

Amr fego said:
how i return to custom rom !?
Click to expand...
Click to collapse
Just unlock bootloader, install TWRP recovery and install custom ROM of your choice

the page huawai to get code to unlockbootloader not opend get me error
any anthor way to install TWRP recovery without unlock bootloader

[GUIDE] A small note about OTA and update.zip

It seem that there is a lot of confusion about how to update your phone with
the "OTA"s provided in the Stock firmware threads and from Huawei's own
support websites.
Rant Warning:
ALL Huawei Support website are totally useless to find any FW updates for any of their devices you have. They only ever show a few and most of the time none.
Once you do find FW (from another source like XDA) the accompanying "changelog.xml" file doesn't tell you anything about what the update is actually doing. They also don't tell you anything about any applied security patches. In addition it often tell you different things depending on the language you're reading. JFC!!​
[EOR]
One problem is that we keep on using the term OTA for something that is essentially always
an OTA. Instead what we call it, should depend on what it is doing. What can it be doing?
1. A full factory update, that can wipe all, usually using the "dload" bootloader folder. Using /dload/UPDATE.APP of your SD-card.
2. A partial update that uses an Edify installation script in:
Code:
/META-INF/com/google/android/updater-script
but also has a one or more SOMETHING.APP in it. These are all coming in the form of an update.zip.
How to Manually update from update.zip?
Code:
0. Do not try to flash update.zip with TWRP/CWM, only use Stock Recovery.
1. Dial: *#*#2846579#*#*
2. Choose option called "Software Upgrade" and then "SDCard Upgrade" and confirm with OK.
1. Go to: Settings > Updater > "New version" > Quick Download
2. When you see the progress bar starting after a few %, hit "Pause".
3. Now open the File browser and got to the "Local" tab.
4. Navigate to the file: "Internal Storage" > "HwOUC"
5. You will see another folder with a 5-digit number, XXXXX.
This is the actual "v" number used in the URL query to fetch the OTA.
It simply corresponds to the XXXXX in:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/vXXXXX/f1/full/update.zip
6. Save time (and your data-plan) by manually downloading this file. (You should get ~10 MB/s on a good day.)
7. Inside the XXXXX folder, you will find a file called "update.zip".
Now you need to replace that file with your recently downloaded one.
8. Used adb to tranfer the file to your device
wget --show-progress -d http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/vXXXXX/f1/full/update.zip -O XXXXX.zip
adb devices
adb shell rm -fr /sdcard/HwOUC/*
adb shell mkdir /sdcard/HwOUC/XXXXX
adb push XXXXX.zip /sdcard/HwOUC/XXXXX/update.zip
# Note: speed is ~7 MB/s, so a 1.4GB OTA will take about 200 sec to transfer.
9. Enable WiFi or Mobile Data again, then hit "Resume" in the Updater.
10. The progress bar will instantly hit 100% and you will be asked to
restart right away or wait until later.
(You only have 15 seconds to decide!)
11. Your phone will reboot a few times to optimize (!?) the system.
Thanks to @shashank1320 useful but hard to read post.
Other very useful things to know about Huawei's updates.
Let's look at the last part (the file) of the Huawei update URL.
Code:
http://update..././././././././vXXXXX/f1/full/update.zip
1. To get a list of files in, and the MD5 of the OTA, use "filelist.xml".
2. To get the changelog of the OTA, use: "changelog.xml".
3. To get the "precheck-script" that does the "apply_patch_check" for
each file, use: "precheck-script". Not all updates has this.​Question: Where the fcuk is the latest update?
Answer:
Quoting THIS article on how updates are pushed.
According to one of Google developers, Dan Morrill, (goo.gl/L85mSS), the
first few OTA updates are sent to 1 % of devices. It happens at random,
regardless of the location or point of sale of a phone/tablet. During
this time, bugs are identified allowing the updating process to be put
on hold if any critical errors are registered with a large number of
users.
After that over a couple of weeks, updating is provided to 25, 50, 100 %
of users, i.e. at the initial stage only one device out of a hundred
stands a chance of getting an upgrade. If the update is not received,
the device drops from the list, and subsequent repeated clicking on the
button ‘check for updates’ automatically sends the device to the bottom
of the list. When a new stage of distribution starts, clicking on the
button get a 25 % chance of receiving the update. Since the device
checks for updates on its own once a day (upon reboot), clicking on the
button might ‘jump the gun’ before it may run its course. But whatever
the outcome, only one check will be made. Subsequent clicking will not
help matters. This is not a situation where ‘first press, first receive’
(first come first serve). In any case, the over the air update will be
available to everyone within a couple of weeks.
Click to expand...
Click to collapse
.Question: WTF does that OTA do?
Answer:
If the OTA is not a UPDATE.APP, but an update.zip, then simply extract it,
and navigate to: /META-INF/com/google/android/ and open the updater-script.
For example, this line:
Code:
# v80166
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "HONOR/KIW-L21/HNKIW-Q:5.1.1/HONORKIW-L21/C432B140:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Android/msm8916_64/msm8916_64:6.0.1/MMB28B/d0090306503211916:user/test-keys");
tell you that you will not be able to use this (v80166) update, unless
your ro.build.fingerprint matches any of the shown strings. Clearly,
this FULL OTA was meant as an update to KIW-L21C432B140 build only.
​
New Proposal
I propose to start using the following terminology instead of just "OTA".
- DLOAD for anything that is factory reset and bootloader flashable, with no previous dependencies. (Everything that uses /dload/UPDATE.APP.)
- PATCH for anything incremental, that depend on some previous or particular state of the phone FW.
- FULL for any update that can be used to skip all previous PATCH's within the same Build (B-number). Like a cumulative update.
Let's call this "type".
In addition we should try standardize our OTA file-naming scheme. Since the current method make it
nearly impossible to distinguish between various OTA patches, we should use something like this:
Code:
<"model">_<v-number>_<type>_<build_ref>.zip
# For Example:
KIW-L21C432_v80166_FULL_C432B370CUSTC432D002.zip
And the file description should also say something about what the update does, since Huawei's changelog does not.
Something like:
"Cumulative 1% test-update for B140 EMUI 4.0.0 to B370 EMUI 4.0.3, ASPL: 20170522"
Click to expand...
Click to collapse
Where "ASPL" is referring to the resulting Android Security Patch Level date.
Finally, if someone can also squeeze in what exact security patches has been applied that would be huge!
​Anyway, just some ideas I throw together to try to clear up this firmware nightmare.
(And yeah , this is not meant for you kernel devs!)

reserved to dogs running around

Thanks for the credit but I did not see anything in my post that is hard to read..no worries, keep up the good work

Nice that someone wrote this for noobs !

I am not getting update on my honor kiw-l21c185B130 plzz help

Anish karki said:
I am not getting update on my honor kiw-l21c185B130 plzz help
Click to expand...
Click to collapse
Download the later firmware from firmware finder and see if you can use dload method to update

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.