I was looking at rooting instructions on another site and it indicated that you may not be able to get OS updates from Google if you root your device. Is there any truth to that if you only root the device? and would it matter if you keep encryption on or off?
ecko19 said:
I was looking at rooting instructions on another site and it indicated that you may not be able to get OS updates from Google if you root your device. Is there any truth to that if you only root the device? and would it matter if you keep encryption on or off?
Click to expand...
Click to collapse
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
nitinvaid said:
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
Click to expand...
Click to collapse
If you modify the flash-all file to remove the flag -w it will not wipe the data from the device.
Is that because when rooting the phone the stock recovery partition is flash over with TWRP and when OTAs are updated they use the recovery stock recovery partition to update the system partition? or does the OTA update process do some check to see if anything was tampered with? or something else?
nitinvaid said:
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
Click to expand...
Click to collapse
Well, I've seen in here that you can install superSU by booting into twrp but without having to flash anything to the drive - meaning everything is stock.. Shouldn't that still allow the OTA updates?
paul_one said:
Well, I've seen in here that you can install superSU by booting into twrp but without having to flash anything to the drive - meaning everything is stock.. Shouldn't that still allow the OTA updates?
Click to expand...
Click to collapse
No. Because rooting modifies the system partition (superuser apk and all related libraries are placed on different locations on the system partition), so the verification done by OTAs fail. Also, so far, the only way to achieve root is to modify the boot image and turn off dm-verity, which will also likely cause OTAs to fail.
craigacgomez said:
No. Because rooting modifies the system partition (superuser apk and all related libraries are placed on different locations on the system partition), so the verification done by OTAs fail. Also, so far, the only way to achieve root is to modify the boot image and turn off dm-verity, which will also likely cause OTAs to fail.
Click to expand...
Click to collapse
Actually, there is a better way to provide root access that we are working on.
At present, I have prebuilt boot images for Nexus 5, 6, 9. I do NOT have prebuilt boot images for 5x or 6p *yet* due to lack of device tree source code on google's git (hopefully they will fill that in soon).
You can read over the thread about it here;
http://forum.xda-developers.com/nexus-6/general/root-t3231211
We are also working on a way to inject the changes into an existing binary sepolicy, but that process is in a very very alpha state currently.
There are two options currently that I can see for providing root access to a 5x or 6p;
1) try using a 6's sepolicy and related files and hope for the best, probably won't work,
2) generate a permissive sepolicy
Once the device tree source is provided and we can generate boot images from source, this will, of course, change -- we will be able to build the proper policy from source.
Summary of this approach;
The system image is *NOT* impacted in ANY way. All of the differences are added to the boot ramdisk.
doitright said:
Actually, there is a better way to provide root access that we are working on.
At present, I have prebuilt boot images for Nexus 5, 6, 9. I do NOT have prebuilt boot images for 5x or 6p *yet* due to lack of device tree source code on google's git (hopefully they will fill that in soon).
You can read over the thread about it here;
http://forum.xda-developers.com/nexus-6/general/root-t3231211
We are also working on a way to inject the changes into an existing binary sepolicy, but that process is in a very very alpha state currently.
There are two options currently that I can see for providing root access to a 5x or 6p;
1) try using a 6's sepolicy and related files and hope for the best, probably won't work,
2) generate a permissive sepolicy
Once the device tree source is provided and we can generate boot images from source, this will, of course, change -- we will be able to build the proper policy from source.
Summary of this approach;
The system image is *NOT* impacted in ANY way. All of the differences are added to the boot ramdisk.
Click to expand...
Click to collapse
So you do not have an su binary or Superuser apk installed in /system?
Sent from my Nexus 5X
craigacgomez said:
So you do not have an su binary or Superuser apk installed in /system?
Click to expand...
Click to collapse
Go read the thread.
doitright said:
Go read the thread.
Click to expand...
Click to collapse
I get an invalid thread message.
Sent from my Nexus 6P using Tapatalk
doitright said:
Go read the thread.
Click to expand...
Click to collapse
@doitright, very nice!! Love it!
Related
Hi! So I'm looking to root my Nexus 5x following this guide. However, I can't find the modified boot.img for my build MMB29P. I have a brand new phone out of the box (my mic stopped working so this is a replacement) so I'd like to get this done in the next little while the phone has no data and I can wipe anything I need to without worry and use the restore afterwards. I also heard something about SuperSU being able to use stock boot.img or something of that nature, could someone clue me in? Thanks!
[GUIDE] Unlock/Root/Flash for Nexus 5X - Heisenberg's How-To Guide For Beginners
take a look at section 6
as an alternative there are some toolkits that may be more convenient to you (on-screen instructions and detailed faq/guides)
The latest version of SuperSU (v. 2.66 I believe) is automated for systems root. I actually used the SuperSU beta v. 2.62 to root. I just unlocked bootloader, flashed TWRP, and then flashed that version of SuperSU.
Sent from my Nexus 5X using Tapatalk
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
https://www.androidfilehost.com/?w=files&flid=43558
k.s.deviate said:
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
Click to expand...
Click to collapse
Even with systemless root?
When it comes to upgrading, there are a couple of routes you can take. Both involve downloading the official factory image ZIP first. Extract the contents, reboot into bootloader, and then you have option:
1. Edit the flash-all script (.bat for windows and .sh for Linux/Mac) by removing the -w option. Removing this option will prevent the upgrade from wiping user data. Once the option is removed, simply run the script to upgrade.
2. Flash the images individually. Sometimes certain things don't change like bootloader.img or radio.img. You should always flash boot.img, system.img, and vendor.img when updating. This is the route I take.
After flashing the images, you will need to reboot into Recovery mode and flash SuperSU. Then wipe cache and dalvik and reboot into system. If you use a custom kernel, you will need to reflash that as well after updating.
Sent from my Nexus 5X using Tapatalk
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
jkingaround said:
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
Click to expand...
Click to collapse
Google posts the official factory images on the developer site. Here is the link: https://developers.google.com/android/nexus/images
AFAIK the boot warning can't be removed, but I may be wrong. It's nothing to worry about though.
Having a custom kernel is not necessary, but there are benefits to using one. Custom kernels typically provide better battery life with same or improved performance. They can also make your device run cooler and use less memory. Custom kernels also allow for various tweaks such as change vibration intensty, screen DPI, headphone/speaker gain, etc. I personally use ElementalX with the Interactive Governor tweaks from the thread in the general forum, but I've read that Franco Kernel is very good as well and will probably try that out in the future.
Sent from my Nexus 5X using Tapatalk
jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
Just pick a custom rom to try and follow OP instructions. Cataclysm seems to be a hit...
Now do you root a HTC 10. Will you still be able to download system updates.
Osakpa said:
Now do you root a HTC 10. Will you still be able to download system updates.
Click to expand...
Click to collapse
Rooting doesn't affect your ability to take OTAs. It's what you do AFTER you root that will impact OTA. Any modifications to System partition will break OTA. The modification can be as simple as just mounting system as read-write, as opposed to leaving it read-only.
Modifying system partition while using the unmodified stock kernel (we think) will also trip verity mode logging which will cause the you to get an error that system is corrupt when you go to check for OTA.
The TWRP FAQ (second post) has all the info you need regarding root and restoring your ability to ota.
Additional information regarding how to fix verity mode logging can be found here
Obviously, if you root and use only systemless exploits and never mount system as read-write, you should never break your ability to OTA. But, that's a lot easier said than done.
jollywhitefoot said:
Obviously, if you root and use only systemless exploits and never mount system as read-write, you should never break your ability to OTA. But, that's a lot easier said than done.
Click to expand...
Click to collapse
Magisk makes it super simple.
I have magisk'd phhh super-su, xposed, and now Dolby Atmos (that I converted to magisk), all still playing well enough together to so that at least android pay works. I won't know about OTA's until the next dev/unlocked one which could possibly just be N.
I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?
djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.
KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june
JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...
KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.
djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't
KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)
JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.
djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?
I forgot how you update the phone when the new monthly security updates come out when rooted? I know when you have recovery it's easier just flash it but without that yet how do we install the latest October patch being rooted only?
Someone correct me if I'm wrong or missing something but this is my understanding:
1. Download image from Google and remove the -w from .bat file if you don't want to wipe data and run the bat to flash the update.
2. Patch new boot.img with Magisk.
3. Use fastboot to flash patched boot.img
shorto85 said:
Someone correct me if I'm wrong or missing something but this is my understanding:
1. Download image from Google and remove the -w from .bat file if you don't want to wipe data and run the bat to flash the update.
2. Patch new boot.img with Magisk.
3. Use fastboot to flash patched boot.img
Click to expand...
Click to collapse
Yep, that's about it in a nutshell :good:
shorto85 said:
Someone correct me if I'm wrong or missing something but this is my understanding:
1. Download image from Google and remove the -w from .bat file if you don't want to wipe data and run the bat to flash the update.
2. Patch new boot.img with Magisk.
3. Use fastboot to flash patched boot.img
Click to expand...
Click to collapse
You can also download the Google OTA image and then ADB sideload the zip file through Recovery. It won't wipe data either.
Will this work while rooted or do you have to uninstall magisk then use the stock recovery to side-load the OTA?
Flyer66 said:
You can also download the Google OTA image and then ADB sideload the zip file through Recovery. It won't wipe data either.
Click to expand...
Click to collapse
Just remove the - w in flash. Bat
You'd have to re root after of course.
Flyer66 said:
You can also download the Google OTA image and then ADB sideload the zip file through Recovery. It won't wipe data either.
Click to expand...
Click to collapse
can you share the steps for doing an ADB Sideload? My PC is all setup for it - but I don't know the exact commands to use...? Thannks
Geekser said:
can you share the steps for doing an ADB Sideload? My PC is all setup for it - but I don't know the exact commands to use...? Thannks
Click to expand...
Click to collapse
Download the full OTA image from Google
Boot into factory recovery
Choose Apply update from ADB
From windows
Code:
adb sideload fullOTAimage.zip
the update will take awhile
Reboot and let the update finish in android
Load magisk and patch the boot.img, copy patch_boot.img to computer
Boot into the bootloader
Flash the patched boot image with:
Code:
fastboot flash boot patch_boot.img
or
Code:
fastboot flash boot_a patch_boot.img
and
Code:
fastboot flash boot_b patch_boot.img
cursixx said:
Download the full OTA image from Google
Boot into factory recovery
Choose Apply update from ADB
From windows
Code:
adb sideload fullOTAimage.zip
the update will take awhile
Reboot and let the update finish in android
Load magisk and patch the boot.img, copy patch_boot.img to computer
Boot into the bootloader
Flash the patched boot image with:
Code:
fastboot flash boot patch_boot.img
or
Code:
fastboot flash boot_a patch_boot.img
and
Code:
fastboot flash boot_b patch_boot.img
Click to expand...
Click to collapse
Very Nice - thank you very much. Very helpful!
Archangel said:
Will this work while rooted or do you have to uninstall magisk then use the stock recovery to side-load the OTA?
Click to expand...
Click to collapse
No, it will work while you're rooted. You will lose root since the OTA sideload will rewrite your patched boot.img with the boot.img from the OTA. You'll have to reroot by first booting your phone into the new image and then using Magisk to patch the new boot.img and then fastboot flash the new patched boot.img.
Once we finally get TWRP recovery, you'll actually be able to "flash" the OTA zip via TWRP instead of having to sideload it.
---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------
cursixx said:
Download the full OTA image from Google
Boot into factory recovery
Choose Apply update from ADB
From windows
Code:
adb sideload fullOTAimage.zip
the update will take awhile
Reboot and let the update finish in android
Load magisk and patch the boot.img, copy patch_boot.img to computer
Boot into the bootloader
Flash the patched boot image with:
Code:
fastboot flash boot patch_boot.img
or
Code:
fastboot flash boot_a patch_boot.img
and
Code:
fastboot flash boot_b patch_boot.img
Click to expand...
Click to collapse
Thanks! You beat me to it.
Flyer66 said:
Thanks! You beat me to it.
Click to expand...
Click to collapse
Sorry about that :good:
I did forget about extracting the updated boot.img from the matching OTA build you sideloaded. Geekser you will need to also download the updated factory image and extract the boot.img and copy it to the phone so magisk can patch it.
Wait, is everyone forgetting that Magisk has the ability to handle taking the OTA like normal and then patch the newly installed OS on the opposite A/B partition before you reboot? The process should be nearly seamless unless something changed recently.
This is what I'm referring to: Magisk OTA Updates with A/B Devices
Hopefully the link actually works now
Sent from my Pixel 3 XL using Tapatalk
WisdomWolf said:
Wait, is everyone forgetting that Magisk has the ability to handle taking the OTA like normal and then patch the newly installed OS on the opposite A/B partition before you reboot? The process should be nearly seamless unless something changed recently.
This is what I'm referring to: Magisk OTA Updates with A/B Devices
Click to expand...
Click to collapse
Link appears to be dead.
lollyjay said:
Link appears to be dead
Click to expand...
Click to collapse
See here : https://************/magisk-17-1-in...uding-ota-updates-with-a-b-partition-devices/
Interesting, it appears XDA is blocking the URL, so google: magisk introduces update
should be first link...
Also see HERE.
It looks like all of our links got mangled, but the new one I posted appears to work.
Where to find and download minor OTA updates to install them on rooted devic
[Moved to proper location, thanks for your advice].
Qui Peccavit said:
Please excuse the naive question, but how/where do you find the OTA files, i.e. the links to download them from?
Capturing the download link via the Android Debug Bridge (ADB) requires the OTA notifications to appear and the respective files to be downloaded, in order to then capture them via adb logcat > OTA.txt. Even if this did not require an unrooted device running an original manufacturer firmware (if we had this, we wouldn't need to go through all the hassle in the first place): it takes a looooong time for the logcat to create a loong file, in which searching for the download link resembles punishment for an amok shooter.
The reason why anybody would need the download links for OTA files is because they are on a custom ROM, have flashed TWRP, rooted their device or similar modifications. In that case, there are no more OTA notifications, i.e. one is not informed of what and when a bugfix or the like becomes available, and if trying to check for updates manually, the phone displays the following error message:
Failed to update software
Your phone's operating system has been modified in an unauthorised way. Try downloading ...
The first thing to note is the impertinence with which manufacturers and telephone operators seem to believe that they had any right to decide what is authorised and what not on our property. Unless somebody with deep pockets or the EU sue them over this BS, there is not much we ordinary mortals will be able to do against those oligopolists.
The burning practical question are therefore:
1.) How to get notified of minor updates, bugfixes and security patches when they become available?
2.) How and where to download them?
3.) How to install them?
The large firmware packages are no problem, those one can find at every corner of the street. The problem are the minor bugfixes, security patches and updates between major version numbers and sometimes even apps. Are there any proven methods that work reliably and that do neither require one to study electronics, programming and voodoo, nor force one to re-flash and re-root everything again from square one before every update, plus reinstalling and configuring everything thereafter?
In case the information is necessary, the phone is a SAMSUNG Galaxy Note 9 with Snapdragon SD-845 (SM-N9600), current firmware BL : N9600ZHS1CSC2, AP : N9600ZHS1CSC2, CP : N9600ZCU1CSAB, CSC : N9600OWO1CSB1
In a nutshell, are there ways to become aware of and apply all updates while keeping the device rooted, or is the procedure more convoluted and repetitive after every update than what Root is worth?
.
Click to expand...
Click to collapse
This has been covered many times. But, security patches generally drop the first Monday of every month. So if you want all the latest bug fixes, etc just wait for the first week of the month. Then download the full factory image for the month, edit out the -w in the flash all batch file you'll find in the factory image ( make sure you save the edited file). Run it. Afterwards, boot to twrp and install the magisk zip file once in twrp. That's it!
Qui Peccavit said:
In case the information is necessary, the phone is a SAMSUNG Galaxy Note 9 with Snapdragon SD-845 (SM-N9600), current firmware BL : N9600ZHS1CSC2, AP : N9600ZHS1CSC2, CP : N9600ZCU1CSAB, CSC : N9600OWO1CSB1
.
Click to expand...
Click to collapse
This is the Google Pixel forums, that's why updates and root are easy from us.
OTA's from Samsung are a whole different animal, you'll need to find your device's forum.
Doing it right once is better than doing it half-baked a hundred times
jd1639 said:
This has been covered many times. Download the full factory image for the month, edit out the -w in the flash all batch file you'll find in the factory image, save and then run it. Afterwards, boot into TWRP to install the Magisk zip file. That's it!
Click to expand...
Click to collapse
Quoting posts in their entirety is not necessary when the one you refer to is just one or two above yours, i.e. repeating the parts you are referring to is suficient.
Second, as with so many topics on this board, the question may have been covered many times, but usually in the same superficial telegram style without details or references as above ― which is the very reason why the questions are repeated in the first place. If there was a reference link to a detailed, step-by-step instruction that explains the necessary operations (where to find the tools for unpacking and later repacking, etc., etc.), people would not have to ask again, until one day somebody provides a comprehensible and complete, detailed step-by-step instruction. Such a guide does not have to be rewritten each time the question pops up, but «has already been covered» without doing so and without directing people to the relevant information is not as helpful as it could be.
It's like with rooting, patching, jailbreaking and other threads here on XDA: Some geeky nerd cannot write three structured sentences in a row or is too lazy to explain the procedure step by step, rather throwing around buzzwords and mentioning things without links so that people then have to hunt down a hundred tidbits from a hundred places, and in those threads, it's incomplete, superficial gibberish just the same. This is no exaggeration: there are threads here about doing something rather simple, but because the guy who started the thread was too lazy to invest the last three hours that were needed to patch it completely and fixing the known issues once and for all, too vain to wait with publishing until that has been done and too verbally incompetent or lazy to explain it properly, there are now 650 posts in that thread because god beware if somebody dared to tell the nerd «try to talk in proper sentences and explain it step by step». Many, many people wasting time, nerves, energy and work to figure something out over months that could be done by anybody in half an hour, if only instead of the imprecise mumbo-jumbo in the first post and three-word answers to questions, the geeks would do it right once in the beginning. This is speaking in general terms, not directed at any one person in particular.
Lastly and referring to the particular issue at hand, of course one can always go through the entire procedure from scratch, i.e. flash a stock ROM, re-root and do it all over again after the next update every month. The question was more in the spirit of «how can a rooted phone be updated without having to run through the entire obstacle course each and every month?», i.e. keeping the configuration, apps, etc., similar to the way it would be if the phone was not rooted. Flashing the new firmware is no problem, but having to do all the installing and configuring afterwards each time is something that, if it can be avoided, would be nice to avoid.
Again, this is not directed at you nor anybody else in particular, just to explain and maybe ring a bell that when questions are repeated over and over again, the previous answers cannot have been so terribly great, can they? And if they were, why not provide or link to them, instead of teasing with «has been answered already»?
Edit:
As already stated earlier above, the question has been moved to the proper location. Therefore it can/should be ignored in this thread, but taking the general considerations above into account in the future cannot hurt, can it now?
The Magisk A/B procedure does not work any more
So, I tried the procedure outlined in https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md on my Pixel 2 running stock Pie but the step of installing the OTA update failed. So it seems something changed recently. I'm no expert (I just follow instructions), so I can't say what changed.
WisdomWolf said:
Wait, is everyone forgetting that Magisk has the ability to handle taking the OTA like normal and then patch the newly installed OS on the opposite A/B partition before you reboot? The process should be nearly seamless unless something changed recently.
This is what I'm referring to: Magisk OTA Updates with A/B Devices
Hopefully the link actually works now
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom
Tom2112 said:
I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom
Click to expand...
Click to collapse
I have seen postings about people fastboot flashing back the original boot.img, then taking the ota then repatching the new boot image and flashing it via fastboot. Not as simple as you hoped i am sure but it works.
The other way is to download the full image, remove the -w option in the flashsall.bat and then run the modded flashall file. You then need to patch the new boot image as above and fastboot flash that to regain root. I have not found any other ways to get updates besides doing one of the 2 above every month
Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.
Tom2112 said:
Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.
Click to expand...
Click to collapse
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Sideloading the ota would be a great option EXCEPT he said he was on a much older version... Like sept.
My understanding is that the ota for dec would only contain changes implemented for the month of December, this in this scenerio he would not get the patches for October and November with your method and i am not even sure if it would boot after that mismatch
It's really not saving much work if any over flashing the full version, and with the full version they're is no potential for bootloop due to missing some patches or updates. It's just much safer.
thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?
Tom2112 said:
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?
Click to expand...
Click to collapse
https://developers.google.com/android/ota
The most simple way to update while keeping root would be to follow the instructions for "Devices with A/B Partitions" at the following link in the Magisk documentation:
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Basically, Magisk allows you to restore the original boot image to the current partition so you can take the OTA when it arrives on your phone. Before rebooting you install Magisk to the inactive slot so that when the phone restarts you retain root without having to mess with Fastboot.
Delete Me!
Think all you have to do is click uninstall magisk, dont reboot... Take ota, but before reboot click install magisk/ install to empty slot...
Oops didnt see the reply above
OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?
Tom2112 said:
OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?
Click to expand...
Click to collapse
This should be a one time issue. One of the latest versions of Magisk changed the default location of the boot.img backup. They released it in December after most of us had already upgraded to the December Pixel update. This means we used the older version of Magisk when we installed the Dec update and it saved the backup to the old/original location. We then updated Magisk sometime later in December, but the Magisk update doesn't move the backup file to the new location (a poor execution from the Magisk team IMHO). Because we are now on the updated version, it expects the boot.img backup to be in the new location, but it is still in the old location and Magisk doesn't check that old location (again, a poor execution from the Magisk team IMHO).
To fix this you have several options.....
Option one is to find the original backup location that Magisk used for the boot.img and move it to the new backup location that Magisk uses. Unfortunately, I don't know where those backup locations are and didn't feel like researching it, so I used one of the other methods.
Option two is to "reinstall" Magisk (choose the patch file option and select the stock boot.img that may still on the phone from whatever the last update was (if you sideloaded the update and then had to rerooted the phone)- or download it from the applicable factory image and move it to the phone) to force Magisk to backup the current boot.img file to the new location. Stop after this initial step (ie you don't actually need to flash the patched file because it has already been done). Then you should be able to follow the normal Magisk update process to move to the January update.
That being said, I have horrible success being able to take the updates OTA (they usually fail) and usually end up sideloading the update. That is the final option - sideload the Jan update and then reroot the phone using the normal root method (ie getting Magisk to patch the stock boot.img file and then flashing the patched file).