Hello all,
For the last 4-5 firmware updates I've had no issue using fastboot to flash the firmware images, then flashing SuperSU, ElementalX kernel, Viper4Android and AdAway host lists through recovery to update to the latest build but keep my root mods.
I would like to now to the same with DP5 (or, at the very least, the first official Nougat build when it drops soon) and make sure I do it safely without any bricking.
Here's the current status -
Bootloader: Unlocked
Build: Android 6.0.1 MTC19Z, July Security Patch
Root Status: Rooted
Root Mods: ElementalX Kernel, Viper4Android, AdAway
Essentially, I want the same set up/root mods as above, only on 7.0. My questions are as follows:
1. Does the process differ at all for both installation of the firmware (through fastboot) or root method (flash TWRP, flash SuperSU)?
2. Is a full data wipe required? Recommended?
3. Anything else I should know?
Thanks in advance for the help. I'd love to make this as painless as the monthly firmware updates without any hiccups.
- Moonboots
The process does not differ much for the installation of the firmware; all you need to do is flash the factory images and TWRP through fastboot, and flash SuperSU/root through TWRP.
However, for a working TWRP and root, you'll need to decrypt your phone again, which will of course wipe your phone's data and internal storage.
I suggest looking at this helpful thread over on the Nexus 6P forums saying how to switch to 7.0 here:
http://forum.xda-developers.com/nexus-6p/general/how-to-switch-to-android-n-preview-t3409538
Even though it's for the 6P, I have used it myself and the procedure is the same. Once you've done all that, you're good to flash the latest SuperSU through TWRP.
As for V4A, I'm not sure whether it is compatible with Android N yet. You can install the ElementalX kernel normally after installing 7.0, but I don't think it's been updated to DP5.
If you do decide to update to Nougat, the modified boot.img for NPD90G can be found here:
http://forum.xda-developers.com/nexus-5x/general/4-17-16-t3360574
Thank you! I actually kept my phone encrypted all this time. Have you seen significant performance increases by decrypting?
EDIT: I see it's actually necessary for working TWRP in 7.0, thus far. Interesting. I'll have to work on getting my data backups set tonight.
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
Worst things that could happen are: OTA fails to install or you have to reinstall Magisk through fastbooting/T
WRP, so just try it.
I just flash full factory image and flash TWRP, Flash Kernel, and Magisk again, instead of waiting for OTA to be available through the phone.
freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
To be safe i would use the flash-all for December update. It will take to back to stock kernel and remove magisk. Then take the January ota. I think that is a sure way and doesn't take to many step.
Better to do flash all bat of January Factory Image, and reflashing magisk after that,
You can edit the flashing script, removing -w to prevent it wiping your data
I've tried it twice to no avail. I was able to go back to magisk and reinstall. I haven't lost anything. Ymmv...
My Pixel 3 XL is currently on the Q beta program. I enrolled for the beta and got the update through OTA. I'm now planning to revert to stock Pie for a more stable phone until the Q final release.
Should I flash the latest 9.0 full factory image or just sideload the OTA image to return to a clean stock rom? Also, is it necessary to unlock the bootloader before flashing the full factory image?
Just roll up on Android beta web and wait the update.
sandy13an said:
My Pixel 3 XL is currently on the Q beta program. I enrolled for the beta and got the update through OTA. I'm now planning to revert to stock Pie for a more stable phone until the Q final release.
Should I flash the latest 9.0 full factory image or just sideload the OTA image to return to a clean stock rom? Also, is it necessary to unlock the bootloader before flashing the full factory image?
Click to expand...
Click to collapse
Yes, you must unlock your bootloader in order to flash a full image. Follow tutorials if needed to get the very latest adb/fastboot binaries on your PC. Download the latest (July) full image to your PC and extract the zipfile into the same folder where the fastboot/adb binaries are located. Unlock the bootloader using fastboot which will wipe the phone. Return to fastboot mode and run (or click) the flash-all script. I would not be switching back and forth between P&Q with a locked bootloader. Even if you never plan to root the phone, having the BL unlocked will just about make the phone un-brickable. Best of luck.
I have a consumer cellular branded XT2052-5. I'm running Android 10 Build Number QPGS30.82-135-16 which has the Dec 1 2021 security patch. I have successfully unlocked my bootloader, installed ofox recovery.img, and patched the boot.img using Magisk app. I'd like to update my ROM to the latest security patch.
As I understand from this webpage: https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/ one option is use the Android Settings -> Systems -> Advanced -> System Update to download and then install the OTA, but don't reboot until after running Magisk and installing on the new partition. However, while it seems to install "Software update unsuccessful, couldn't apply system update to moto e..." (not verbatim since the message disappears quickly). Note also that the update file size is listed as only ~65MB while the example screen in the instructions at thecustomdroid.com inedicate it sholud be >1.5GB.
Anyway, I have resisted patching the boot.img and installing it in the other A/B partition via the Magisk app and am wondering how to proceed.
Can someone help me?
Mike
I had the same issue when trying to update via OTA. After testing I realized that the reason I couldn't update was because of the custom recovery installed. So I started all over went back to stock firmware using a program called RSD Lite to remove custom recovery completely and updated via OTA then patched with magisk. I ditched the custom recovery since it is not needed if you are on stock firmware.
Just got the march security update. 490mb.
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
My phone went into bootloop today after updating Magisk (magisk update prompt), BEFORE march update. That was a bit odd. Maybe your bootloop has nothing to do with March update, but with the new magisk version being flashed is incompatible to certain modules.
Well hell, I am failing.....and understand the message, but dont understand why or what transpired....and not sure what bootloader the message refers to.....this is a factory flash....
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.0-8062051'.
Update requires 'slider-1.1-8118264'.
fastboot: error: requirements not met!
Hmm, now not exactly sure what to do....8062051 is the bootloader from the 2nd February image, so not sure where to get 8118264 so I can update.......very odd.
***EDIT: OK I see thats the bootloader from A12L not from A12.......wtf!!!!
****RE-EDIT: PEBCAK here on my end.....doh! Working now
Same here, just checked and it showed up.
I was running into issues flashing the Factory image via Fastboot so I decided to try the FLASH method from the Android Flash Tool. That worked. But when I try to install the Magisk patch file, it fails and then I get stuck in a bootloop. So there you have it. I'm going to have to deal with no root until someone figures out what's going on.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
Once I disabled the Typhus ROM Control module in Magisk then my phone booted with root enabled with 24.304. Magisk stable probably works too.
TimFlex said:
Just got the march security update. 490mb.
Click to expand...
Click to collapse
This in more in line with the following thread which is where you need to bring this discussion. We really don't need another misleading thread that is merely a Magisc "how do I...?"
April 10, 2023 TQ2A.230405.003.E1 Global - Root Pixel 6 Pro [Raven] / all relevant links
Pixel 6 Pro [Raven] March 9, 2023 I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them. Someone reported it to Google (added a comment about 34.0.1 to the existing...
forum.xda-developers.com
Same issue here. Flashed March factory image. No wipe flag. Flashed Magisk patched file. Stuck in bootloop.
Reflashed factory image and didn't flash boot image and I can boot up. I guess no root until this is fixed.
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
jcp2 said:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
Click to expand...
Click to collapse
Can you upload your patched file by any chance?
tonyfiore75 said:
Can you upload your patched file by any chance?
Click to expand...
Click to collapse
This is for Magisk Stable - Not Canary!!
Thesis so much @jcp2 !
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
mkhcb said:
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
Click to expand...
Click to collapse
Edit>>>> As long as you're on stock kernel, Canary is fine.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
I rolled back to Stable and still cannot gain back root....
I sideloaded the March OTA then rooted successfully with 24.3, but I didn't do the magisk uninstall.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
Not accurate. Using latest Canary (24304) and updated fine. Sideloaded ota in recovery, reboot to let system update complete, reboot to bootloader and flashed patched boot.img. All is fine.
did you try the patched boot.img I uploaded a few posts back? Make sure you're on March update with Magisk 24.3 stable before flashing.