Nougat update - X Play Q&A, Help & Troubleshooting

Nougat update - X Play Q&A, Help & Troubleshooting

Hello everyone. Please send me a link who captured the official nougat update ota zip. Because I am not a techy guy. I only able to do method 1
{Just Save the downloaded file to Root of SD Card [External Memory Card and not Internal Memory] and go to Settings --> About Phone --> System Updates. Update will be auto recognized and user will be prompted to apply update.}
Iam still not got official update notification. But I want nougat very eagerly. I am very happy I someone help me.

Didn't captured anyone?

Anyone capture the ota:
When you receive an OTA notification, DON'T download it. To capture the OTA, follow the steps mentioned below:
1. Download Terminal Emulator from the Play Store (https://play.google.com/store/apps/d...ww.apk4fun.com).
2. Open Terminal Emulator and type: "logcat > /sdcard/ota.txt" (without quotes).
3. Go back to the OTA notification & click on download.
4. When the download process is starting, switch back to terminal emulator & close it.
5. Browse to your SD Card using any file manager. There you'll find a file named "OTA.txt". Open it & search for OTA download link in it.
That's it.

Related

ROOTED rc30 ????????

since the brand new root for ota rc30 i can not find the general stickies for "how to keep root" installing "eng bootload" and "updating to jf 1.3" for the 90% of users who had ota rc30 where do we look. i tried checking darkrifts wiki but it is no where as detailed as these subtopics here. its telling me to copy the androidmod1.0.zip to my /system/recovery partition and copy the jf 1.3.zip to the /sdcard not renaming either but then doing a reboot... am i missing something.
can we clarify this?
i got the root... but what order do we do this in now?

edit didnt work but it seems as All of the prior stickies are over written by all of the new root your ota rc30 topics

http://forum.xda-developers.com/showthread.php?t=466455
Theres links in that thread to the wiki that explains how to install the modified updates after down grading. You have to install the recovery test keys to allow the modifed updates to be installed.
The terminal commands for doing the test key stuff is down using a terminal on your phone. Download telnet from the market and connect to localhost. You will need root access. Restart your phone and once booted, type telnetd then enter. Dont worry about a contact search coming up. Ignore it. You now have root.

ok what you are missing verbatim from rifts wiki.....
AndroidMod1.0 .xxx file G1 downloadable link (rename to .zip)
AndroidMod1.0 .zip file Non G1 download, no need to rename,
Unzip the file and copy (or adb push) recovery_testkeys.img to /sdcard
Download the modified update (Do not unzip it!):
ok its worded so funny recovery test keys is in the file mod1.0.zip but it explicitly tells you DO NOT UNZIP it ? but line 2 says copy the recovery keys in that zip to the card... then it skips to updating to jf.1.3.zip
and more glaring errors in directions?

Its a bit of a confusing read at first. Thetres 2 files to download. 1 has the tesst keys which u extract and copy to the sd card. With root access this gets written to the system artition ia terminal on the phone. then the other download is rc30 or tc8 depending if you r us which gets renamed to update.zip and goes to your sd card.

Seems i have found a way to capture OTA without need to root for sharing with other people. If any step seems wrong one can correct me. @S0bes and @MarckozZ can take a look if its relevant or not doing so Since i find you guys know more into this.
Disclaimer: I am not responsible for any brick. Shared this just for your information. You may try at your own risk.
As soon as one receives OTA notification.
1. Connect your phone with your PC and Take adb logcat > log.txt
2. Tap "Download" button on your phone to initiate download of update.
3. Press Ctrl+C to stop logcat. Now, look into log.txt file for the URL. Press Ctrl+F and look for keywords like URL. A line will appear something like "http://android.clients.google.com.........546.zip". Now this filename need not be the system_version name Eg: Blur_version.xxx.zip. It may appear as some unknownfilename Eg: 9851455bbsfdxxxxxxxxx.zip
4. Now this URL can be shared to users for downloading the official OTA manually. User can then download OTA via shared URL on their PC and place in their adb folder.
5. Reboot into Stock recovery and select option "Appy update from ADB".
6. Now, from PC do "adb sideload OTAfilename.zip". Where OTAfilename is the name of the OTA file that you downloaded.
This should install the OTA on your phone. Once you see Install from ADB is complete , proceed to reboot.
References: Droid-life and 9to5google
Install Motorola Drivers and Setup ADB . You may Download Motorola drivers and adb tools from this thread. Extract Adb-tools_treibier.zip and get ready for above steps.

Really?wow hope this is real!that would be great
Sent from my VS985 4G using XDA Free mobile app

I think you will need to disconnect the phone before opening that log file..
if not logcat might still want to throw contents in it continuously..
Also it will be good to include a link to guide to setup of adb for Moto G to avoid users coming with any queries related with it.

Pretty interesting if this works its a great find, thanks! I gave your post a thumbs up.

Will definitely verify this method when the Lollipop OTA comes.

This method is known, but thanks, anyway.

Great Post @==vj== ...
Guys whoever gets the update please be kind enough to do this and post the link ......

Capture OTA Without Root

Prevent Sprint LG G4 [And Probably Others] From Upgrading to 6.0

If you are like me, you own an LG G4 with a bootloader that cannot be unlocked. This, at least for the moment, means that we cannot have both Android 6.0 Marshmallow and our beloved root access. We must choose one or the other. I assume that if you are reading this, that you have chosen root over marshmallow. If you did choose to stay rooted on 5.1, then I am sure you are being harassed to update. Well, I believe that I have your solution.
First, I must explain what this guide will do and what you will need.
What we're doing.
1. We will delete the update.zip.
2. We will make a dummy update.zip that will not be replaceable or modifiable, even by the root user. This fake update file will prevent a legitimate update from downloading and installing.
3. [OPTIONAL] We will remove the annoying update notification.
What is needed.
1. Root. [duh...]
2. File explorer with root privileges a.k.a. a "root explorer". (If you need one, I personally recommend the free yet feature packed ES File Explorer.)
3. A proper Busybox installation.
4. A terminal emulator.
5. A few minutes of your time.
***AS ALWAYS, I, XDA, XDA MODERATORS, XDA MEMBERS, OR ANYONE ELSE IS NOT RESPONSIBLE FOR THE CONSEQUENCES OF FOLLOWING THIS GUIDE. THE DEVICE YOU HOLD IS YOURS AND ANYTHING THAT HAPPENS TO IT IS YOUR FAULT. YOU HAVE BEEN WARNED!***
The procedure.
-Part 1.
1. Open your root explorer and make sure that it has root privileges.
2. Navigate to /cache
3. If you have a file called update.zip then delete it, if not, then just move on to part 2.
-Part 2.
4. Make a new .zip file with nothing in it and save it as update.zip (make sure it is saved to "/cache" and nowhere else, not even in a folder inside "/cache"!)
5. From here move on to your terminal emulator.
6. Once inside the terminal emulator, type the following commands.
Code:
su
cd /cache
ls
chattr +i update.zip
From here I recommend that you check that it worked by typing in
Code:
lsattr update.zip
If the command works you will see a lowercase 'i' amongst a string of letters and dashes.
-Part 3. [Optional] (I don't recommend doing this, but the harm is non-existent as far as I can tell.)
The annoying update notifications are actually Google Play Services fault. All you have to do is go to "Settings > Apps > All" and find Google play services and disable the apps ability to show you notifications.
Thats pretty much it. Now I must tell you that you will still receive notifications saying an update was downloaded, verified, and is ready to install, assuming that you did not go through with part 3. All you have to do is click the install button, and let it restart to install the bogus update. The update process will error and all you have to do now is pull and reinsert the battery and power on the phone. I have been doing this myself for a few weeks now and have not had a single issue. This also includes 4 times that it has failed to install the update from within recovery.
I hope that you find this useful and happy modding!

Reserved

Reserved.

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.

Database Users

welcome