Related
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.
RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/
Alright, so I just flashed MRA58N yesterday, and today there is a new MRA58R image added? What's the difference here? The first build was a security update, but what's this new one? And why only a day difference? Thanks!
Sent from my Nexus 6
Changelogs aren't made readily available.
Perhaps this script will help people who update their local AOSP repo's will help.
https://groups.google.com/forum/#!msg/android-building/0DtsHawjs4k/And8o3Dni_UJ
Obviously some modification will be required
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Quetzalcoalt_Lp said:
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Click to expand...
Click to collapse
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Rektifying said:
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Click to expand...
Click to collapse
What kernel are you using?
H4X0R46 said:
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
Click to expand...
Click to collapse
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
scryan said:
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
Click to expand...
Click to collapse
I never do a dirty flash just to avoid conflict, but I guess it couldn't hurt to try right? So not wiping userdata should work?
Sent from my Nexus 6
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
I have always had zero issues applying newer stock images over older stock images on a Nexus device. I do this all the time when the OTA is not available and only the main updated Google Factory image is available.
I think the trick is to always wipe dalvik and cache after a flash of system and use TWRP that supports encryption. When you wipe the dalvik and cache the system acts like an OTA and performs an upgrade on all your apps. I *think* it effectively rebuilds the cache for all apps, but it never touches the app data or user data (sdcard/pictures/etc).
I also always flash the radios and bootloader *IF* they are updated from the last image. I used to flash the stock boot images too, but now that looks like from a going forward point we won't be able to do this and have root. I do look forward to system-less root
scryan said:
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
Click to expand...
Click to collapse
Cool dude! Thanks for the advice! Yea, I use ElementalX kernel on my device, unencrypted device makes no noticeable difference for performance to me, but the battery life is another story! ElementalX has superb battery life!
Sent from my Nexus 6
Any word on the changes between this and previous build yet?
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
dahawthorne said:
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
Click to expand...
Click to collapse
The security updates were also in the previous build, MRA58N.
All we really know for sure is that the OTA for MRA58R is being pushed out by Verizon. The OTA path skips MRA58N.
Pushed out by big red.... I think that's something I'll definitely wait on.
jbeezley said:
Pushed out by big red.... I think that's something I'll definitely wait on.
Click to expand...
Click to collapse
I've never had a problem with their updates and, realistically, this is actually a Google update. I'm just impressed that they're leading the charge.
I'm on MRA58K after sideloading the first Marshmallow OTA. I just noticed there's an OTA from K to N but there's nothing from any Marshmallow build to R.
I'm on N and haven't seen anything detailing what's different in R. I'm just a bit suspicious of anything pushed by Verizon, although you are correct @GilmourD3. It's Google's update, but why would Verizon spearhead the rollout? I would rather just stay on N awhile until we have someone in the know look over the details of the update to R.
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
H4X0R46 said:
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
Click to expand...
Click to collapse
Anything change from K to N? I might just sideload the N OTA since I'm currently on K and I'm not finding an OTA path from K to R.
R is apparently the OTA update to 6.0 and the November security update for Verizon Nexus 6. My wife got it Thursday and her build and security date both changed.
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
lgmayka said:
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
Click to expand...
Click to collapse
Any reason not to use a Google Factory image? It looks like MMB29V is the most recent.
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer. As I mentioned, joining the Android Beta program actually seems to be the easiest solution, if the current beta (NPD30G) is stable enough.
Frankly, I am surprised that Google/Motorola/AT&T (or any cell phone designer/manufacturer/carrier) allows a working cell phone to get into this state where the phone refuses to accept security updates.
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
That's half the fun of owning a Nexus, not waiting for updates. Dl the factory image, unzip it and the zip file inside and flash the system. IMG only and you'll lose nothing but root. If, of course, you are rooted.
http://forum.xda-developers.com/showthread.php?p=59561445/ You may give it a try..... prerooted lite stock rom.
lgmayka said:
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer.
Click to expand...
Click to collapse
As already suggested, just install the system image. The simplest way to do that is via fastboot. Nothing gets erased unless you flash the userdata.img. Using Google's script to flash everything would overwrite the userdata partition.
The version you are on (MMB) is released to provide updates without updating the radio. The MOB release is the same as the equivalent MMB plus the package includes the updated radio. This is a requirement of the carriers who want to approve the radio before it's released.
You will be unable to take any *incremental* OTA if there is any differential between what's on your system partition and what the OTA is expecting. You can not hop over incremental OTA updates. They must be sequentially applied. Therefore, the safest way to get to a known state is with a factory image.
If fastbooting a factory image is unacceptably risky, then maybe an eBay phone wasn't a great choice.
Or, as you say, you go straight to N. If the beta program is still available now that N is released.
stevemw said:
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
Click to expand...
Click to collapse
I decided to do this. NPD90G is running well enough for me, and before long Google will release Android 7.0 Final.
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.
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: