Database Develop

Nexus 6 Official June OTA flash help !!

Guys i have nexus 6 but i am not getting any OTA since April , last time i got April security patch (7.0.0 NBD92G)
but when i check on https://developers.google.com/android/ota it shows OTA images till june so
how can i flash that OTA image ?? i have lock bootloader and is there any chance of phone brick ??

Do a Google search for sideloading ota images. It's actually pretty easy. I'm unlocked running a rom so I can't give you a step by step off the top of my head.

nissan skyline said:
Guys i have nexus 6 but i am not getting any OTA since April , last time i got April security patch (7.0.0 NBD92G)
but when i check on https://developers.google.com/android/ota it shows OTA images till june so
how can i flash that OTA image ?? i have lock bootloader and is there any chance of phone brick ??
Click to expand...
Click to collapse
The instructions are on the download page for the OTA and I have pasted them below. You don't need an unlocked bootloader and there is always a chance that something could go wrong when flashing your phone but this method seems pretty safe.
To update a device using one of the OTA images below, you need the latest adb tool. You can get it from the Android SDK Platform-Tools package, which you can download here.
Don't forget to either add adb to your PATH environment variable or change into the directory containing the executable.
Also be certain that you've set up USB access for your device, as described in Run Apps on a Hardware Device.
To apply an OTA update image:
Download the appropriate update image for your device below.
Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
With the device powered on and USB debugging enabled, execute:
adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device instead, and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
For security, you should disable USB debugging when the device is not being updated.

Were you able to sideload the OTA? I tried on the 8th but got an error -- footer error. I'm on 7.1.1 and attempted to load N6F27E.

Adb sideload
I tried same method. Kept getting various errors.
Finally, I gave in. Phone needed to be cleaned out anyway. So, I used wugs.. Unlocked and rooted
I then used flashfire to go from 7.0 to 7.1.1 to 7.1.1 June.
Did not want to take chances. So just did updates in monthly order. I used the flash zip or ota option.
Everything went perfect. Done in five minutes.
Now, obviously. You can always relock and unroot w wugs. But, I left it alone. Hope this helps.

I also have a rooted nexus 6 via Wugs toolkit but I'm stuck on 7.0. where did you get the zip for 7.1? im relatively new too root exploration. Also idk if this is the right forum to ask this but while I'm here i was also curious if anyone has had any lagging, wifi and some blue tooth issues running 7.0 & if 7.1 is any better of experience.? Thanks for your time and consideration!!

Here is a link to gdrive with ota zips. Not reall great at this. So, hopefully you can download. I have not experienced any of the issues you have. None https://drive.google.com/drive/folders/0B1PLXsZI0UyjTGJEVDFaRy1ITms?usp=sharing

Liftkit said:
I also have a rooted nexus 6 via Wugs toolkit but I'm stuck on 7.0. where did you get the zip for 7.1? im relatively new too root exploration. Also idk if this is the right forum to ask this but while I'm here i was also curious if anyone has had any lagging, wifi and some blue tooth issues running 7.0 & if 7.1 is any better of experience.? Thanks for your time and consideration!!
Click to expand...
Click to collapse
https://developers.google.com/android/ota
Edit:I see that this URL already appears in the first post. Hmmm...
Sideloading the OTA is by far the simplest way of upgrading. You keep everything - data, apps, etc. You lose root, but that's easy to reinstall.

I'm currently on N6F26Q. Could I jump straight to June OTA or do I need to downgrade to 7.0 and then go back to 7.1.1 N6F27E?

NCtwin said:
I'm currently on N6F26Q. Could I jump straight to June OTA or do I need to downgrade to 7.0 and then go back to 7.1.1 N6F27E?
Click to expand...
Click to collapse
OTAs are complete packages. You can sideload the latest one directly.

Maybe that's why I keep getting an error when trying to use Wug to update. I'll do the sideload option and see what happens. Thanks a lot.

I went to the downloads page and my bill number nbd92g ends at 7.0 any suggestions?
---------- Post added at 08:28 PM ---------- Previous post was at 08:13 PM ----------
pckarma112 said:
I tried same method. Kept getting various errors.
Finally, I gave in. Phone needed to be cleaned out anyway. So, I used wugs.. Unlocked and rooted
I then used flashfire to go from 7.0 to 7.1.1 to 7.1.1 June.
Did not want to take chances. So just did updates in monthly order. I used the flash zip or ota option.
Everything went perfect. Done in five minutes.
Now, obviously. You can always relock and unroot w wugs. But, I left it alone. Hope this helps.
Click to expand...
Click to collapse
what is your build #

Liftkit said:
I went to the downloads page and my bill number nbd92g ends at 7.0 any suggestions?
---------- Post added at 08:28 PM ---------- Previous post was at 08:13 PM ----------
what is your build #
Click to expand...
Click to collapse
Take a backup and then sideload N6F27H, Jul 2017. You lose nothing, you boot back into pretty much what you had before, but with security enhancements and a few minor feature improvements.
And before you do any more, read my first sentence again.

November update

https://developers.google.com/android/ota
I've update via adb.
Swiping via Soli seems much improved for me when using the music player.

What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.

ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
I followed the below steps. This is assuming you are already rooted on October patch level and want to maintain root.
1) Downloaded the factory images for the Nov update (https://developers.google.com/android/images) to the PC.
2) Extracted the zip file (make sure to extract the zip file inside the first one. That zip contains the .img file which we will need in step 4 ).
3) Edited the flash_all.bat file to remove '-w' parameter so that the data is not wiped.
4) Copied the 'boot.img' to the phone and used magisk manager to patch the boot file (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching).
Copied the patched 'magisk_patched.img' from the phone to the PC.
NOTE: I also disabled all magisk modules before the next steps. This is just to ensure that custom module don't mess up the update (have seen this with the Oneplus 7 PRO android 10 update when i had that device)
5) Reboot phone into bootloder and connect to PC
6) Flashed the update by running the flash_all.bat file (make sure to remove the '-w' parameter before flashing so that DATA is not wiped). I did run into issue where the vendor.img failed at flashing but a change of USB cable fixed that (I have seen this issue before. some cables just don't work in fastboot/adb).
7) Once the flashing completes the phone reboots and does some update after booting up.
8) Again reboot into bootloader. Flash the boot with the 'magisk_patched.img' that was copied in step 4.
Code:
fastboot flash boot magisk_patched.img
I always flash it on both the a & b partitions by using below command.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
9) Reboot the phone. At this point you have ROOT with Magisk and your custom kernel would be gone since stock/patched boot.img would have replaced it. You can re-flash your kernel (make sure the kernel has been updated for the November security update). Also at this point you can enable any modules that you may have disabled before the update.

I got november update now from ota..

Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
meek2100 said:
Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
Click to expand...
Click to collapse
Actually I just found the answer here: https://support.google.com/pixelphone/thread/18553639?hl=en
Pixel 4 (XL):
US (ATT & Verizon): QD1A.190821.014.C2
US (TMobile, Sprint, Google Fi) & UK carriers: QD1A.190821.014
All other carriers (AU/JP/CA/TW/US): QD1A.190821.007.A3

ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
The post above (post #3) that says to use the factory image isn't wrong, but it isn't the easiest method either.
You can side-load the OTA image. You can do this on a phone with a locked or unlocked bootloader and you don't need to modify any files to prevent it from wiping the phone. It's just like the OTA update and will not wipe the phone.
You can find the files and directions directly from Google. https://developers.google.com/android/ota
Once the update is done, you will need to reroot the phone using the standard modified boot image method and then reflash your custom kernel (after making sure it has been updated to the latest OTA version). Just be aware that while the actual flashing time is much shorter than taking the OTA normally, it may have to optimize all of the apps during the initial boot. Unfortunately it doesn't give you any indication this is going on (unlike during a normal OTA update) and therefore people tend to get impatient and reboot during the initial boot. Don't do this. Just be patient and let the phone do it's thing. My phone took about 20 minutes to boot initially after side-loading the Nov update because I have a decent number of apps that it had to optimize.

Oops, nevermind. fixed

How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.

Spookymyo said:
How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.
Click to expand...
Click to collapse
Instructions here
https://developers.google.com/android/ota

Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?

xxaarraa said:
Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?
Click to expand...
Click to collapse
Pure speculation on my part, but I wonder if Google didn't tweak the auto-white balance due to the complaints about how the phone handled white balance in pictures with a predominantly red color.

Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Sent from my Pixel 4 using Tapatalk

BubbaGumprc said:
Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Click to expand...
Click to collapse
I had the same issue, the check update function did not work on my P4. It was working great on my P3.

Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.

sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed

sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine

Does this undo the tweak to get Google pay to work with magisk? Or will we have to re do it?

ahsank128 said:
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed
Click to expand...
Click to collapse
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
thehartk said:
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine
Click to expand...
Click to collapse
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.

sn0warmy said:
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Look here: https://support.google.com/pixelphone/thread/18742521?hl=en

sn0warmy said:
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Yes flash the .007.A3 if you were on the .007 before. I went through the same problems with the .014 too but .007.A3 fixed it.

December update issue

I am struggling trying to get the December update installed. Originally, I unlocked my bootloader, applied the November update, rooted the phone and installed the Floral kernel. Everything was working great. Since then I tried to install the latest version of the kernel and almost bricked the phone right away. I was able to get back on the November update, now I have the November update running, version 10.0.0 (QD1A.190821.014.C2, Nov 2019). I have not rooted or installed a custom kernel. I still have an unlocked bootloader. All I want to do now is install the December update, but when I install this version 10.0.0 (QQ1B.191205.011, Dec 2019, EMEA carriers, T-Mobile (US), Google Fi) - I have a "Google Fi" Pixel 4 XL purchased from the google store.. I can get it to load to the setup screen but I completely use touchscreen ability so the phone is useless.. My question is - Which December update is correct for my phone ? I am thinking it could be the next file under that one - 10.0.0 (QQ1B.191205.012.A1, Dec 2019)... But I am hesitant to attempt flashing a file I am unsure of. I have read that the reason I cant use the touchscreen is because the boot.img is different. I pushed the boot.img and pfpt.img (or whatever it is called) from that factory image and still it did not work. At this point I am almost ready to return it to bone stock out of frustration. Please advise how to verify what the correct file is, or the most simple method to get the update running. Thank you !
TL;DR
Would like december update installed - having a hard time figuring out the correct factory image to use or getting it to work correctly

The first build would be correct for you on Google Fi. Don't know why you're having touchscreen issues.
Are you trying to maintain root? If so, flash the factory image with the -w flag removed from the flash-all.bat. Also, make sure you disable Magisk modules if you have any installed, before flashing the factory image.
If you want to start fresh, leave the flag alone and just flash the image.
Edit: Didn't see that you aren't even rooted or anything in your wall of text.
Either way, since you're having issues, best to clean flash and start over. Once your running properly, I'd say read everything in the forums to get a grasp of everything before doing anything to modify the phone again.

subarubdub said:
I am struggling trying to get the December update installed...
...having a hard time figuring out the correct factory image to use or getting it to work correctly
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...-10-q-root-t3996969/post80774791#post80774791
In the guide above read Prerequisites, and #1, then do #4 to install factory image, then #9 to root/reroot
If you are reading the guide with the XDA app tap the three dots (on the top right) select open in browser.

subarubdub said:
I am struggling trying to get the December update installed. Originally, I unlocked my bootloader, applied the November update, rooted the phone and installed the Floral kernel. Everything was working great. Since then I tried to install the latest version of the kernel and almost bricked the phone right away. I was able to get back on the November update, now I have the November update running, version 10.0.0 (QD1A.190821.014.C2, Nov 2019). I have not rooted or installed a custom kernel. I still have an unlocked bootloader. All I want to do now is install the December update, but when I install this version 10.0.0 (QQ1B.191205.011, Dec 2019, EMEA carriers, T-Mobile (US), Google Fi) - I have a "Google Fi" Pixel 4 XL purchased from the google store.. I can get it to load to the setup screen but I completely use touchscreen ability so the phone is useless.. My question is - Which December update is correct for my phone ? I am thinking it could be the next file under that one - 10.0.0 (QQ1B.191205.012.A1, Dec 2019)... But I am hesitant to attempt flashing a file I am unsure of. I have read that the reason I cant use the touchscreen is because the boot.img is different. I pushed the boot.img and pfpt.img (or whatever it is called) from that factory image and still it did not work. At this point I am almost ready to return it to bone stock out of frustration. Please advise how to verify what the correct file is, or the most simple method to get the update running. Thank you !
TL;DR
Would like december update installed - having a hard time figuring out the correct factory image to use or getting it to work correctly
Click to expand...
Click to collapse
Go by the recommended factory image based on your carrier found here...https://support.google.com/pixelphone/thread/21769134?hl=en
You may have indeed already flashed the correct one, or maybe not, but it appears you have. Also, have you tried switching to your inactive slot, and flashed it again? I would at least try that before anything else to see if you get your touch input back.

ilal2ielli said:
The first build would be correct for you on Google Fi. Don't know why you're having touchscreen issues.
Are you trying to maintain root? If so, flash the factory image with the -w flag removed from the flash-all.bat. Also, make sure you disable Magisk modules if you have any installed, before flashing the factory image.
If you want to start fresh, leave the flag alone and just flash the image.
Edit: Didn't see that you aren't even rooted or anything in your wall of text.
Either way, since you're having issues, best to clean flash and start over. Once your running properly, I'd say read everything in the forums to get a grasp of everything before doing anything to modify the phone again.
Click to expand...
Click to collapse
Ive been rooting and playing with android phones since my G1. This is suddenly an issue for me haha, I think it was my platform tools or something.. a few things in my android studio needed updating. Now It is working ! thanks for the help everyone.. :silly:

March - Broken Face Unlock

I was on the January patch, unrooted, sideloaded the new March update(with -w taken out of the sh and bat files) then booted up and patched the boot file with magisk, rebooted to flash patched boot and when I finally got back in and started checking my apps for functionality, I noticed the face unlock was being slow. I deleted my face unlock and went to reregister and got the error "Enrollment was not completed. Face enrollment didn't work."
I tried deleting all security from the phone and rebooting to readd, but I still get the error.
Ideas?

ibphantom said:
I was on the January patch, unrooted, sideloaded the new March update(with -w taken out of the sh and bat files) then booted up and patched the boot file with magisk, rebooted to flash patched boot and when I finally got back in and started checking my apps for functionality, I noticed the face unlock was being slow. I deleted my face unlock and went to reregister and got the error "Enrollment was not completed. Face enrollment didn't work."
I tried deleting all security from the phone and rebooting to readd, but I still get the error.
Ideas?
Click to expand...
Click to collapse
You sideloaded the factory image or fastbooted it?
At any rate, you could try fastbooting the factory image again to both slots, one at a time, to see if that works. However, more than likely you'll need to do a factory reset. Going forward, it's always a good idea to remove face ID before doing a monthly update. Haven't had a problem with any update in that regard since I got the device last October :good:

Happened to me too. I fixed it by dirty flashing the march factory image. (I noticed that issue started after I flashed fsociety kernel)
(I was on a clean install of the march factory image; already did a factory reset before flashing and already cleared security/face data/etc beforehand. )

neo_lithic3K said:
Happened to me too. I fixed it by dirty flashing the march factory image. (I noticed that issue started after I flashed fsociety kernel)
(I was on a clean install of the march factory image; already did a factory reset before flashing and already cleared security/face data/etc beforehand. )
Click to expand...
Click to collapse
Could you explain your process just a little more. You deleted face data and then how did you dirty flash? Did you just 'adb reboot bootloader' then 'adb flash marchupdate.zip?

ibphantom said:
Could you explain your process just a little more. You deleted face data and then how did you dirty flash? Did you just 'adb reboot bootloader' then 'adb flash marchupdate.zip?
Click to expand...
Click to collapse
Dirty flash in essence means removing the -w characters from the flash-all.bat file. This prevents your data from being wiped, when you fastboot the factory image. It's pretty much like taking an OTA :good:

Yup, I can definitely go into more detail., but my situation probably doesn't match yours completely.
As badger50 mentioned, dirty flash is basically removing the -w. In my case, I removed the '-w" from the March factory image's (flash-all.bat) file. Then I cleared the face data from settings-security, removed any pins/pws/patterns, & did a factory reset from settings-system (b/c I read that the titan chip can only be cleared via factory reset). I then booted to bootloader (adb reboot bootloader or use the power-volume down method) and ran the edited flash-all.bat. That basically reinstalls the factory image without erasing my user data.
The reason I dont sideload OTA is because I never had good luck with sideloading. Something comes out wrong or I run into odd issues.
ibphantom said:
Could you explain your process just a little more. You deleted face data and then how did you dirty flash? Did you just 'adb reboot bootloader' then 'adb flash marchupdate.zip?
Click to expand...
Click to collapse

neo_lithic3K said:
Yup, I can definitely go into more detail., but my situation probably doesn't match yours completely.
As badger50 mentioned, dirty flash is basically removing the -w. In my case, I removed the '-w" from the March factory image's (flash-all.bat) file. Then I cleared the face data from settings-security, removed any pins/pws/patterns, & did a factory reset from settings-system (b/c I read that the titan chip can only be cleared via factory reset). I then booted to bootloader (adb reboot bootloader or use the power-volume down method) and ran the edited flash-all.bat. That basically reinstalls the factory image without erasing my user data.
The reason I dont sideload OTA is because I never had good luck with sideloading. Something comes out wrong or I run into odd issues.
Click to expand...
Click to collapse
Thank you. You're a wonderful person and I appreciate your time.:fingers-crossed:
Thanks to you as well Badger50:victory:

factory reset fixes it all... for some reason using -w may or may not delete something that a factory reset does?

Confirm. Works only factory reset from settings.
Dirty, clean flash, safe mode - doesn't work.

I've never had a problem on the pixel devices leaving my security in when flashing the full image but it can't hurt to remove it. I agree with others above as regards flashing it BTW, it's easy and works every time without having to research the secret handshake sometimes needed to get the OTA to go. You also don't have to wait for it and you don't have to deal with problems like this that come up here and there when sideloading an OTA.
I'm not really sure why so many are resistant to flashing the full image but you get a lot of push-back on it here which seems misplaced; over time you're ahead of the game.

If I install the March 2020 factory image, face unlock works fine. If I install the April 2020 OTA, face unlock breaks. If I install April 2020 or May 2020 factory images, face unlock is broken. SO FRUSTRATING!!!

jtwebfusion said:
If I install the March 2020 factory image, face unlock works fine. If I install the April 2020 OTA, face unlock breaks. If I install April 2020 or May 2020 factory images, face unlock is broken. SO FRUSTRATING!!!
Click to expand...
Click to collapse
Same it will only work for me on March or DP 3 of the beta. Just RMAd my Pixel

TechOut said:
Same it will only work for me on March or DP 3 of the beta. Just RMAd my Pixel
Click to expand...
Click to collapse
I have an RMA in for mine, but Google has nothing in stock.

jtwebfusion said:
I have an RMA in for mine, but Google has nothing in stock.
Click to expand...
Click to collapse
I'm doing one last full wipe and flash of the may update in hopes it might just work.
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
jtwebfusion said:
I have an RMA in for mine, but Google has nothing in stock.
Click to expand...
Click to collapse
How long did it take for you to get the email with shipping label? Been waiting about 5 minutes and nothing yet.

TechOut said:
I'm doing one last full wipe and flash of the may update in hopes it might just work.
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
How long did it take for you to get the email with shipping label? Been waiting about 5 minutes and nothing yet.
Click to expand...
Click to collapse
It took about 5-10 minutes to get it...

jtwebfusion said:
It took about 5-10 minutes to get it...
Click to expand...
Click to collapse
Yeah just got it and while scheduling the fedex pickup realized I mistyped the address so had to cancel and do it all over...

jtwebfusion said:
I have an RMA in for mine, but Google has nothing in stock.
Click to expand...
Click to collapse
Are they repairing any of these or have they just been replacing them?

TechOut said:
Are they repairing any of these or have they just been replacing them?
Click to expand...
Click to collapse
You'll get a refurbished one

Fixing bootloop?

so my bramble spazzed and did a soft reboot and then the system ui wouldn't load (I was able to use the phone, but not the status bar, navbar). i disabled the lockscreen security and removed my magisk modules. then i tried flashing the stock firmware (december) *after erasing the -w*, then i tried sideloading the december ota via recovery, then i tried to do the same withe november versions and then again the december, you get the idea. nothing doing, the best i get is it'll get to "pixel is loading" for a split second then go to bootloader. anyone have any suggestions for me?
sorry, asking on the P5 forum because the phones are so similar the P5 forum is more active.

mistermojorizin said:
so my bramble spazzed and did a soft reboot and then the system ui wouldn't load (I was able to use the phone, but not the status bar, navbar). i disabled the lockscreen security and removed my magisk modules. then i tried flashing the stock firmware (december) *after erasing the -w*, then i tried sideloading the december ota via recovery, then i tried to do the same withe november versions and then again the december, you get the idea. nothing doing, the best i get is it'll get to "pixel is loading" for a split second then go to bootloader. anyone have any suggestions for me?
sorry, asking on the P5 forum because the phones are so similar the P5 forum is more active.
Click to expand...
Click to collapse
Are you booting on the right slot ?

jaythenut said:
Are you booting on the right slot ?
Click to expand...
Click to collapse
Thanks, yes I was. I ended up dirty flashing the stock firmware from December and from November and sideloading otas from both months over and over till it was working again. Took all day but I saved my data. I was flashing the all carrier December image as they was the one I was on, not flashing verizon one did the trick. Something to keep in mind for next time.