Related
I've read about updating to the latest OTA and keeping root from several places including from topjohnwu himself but still a little unclear about this and don't want to mess it up. So in the manager I click uninstall and then press restore images. Then apply the system update? I'm not understanding if I have to download the new boot.img to re-root? That's where I am confused.
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
Ok thank you. Unhiding magisk is not necessary?
qman66 said:
Ok thank you. Unhiding magisk is not necessary?
Click to expand...
Click to collapse
I don't think so
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
Is this pixel specific? Or do you think this would work on the 7T as well
In theory it should work with any phone that has A/B (dual partitions) support.
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
One question. I have viper4android installed and I'm wondering when I uninstall and restore images, then update, will I lose viper and have to reinstall and redo all of my settings when I reinstall magisk?
rellomar said:
One question. I have viper4android installed and I'm wondering when I uninstall and restore images, then update, will I lose viper and have to reinstall and redo all of my settings when I reinstall magisk?
Click to expand...
Click to collapse
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Badger50 said:
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Click to expand...
Click to collapse
delete
Badger50 said:
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Click to expand...
Click to collapse
Could you possibly give me little more detailed instructions? I'm just coming back to Android after using an iPhone for a few years so I'm a little out of the loop with flashing. Mainly, I'm confused when you said fastboot flash the the factory image with the -w removed.
rellomar said:
Could you possibly give me little more detailed instructions? I'm just coming back to Android after using an iPhone for a few years so I'm a little out of the loop with flashing. Mainly, I'm confused when you said fastboot flash the the factory image with the -w removed.
Click to expand...
Click to collapse
After you download and extract the factory image, you will see a file named, flash-all.bat. Within that file, toward the end of the script, you'll see the -w flag which tells the script to wipe your device. By removing that flag, your are essentially updating your OS without loosing any internal data kinda like an OTA does :good:
with magisk installed how we can check whether we have update on the road, simply check in settings work?
Badger50 said:
After you download and extract the factory image, you will see a file named, flash-all.bat. Within that file, toward the end of the script, you'll see the -w flag which tells the script to wipe your device. By removing that flag, your are essentially updating your OS without loosing any internal data kinda like an OTA does :good:
Click to expand...
Click to collapse
That worked. Thanks for the advice....makes updating very easy :good:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
DoughMucker said:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
Click to expand...
Click to collapse
Just a couple things to try.
1. Did you fastboot the factory image to both slots? If not I would try that first, without the -w of course.
2. When you patched the boot.img, was dm-verity checked off? If not, enable it, then patch it again.
3. Have you tried from a cmd....
fastboot flash boot magisk_patched.img --slot=all
Whatever it is, I hope you get it working :good:
Badger50 said:
Just a couple things to try.
1. Did you fastboot the factory image to both slots? If not I would try that first, without the -w of course.
2. When you patched the boot.img, was dm-verity checked off? If not, enable it, then patch it again.
3. Have you tried from a cmd....
fastboot flash boot magisk_patched.img --slot=all
Whatever it is, I hope you get it working :good:
Click to expand...
Click to collapse
Thanks for the suggestions. I tried each one. Unfortunately, no luck.
DoughMucker said:
Thanks for the suggestions. I tried each one. Unfortunately, no luck.
Click to expand...
Click to collapse
Bummer man! How about different 2.0 USB A to USB C cables and ports??
Badger50 said:
Bummer man! How about different 2.0 USB A to USB C cables and ports??
Click to expand...
Click to collapse
Just tried that too. :crying:
DoughMucker said:
Just tried that too. :crying:
Click to expand...
Click to collapse
Sheesh! You using canary or stable magisk? Either way, I'd switch to the other one and try that as well. If that doesn't work, then you may have no choice but to either factory reset, or remove all your drives, platform-tools, redownload everything, and start over. I can't think of many other things to try
Badger50 said:
Sheesh! You using canary or stable magisk? Either way, I'd switch to the other one and try that as well. If that doesn't work, then you may have no choice but to either factory reset, or remove all your drives, platform-tools, redownload everything, and start over. I can't think of many other things to try
Click to expand...
Click to collapse
I was stable before, but had just tried canary. Same situation.
I'm reading https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605/page6 and wondering if it's related to systemless hosts for adaway which i did not disable.
DoughMucker said:
I was stable before, but had just tried canary. Same situation.
I'm reading and wondering if it's related to systemless hosts for adaway which i did not disable.
Click to expand...
Click to collapse
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Badger50 said:
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Click to expand...
Click to collapse
I'm using 012.A1. Google updated their factory image/OTA site and removed the reference to ATT. I had double checked someone else's phone here that got the Dec OTA update and she had 012.A1 after being on 007.A3.
Going to take a break from trying things for a day or so because it's frustrating. Arrghh.
And thanks for the help!
Badger50 said:
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Click to expand...
Click to collapse
I did one final thing and it worked...I flashed your patched boot.img from here and it worked. Was it .012.A1? What version of Magisk Manager are you using?
DoughMucker said:
I did one final thing and it worked...I flashed your patched boot.img from here and it worked. Was it .012.A1? What version of Magisk Manager are you using?
Click to expand...
Click to collapse
Yep, that was from the .012.A1 factory image. I'm using stable magisk. Question, did you have dm-verity checked off before you patched the boot.img, and, did you disable all magisk modules before you patched and flashed the boot.img? Either way, I'm glad you got it to boot up :good::good:
Badger50 said:
Yep, that was from the .012.A1 factory image. I'm using stable magisk. Question, did you have dm-verity checked off before you patched the boot.img, and, did you disable all magisk modules before you patched and flashed the boot.img? Either way, I'm glad you got it to boot up :good::good:
Click to expand...
Click to collapse
The first time I successfully patched the November boot.img I did not check off dm-verity. I didn't either for the first time(s) I tried the December image. I only tried, unsuccessfully, with dm-verity checked after you mentioned it here.
I did have the Systemless Hosts module enabled when patching the December image. This is what I was referring to earlier when I mentioned I thought it was related to systemless hosts for adaway. I actually didn't realize that when you enabled that in Magisk Manager, that it installed a module. So I never thought I had a module active, but I did.
To end this saga...after getting root again, I did a Titanium Backup, Factory Reset, and re-rooted by patching boot.img again with Magisk Manager canary. It went smoothly, as it should have originally. Now to restore....
This error seems to occur when you flash a boot.img that doesn't match the exact firmware version.
=> Download the correct, currently installed full firmware package, extract the boot.img and flash it.
Solution
This occurs when you're on Android 11 build and try to install the Android 10 build.
There's a simple fix though, thankfully.
Download the Android 10 ota image for Pixel 4 XL from google, and extract the dtbo.img from it. Flash it using
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
If that doesn't work, you can flash the whole stock Android 10 build and then you can boot whatever you were trying to.
Please click "Thanks" if this worked for you so that others can see.
Same Issue on Pixel 3a XL - please Help
DoughMucker said:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
Click to expand...
Click to collapse
Pixel 3aXL with LineageOS 17
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now. No ADB Connection.
How can I get out of that?
I used the boot.img from the firmware I built Lineage on. Should I use a boot.img from LineageOS .zip?
What is dm-verity?
Can I get to my previous unrooted device?
''bootslot: b
enter reason: error boot prepare''
dadu1257 said:
Pixel 3aXL with LineageOS 17
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now. No ADB Connection.
How can I get out of that?
I used the boot.img from the firmware I built Lineage on. Should I use a boot.img from LineageOS .zip?
What is dm-verity?
Can I get to my previous unrooted device?
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Post your question on the Pixel 3a XL 'Question and Answer' thread, not the Pixel 4 XL 'Question and Answer' thread.
or
Post your question on the LineageOS 17 thread.
I just received my direct from Google Pixel 4 XL running the June 2020 update and proceeded to root it using the instructions found here https://www.xda-developers.com/google-pixel-4-root-magisk/ after flashing the patched boot.img and rebooting the phone doesn't boot past the G logo; the status bar just loops indefinitely. Is there something I'm missing? Any help would be much appreciated.
I have no modules loaded, no custom kernel or ROM.
Go to recovery and reset the phone,
And reboot the phone in each steps
The guide looks mostly like what I do every month, though I haven't done June yet.
I don't think this will solve your issue, but usually I flash the patched boot image to both slots as Magisk in-place updates seem to fail if I don't...
Code:
fastboot flash boot magisk_patched.img --slot=all
I assume you didn't have any obvious issues with the guide steps aside from not booting after Step 5?
Make sure your platform tools are the newest you can get. Also make sure that you didn't get the Telstra variant of the June update.
If all else fails, try to revert by dirty flashing the (correct) June 2020 stock ROM. You'll only lose root if you do it correctly. (you don't have working root anyways)
Take the giant ZIP file you downloaded to get the boot image, merge it with platform tools and edit the flash-all.bat file... near the bottom, remove the "-w " from the command so it reads
Code:
fastboot update image-coral-qq3a.200605.001.zip
Save the changes and run the .bat file after booting the phone to fastboot and making sure its visible to platform tools.
jljtgr said:
The guide looks mostly like what I do every month, though I haven't done June yet.
I don't think this will solve your issue, but usually I flash the patched boot image to both slots as Magisk in-place updates seem to fail if I don't...
Code:
fastboot flash boot magisk_patched.img --slot=all
I assume you didn't have any obvious issues with the guide steps aside from not booting after Step 5?
Make sure your platform tools are the newest you can get. Also make sure that you didn't get the Telstra variant of the June update.
If all else fails, try to revert by dirty flashing the (correct) June 2020 stock ROM. You'll only lose root if you do it correctly. (you don't have working root anyways)
Take the giant ZIP file you downloaded to get the boot image, merge it with platform tools and edit the flash-all.bat file... near the bottom, remove the "-w " from the command so it reads
Code:
fastboot update image-coral-qq3a.200605.001.zip
Save the changes and run the .bat file after booting the phone to fastboot and making sure its visible to platform tools.
Click to expand...
Click to collapse
Your first suggestion results in the phone booting, but ending up on a black screen with only the power menu
dirty flashing results in a successful unrooted boot, but rooting seems to not be possible for some users including myself. No clue why
Try flashing the patched boot to both boots but don't use the all slots command, do them one at a time, A, then B. See if that gets it.
So I am a fool.
I didn't run these commands using the latest "platform-tools"
but I will remember this instructions if I have issues in the future!
I am on latest platform tools and have tried all options presented and still get black screen with adb access and power menu. Other thoughts?
I just downloaded the full image and was getting ready to patch the boot image and flash it on my 2 day old Pixel 4xl. Maybe I will wait unless others have had success with this. I am on the June update. I made sure I didn't download the Telstra version.
Is there any reason to not just use the "Download Zip" option in Magisk? That always worked fine for me on my last phone.
Thanks, Chris
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
I took the plunge and it booted just fine. I am on a G020J if that help. Hardware MP1.0.
I did not realize that TWRP was not available for the Pixel 4xl yet. What is everyone using for a custom recovery?
reedc83 said:
I just downloaded the full image and was getting ready to patch the boot image and flash it on my 2 day old Pixel 4xl. Maybe I will wait unless others have had success with this. I am on the June update. I made sure I didn't download the Telstra version.
Is there any reason to not just use the "Download Zip" option in Magisk? That always worked fine for me on my last phone.
Thanks, Chris
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
I took the plunge and it booted just fine. I am on a G020J if that help. Hardware MP1.0.
I did not realize that TWRP was not available for the Pixel 4xl yet. What is everyone using for a custom recovery?
Click to expand...
Click to collapse
I feel like the options inside Magisk are for phones that are already rooted to update Magisk. I guess what your edit is saying is that you used to use TWRP with the ZIP?
Anyways, there are no custom recoveries for the same reason there is not TWRP. The partition scheme for Pixel phones that come with Android 10 pre-installed is too different for TWRP to live on it. I don't know enough about this subject, but I thought I read there was no separate recovery partition that could be made custom.
Everyone has been doing it all along, when people have issues it's usually the wrong boot image, wrong complete image, flashed boot image to wrong slot, used the factory cable (yes, it's a thing, don't use it or flashing), don't have the correct and/or latest tools. There was an issue with windows 8.1 and flashing, I don't remember what that was but those of you flashing and still on 8.1 you'll want to do a search for that.
@Brakiss, you may want to try the whole smash if all else has failed... THIS WILL DELETE YOUR DATA!
Start by going over to Goog ---> https://developers.google.com/android/images and getting the full factory image and the latest tools; even if you already did it do it again being careful to verify you have the correct image. While you're grabbing goods get the Magisk APK so you can install it after the image is flashed. For the flashing portion please follow the directions on that page to the letter. Do not use the factory cable; use an A to C. Before you flash run these commands one at a time
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
After flashing get the boot image directly from the factory image you downloaded and not any other source and move it over to your phone along with the Magsik APK. Install magisk manager and then use it patch the boot image. You'll take that over to your PC and flash it as usual but do it to both slots and do them separately, do not use the all slots.
jljtgr said:
I feel like the options inside Magisk are for phones that are already rooted to update Magisk. I guess what your edit is saying is that you used to use TWRP with the ZIP?
Anyways, there are no custom recoveries for the same reason there is not TWRP. The partition scheme for Pixel phones that come with Android 10 pre-installed is too different for TWRP to live on it. I don't know enough about this subject, but I thought I read there was no separate recovery partition that could be made custom.
Click to expand...
Click to collapse
Correct, there is no recovery partition anymore. That has been a thing for a while now and not specific to the Pixel. My Moto x4 that I used prior to the Pixel 4xl had the recovery in the boot image but there was still TWRP for it. Whenever rooting that phone you have to boot a custom recovery image then from in there flash the separate custom recovery image/zip installer. It would modify the recovery that is embedded into the boot image.
I really hope that devs smarter than myself will figure it out and make a way to get TWRP on there.
On Android 11 Beta 2.5, I patch the original boot image, I then send it via fastboot, I tried flashing all partitions, manually _a and _b and stuck on Google logo ... When I put back the original boot.img, everything works properly. Miss my root but haven't seen any help on this :| Worked until I switched to 11 Beta ...
I have the problem too
Just as Chronos300 reported, I got stuck on the G logo. Some of my problem may be self-inflicted since I was not careful enough in following the directions: evidently it's important to finish the process for unlocking the bootloader before going to fastboot again to flash the Magisk boot image. I got stuck on the G logo but thought that I would have my way out by flashing the July factory image.
Most of that process worked out: things were good until the end when I saw a lot of messages about files that aren't present in image-coral-qq3a.200805.001.zip like boot.sig or recovery.img. I guess these are optional: the *.sig files may be intended to contain a checksum or hash and the recovery.img may just have gone away with the recovery partitions. Finally was an error that was fatal:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
That's awful cheery. I see that the difference between flash-all.sh and flash-base.sh is that the former has the "fastboot -w update" that Shayded talks about. I tried running the update command as Shaded recommends, without the -w switch. This time it got farther, but this time the final message was "failed to extract 'product.img': I/O error"
Sure enough, image-coral-qq3a.200805.001.zip contains no product.img file. Is this my problem, or is the solution somewhere else? Would an older factory image have the missing file?
Sigh of relief
My phone's back in the land of the living. I had noticed the links on the factory-image page for the flash tool. Thinking that maybe these were better maintained, I thought to try out the August update for coral.
The flash tool downloaded whatever big image it grabs and then started into the installation. After a few minutes the fastbootd screen came up and the progress bar went to about 80%--and then everything hung. Hoping on hope, I decided I could leave it like this all night if I had to.
It might have taken half an hour, but it did finally come up with the screen saying everything had updated. Sure enough, it made it through the boot and came up to the setup screens.
Enabled developer mode, saw that the bootloader was indeed unlocked, and went about setting some settings. Haven't tried root yet, but it's sure great to be back in business!
epic_task said:
{...}
Sure enough, image-coral-qq3a.200805.001.zip contains no product.img file. Is this my problem, or is the solution somewhere else? Would an older factory image have the missing file?
Click to expand...
Click to collapse
Personally, I don't understand how you ended up without product.img... it's literally half of the internal ZIP file. (you're not supposed to extract this ZIP, anyways)
jljtgr said:
Personally, I don't understand how you ended up without product.img... it's literally half of the internal ZIP file. (you're not supposed to extract this ZIP, anyways)
Click to expand...
Click to collapse
No, I never altered that zip file and was not trying to extract individual files from it when making that final run of fastboot update.
What I can tell you is that I was sleepy by the time I was doing that. There were two things I missed noting at the time but see this morning: product.img is indeed in the internal zip file and a message a couple of lines above the final error message (I had left the terminal window open):
extracting product.img (2102 MB) to disk...ziparchive W 08-18 00:00:43 31524 31524 Zip: unable to allocate 2204832024 bytes at offset 0: No space left on device
Click to expand...
Click to collapse
I would think that my failing to wait for a complete boot with an unlocked bootloader before attempting to flash magisk_patched.img did something unfortunate to the partitioning scheme. Evidently the web-based flash tool cleared it up.
Maybe I'm suggesting the obvious... but do you have 2-4GB available on every drive? It's complaining there's no available space. Typically product.img is split into 500MB parts and sent separately... so you'd need at least 2x the space available for the parts.
The flash-all is generic and looks for some files which are not used by these phones. This failure described is usually the wrong cord, you must use a USB A to USB C rather than a C to C. If not that it's going to be a tools/driver issue. There are a number of guides which can show how to find and delete old drivers and reinstall new drivers. Removing the W gets rid of the wipe but doesn't otherwise affect the flashing and will have nothing to do with it's success or failure; you are in effect dirty flashing when you remove it from the flash-all.
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
pastorbob62 said:
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
Click to expand...
Click to collapse
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
Thanks KtownJeff, that does sound much easier. Why aren't others posting this much simpler solution? Has anyone else tried this?
I haven't tried it yet as it looks like they may be about to figure out the low call volume issue in custom ROMs and then these OTA updates won't be necessary anyway? I'll wait and see what happens over the next week or so.
I'm wondering why it's necessary to wipe the data though. Why isn't uninstalling Magisk and booting with the original kernel enough?
JerseyChewi said:
Yeah the calling issue is just a lineage thing...and lineage is so generically lame. mokee or corvusos are my favs. Most of the custom Roms work well.... and there is a lot more ROMS for our device that is not on XDA.... The Data may be fine Just back it up first....and I put this on telegram and if you haven't checked it out there is five channels for our phone with tons of stuff.....more ROM builds We also have Pitch Black Recovery now available which is twrp with a cleaner UI and lots more options
Click to expand...
Click to collapse
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
WHHAAAT?? I got a few questions...
Why is it important not to have the copy-partitions.zip installed?
Why you should be on slot _a?
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
WoKoschekk said:
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Click to expand...
Click to collapse
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
WoKoschekk said:
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
Click to expand...
Click to collapse
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
JerseyChewi said:
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
Click to expand...
Click to collapse
Assuming this is not your first time flashing the firmware and you already have a flash script/.bat file:
1. run the script
Done! One command and 5 min later you are on the latest firmware.
JerseyChewi said:
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
Click to expand...
Click to collapse
Motorola provides you OEM signed images and a .xml sheet with proper commands to flash them as a .zip file. I've never heard that someone bricked his device by using the manufacturer's recommended way. I think it's risky to use your own workaround just because you're nervous about it.
Even if you unplug the device in the middle of the flashing process you won't face any trouble. Every single flashing command loads the image into your device's RAM before it gets written to the device.
fastboot oem fb_mode_set = no matter what reboot command you run your device boots into bootloader
Why are you nervous about it?
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary.... so that way when OTA comes it will move to the B partition the way that it was intended to.....but the boot-loader is unlocked now both slots start with a boot-loader, bootloader_a and bootloader_b.. .and the on board preboot chip will trip the first flag that communicates with stock flashed boot image which also holds the recovery and the kernel... even if its backed up stock.img with magisk, it will break the next flag on the device along with the custom logo.bin.... now the custom logo if it is cloned with a moto signature official it wont matter and the only one Im aware is logo.bin for the TMOBILE REVVLY variant.... when you boot not flash the stock boot.img it bypasses the security chain until reboot.... I've flashed b slot on accident and then booted several GSI and other lake Roms and at some point ill notice on the bootloader screen that maybe i have April 2020 when Im running July 2020 version....which is headache to fix and i booted to b slot flash stock as normal let boot to the setup wizard then reverse to a and do it again because it brings it back together... now the mapping for the AB partition with duel slots t is standard for all ARM64 AB devices Bootloader a and b Boot a and b Radio a and b which is (firmeware) slot Vendor a and b System a and b....
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
the reason why I wrote it the way that I did was because I tried everything to OTA back and this was the only way it worked for me.... and trust me I stayed up for weeks trying to break it or fix it....I finally I came across a moto g6 thread where some one relocked there bootloader and didnt have the oem unlock set and they couldnt do anything to unlock it again using fastboot because the switch was grey out on developer options which means they couldnt root to fix..., I believe it was Sd_shadow that recommended trying to boot the boot.img like how we boot the twrp.img because it bypasses the security flag... well my first attempt it didn't work which led me to the mismatched boot-loaders and I kept at it and by process of elimination and fully learning the way these partitions communicate..... which is totally backwards from the way it used to be... If u leave data then flash back stock, the boot-loader thinks its fresh but finds its not......so boot-loop... tried it cussed and tried again and screamed but now its automatic. for me because of trial and error... I've been at this a few years now and I'm learning something new all the time and most of time when people don't post is because they either don't know or don't wanna give wrong info or maybe nobody showed them. There kinda is an unwritten bylaw at XDA (tough love)... you gotta learn by experience that way when get an opportunity to help or find a new way it makes it worth the stress
That is why I wrote it the way I did step by step in the easiest way possible because of my experiences and headaches...If it don't work you didn't follow directions.... Now I'm gonna tell you I re-locked my bootloader too and was not able to flash back ota don't even try its a waste of time because the only way to get that flag back is to re ball a chipset, or replace the motherboard, or buy a new phone....
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
KtownJeff said:
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary....
Click to expand...
Click to collapse
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
BTW: You can call me what you want but that doesn't make your statements right either.
WoKoschekk said:
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
Click to expand...
Click to collapse
KtownJeff said:
Yes correct it easier to flash rom after it is available for download with a month behind....
Click to expand...
Click to collapse
You should check your sources.
KtownJeff said:
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
Click to expand...
Click to collapse
I also want to leave my device in oem_locked state and not in flashing_locked
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
pastorbob62 said:
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
Click to expand...
Click to collapse
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
WoKoschekk said:
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Click to expand...
Click to collapse
I'm thinking not, since this was the first thing I tried when I got the notification for the update. And the update still failed.
WoKoschekk said:
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
Click to expand...
Click to collapse
Telegram didn't have it when I installed the update. LMSA kept giving me a "Decompression failed" error message. So I just reinstalled the stock version I was already on and allowed the update to complete. Then reinstalled TWRP and Magisk without any issues once I had all of my apps and data restored.
Not taking any offense here, but I am not a noob and while I didn't give all of the details to what I had tried I also didn't want to reinvent the wheel. I didn't think about eliminating the line "erase userdata". Since it was very simple with previous devices to do it I knew there had to be an easier way. By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
pastorbob62 said:
Telegram didn't have it when I installed the update.
...
By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
Click to expand...
Click to collapse
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
WoKoschekk said:
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
Click to expand...
Click to collapse
That's nice. But the one for my phone was not available on tracker until the day after I updated via OTA.
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
Click to expand...
Click to collapse
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
[email protected] said:
I tried this to go back to stock rom from LOS17.
I've never seen that error before have you tried google search for the error?
Click to expand...
Click to collapse
[email protected] said:
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
Click to expand...
Click to collapse
Don't know what your error means, but flash the stock ROM and it should be fine.
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...
Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help
features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.
If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.
Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work
features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.