Database Develop

Android 4.4 KitKat installation failed on nexus 7 (2012)

Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks

Mob_Dev said:
Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks
Click to expand...
Click to collapse
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
OTAs will never work on a system which is modified in some way, because they contain only bytes which were changed between two Android versions. If files on the device are changed (custom ROM, different kernel, MultiROM-injected init, sometimes even root), OTA simply can't be applied. Everyone who roots his device should be aware of that.
Wait for the flashable ZIPs,
Click to expand...
Click to collapse
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi

topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
Aha, i see. So maybe because i've rooted my nexus 7, and i've also got a different kernel for MultiRom( I've installed ubunto touch on my device). ... Those the reasons that leads the installation to be failed?
Anyway, my system auto downloaded the update, it name was "nakasi".
I tried to go to Recover mode, and tried to flash the nakasi ZIP file and flash it,,, but the operation was failed!
What should i do?
How i get auto update installation for kitkat on my nexus 7?
Another question, if i downloaded the Factory image from the link you gave me: https://developers.google.com/android/nexus/images#nakasi and flash it in Recovery Mode... Let say it will success? then i''ll lose auto system update on my nexus in future - because it will be installed manually.
=========
Please Copy the questions in your reply, and post the reply below each one.
Thanks

You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).

topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app

khaytsus said:
You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).
Click to expand...
Click to collapse
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?

Another 4.4 Upgrade failure
I am having problems with the OTA upgrade too. However I am running a unmodified/rooted version of 4.3. I have also tried sideloading the factory zip and doing OTA and sideload from a factory reset.
I get the dead android and red triangle error and if I go to the restore menu then this is the error report I get each time
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/system/apps/hangouts.apk produces some type of verfication error.
I can then reboot and I am back to 4.3
Any thoughts on solutions are gratefully recieved

Mob_Dev said:
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?
Click to expand...
Click to collapse
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom

dbgeek said:
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.

yusopa said:
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom
Click to expand...
Click to collapse
I am following this guide to install Android kitkat on my nexus 2012 (Wifi only): http://www.droidviews.com/install-kitkat-factory-image-on-nexus/
But if you can see the last step satisfy that i need to flash the 4.4 Factory Image, type, using the following command:
fastboot -w update image-nakasi-krt16s.zip
Click to expand...
Click to collapse
The problem is that, the nakasi file i downloaded from here: https://developers.google.com/android/nexus/images
is not a ZIP file!. It's (.tar) file. And i can't process that command!!
Let me know what is the problem.
Thanks in advance

topet2k12001 said:
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.
Click to expand...
Click to collapse
My bad. I read the "different kernel..." as an example of mods that might be made, that could cause failure, not a specific listing of mods that would cause a failure (implying that if the mod's not on the list then it wouldn't be a problem).

So i have the same problem, but aditionally my Windows 8 is unable to recognize my Nexus 7 while in recovery mode and i can't mount the sdcard to install a new rom. Only recognizes it as "grouper". Any advice?

I think Wug Fresh for nexus toolkit can help you guy to bring back your nexus to life. I use from the start.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Switching to FI with rooted Nexus 6

I have an unlocked, rooted (Chainfire SuperSU) Nexus 6 running LMY48I with TWRP as recovery. Today, my Google FI SIM card is arriving in the mail. I would like to do the following:
* Switch to LVY48E (5.1.1 for FI)
* Ensure the resulting ROM is rooted
* Avoid losing existing apps and settings
My plan is to perform the following in order:
* Download LVY48E (shamu-lvy48e) from the Google factory images site to my laptop
* Boot to bootloader
* Flash the radio.img with fastboot
* Reboot to bootloader
* Flash the boot.img with fastboot
* Reboot to bootloader
* Clear the caches with fastboot
* Flash system.img with mfastboot (have had problems with large files previously)
* Flash cache.img with fastboot
* Power down
* Insert new FI SIM card
* Boot normally
* Reboot to TWRP recovery
* Root the device with TWRP
* Reboot normally (all done)
In the steps above, I am not flashing recovery.img (to maintain TWRP) and not flashing userdata.img (to keep my existing apps and settings).
Does the above sound like a sensible plan of attack? Am I inserting the SIM card at the right point? There was information on other forum posts about allowing the phone to boot normally once without using TWRP to root so the system partition is set up properly and then rooting on the next boot. Is that right? And finally, TWRP has previously given me an option to fix the system partition after I have flashed prior factory images. Should I allow it to do that? What is it fixing?
Much obliged, looking forward to enjoying a Nexus with FI! And thanks to XDA for such a great resource and for all the time everyone has put into making these flashes a less intimidating process for novices like me.
- Saschter

You can just power off, put the sim in, power on and download the Project Fi app the way you are now. Or are you just wanting to start fresh for some reason?

obtained said:
You can just power off, put the sim in, power on and download the Project Fi app the way you are now. Or are you just wanting to start fresh for some reason?
Click to expand...
Click to collapse
Thanks for the quick response. I assumed that I needed the full blown FI android factory image (or at least the radio) and that OTA would not work since I am rooted. There is simply an app to install? Is that the only difference between LMY48I (5.1.1 AT&T) and LMY48E (5.1.1 FI)? If yes, that is great news.
Saschter

Similar question. I'm on T-mo LYZ28J 5.1.1. Do I need to flash the Fi rom to get full support for Fi? My guess would be yes, but I'm asking anyway.

Saschter said:
Thanks for the quick response. I assumed that I needed the full blown FI android factory image (or at least the radio) and that OTA would not work since I am rooted. There is simply an app to install? Is that the only difference between LMY48I (5.1.1 AT&T) and LMY48E (5.1.1 FI)? If yes, that is great news.
Saschter
Click to expand...
Click to collapse
Fi should activate and work just fine on both of those builds. Pure Nexus is great and works very well with Fi if that's something you would want to do.
Groid said:
Similar question. I'm on T-mo LYZ28J 5.1.1. Do I need to flash the Fi rom to get full support for Fi? My guess would be yes, but I'm asking anyway.
Click to expand...
Click to collapse
Fi should work fine LYZ28J. I'm not too sure of it, but I think if you wan't the best customer support from the Fi support team, they would recommend using the Fi factory image, but most other builds work just fine with Fi.

obtained said:
Fi should activate and work just fine on both of those builds. Pure Nexus is great and works very well with Fi if that's something you would want to do.
Fi should work fine LYZ28J. I'm not too sure of it, but I think if you wan't the best customer support from the Fi support team, they would recommend using the Fi factory image, but most other builds work just fine with Fi.
Click to expand...
Click to collapse
Thanks so much @obtained. If we do want to flash to the FI ROM, do the above steps sound reasonable? FWIW, I will try first with my existing ROM and see how that goes.
Thanks again,
Saschter

Saschter said:
Thanks so much @obtained. If we do want to flash to the FI ROM, do the above steps sound reasonable? FWIW, I will try first with my existing ROM and see how that goes.
Thanks again,
Saschter
Click to expand...
Click to collapse
The above steps should work flawlessly.

No need for all the reboot to bootloaders or the mfastboot.

obtained said:
The above steps should work flawlessly.
Click to expand...
Click to collapse
Scwheeet. Thanks.
Saschter

prdog1 said:
No need for all the reboot to bootloaders or the mfastboot.
Click to expand...
Click to collapse
Good to know. Thanks. I have had to use mfastboot in the past as flashing the image (or the full zip file) results in a buffer overflow error with vanilla fastboot (even the latest version from the platform tools). The only reliable way I have handled truly large files to flash (at least for Motorola) devices has been mfastboot, but will try again and let you know.
Thanks,
Saschter

Saschter said:
Good to know. Thanks. I have had to use mfastboot in the past as flashing the image (or the full zip file) results in a buffer overflow error with vanilla fastboot (even the latest version from the platform tools). The only reliable way I have handled truly large files to flash (at least for Motorola) devices has been mfastboot, but will try again and let you know.
Thanks,
Saschter
Click to expand...
Click to collapse
Never have used mfastboot so don't know. I just use the one in SDK.

Just to wrap this thread up. I did not need to flash to enable my rooted (nearly stock) 5.1.1 to use FI. As indicated earlier, simply inserting the SIM card, powering up, downloading the Project FI app and then following the instructions in the app were enough to get everything working. (Note, it took 40 minutes or so for AT&T to switch my cellular over to the new SIM).
I separately then flashed everything as indicated in the beginning of this thread. The only gotcha was that TWRP had to be re-flashed (not sure why, since I did not flash recovery.img). However, that was relatively painless. Then rooted via TWRP, ran the SuperSU re-install process, then rebooted and all is now well.
Thanks to everyone who replied.
- Saschter

Saschter said:
Just to wrap this thread up. I did not need to flash to enable my rooted (nearly stock) 5.1.1 to use FI. As indicated earlier, simply inserting the SIM card, powering up, downloading the Project FI app and then following the instructions in the app were enough to get everything working. (Note, it took 40 minutes or so for AT&T to switch my cellular over to the new SIM).
I separately then flashed everything as indicated in the beginning of this thread. The only gotcha was that TWRP had to be re-flashed (not sure why, since I did not flash recovery.img). However, that was relatively painless. Then rooted via TWRP, ran the SuperSU re-install process, then rebooted and all is now well.
Thanks to everyone who replied.
- Saschter
Click to expand...
Click to collapse
So were you able to flash system with fastboot or did you use mfastboot? When I flashed the T-mo LYZ28J it failed with fastboot, but flashed with mfastboot. Maybe I don't have the latest fastboot. Anyone who flashed system with fastboot, please let me know the version of fastboot. Mine is March 13,2015 @ 196,608 bytes.

Groid said:
So were you able to flash system with fastboot or did you use mfastboot? When I flashed the T-mo LYZ28J it failed with fastboot, but flashed with mfastboot. Maybe I don't have the latest fastboot. Anyone who flashed system with fastboot, please let me know the version of fastboot. Mine is March 13,2015 @ 196,608 bytes.
Click to expand...
Click to collapse
Flashed with mfastboot as well. Have never been able to flash on my Nexus 6 with vanilla fastboot, even the most recent version from platform-tools.
Saschter

Stock Nexus 6 (Verizon) will not update!

Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!

Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.

PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.

lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images

simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"

Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions

PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.

BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.

gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.

is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?

MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.

Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?

MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.

Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.

Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk

Manual OTA update for rooted device

The phone that I would like to update is a Moto G6, type M390A. The phone is currently running Android 8.0.0, build OPS27.104-92. The phone is rooted, stock ROM, and has TWRP and Magisk installed.
Earlier today, I followed the instructions here https://highonandroid.com/android-howtos/how-to-ota-update-rooted-pixel-phones-without-computer/ to update my Pixel 3XL. The instructions were almost flawless – the only two minor ‘gotchas’ were 1) having to first update to the most recent version of TWRP (when I tried the version that was a few months old, I received a kDownloadPayloadPubKeyVerificationError) and 2) I had to reinstall Magisk after the reboot mentioned in Step 9. Bottom line – the process went quickly and easily. Needless to say, all of my apps, settings, and data were unaffected by the upgrade.
I am hoping that the experience with the Moto G6 might be as smooth and easy. However, there are three differences of some concern:
The OTA zip file is not from the Motorola site – I found what appears to be the proper file here: https://www.skyneel.com/moto-g6-pie - I selected the ‘Download Moto G6 Pie Android 9.0 OTA ROM’ link.
The TWP file is only available as a .img file, not a zip file.
For the Pixel 3XL, the OTA was a minor version upgrade as it was already running Android 9; for the Moto G6, this would be a major version upgrade.
My question for the group is simply this: Using the files mentioned above, if I follow the procedure described in the first link; namely copy ota.zip, magisk.zip, and twrp.img to the phone; reboot to TWRP and install, in order, OTA, TWRP, and magisk; and then reboot; will I likely succeed in updating the phone while not messing up my data, settings, and data?
Thank you.

There are a bunch of g6's. Trying to apply an OTA at random will fail. Your pixel has a/b partitions, g6 does not. A only.
The best way I know to update a Moto is, make sure you know your exact model number, and update channel. Both can be found in about phone section in settings. Download a full firmware package (not an update zip) and either
1. Extract it and flash every partion with fastboot
Or
2. Use RSDlite (windows PC program) and flash the firmware with that. Then flash TWRP again (or just boot it) and flash magisk.
I prefer option 2. Easy peasy. And RSDlite will ask if you want to use flashfile.xml (wipes data) or the servicefile.xml (doesn't wipe data.
RSDlite basically performs all of the fastboot flashes for you, and the servicefile skips the data format.
Even if you restore 5je stock recovery, most attempts at trying to flash an OTA zip will fail. You may have made some changes to the system at some point which will trigger an assert prop failure.
Plus the OTA would have to be for your specific g6.
Someone else may chime in with different instructions.
But this is not a Pixel. There are like 20 something different g6's and update channel combos.

madbat99 - I appreciate your taking the time to provide a thorough reply, thank you. Sadly, I still have questions: Following is a screen grab of the About Phone tab.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You indicated that I need:
Exact model number: It appears to simply be moto g6
Update channel: I see a 'Software channel' - is this the same thing?
When I went looking for firmware, I found this page https://www.getdroidtips.com/moto-g6-plus-play-stock-firmware/, but
Android 9.0 is not shown as being available (but other sites suggest that at least a beta version has been released)
I do not see the existing build listed, thus I am worried that none of these are correct
Would you please be so kind as to point me directly to an appropriate source of firmware files for this phone?

groston said:
madbat99 - I appreciate your taking the time to provide a thorough reply, thank you. Sadly, I still have questions: Following is a screen grab of the About Phone tab.
You indicated that I need:
Exact model number: It appears to simply be moto g6
Update channel: I see a 'Software channel' - is this the same thing?
When I went looking for firmware, I found this page https://www.getdroidtips.com/moto-g6-plus-play-stock-firmware/, but
Android 9.0 is not shown as being available (but other sites suggest that at least a beta version has been released)
I do not see the existing build listed, thus I am worried that none of these are correct
Would you please be so kind as to point me directly to an appropriate source of firmware files for this phone?
Click to expand...
Click to collapse
So your software channel is fi. Not sure where to get that one. Clicking on hardware in that menu gives you your model number. Under SKU. See in screenshot. I'll look for a firmware for you.

Forgot screenshot

You have a Google fi device. It doesn't appear pie is available for yours yet. It will be, I would wait if I were you.
here are the currently available firmwares for your model. There are ones that have been updated to pie, and one or more of those may be able to be flashed to your phone. I don't know what that would do to your fi eligibility/connectivity. So someone else will have to chime in on that.
The 2 firmwares on that page are newer than what you are on. Newer security patch updates than you have now. Good.
Now if you want pie, skip to the bottom of your thread here!

@groston
I found this post, where a member with the fi version of the g6 that says he flashed the pie firmware for the retail g6 and all went well. I will also link the post that he mentions which contains the flashfile.

madbat99 - again, thank you! The version for this phone is PVT1, SKU XT1925-6.
In your opinion, can I use the zip file linked in the post your cited with the RSDlite process you outlined, specifically using the servicefile.xml approach? The SKU for the phone the poster mentioned is XT1925-5 reteu - close, but the same?

Here is the post with instructions and links to everything you need. It's official Moto firmware, so no "need" to even have an unlocked bootloader (but I'm sure yours is already unlocked).
So now you have a couple options. you can either update to the newest Oreo security patch for your device, or update to pie if you like.
---------- Post added at 09:16 PM ---------- Previous post was at 09:06 PM ----------
groston said:
madbat99 - again, thank you! The version for this phone is PVT1.
In your opinion, can I use the zip file linked in the post your cited with the RSDlite process you outlined, specifically using the servicefile.xml approach?
Click to expand...
Click to collapse
Yes you can use RSDlite to flash it if you want.
But... With the jump from Oreo to Pie, and switching software channels, I would recommend a data wipe. Meaning the flashfile in RSDlite.
You can try without the data wipe, then if something doesn't work properly for you you can always wipe data afterwards.
@groston do you have RSDlite?
Guess I might as well grab you link for that too, lol
I realize that the bulk of that post was from a RETEU version, but the person quoting it said they have the fi version and it worked.

Here is the RSDlite I use (plus a bunch of other useful programs). Check my screenshot, I circled the one you want.
One last thing, you might want to pop in to the thread I linked and ask others about flashing it on the fi version. Just so you cross all the t's and dot all the i's.

groston said:
madbat99 - again, thank you! The version for this phone is PVT1, SKU XT1925-6.
The SKU for the phone the poster mentioned is XT1925-5 reteu - close, but the same?
Click to expand...
Click to collapse
This is the part that I saw that related to your phone.

I asked Google Fi tech support if they could point me to a firmware version for the fi software channel. Here is there (not terribly helpful) reply:
I see that you'd like to update OS to Android 9.0 on your Moto G6. Please know that we only control updates of Android One model devices such as Moto X4 and Pixel Designed for Fi phones. For devices such as Moto G6, LG V35 and LG G7 users need to check with the OEM. Therefore, I'll provide you the manufacturer contact details. They'll definitely help you with the update.
We've looked into all possible options to provide you the firmware file. However, I'm sorry to say that we didn't find any firmware file which can be used to update OS to Android 9 on your Moto G6. Please be assured, Motorola will help you with the OS update.
Click to expand...
Click to collapse
I will follow madbat99's suggestions...

General June update finally :)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So? Did it finish? It's your Pixel "better" now?

I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.

gerhard_wa said:
I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.
Click to expand...
Click to collapse
Forget about real OTA. Install full OTA files or factory images (if rooted or not) via Pixel Flasher. Download the files here:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
And use PF...
Releases · badabing2005/PixelFlasher
Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.
github.com
No waiting for hours on the OTA, all work on PC, only dl time for the big files.

justDave said:
So? Did it finish? It's your Pixel "better" now?
Click to expand...
Click to collapse
Lol, I never see a difference

t-ryder said:
Forget about real OTA. Install full OTA files or factory images (if rooted or not) via Pixel Flasher.
Click to expand...
Click to collapse
Pixel Flasher only works with unlocked bootloaders though.

justDave said:
Pixel Flasher only works with unlocked bootloaders though.
Click to expand...
Click to collapse
You can sideload the Full OTA with a locked bootloader with Pixel Flasher.

justDave said:
Pixel Flasher only works with unlocked bootloaders though.
Click to expand...
Click to collapse
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...

ldeveraux said:
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...
Click to expand...
Click to collapse
IDK, but last time I offered a handful of Pixel owners a workaround that needed root (or at least an unlocked bootloader), I got no takers.

ldeveraux said:
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...
Click to expand...
Click to collapse
Couldn't agree more. The ease of unlocking, flashing, rooting etc without warranty implications is my favorite Pixel feature.

gerhard_wa said:
I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.
Click to expand...
Click to collapse
Stock System Update = 2 hours
Downloading OTA image file and manually flashing (PixelFlasher or sideload in Recovery Mode) = less than 20 minutes
Hell...with an unlocked bootloader, the non-OTA Full Factory image takes less than 20 minutes when manually flashing in CMD
Stock System Update < sideloading/PixelFlasher

simplepinoi177 said:
Stock System Update = 2 hours
Downloading OTA image file and manually flashing (PixelFlasher or sideload in Recovery Mode) = less than 20 minutes
Hell...with an unlocked bootloader, the non-OTA Full Factory image takes less than 20 minutes when manually flashing in CMD
Stock System Update < sideloading/PixelFlasher
Click to expand...
Click to collapse
I updated the factory image for June on my Pixel 7 in 134 seconds using Pixel Flasher. Full device backup (apps/app data/data), using Pixel Flasher to update and re-root, flashing custom kernel in FKM... on my Ryzen 3900X machine with M.2 SSDs it's all together like 15 min. for me. Since having the Pixel 7 I tested real OTA like once, and it took hours. Bananas.

Does this update fix the AVRCP issues with this phone's bluetooth?

t-ryder said:
I updated the factory image for June on my Pixel 7 in 134 seconds using Pixel Flasher. Full device backup (apps/app data/data), using Pixel Flasher to update and re-root, flashing custom kernel in FKM... on my Ryzen 3900X machine with M.2 SSDs it's all together like 15 min. for me. Since having the Pixel 7 I tested real OTA like once, and it took hours. Bananas.
Click to expand...
Click to collapse
exactly...
honestly...most of that "under 20 minutes" stuff is downloading the 2.6GB image, extracting it, copying it over to the platform-tools folder....
and that's me doing everything manually; i've never used PixelFlasher, but I imagine badabing2003 streamlined it so the GUI/program just points to the image files than needing it to be in the same folder....
Before I convinced my wife to allow me to root her P7P, I did the real OTA once with it and it was nails on a chalkboard as I was manually flashing my rooted P7P -- again, not that one needs a rooted device to sideload an OTA; which is still considerably faster than using the stock System Update...

Still haven't received the OTA update.
Pixel 7, purchased from Google, on AT&T.

this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?

Albirew said:
this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?
Click to expand...
Click to collapse
Did you install the latest OTA over GrapheneOS? Was that a GrapheneOS OTA or the Google OTA the rest of us are talking about?

justDave said:
Did you install the latest OTA over GrapheneOS? Was that a GrapheneOS OTA or the Google OTA the rest of us are talking about?
Click to expand...
Click to collapse
It was GrapheneOS OTA of course =) , but update content is the same (QT3A)

Albirew said:
this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?
Click to expand...
Click to collapse
Magisk works fine on June stock update.

Lughnasadh said:
Magisk works fine on June stock update.
Click to expand...
Click to collapse
Thanks.
Since it's a GrapheneOS specific issue, I started my own thread.