Related
Hi,
What are experiences of current owners of Nexus phones ? My Desire Z is rooted ( only rooted, don't have a custom ROM), and I never got Gingerbread update so I'd hate the same thing happening to G Nexus.
Thanks.
zljk said:
Hi,
What are experiences of current owners of Nexus phones ? My Desire Z is rooted ( only rooted, don't have a custom ROM), and I never got Gingerbread update so I'd hate the same thing happening to G Nexus.
Thanks.
Click to expand...
Click to collapse
That will never happen with the GN. When you own this phone you're first in line for the updates until the next is coming out then you're second but still faster than the others.
Sent from my HTC Desire using XDA App
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
you could do that, but chances are someone will get the OTA before you and pre root it for everyones pleasure and you can just flash that via recovery
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
If my experiences with my OG Droid match up with the Nexus line, if you've only rooted and haven't actually installed another ROM, you should be able to apply the OTA update and lose root because of it. Then just root again.
martonikaj said:
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
Click to expand...
Click to collapse
I've seen some threads claiming that root itself doesn't affect updates, but changing of data on system partition.... Was kind of hoping there is a way to have my cake and eat it too - don't mind having to root the phone all over again after the OTA....
Anyhow - as an alternative, is there a way to get official Nexus updates ( stock ) using other channels except OTA ? What was happening with old Nexus phones ?
zljk said:
I've seen some threads claiming that root itself doesn't affect updates, but changing of data on system partition.... Was kind of hoping there is a way to have my cake and eat it too - don't mind having to root the phone all over again after the OTA....
Anyhow - as an alternative, is there a way to get official Nexus updates ( stock ) using other channels except OTA ? What was happening with old Nexus phones ?
Click to expand...
Click to collapse
The alternate way to get official Nexus updates is to download the update zip file once someone copies it off their device and uploads it, and install it in whatever fashion works.
I rooted my Nexus One without unlocking the bootloader or using custom recovery. I definitely still got OTA updates and they worked fine, but would unroot the phone.
The solution is to use a custom recovery and apply the update .zip manually, then reflash superuser before rebooting. Whenever an OTA update comes out, someone eventually uses logcat to get the URL to the zip and posts it so anyone can download it.
I was rooted on Froyo and got the OTA update to Gingerbread no problem, but I lost root. I eventually got root again (Gingerbreak) and when the 2.3.4 update came out, I did it manually in custom recovery to keep root.
Now I run CM7.1 so I definitely don't get OTA updates from Google
TulpiX said:
You cant get them at all?
Not even: get update and apply it, loose root because of the update, reroot?
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
It will often download and you can try but it will either fail, unroot you, or cause troubles.
You're best off applying the pre-rooted update, or unrooting and taking the OTA.
martonikaj said:
When you're rooted you can't get the OTA updates. You have to unroot to apply them. That's true for all Android phones.
Click to expand...
Click to collapse
True. However it's trivial to repackage an OTA update to a rooted update and since it's very compatible with the source in AOSP and you get working drivers very early you can start messing around with it straight away.
blunden said:
True. However it's trivial to repackage an OTA update to a rooted update and since it's very compatible with the source in AOSP and you get working drivers very early you can start messing around with it straight away.
Click to expand...
Click to collapse
Of course, as is often the case for most phones supported here on XDA. the rooted OTA comes in the form of a .zip soon after it comes out.
slowz3r said:
you could do that, but chances are someone will get the OTA before you and pre root it for everyones pleasure and you can just flash that via recovery
Click to expand...
Click to collapse
When flashing the rooted OTA via recovery, does it wipe the phone (apps and all)?
Also for the other method, when unrooting >> applying OTA >> rooting again, does it wipe the phone at any point during this process?
Help would be appreciated and rewarded!
I just received my OTA update notification and found the update zip itself in the cache of my phone. I can post that update zip here if a mod can come along and tell me where to put it. I am going to wait till I'm home so I can have my rooting facilities handy before starting.
phazerorg said:
I rooted my Nexus One without unlocking the bootloader or using custom recovery. I definitely still got OTA updates and they worked fine, but would unroot the phone.
The solution is to use a custom recovery and apply the update .zip manually, then reflash superuser before rebooting. Whenever an OTA update comes out, someone eventually uses logcat to get the URL to the zip and posts it so anyone can download it.
I was rooted on Froyo and got the OTA update to Gingerbread no problem, but I lost root. I eventually got root again (Gingerbreak) and when the 2.3.4 update came out, I did it manually in custom recovery to keep root.
Now I run CM7.1 so I definitely don't get OTA updates from Google
Click to expand...
Click to collapse
+1. Exactly.
There is a lot of wrong (or slightly incorrect) information in this thread.
Have root has no impact whatsoever in your ability to receive or apply the OTA update. This has been the case on every Android device. However, if you have a custom recovery flashed, you will not be able to automatically apply the update - you will have to find the zip file in the cache and use your custom recovery to apply it.
On a slightly separate note, once you apply the update either automatically or manually via custom recovery, you will lose root. However, if you do have a custom recovery, as long as you flash ChainsDD's superuser package immediately after applying the update, but before rebooting, you will retain root.
On another separate not, if you flash the update as is from Google, it includes a file (/system/recovery-from-boot.p) that re-flashes the stock recovery on every boot, so you will lose your custom recovery. Either remove the file before flashing the update, or just re-flash your custom recovery.
Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?
Did you reflash the ota after you flashed supersu?
What was the error message?
sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?
It will lose the option to blend milkshakes
church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.
datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.
Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!
hi all
assuming that i've flashed TWRP + rooted the phone
will i still be able to update the phone via OTA updates?
as this does not work on samsung phones once KNOX is tripped
i was wondering if it would be the same on oneplus devices
your input is appreciated. thanks!
leongzxc said:
hi all
assuming that i've flashed TWRP + rooted the phone
will i still be able to update the phone via OTA updates?
as this does not work on samsung phones once KNOX is tripped
i was wondering if it would be the same on oneplus devices
your input is appreciated. thanks!
Click to expand...
Click to collapse
Short answer: No. Custom recovery can't process the OTA update. There's another thread talking about this topic here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
If you want the latest updates Funk Wizard usually posts their full zips (not small OTA zips) on XDA (just search in the 5T section) and OnePlus usually has them under the device support page.
I've not tried it myself but I heard once you root and go to software update section oneplus will detect your root and instead will download a full OTA zip which you can then dirty flash in your custom recovery (TWRP) without any issues. of course the flash will remove root and then you will need to flash root zip file to gain root again.
Well, actually I downloaded latest OTA (4.7.4) over wifi and then updated phone while rooted and with custom recovery (oficial 3.2.0 I think). And it worked! I lost root in the process (I rooted again later), but otherwise phone was updated and it was done via custom recovery. So far, I don't have any problems, but not sure if any problems will come later.
shadeau said:
Short answer: No. Custom recovery can't process the OTA update. There's another thread talking about this topic here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
If you want the latest updates Funk Wizard usually posts their full zips (not small OTA zips) on XDA (just search in the 5T section) and OnePlus usually has them under the device support page.
Click to expand...
Click to collapse
Revin said:
Well, actually I downloaded latest OTA (4.7.4) over wifi and then updated phone while rooted and with custom recovery (oficial 3.2.0 I think). And it worked! I lost root in the process (I rooted again later), but otherwise phone was updated and it was done via custom recovery. So far, I don't have any problems, but not sure if any problems will come later.
Click to expand...
Click to collapse
thanks for the response!
digitalmahdi said:
I've not tried it myself but I heard once you root and go to software update section oneplus will detect your root and instead will download a full OTA zip which you can then dirty flash in your custom recovery (TWRP) without any issues. of course the flash will remove root and then you will need to flash root zip file to gain root again.
Click to expand...
Click to collapse
wow for real?
so if you're rooted. it will not download small zips of OTA but instead the full sized OTA?
then we can choose to flash in TWRP instead?
I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?
djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.
KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june
JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...
KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.
djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't
KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)
JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.
djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?
This is the OTA update I received for the G5 Plus.
The phone was running a North American (retus) build OPSS28.85-17-2 (October 1, 2018 patch level) prior to the update. After the update, the phone is running OPSS28.85-17-4 (December 1, 2018 patch level).
MD5: f840a71b9a1b347b13274c668adf77a0
SHA1: fb53a9a872c8a881f4bde111aaade4f23bb7a9a4
SHA256: d20bcd877222429dfc1620c5265b91cf29b2768d8e51314ef7b8f3ee0d9bba45
File size: 73,434,767 bytes (~70MB)
https://drive.google.com/file/d/1XWbH8emmxduw_yosNJASndgxesbwrp5d/view?usp=sharing
https://www.dropbox.com/s/1tyh80849p1qdsy/potter_US_OPS28.85-17-4_patch.zip?dl=0
reserved for future use
Please help!
Hello, how do I install this update if I have TWRP? I have searched for the stock recovery and I have not had luck.
MasterDoggy said:
Hello, how do I install this update if I have TWRP? I have searched for the stock recovery and I have not had luck.
Click to expand...
Click to collapse
If you have TWRP installed I suspect you have rooted your device or tweaked it in some other way.
In this case OTA updates won't work.
You have to be on unrooted full stock firmware incl. stock recovery (can be found in the related fastboot firmware as "recovery.img").
If you are:
Transfer the file to phone’s internal storage. Go to Settings > apps Provide storage permission to Motorola Update Services app. Check for OTA updates from Settings.
The package will be automatically detected and system upgraded.
(Source: https://forum.xda-developers.com/g5...fficial-moto-g5-g5-plus-t3848246/post77748504 )
Wolfcity said:
If you have TWRP installed I suspect you have rooted your device or tweaked it in some other way.
In this case OTA updates won't work.
You have to be on unrooted full stock firmware incl. stock recovery (can be found in the related fastboot firmware as "recovery.img").
If you are:
Transfer the file to phone’s internal storage. Go to Settings > apps Provide storage permission to Motorola Update Services app. Check for OTA updates from Settings.
The package will be automatically detected and system upgraded.
(Source: https://forum.xda-developers.com/g5...fficial-moto-g5-g5-plus-t3848246/post77748504 )
Click to expand...
Click to collapse
Phone doesn't detect the update package using this method. Please suggest if the file name needs to be changed.
checksamir said:
Phone doesn't detect the update package using this method. Please suggest if the file name needs to be changed.
Click to expand...
Click to collapse
You have to ask the OP, @Amishrabbit for that. But yes, the name the file has now is wrong, it has to be named something like Blur_Version.xx.xx.xx.potter.retail.en.US .
-redacted-
Wolfcity said:
You have to ask the OP, @Amishrabbit for that. But yes, the name the file has now is wrong, it has to be named something like Blur_Version.xx.xx.xx.potter.retail.en.US .
Click to expand...
Click to collapse
Well, my initial reply closed itself without posting, so I'm trying again.
I'm a novice at this stuff. I don't know any instructions about how to install it. I do know that I extracted the URL for the update from the logcat output from the phone on a debugger, and the URL was live for about 10 minutes and now doesn't respond, so presumably it's a time-limited download.
I did rename the file, and I know it's from an official OTA source URL, so I'm pretty sure you can't install it with TWRP. I don't have TWRP installed on this phone and retrieved and installed it using the normal System Update method.
I've attached a screenshot of the phone's version numbers. I can't find a reference to the "Blur" number above on the phone's UI, but the file itself contains the following string, so this appears to be a pairing of (newer version) (older version)
Code:
Blur_Version.28.231.5.potter.retail.en.US )Blur_Version.28.211.2.potter.retail.en.US
The Blur* filenames were only for nougat OTAs, Oreo OTAs are named according to the version you are upgrading *from*.
They can't be installed using TWRP, the stock recovery is required, as is an untouched system, OEM, modem, and other partitions.
If you're rooted, just use the TWRP flashable zips, easier...
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Note that I do have the most recent retus zip there, but haven't yet updated the OP. Link for that is in the last couple of pages.
NZedPred said:
The Blur* filenames were only for nougat OTAs, Oreo OTAs are named according to the version you are upgrading *from*.
They can't be installed using TWRP, the stock recovery is required, as is an untouched system, OEM, modem, and other partitions.
If you're rooted, just use the TWRP flashable zips, easier...
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Note that I do have the most recent retus zip there, but haven't yet updated the OP. Link for that is in the last couple of pages.
Click to expand...
Click to collapse
I guess Blur version works for Oreo as well. I have used the name "Blur_Version.28.21.5.potter.retail.en.US.zip" and system detected the update immediately.
Unable to upload the screenshot due to network issues..
SujataSam said:
I guess Blur version works for Oreo as well. I have used the name "Blur_Version.28.21.5.potter.retail.en.US.zip" and system detected the update immediately.
Unable to upload the screenshot due to network issues..
Click to expand...
Click to collapse
Thanks. It worked like a charm.
february security patch maybe?
any news of February 2019 update?
ashutoshmatari said:
any news of February 2019 update?
Click to expand...
Click to collapse
Seems not. If you see only questions about it but no answers it's unlikely. But feel free to search by yourself in the known sources or use Google and if you find something: Share it.
https://support.motorola.com/in/en/solution/MS137632
here is the maintenance release note of February 2019, but actual release of update is not known.
ashutoshmatari said:
https://support.motorola.com/in/en/solution/MS137632
here is the maintenance release note of February 2019, but actual release of update is not known.
Click to expand...
Click to collapse
Just got it
I have an ota to move from 17-4 to 17-6.
https://www.dropbox.com/s/b8i3l0qgi...8.85-17-6_OTA_Package_OPSS28.85-17-4.zip?dl=0
You'll have to rename it to get it to work automatically. Unfortunately I don't know what the name would need to be. You can however sideload it through ADB. Haven't done that myself so hopefully someone can help with that too.
hopefully they will release it soon for other regions too.
ashutoshmatari said:
hopefully they will release it soon for other regions too.
Click to expand...
Click to collapse
Why shouldn't they?