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
Related
On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?
wy1d said:
On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?
Click to expand...
Click to collapse
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.
mac796 said:
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.
Click to expand...
Click to collapse
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA
mac796 said:
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA
Click to expand...
Click to collapse
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.
mac796 said:
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.
Click to expand...
Click to collapse
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it
mac796 said:
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it
Click to expand...
Click to collapse
Such a bummer the Magisk method doesn't work anymore. It's definitely the safest and most graceful.
Sent from my Pixel 2 XL using Tapatalk
Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?
I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.
droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.
charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.
How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx
sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs
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.
I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..
This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.
Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?
Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.
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).