Related
My 64gb n6 is coming on the 14th and I read if I root I won't get any ota... Is this true
PunishedSnake said:
My 64gb n6 is coming on the 14th and I read if I root I won't get any ota... Is this true
Click to expand...
Click to collapse
The ota checks if everything is stock before flashing and being rooting will cause it to fail.
papi5120 said:
The ota checks if everything is stock before flashing and being rooting will cause it to fail.
Click to expand...
Click to collapse
People usually modify the update script to remove all asserts and then the ota flash able zip will work.
Sent from my Nexus 6 using Tapatalk
Causes it to fail, but you can still get updates just as easy.
KingMarkous said:
Causes it to fail, but you can still get updates just as easy.
Click to expand...
Click to collapse
How?
PunishedSnake said:
How?
Click to expand...
Click to collapse
Flash a modified zip with the assert disabled.
Sent from my Nexus 6 using Tapatalk
zephiK said:
Flash a modified zip with the assert disabled.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I cant seem to find it can you link me?
Rooting here I come.....
Does anyone run ADAWAY on their n6?
PunishedSnake said:
I cant seem to find it can you link me?
Rooting here I come.....
Does anyone run ADAWAY on their n6?
Click to expand...
Click to collapse
You'd have to download the ota then edit it. OTA is not the only option either. There are full ROM.zip available to flash from recovery too or even fastboot flash the system and boot images.
One problem removing the asserts can cause is if you modify your ROM in any way besides root, you can be patching with the ota, mismatched code...
I've been searching for ages on how to receive the OTA update while rooted with TWRP recovery.
To add on to the difficulty, I have a mac so all the directions and steps I've seen are for windows users (the whole fast boot everything except user or something).
Can anyone link me to the stock ROM that someone mentioned in this thread or at least give a or give me a link to a step by step instruction on how to update on a rooted Nexus 6 running twrp? encrypted as well.
waqar.qu said:
I've been searching for ages on how to receive the OTA update while rooted with TWRP recovery.
To add on to the difficulty, I have a mac so all the directions and steps I've seen are for windows users (the whole fast boot everything except user or something).
Can anyone link me to the stock ROM that someone mentioned in this thread or at least give a or give me a link to a step by step instruction on how to update on a rooted Nexus 6 running twrp? encrypted as well.
Click to expand...
Click to collapse
The steps are easy,
1. New OTA?
2. Download zip (not the official OTA but a modified OTA script that removes asserts)
3. Flash the zip
4. You have new OTA.
Even easier because you wont have to wait for the OTA to come to you and can flash the OTA.
Its not really difficult
PunishedSnake said:
How?
Click to expand...
Click to collapse
Google publishes fastbootable images for all Nexus updates. Just do a google search for "factory images for nexus devices".
A little warning... they need some **very trivial** modification before being written, or they will wipe your phone's userdata.
zephiK said:
The steps are easy,
1. New OTA?
2. Download zip (not the official OTA but a modified OTA script that removes asserts)
3. Flash the zip
4. You have new OTA.
Even easier because you wont have to wait for the OTA to come to you and can flash the OTA.
Its not really difficult
Click to expand...
Click to collapse
Where does one find a modified OTA script that removes "asserts"?
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
FWIW: I would recommend that you:
1) Unlock bootloader
2) Decide if you want uncrypted kernel, or not (since it wipes data, just like unlocking bootloader).
3) Fastboot flash TWRP recovery.
4) Download SuperSU .zip and flash it in recovery.
5) Now, when a new OTA comes out, they usually show up here > http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
6) You can download your current factory image here > https://developers.google.com/android/nexus/images
7) Unzip your current factory image. Fastboot flash the system.img and that will unroot and restore the stock recovery.
8) Fastboot flash the stock boot.img if you have a custom kernel (or an unencrypted stock kernel).
9) Relax and wait for the OTA.
RW-1 said:
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
Click to expand...
Click to collapse
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
mad_rulzzz said:
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
Click to expand...
Click to collapse
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
RW-1 said:
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
Click to expand...
Click to collapse
Yup.
@rw_1 @cam30era thanks guys
I would do what gee2012 said.
From what I have seen the OTA and the images are released pretty close together.
Instead of flashing images to get back to stock and waiting for the OTA. and then re-rooting
Just download the image files from Google. Manually flash all the files EXCEPT user data if you want to keep your data.
Re-root.
You are now updated and don't have to wait for OTA.
Either way works so it depends on which you are happier with.
mad_rulzzz said:
@rw_1 @cam30era thanks guys
Click to expand...
Click to collapse
Welcome. And BTW: there's a button for that.
gee2012 said:
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
Click to expand...
Click to collapse
Just to be sure I understood right:
If I don't care about app data or settings ( I have titanium backup),
1)I can just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
one last thing... Does Google upload factory images after each OTA happens?
cam30era said:
Welcome. And BTW: there's a button for that.
Click to expand...
Click to collapse
My BAd!!
mad_rulzzz said:
If I don't care about app data or settings ( I have titanium backup),
1)Can I just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
Does Google upload factory images after each OTA happens? i.e; If Nexus 6 receives an OTA to 5.2, will they upload the 5.2 factory image soon?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the contents of your SD card. Make sure it is backed up on your PC.
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
cam30era said:
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
Click to expand...
Click to collapse
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
mad_rulzzz said:
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
Click to expand...
Click to collapse
Correct. M is intended for T-Mobile. My point, though, is that Google doesn't always, 100% of the time publish a factory image for every OTA.
Hello all,
On my new Pixel 3 XL, I installed Magisk immediately after doing the initial setup. I then tried taking the January 2019 OTA update (the phone was running the original build from September 2018) and installing the update using the instructions here for devices with A/B partitions: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
This however did not work and the update still failed to install. I ended up doing the upgrade manually via the bootloader but I would like to ask about how to handle this process for future updates. I am running the latest stable version of Magisk.
Thank you
Is it possible that /system or /vendor have been altered in some way? That would cause the OTA to fail...
Didgeridoohan said:
Is it possible that /system or /vendor have been altered in some way? That would cause the OTA to fail...
Click to expand...
Click to collapse
I still pass SafetyNet though. Wouldn't modifying either of those cause it to fail?
David B. said:
I still pass SafetyNet though. Wouldn't modifying either of those cause it to fail?
Click to expand...
Click to collapse
As a rule, you can do quite heavy modifications to both /system and/vendor and still pass SN. So, not necessarily...
Didgeridoohan said:
As a rule, you can do quite heavy modifications to both /system and/vendor and still pass SN. So, not necessarily...
Click to expand...
Click to collapse
Well I do use the Internal Audio Plugin which may write stuff to /system and/or /vendor. I am not sure though. I do not remember if I had it installed at that point though. I do have it installed now though. If it turns out that the app is the reason it's not working, hopefully I will be able to uninstall it when trying the OTA again.
Hi all. I have searched for information and have seen a lot and varied. I come to confirm more than anything and to know if you have a clear idea.
I have my 3XL pixel rooted with Magisk.
First question: With the root of magisk the system does NOT detect the new monthly update updates. Is this normal? I understood that I would detect it but that it would NOT let me update it.
As a result of that question I found this other ...
https : // topjohnwu. github.io/Magisk/tutorials.html (sorry, there are spaces)
I'm not sure if this tutorial is valid for the Pixel 3XL. I have reproduced it and ... or something I have not done well or is not compatible with our device.
The objective of all this is to know if, with the rooted phone, OTAs can be detected and, in case the answer is no, to know if there is any method like the one that Magisk proposes without having to download the OTA, install by the recovery and re-root with twrp.
I have not used any magisk module, but I do have Es File Explorer installed with root viewer, titanium backup and Swift Insaller. I do not think this has modified / system or / vendor.
Thanks and best regards!
ciltocruz said:
Hi all. I have searched for information and have seen a lot and varied. I come to confirm more than anything and to know if you have a clear idea.
I have my 3XL pixel rooted with Magisk.
First question: With the root of magisk the system does NOT detect the new monthly update updates. Is this normal? I understood that I would detect it but that it would NOT let me update it.
As a result of that question I found this other ...
https : // topjohnwu. github.io/Magisk/tutorials.html (sorry, there are spaces)
I'm not sure if this tutorial is valid for the Pixel 3XL. I have reproduced it and ... or something I have not done well or is not compatible with our device.
The objective of all this is to know if, with the rooted phone, OTAs can be detected and, in case the answer is no, to know if there is any method like the one that Magisk proposes without having to download the OTA, install by the recovery and re-root with twrp.
I have not used any magisk module, but I do have Es File Explorer installed with root viewer, titanium backup and Swift Insaller. I do not think this has modified / system or / vendor.
Thanks and best regards!
Click to expand...
Click to collapse
Hello,
The issue that you are describing is identical to what I observed during the February OTA update. It was not showing up on my phone. Supposedly if you wait long enough it will be detected, but I got impatient with waiting and just did it manually. It is worth noting however that when I got my Pixel 3 XL (I got it in January), I rooted it immediately before installing the January patches, and the behavior that you described as what should have happened is what I observed: the update was detected, but I could not install it. The odd thing about it was that even after uninstalling Magisk, I still could not get it to install and therefore ended up manually sideloading that update as well. It is worth noting that as part of that sideload, I chose to wipe the phone so that whatever modifications I must have made to /system or /vendor would be gone.
I am sorry that I could not provide any real help for this issue since I have been sideloading as a workaround. If you come up with a real solution to this, please let me know. Otherwise, you may want to just sideload manually.
David B. said:
Hello,
The issue that you are describing is identical to what I observed during the February OTA update. It was not showing up on my phone. Supposedly if you wait long enough it will be detected, but I got impatient with waiting and just did it manually. It is worth noting however that when I got my Pixel 3 XL (I got it in January), I rooted it immediately before installing the January patches, and the behavior that you described as what should have happened is what I observed: the update was detected, but I could not install it. The odd thing about it was that even after uninstalling Magisk, I still could not get it to install and therefore ended up manually sideloading that update as well. It is worth noting that as part of that sideload, I chose to wipe the phone so that whatever modifications I must have made to /system or /vendor would be gone.
I am sorry that I could not provide any real help for this issue since I have been sideloading as a workaround. If you come up with a real solution to this, please let me know. Otherwise, you may want to just sideload manually.
Click to expand...
Click to collapse
I see that there is no other option than to do it manually and reinstall magisk later every month ...
ciltocruz said:
I see that there is no other option than to do it manually and reinstall magisk later every month ...
Click to expand...
Click to collapse
Well at this point I will not have a chance to test this belief out until March.
David B. said:
Well at this point I will not have a chance to test this belief out until March.
Click to expand...
Click to collapse
I rerooted the phone with Magisk and it's perfect.
Unfortunately, with the March update, my 3LX pixel will not notify me of this update and I will have to install it manually with adb.
Then I will have to manually re-root magisk. I can not find a way to make the magisk tutorial work so I do not have to do this manual process. I believe that Magisk modifies /vendor and /system and "to uninstall magisk with the boot_patched", to the new pixel 3 or to Android Pie does not matter to him because he knows what is happening.
ciltocruz said:
I rerooted the phone with Magisk and it's perfect.
Unfortunately, with the March update, my 3LX pixel will not notify me of this update and I will have to install it manually with adb.
Then I will have to manually re-root magisk. I can not find a way to make the magisk tutorial work so I do not have to do this manual process. I believe that Magisk modifies /vendor and /system and "to uninstall magisk with the boot_patched", to the new pixel 3 or to Android Pie does not matter to him because he knows what is happening.
Click to expand...
Click to collapse
I am confused. How can you know what is going to happen with the March update when it has not been released yet?
David B. said:
I am confused. How can you know what is going to happen with the March update when it has not been released yet?
Click to expand...
Click to collapse
Nooooo Sorry, maybe I explained wrong.
I want to say that, like in January and February, when the March update is released, the Pixel 3XL, as it is rooted, will not recognize it. It will not give me the notice of a new update.
Better like that?
ciltocruz said:
Nooooo Sorry, maybe I explained wrong.
I want to say that, like in January and February, when the March update is released, the Pixel 3XL, as it is rooted, will not recognize it. It will not give me the notice of a new update.
Better like that?
Click to expand...
Click to collapse
Oh I understand. I suppose we'll just have to wait and see. ?
David B. said:
Oh I understand. I suppose we'll just have to wait and see.
Click to expand...
Click to collapse
I installed the March update via recovery. No problem. Then I have reinstalled Magisk with the TWRP image.
I still do not know how to make this tutorial for Pixel 3 work
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Has anyone succeeded? The objective is:
- That the rooted phone detects the OTA.
- To be able to uninstall the root with the Magisk Manager application.
- To be able to install the OTA like any normal user.
- Be able to reinstall the root via Magisk Manager.
All without the need of adb, sideload, recovery, TWRP or anything "technical".
Greetings!
ciltocruz said:
I installed the March update via recovery. No problem. Then I have reinstalled Magisk with the TWRP image.
I still do not know how to make this tutorial for Pixel 3 work
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Has anyone succeeded? The objective is:
- That the rooted phone detects the OTA.
- To be able to uninstall the root with the Magisk Manager application.
- To be able to install the OTA like any normal user.
- Be able to reinstall the root via Magisk Manager.
All without the need of adb, sideload, recovery, TWRP or anything "technical".
Greetings!
Click to expand...
Click to collapse
I also had to install the update via recovery, as the option to use the built-in updater was not detecting that the update was available again. Perhaps it's time we ask @topjohnwu Magisk Queries/ @topjohnwu about this?
I've seen (and commented in) at least 4 previous threads reporting the same issue with OTA updates and none of them have been taken seriously or prompted any kind of further investigation. Oh well, 5th time lucky perhaps?
Anyway, I have exactly the same issue with my Pixel 2; I used to receive notifications for OTA updates back when I was running on Oreo with Magisk, but after updating to Pie in September 2018 I haven't received a single new OTA notification.
Pie was installed from the factory image, including a device wipe, so it was a completely fresh start. I've also tried reflashing system.img and vendor.img just in case those partitions somehow got modified at some point, but it made no difference. My device simply will not detect new OTA updates, so my only option is to sideload the update and reflash magisk every month.
As per a previous post of mine, I found other reports of the same issue on Reddit and the common factors seemed to be Pixel devices, Pie and Magisk.
nogaff said:
I've seen (and commented in) at least 4 previous threads reporting the same issue with OTA updates and none of them have been taken seriously or prompted any kind of further investigation. Oh well, 5th time lucky perhaps?
Anyway, I have exactly the same issue with my Pixel 2; I used to receive notifications for OTA updates back when I was running on Oreo with Magisk, but after updating to Pie in September 2018 I haven't received a single new OTA notification.
Pie was installed from the factory image, including a device wipe, so it was a completely fresh start. I've also tried reflashing system.img and vendor.img just in case those partitions somehow got modified at some point, but it made no difference. My device simply will not detect new OTA updates, so my only option is to sideload the update and reflash magisk every month.
As per a previous post of mine, I found other reports of the same issue on Reddit and the common factors seemed to be Pixel devices, Pie and Magisk.
Click to expand...
Click to collapse
What's odd about my situation is that when I first got the phone and rooted the image that it came with (September 2018), I did get the OTA notification. I just could not get it to install even after following the Magisk uninstallation steps provided in the official Magisk tutorial. It's only a minor inconvenience and I can live with it, but the fact that it happens still bothers me.
David B. said:
What's odd about my situation is that when I first got the phone and rooted the image that it came with (September 2018), I did get the OTA notification. I just could not get it to install even after following the Magisk uninstallation steps provided in the official Magisk tutorial. It's only a minor inconvenience and I can live with it, but the fact that it happens still bothers me.
Click to expand...
Click to collapse
This happened to me too. I put the root and the first OTA did arrive but, because I had root, I could not install. I had to do it manually with adb.
ciltocruz said:
This happened to me too. I put the root and the first OTA did arrive but, because I had root, I could not install. I had to do it manually with adb.
Click to expand...
Click to collapse
Did you try using the tutorial as well?
David B. said:
Did you try using the tutorial as well?
Click to expand...
Click to collapse
Yes, but with my rooted device the notification of NEW UPDATE does not appear. I know I can not INSTALL it, but is there also no update notice? This is what I need. An update notice.
With that warning I will be able to patch the boot image with magisk and then I will be able to download and install the OTA. Then re-rooted and ready.
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.
So, as title says, i'm rooted with the first october update and now i want to go with november one, but i'm rooted and of course OTA isn't working. How to correctly do it with factory image? With oneplus was easy, flash update package .zip with internal updater and then install magisk on the other slot but here is different (i think). Anyone already did it?
Thanks
Hitman478™ said:
So, as title says, i'm rooted with the first october update and now i want to go with november one, but i'm rooted and of course OTA isn't working. How to correctly do it with factory image? With oneplus was easy, flash update package .zip with internal updater and then install magisk on the other slot but here is different (i think). Anyone already did it?
Thanks
Click to expand...
Click to collapse
Hi Dude,
PIXEL-Flasher is your friend.
📳🔥PixelFlasher for Google Pixel 7 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
How to use the Pixel flasher tool is perfectly explained in the OP's!
For me the Update (Nov fact-img) worked w/o any problems inclusive keeping root! (in PixelFlasher you can patch the init_boot and will be flashed automatically)
Just updated with pixel flasher keeping root with magisk and xposed and all modules, everything works without any type of issues! Absolutely reccomended to those who have my doubts. Amazing software for pixel users!
If somebody is looking for an alternative method, check out this video tutorial.
It worked perfectly for me.
I only just got my pixel 7, but the pixel flasher way seems way more simple than that alternative method.
Well, I just updated using the pixelflasher...
That was just about as simple as it gets. I recommend!
Can you skip a monthly update using pixel flasher? Say you're on October/rooted. Could you update to December/rooted or should you update to November first?
happynexuss said:
Can you skip a monthly update using pixel flasher? Say you're on October/rooted. Could you update to December/rooted or should you update to November first?
Click to expand...
Click to collapse
hi,
yes you can go directly Oct > Dec!
Can't we just use the old way mind u haven't had any updates since I rooted but can't we I stall to a inactive slot threw magisk?
rob420p said:
Can't we just use the old way mind u haven't had any updates since I rooted but can't we I stall to a inactive slot threw magisk?
Click to expand...
Click to collapse
Unfortunately not. See https://forum.xda-developers.com/t/...vember-update-with-magisk-ota-method.4515951/
I gave it a shot going to qpr2. Freak07's solution works to recover.
rob420p said:
Can't we just use the old way mind u haven't had any updates since I rooted but can't we I stall to a inactive slot threw magisk?
Click to expand...
Click to collapse
No, because it's not working. You need to use flash-all.bat (after editing and deleting the "-w") from stock when updating and re-root. Faster than the OTA upgrade, takes less time.