Database Info

Nexus 5 with "TeamWin" failed update - and won't start again

Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!

Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.

Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.

if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.

simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.

I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.

Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.

simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?

[solved] June updates are out, but which one?

Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.

CatThief said:
[solved] Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
Click to expand...
Click to collapse
There's actually 4 different builds.
See here for what's what

Yep, I did that. There is no description there for "N" but I found out "B" is the one I want.

I always get Failed to udate, try again when installing the ota via settings.

Juli112 said:
I always get Failed to udate, try again when installing the ota via settings.
Click to expand...
Click to collapse
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.

alluringreality said:
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
Click to expand...
Click to collapse
Did you update already. I read somewhere since the may update that if you have bootloader unlocked, rooted, and another kernel you get bootloops?
Is that true? I'm still on April security update and been using stock rom, just unlocked bootloader, rooted, and using elementalx kernel

I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435

I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.

alluringreality said:
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
Click to expand...
Click to collapse
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!

Nope. twrp.img must be firstly boot into the phone, then via this temporary twrp,you can install twrp.zip from your phone.
kazemitsui said:
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse

CatThief said:
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
Click to expand...
Click to collapse
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?

TENN3R said:
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I used twrp-3.0.2-0-RC1-fastboot-sailfish.img because it was the only version that was stable for me from the start. When the January update came out I tried the current TWRP at that time (it was an RC3, can't remember the version) and while others had no problems I had an experience of my own that I'm not keen on repeating.
As for SuperSU, I installed SR5-SuperSU-v2.78-SR5-20161130091551.zip then updated to the latest 2.82 from Google Play.
I know​, newer releases may work now, but I was only going to try something newer if my "old" method failed. Like I said, I only boot to TWRP, I don't​ flash it. I just want root.

kazemitsui said:
i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
TENN3R said:
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.

alluringreality said:
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
Click to expand...
Click to collapse
I just flashed TWRP through my computer I couldn't bother trying to figure out if FlashFire will flash TWRP or not haha

8.1 developer system image

Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?

Horgar said:
Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Click to expand...
Click to collapse
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.

mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?

Horgar said:
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Click to expand...
Click to collapse
I'm not bothered with twrp recovery so did not flash the zip, but like I said I booted into twrp.img, flashed supersu and suhide and that's it. All working for me including SafetyNet. I used USB OTG for this process.

I did the same as the poster above.

just curious;
but how is Android 8.1? ?
I've found 8.0 to not be as good on battery life as 7.x.x, although I think I have mostly worked that out on my custom kernel...
any other notable goodies?
(ps: I don't care for the pixel launcher or the ambient services stuff..)

mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
I flashed factory image and I have error.

Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
Move the entire folder to a drive other than C drive. I think that might fix it.

NoobInToto said:
Move the entire folder to a drive other than C drive. I think that might fix it.
Click to expand...
Click to collapse
I did. But the error exit

Myo Thu Htet said:
I did. But the error exit
Click to expand...
Click to collapse
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.

NoobInToto said:
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
Click to expand...
Click to collapse
I did all u did ?
Yes I checked G+
Only few can install.

Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5

mannunikhil said:
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
Click to expand...
Click to collapse
Nope. It looks like Google's fault this time.

NoobInToto said:
Nope. It looks like Google's fault this time.
Click to expand...
Click to collapse
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.

mannunikhil said:
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
Click to expand...
Click to collapse
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...

NoobInToto said:
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
Click to expand...
Click to collapse
Mine was the fair test just to check if OTA zips are corrupt or not. I provided suggestions for factory image not for OTA, no point in extracting the OTA anyway. And if you had gone through all the threads you would see I mentioned I had similar issue sideload'ing OTA over 8.0.0, so that means we are sailing in same boat. OTAs had compatibility issue with 8.0.0, glad google listened and taken them off.
I still have little lag in app drawer hoping that would be fixed too in republished OTA.

Just signed up for Android beta program and got the 8.1 update for my project fi carrier unlocked Google pixel XL. The update seems to be running smoothly and everything is working so far on my device... I didn't have any issues with installation it installed just fine... Can't wait for Nov security patch supposed to be a good network feature in there in Dev settings.

I am not sure if this may help anyone trying to look at why the issues are present when trying to install:
Android 8.1 beta OTA upgrade on OG Pixel
I, just like many of you, have been experiencing OTA "installation problem" when trying to upgrade to the 8.1 beta. After reviewing comments and what worked for who, I decided to give this a shot and it worked. I am not sure if this will work for other devices (nexus or XLs) and keep in mind that you WILL lose all your data stored on the device, so back up prior to this method.
1. Be sure you are enrolled in the beta program.
2. Wait for the OTA to notify you that it's available.
3. Select "Download and Install".
4. After it has done its duty, DO NOT select "Restart and Install"
5. Go to "Factory Reset" and pull the trigger.
6. Your phone will factory reset, stating it's wiping everything, then it will install the update successfully.
NOTE: this is what worked for me. I'm unsure if it will solve all the "Installation problem" reports which have been made.
It's weird cause when I tried to factory reset, then download and install, it didn't work. Yet, downloading but NOT installing, then factory resetting worked.
After doing this I posted it here: https://plus.google.com/+ChristopherLeeMurray/posts/KDCZXbfAxLJ

You don’t need to sign up to the beta program. Just go to the Google website and download the latest 8.1 factory image. That's what I did and had no problem with flashing it. You can also delete the - w and keep your data. It's getting past the TWRP password to decrypt that I cant do. So can't flash root or recovery. Anyone managed this?

I'd prefer to be in the beta program since I'm a Android apps beta tester. I beta test everything and when it was installing it said on the screen that it's a beta version of the original software version of 8.1 which is what I believe is on Googles page and mine may have errors and defects.. the beta program gets different software than what Google usually posts. Different features and such which isn't in the official version which makes it a beta version.

June update is out! (Android 9.0.0 Build PQ1A.190105.077)

When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?

liquor said:
When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?
Click to expand...
Click to collapse
When will it end? Probably August 2020 as Essential has promised 2 years of OS updates and 3 of security updates like the Pixel. Android Q would be the last OS update, followed by a year of security updates. And August because the phone launched late August. It might get support through September. All assuming nothing happens to Essential before then.

Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip

Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?

goofball2k said:
Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip
Click to expand...
Click to collapse
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.

jxcorex28 said:
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.
Click to expand...
Click to collapse
I have TWRP installed. This is my way of doing the update.
Ensure the OTA zip and TWRP zip (optional, you can choose to install TWRP your own way) and Magisk zip (optional, only if you want to be rooted) are on the phone storage
Reboot to TWRP recovery
Select Install, then install the OTA zip file and then the TWRP recovery zip.
Reboot to system, or if you wish to have Magisk installed, flash the Magisk zip file.

knochnkopf said:
Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?
Click to expand...
Click to collapse
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install

cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
I had no issues installing the June OTA through TWRP after going back to stock May ROM from the Q Beta.
I would recommend you to back up again and start with the stock fastboot June ROM.
Good luck.
Sent from my PH-1 using XDA Labs

cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Update: Flashed OTA zip from stock recovery without loss of data. They should really make that clearer on their website because it says flashing OTA "may" result in loss of data.

knochnkopf said:
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Click to expand...
Click to collapse
I flashed the OTA via TWRP and retained all app's and the data without any problems.
Sent from my PH-1 using XDA Labs

The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.

Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy

marcdw said:
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
Click to expand...
Click to collapse
Actually I did try that, but I can't flash it due to fastboot not working unfortunately. It seems like one of my slots is corrupted.

Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
I don't use TWRP, but I was able to successfully flash Magisk-patched boot image after the latest update, so fastboot seems to be working just fine for me...

Tried Multiple Ways to get Android 10...All Result in some sort of Bootloop

So I have a rooted Pixel 3 through Magisk that I have been updating monthly up until this point via flashing the factory image with the flash.bat edited to remove "-w" from it to ensure that my phone does not become wiped after flashing each month's update. Afterwards, I would boot up the temporary TWRP image to then install the Magisk zip to re-root it. This had worked well up until this point. However, this month with the Android 10 update, this method has failed me. For this month, I did the exact same thing...download the factory image extract the image and other parts (including the flash.bat file), edit the flash.bat file and run. The issue was after flashing, the phone would try to boot and then get stuck at the G-logo with the loading bar under. It would use up about 5-10 mins to try and boot up, then fail, and then reboot again, fail again a second time and then just go fastboot mode. I tried this with both the .019 and .020 firmware and both failed me. In order to fix my phone, I'd just install the factory image of the August update instead, which had no issue.
I next attempted to ADB sideload the OTA update. I made sure to start with an unrooted install of the August update (by doing what I said above), and then using stock recovery would use ADB sideload with the new Sept OTA update. After sideloading, when trying to boot up the phone would attempt to boot around 7-9 times and just fail as it kept trying and trying to load up. Again, needed to fix it by flashing the August update.
I've done a bit of reading and it seems people have done factory resets and wipes of the phone before finally having success updating their phone to Android 10. I'm really hoping a method to fix this WITHOUT needing to do a factory wipe of my phone....

if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.

guest12233213113 said:
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
Click to expand...
Click to collapse
Are you referring to the SDK Platform tools? I was using version 29.0.2 from July for the past week until I recently saw 29.0.3 popup in the last day or so (was released a few days AFTER the factory images for Android 10 were released). Have tried with 29.0.3 and still not working. I get the issue "no valid slot to boot".

You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.

ktdt00 said:
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
Click to expand...
Click to collapse
Just tried your suggestion of flashing to both slots. Unfortunately, same result.

Toronadian said:
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Click to expand...
Click to collapse
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.

jd1639 said:
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
Click to expand...
Click to collapse
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.

Toronadian said:
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Click to expand...
Click to collapse
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.

jd1639 said:
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
Click to expand...
Click to collapse
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?

Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.

jd1639 said:
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
Click to expand...
Click to collapse
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?

Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Toronadian said:
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Click to expand...
Click to collapse
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.

Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?

Toronadian said:
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Click to expand...
Click to collapse
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.

Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Tulsadiver said:
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Click to expand...
Click to collapse
I boot the temporary TWRP image for Android 9 as it works on that. I'd assume I would use the install option with the uninstaller zip? Keep in mind currently I'm on Android 9 right now (every time I bootloop due to the Android 10 flashing not working, I run the flash.bat script to reinstall the August firmware).
And speaking of nonworking TWRP on Android 10...if for some reason magisk causes bootloop, in order to uninstall magisk, would I need to adb sideload it then?

OK seriously....really have no idea what the issue is. In TWRP on Android 9, I flashed the Magisk Uninstaller zip then attempted to run the flash.bat file to try and flash Android 10. Exact same issue before with the bootloop. Before that, I also tried flashing Android 10 after I had removed the Systemless Hosts "module" that was there (yes, I did restart the phone first after removing it), same thing with the bootloop. I have no clue.

Update Sept. 24:
Whelp, seems like people are just as out of ideas as I am. I tried today the NEW firmware Google just released (.20.C3, differs from the one released earlier in the month) as well as the newest SDK Platform Tools (29.0.4, a second update that was released in September), still not working. I installed the factory image using the edited flash-all.bat file (removing "-w") and again, device tries to boot up twice and then restart back in fastboot mode, with the issue being "no valid slot to boot".
EDIT: Re-flashed August firmware back onto the phone, and then tried to sideload the new .20.C3 firmware as a OTA (yes, I made sure to use the OTA zip and not the factory image), now just continuously bootlooping. I think I'm on bootloop #5 or 6 right now.

FINALLY have a positive update. I have Cerberus, an anti-theft app on my phone that I tried to uninstall just for the sake of trying to see if some apps were causing compatibility issues. I was trying this after reading one of the really long threads on the Google support threads that someone managed to get the Android 10 update to work AFTER removing some apps. After taking some time to finally remove Cerberus for the time being, I once again tried to flash the factory image for Android 10 (the newest one, .20.C3) and it ACTUALLY managed to work. I'm now finally on Android 10.
With my own device finally figured out, I think I may give my wife and dad's devices a try to update to Android 10 (they're on Pixel 2 and 2XL respectively). I installed Cerberus on their devices as well and I think I'm gonna try removing that first and seeing if that manages to allow me to update the Pixel 2 and the 2XL to Android 10.