Database Users

sideloading ota

Hi I have an unrooted 6p I have never messed with the software but I am on the dp program I usually get the updates within hours of it being announced. But for some reason I have not gotten the 7.1.1 stable with December security patch which is odd but anyway I tried side loading the OTA and it gets to 40% and then says installation aborted. I have the and setup right and all that I can reboot into bootloader does anyone know why it would be doing this? When I was at work today I thought maybe if I disable the allow seamless update option in developer options maybe that will allow it. Any thoughts?

Ok I feel like an idiot. I tried again when I got home from work and it seems that the file I am trying to flash is from November 1 which I already have installed. It is the last one one the Google OTA page. So is it not out yet for the 6p? I'm confused can anyone help me out please

I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.

redduc900 said:
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
Click to expand...
Click to collapse
Ok if I unenrolled from the dp program I should just get the OTA then I won't have to side load is what I'm guessing. It seems that Google had the stable build done before they released the last dp because the file says November 1 build and I got mine on November 5 that is why it won't allow it.

Software: Modified... Not rooted... want to be able to get updates

I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
My phones info;
Software status: Modified
Android Security patch level: May 1 2016
Baseband version: M8992_1253331 .29.01.88.02R SUPER_NA
Kernal Version: 3.10.84-perf-g329ac5f
[email protected] #1
Thu Apr 21 00:11:23 CDT 2016
System Version: 24.221.4.clark_retus.retus.en.US.retus
Build Number: MPHS24.49-18-4
The pending update: New version:24.221.8.en.US
Thank you.

u need to flash official factory image inorder to get the updates
i hardly recommend you to use fastboot and install stock firmware from this site
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick...
install the latest firmware and then check for updates
if u have any queries then go through this.... make sure that u don't mess up
https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

Cjet said:
I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
Click to expand...
Click to collapse
If I understand your post correctly, and the COMPLETE firmware image was flashed, then you should have no issues taking an OTA update... the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt.
Try this, before you accept and download the update, boot into stock recovery and wipe cache. Or better yet, do a full factory reset and accept the update and apply it, then let it boot fully, do another factory reset and then set it up clean.
I don't know why this happens... it just seems like a few every update won't take it no matter what we do, and for we do not have the latest full factory image yet so there isn't much we can do to find another way.

Thank you both for your reply. However, I am still not clear on something.... there seems to be confusing/conflicting advice regarding the Software "Modified" status and it's role in accepting updates.
1. "if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick..."
2. " the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt."....... If the Software status says "modified" doesn't that mean that the system is indeed modified, and that trying to load the OTA in this state will result in a bootloop? .

u neee to flash official firmware.... the only way to remove modified and change it to official....
it actually doesn't matter that if bootloader is unlock u can install the updates...... i was on may patch and i also wanted to change the software status from modified to official in order to get sept patch... but in moto firmware center the latest was feb 2016.... so i had to downgrade... i tried and it worked... then i was eligible for ota and yes im on sept patch
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/

Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk

Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....

Prazaar said:
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Click to expand...
Click to collapse
I disagree... it CAN go back to Official, I had several ROMs on my device, then flashed stock image and somehow mine went back to Official. Was mine a fluke? I don't know, but it is clearly Official now. Note the picture clearly shows the bootloader was unlocked (Status 2) and I had at least dozen different ROMs flashed over time before going back to stock using the May 2016 security image and then successfully OTAing up to October security update.
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.

I know what you mean. My Software status is with LineageOS "official" i can flash every rom an the status stuck in official.
Factory img is no warranty for official status but also makes no difference for ota
Getapatalkt vom meinem Moto X Style

thebaconbox said:
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Click to expand...
Click to collapse
Because I am new to all of this and don't know anything about custom Roms. All I want to do is get this thing back to stock.

[/QUOTE
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.[/QUOTE]
Wow, thanks everyone for the suggestions and patience!
OK, so the software status does not affect OTA update installation. Software status being modified does not necessarily mean that the SYSTEM is modified. Yet if the SYSTEM is modified then taking the OTA update will cause a softbrick.
How can I tell if my SYSTEM is modified before deciding on taking the OTA update?
I have had the official Motorola firmware flashed/reinstalled previously by friend's son, and that didn't take the OTA update. It caused soft brick (No Command error bootloop)
I then went to the Motorola site myself, downloaded the firmware and flashed/reinstalled it. This is where I am currently, trying to decide if I should take the update or put it off until I have a couple of hours free to troubleshoot in case the OTA softbricks this thing again (it takes me much, much longer to figure this stuff out than it does for you guys. )
And if that does soft brick it again, then I am not sure what I am doing wrong with the flashing. So, is there any way for me to check to see if the SYSTEM is modified before I try the update.? Thank you!

Sagar_1401 said:
u neee to flash official firmware.... the only way to remove modified and change it to official....QUOTE
This was done twice and still says modified
Click to expand...
Click to collapse

Status modified will change to official after an OTA update.
Sent from my XT1572 using Tapatalk

Anyone? No one knows if there is any way for me to check to see if the SYSTEM is modified before I try the update.?

Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style

Prazaar said:
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Click to expand...
Click to collapse
I don't understand what you are saying. I cannot see "what" if it is modified? Edited - removed earlier rant.
(Sorry)
SOLVED.....
Today I backed everything up, bit my lip and hit "install update". It did update the phone and it did change the software status to "Official". I did this with the bootloader unlocked, and it worked . It does say Status Code 3, and the bootloader unlocked warning screen on startup appears, both of these I am guessing is normal. Everything seems good.

Mi A1 Oreo 170623.026.7.12.29 Encountered Bugs

Hi Guys,
I did not receive OTA for Oreo on my Android One and had to reset my phone to get the OTA update. After that once I installed Nougat Fastboot Rom and it was on August 2017 patch and wasnt receiving OTA again so I flashed Oreo Fastboot Current Rom and later locked the bootloader through fastboot oem lock command. I thought it was only me who is not getting the latest January Patch. Following are my questions:
1. Are we going to get Oreo 8.1 or any patch for january? I am not a beta tester.
2. How do I know if my phone is still receiving OTA?
Bugs encountered, please let me know if any one has the similar bugs.
1. Sudden crash of google chrome, android web view or some other apps like ventura wealth etc.
2. Camera doesnt start sometimes.
3. Battery Drain.
4. Phone rings but there is no caller id when phone is locked.
5. Multiple Contacts for various apps can be seen in native contact apps which makes it difficult to select the required contact.
6. No Fingerprint Gesture control.
7. Mi Remote not able to put shortcuts on desktop and no option to grant permission too.
8. No Flash Notification.
Please let me know something useful.
I have got Nougat Rom of December patch. Is it wise to use that?

So I just flashed Nougat December patch official fast boot rom.
I am not being shown any ota for oreo or for any thing.
Is this normal.

rajputz said:
So I just flashed Nougat December patch official fast boot rom.
I am not being shown any ota for oreo or for any thing.
Is this normal.
Click to expand...
Click to collapse
Yeah, I did a fastboot flash last night. Just got the update. Just wait.
The update rolls out in batches so you just have to wait your turn

KalolParty said:
Yeah, I did a fastboot flash last night. Just got the update. Just wait.
The update rolls out in batches so you just have to wait your turn
Click to expand...
Click to collapse
What you mean is that as soon as I put official fastboot rom, I wont immediately get the OTA. I will have to wait. For eg. I am trying with August Patched Official Tissot rom now.

rajputz said:
What you mean is that as soon as I put official fastboot rom, I wont immediately get the OTA. I will have to wait. For eg. I am trying with August Patched Official Tissot rom now.
Click to expand...
Click to collapse
Stay with the December update since you'll only get OTA if you're on December update.
Just be patient. It may take a day or two or even a week but you'll get it.
Installing a fastboot ROM helps improve your chances but doesn't guarantee anything

Magisk might not work anymore after new updates :(

Oh boy, Huawei trying to screw us all over. Magisk apparently is no longer working, so no root for once a new OTA installs for Huawei devices.
https://forum.xda-developers.com/showpost.php?p=77415750&postcount=6555
https://forum.xda-developers.com/showpost.php?p=77418253&postcount=6557
New issue on Huawei Phones - Mate 10, Mate 10 Pro, P9 - Huawei roll out a new OTA called: "patch01". In the changelog is some fix mentioned (example: mms...) but the main patch is to disable the possibility of Root.
That means: if someone flash Magisk with TWRP, or flash patched_boot.img to ramdisk and reboot the phone, Phone get stuck on the splash screen: "Your device cannot be trusted..."
Only flashing back the original Huawei ramdisk.img helps to boot again to system. But no Root with Magisk is anymore possible.
Downgrade helps (if available, because for some Phones like Mate 10 it is dangerous to downgrade, if the Downgrade Firmware has another Xloader.img... but this is another story)
→ So, for Users of Huawei Phones it is better not to install OTA with Patch01 and disable Systemupdate in /system/app/HwOUC - rename HwOUC.apk to HwOUC.bak
I attach here the patch from Huawei for P9 - may you take a look, thanks
Click to expand...
Click to collapse
I have dm-verity always off (not enabled in Magisk Manager) and I have also avb disabled in /vendor/etc/fstab.ext4.hi.... and fstab.f2fs.hi.... (I have different Huawei devices)
To make the issue clearer here is another summary:
I made a Rebrand Thread for Huawei P9-EVA here: https://forum.xda-developers.com/p9/...9-eva-t3820849
The main reason for this is to allow users to unofficially update their device to Android 8 Oreo. Huawei has rolled out the Oreo OTA update in China, but has no plans to release this update outside of China. Although Oreo runs much better on the devices.
To make this possible, root is an important part, otherwise the mobile network will not work on the rebranded devices. Many users were very happy because they can now also use Oreo Treble Roms by the Open Kirin Team.
Okay → Devices rebranded to EVA-AL10 and updated to the official Oreo Firmware b528. With some modification everything is working fine.
→ Yesterday OTA Patch01 was available. I flashed the unmodified original Huawei ramdisk.img, uninstalled Magisk Manager and flashed the original EMUI Recovery. Then I agreed to the OTA update. The update was succesful installed.
After that I flashed the Magisk patched_ramdisk.img again, but the phone did not boot → it booted only with original b528 ramdisk.img
We were three people who tested it. Me and @dkionline and @zgfg We tried everything that came to our mind. → flashing first original ramdisk and kernel.img and booted to system. Then flashing patched ramdisk.img b528 with Magisk 16, Magisk 16.7 with flag "force encryption" and without "force encryption" (related to - if device is with data encrypted or data decrypted)
Flashing TWRP was not a problem, and together with the original Huawei ramdisk.img phone was able to start to system. To get Root again, we must downgraded to b528 without this Patch.
→ The Patch includes a Fix for mms and Fix for gaming (changes a Line in a local.prop) and it includes also a Kernel patch.
Looking back, we should have tested a little more. What we did not test → making dd with TWRP from ramdisk.img after the OTA Patch and then patch the "dump" ramdisk.img with Magisk. → Maybe that would have worked - we do not know it now and I do not feel like reproducing it again. But perhaps @zgfg can try this in a view days (he did not downgrade yet, because he is outside).
With this last test we could say it for sure, if the Kernel patch includes something to make Huawei Phones unbootable together with Magisk.
And coincidentally I read then in the Mate 10 forum that there also a user (with ALP-L29c636) got an OTA with a Patch01 and similar problem " I got a patch notification so I download it, rebooted and the patch installed (phone booted and I checked version and it was patch1). Cool. So then I rooted using magisk and phone was soft bricked..." : https://forum.xda-developers.com/sho...&postcount=256
My first thought was simple, Huawei is now trying to prevent root with this patch01 and much confirms this theory....
→ Bootloader Unlock Site closed
→ TrustSpace is a new App in system which definitely check and disable Root (we had this app disabled and two of us has it deleted in system)
→ Downgrade with unofficial methods become danger for hardbrick, because of two different Xloader.img in the Firmware (Mate 10)
Click to expand...
Click to collapse
Big thanks to @Tecalote for bringing this to my attention.

Not sure if this will hit the Honor 7x, it probably will. I am prepared for the worst, really hate it when Huawei does this.
Its looking like Huawei just shot themselves in the foot on this if its infact the case, there is nothing worse then developers getting middle fingered and scorned. If you think a Developer using a fork (github joke) is dangerous just wait till they nuke that commit/submit button! This is not going to bold well for honor/huawei
As i have already stated if this turns out to be Honor/Huawei out right middle fingering devs and users choice I will be looking for another phone pronto.
Click to expand...
Click to collapse

Holy shiet

Yes, i can confirm this, please do not flash that Patch01, it will make your device stuck on boot message after you flash magisk.
I'm on Huawei Nova 2s.

How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389

heindrix said:
How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
Click to expand...
Click to collapse
How can you tell if you've gotten the Patch01 update?
My phone is currently BND-L24 8.0.0.341(C567), with a July 1 2018 Android security patch.
For the link you posted im assuming id have to use "B) If the TWRP for your device has not access to encrypted /data then you can do the following:"
The site here http://pro-teammt.ru/firmware-database/?firmware_model= that has firmware doesn't seem to show 8.0.0.341? Should I use BND-L24AC567B330 (8.0.0.330) because it seems to be an update from May, and when I google my build number Huawei tweeted that it was a May security update? Or will using that brick my phone? Of the availible BND-L24 firmwares, which one should I use?
Also do I already need TWRP installed? can I do that on my unrooted device?

battleforce said:
How can you tell if you've gotten the Patch01 update?
My phone is currently BND-L24 8.0.0.341(C567), with a July 1 2018 Android security patch.
For the link you posted im assuming id have to use "B) If the TWRP for your device has not access to encrypted /data then you can do the following:"
The site here http://pro-teammt.ru/firmware-database/?firmware_model= that has firmware doesn't seem to show 8.0.0.341? Should I use BND-L24AC567B330 (8.0.0.330) because it seems to be an update from May, and when I google my build number Huawei tweeted that it was a May security update? Or will using that brick my phone? Of the availible BND-L24 firmwares, which one should I use?
Also do I already need TWRP installed? can I do that on my unrooted device?
Click to expand...
Click to collapse
You can see it in System->About.
See at Build Number section, it will be printed XXX-XXXX X.X.X.XXX(XXXPatch01).
You can use Huawei Firmware Finder : https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Go to Common Base menu, and set (click gear button) this value (G:2649 g:1699), that value is identifier for Honor 7x.
And type L24 in the search box.
After that, click on search button (magnifier glass button), you'll see all available updates for Honor 7x.
And there you go, all of firmware lists for Honor 7x L24.
I made some screenshot for you.
Enjoy.

Best path to Pie upgrade?

Picked up a Moto 6 Plus (XT1926-7, retla) last month and have been running the latest 8.0 (8.0.0_OPWS27.113-89-5) with unlocked bootloader and Magisk. Working flawless. :good:
Decided to take the plunge to Pie last night, which ended up with me have to do a full restore of a 8.0.0_OPWS27.113-89-5, then taking the OTA to 9.0
Upon successful OTA to 9.0, I then rebooted and used fastboot TWRP to try to take a clean nandroid backup. I could backup all partitions except Data (fork failure to make the rar).
I then rebooted again (still stock, no Magisk install yet), and noticed that I was getting a "dm-verity disabled" warning on my bootup screen and then a warning under System Update check that says "Updates are disable for this device due to compromised system integrity".
Have others tried the same yet? Is this "compromise" due to the unlocked bootloader, or did TWRP trip something? Is it possible to run Pie with Magisk and still be a google certified device?

Just tried again:
* Clean wipe and install to 8.0 (89-5)
* Bare bones phone config.
* enable USB Debug
* Accepted OTA Update and reboot
* Successful update to 9.0 (PPW29.116-11, patch level Dec 1, 2018)
* Play Store version 13.0.23-all [0] [PR] 227930514
* enable USB Debug
* reboot
* following warning on the blue/yellow bootup screen: "Verity mode is set to disabled"
* System Update page: "System Integrity is Compromised", "As your device system integrity is compromised, it is no longer eligible for software updates. Please contact customer service to re-program the device with official software."
EDIT:
* Magisk rooting still works: https://forum.xda-developers.com/g6-plus/how-to/3-how-to-install-root-aka-magisk-t3854244
* TWRP installer works: https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657

Can you share wich files do you use to upgrade? (Screenshot)
Sent from my Motorola moto g(6) plus using XDA Labs

RokCruz said:
Can you share wich files do you use to upgrade? (Screenshot)
Sent from my Motorola moto g(6) plus using XDA Labs
Click to expand...
Click to collapse
I used the files below to return to stock 8.0 prior to upgrade. I did not use files to upgrade to 9.0, I used the OTA system updater.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETLA/

thump said:
* TWRP installer works: https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657
Click to expand...
Click to collapse
Hmm. I would not use the twrp installer, since I haven't heard anywhere that it would work flawless with evert. Skip that and use fastboot boot twrp.img to access recovery. Do not flash. Boot.

May i ask you a question kind sir. I have the same model (G6 plus) de same oppw thingy (8.0.0_OPWS27.113-89-5) and when i hit the update button did not get any OTA. It says i have the latest version and still in november security patch. How did you trigger the OTA? Or you sideload it? Thanks kind sir

Nice to see that you had an OTA to Pie. I was about to ask where you live, because I don't have the OTA here in Belgium yet. But then I saw you have a RETLA device, so I guess I will have to wait some more!
Is the phone working well on Pie?

weazie said:
Hmm. I would not use the twrp installer, since I haven't heard anywhere that it would work flawless with evert. Skip that and use fastboot boot twrp.img to access recovery. Do not flash. Boot.
Click to expand...
Click to collapse
I've used both, but the installed one worked identically so far for backing up and installing Magisk.
The_Pacifier said:
May i ask you a question kind sir. I have the same model (G6 plus) de same oppw thingy (8.0.0_OPWS27.113-89-5) and when i hit the update button did not get any OTA. It says i have the latest version and still in november security patch. How did you trigger the OTA? Or you sideload it? Thanks kind sir
Click to expand...
Click to collapse
I'm on the retla software channel, which I believe is the first to get the Pie OTAs.
knevelsg-j said:
Nice to see that you had an OTA to Pie. I was about to ask where you live, because I don't have the OTA here in Belgium yet. But then I saw you have a RETLA device, so I guess I will have to wait some more!
Is the phone working well on Pie?
Click to expand...
Click to collapse
Yep.. purchased on Amazon in the US (I don't think they ever officially released G6+ model direct to US). So far, working smooth. Haven't found any bugs.
Should also note that even with the Verity and "not update eligible" issues, and now rooted with Magisk, it does still show as Play Store Certified.

@thump i am in the retla too. I did not get the pop up update neither via security o update section. I have the same OPWS as yours too ??

The_Pacifier said:
@thump i am in the retla too. I did not get the pop up update neither via security o update section. I have the same OPWS as yours too
Click to expand...
Click to collapse
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?

thump said:
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
Click to expand...
Click to collapse
Yes maybe... latin america is pretty wide...going to keep pressing the update button or in the case a factory reset may help or not?

thump said:
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
Click to expand...
Click to collapse
@thump Hello kind sir!! Remember me? Yes the updates are released in staggered waves, just got prompted the Android Pie update!! ?? Appreciate your help.

The_Pacifier said:
@thump Hello kind sir!! Remember me? Yes the updates are released in staggered waves, just got prompted the Android Pie update!! ?? Appreciate your help.
Click to expand...
Click to collapse
Excellent. Good luck!