Related
I am sure this has been asked and answered 100 times but for the life of me I can't find a definite answer. I have a Pixel 2 XL and it is rooted and I have Magisk and TWRP installed on it. I want to be able to install the OTA for this month, but I do not want to lose anything on the phone. I also would rather not lose Magisk or TWRP. Normally on my android phones I use ROMs and can just update through TWRP, but I want to stay on stock because I don't want to lose Active Edge. So can someone please help me by giving me step by step instructions or point me to instructions that are simple to follow so I can take the OTA?
I really appreciate the help.
I was having the same problem and was helped by some of the members here.. Best way is to flash the firmware after removing the -w from the flash all file. Then flash twrp and magisk.
Ota
Thanks for your help. I will try that.
magicmaker said:
Thanks for your help. I will try that.
Click to expand...
Click to collapse
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
rank78 said:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
Click to expand...
Click to collapse
Not that I'm aware of, but maybe some on the horizon...
Badger50 said:
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Click to expand...
Click to collapse
Hi, quick question
I am only able to do them steps above if I have done 'fastboot unlock_critical'? I have only done 'fastboot unlock'
Also I would need to boot into TWRP and flash a kernel + magisk to retain root?
You have to issue the "fastboot unlock_critical" command in order for the bootloader to update, since the bootloader is included in both factory images and full OTAs. Speaking of full OTA's, one of our recognized developers, @elliwigy, revealed (thread here) that it is possible to flash a full OTA image through TWRP, which eliminates the need to open the factory image and remove the -w flag from the last line. Flashing the OTA works because TWRP doesn't check signatures like the stock recovery. You will lose both root and TWRP upon reboot however, so you will still need to connect to a PC in order to reinstall TWRP so you can subsequently replace the stock Kernel with the Flash Kernel and then root.
I can verify this works, as I tried it with the May update.
Hi, I just tried to install the September OTA update based on the Magisk OTA installation tips however the installation of the update fails during step 1. At least I am still rooted on the August patch level. How can I update my phone without losing data? I thought about reflashing system and trying the steps again but I don't know where to get the factory images for 9.6.6.0 (August) or 9.6.8.0 (September). This is my first A/B phone by the way. Thanks in advance.
rfkd said:
Hi, I just tried to install the September OTA update based on the Magisk OTA installation tips however the installation of the update fails during step 1. At least I am still rooted on the August patch level. How can I update my phone without losing data? I thought about reflashing system and trying the steps again but I don't know where to get the factory images for 9.6.6.0 (August) or 9.6.8.0 (September). This is my first A/B phone by the way. Thanks in advance.
Click to expand...
Click to collapse
You can check @BubuXP's reply here it might help you out. :good:
On this page only the ROM for 9.6.4.0 (July) can be downloaded. Later versions are not available anywhere? If not I have to flash July with fastboot, root again and retry the OTA update?
rfkd said:
On this page only the ROM for 9.6.4.0 (July) can be downloaded. Later versions are not available anywhere? If not I have to flash July with fastboot, root again and retry the OTA update?
Click to expand...
Click to collapse
No, the only fastboot image at the moment is this. It should be not a problem downgrading, as long as the same Android version is involved (Oreo 8.1 in this case).
And yes, you can flash that fastboot image and then follow my guide to install Magisk, and then install the OTA update always following my guide, just to test that everything is working as intended.
This did not work. Seems like using flash_all_except_storage.bat was not the right choice, my unlock pattern during booting is not accepted.
rfkd said:
This did not work. Seems like using flash_all_except_storage.bat was not the right choice, my unlock pattern during booting is not accepted.
Click to expand...
Click to collapse
So you must use flash_all.bat, but you will lose your data. At the moment the data is in the phone memory, but is encrypted and you probably lost the decryption key when you flashed the other partitions, so not a great lose anyway.
I don't know if there is a way to get your data back.
Yes, I already did this. Had forgotten to disable the pattern.
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
So I decided to root my Pixel 3 XL. I've read a lot of tutorial and I'll root it later today. One thing I don't like is the fact I can't update OTA. Is there a easy way to update when the December update is out without losing data? Can I use the flash-all script?
open flash-all and remove "-w" (implies wipe) and you should be ok.
make backups as necessary etc
Chippelchen said:
So I decided to root my Pixel 3 XL. I've read a lot of tutorial and I'll root it later today. One thing I don't like is the fact I can't update OTA. Is there a easy way to update when the December update is out without losing data? Can I use the flash-all script?
Click to expand...
Click to collapse
Yes, but delete the -w from the flash-all batch file (and save/close the file before running flash-all). Also, be sure you have the latest SDK Platform-Tools. Here is the link. https://developer.android.com/studio/releases/platform-tools
Note after running flash-all.bat to return to stock (with -w flag removed if you want to preserve data), you will need to reroot. And then you'll need to do this every time an update comes out (monthly).
If you don't want to root again you could lock the bootloader AFTER you run flash-all.bat to return to stock. Relocking the bootloader will restore things like Google Pay and other apps that check Safety Net.
Thanks that worked. Could you guys also provide a guide how to go to stock firmware image again? I didn't find a guide.
Chippelchen said:
Thanks that worked. Could you guys also provide a guide how to go to stock firmware image again? I didn't find a guide.
Click to expand...
Click to collapse
The flash-all.bat is the stock firmware..
fury683 said:
The flash-all.bat is the stock firmware..
Click to expand...
Click to collapse
Thanks but somehow that didn't work on macOS. Is it also okay to open the .sh file and run the commands yourself?
Chippelchen said:
Thanks but somehow that didn't work on macOS. Is it also okay to open the .sh file and run the commands yourself?
Click to expand...
Click to collapse
Yes
Is not being able to flash an OTA update a TWRP issue, or is it the device itself?
And will this always be the case?
Gordietm said:
Is not being able to flash an OTA update a TWRP issue, or is it the device itself?
And will this always be the case?
Click to expand...
Click to collapse
It's a twrp issue right now. I'd either sideload the ota in the stock recovery or edit the flash-all.bat by removing the -w in it. Make sure you save the edited version before you run it.
Sent from my [device_name] using XDA-Developers Legacy app
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).