Related
[UPDATE/KEEP ROOT GUIDE] OCT 2020 (RP1A.201005.004) "CORAL" Magisk/Stock Boot Images
PLEASE NOTE: I STILL HAVE NOT UPDATED TO ANDROID 11 YET, SO PLEASE FLASH AT YOUR OWN RISK AS ASSISTANCE FROM ME WILL BE VERY LIMITED. PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! AND SORRY FOR THE LATE POST. JUST GOT BACK FROM A LONG WEDDING WEEKEND, AND THE 8-HOUR DRIVE (EACH WAY) WITH A 9 MONTH OLD BABY WAS... QUITE AN ADVENTURE.
PLEASE DROP A THANKS IF YOU STILL FIND THESE GUIDES HELPFUL! :good:
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.201005.004, Oct 2020"!
Magisk Canary v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675557936
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675557937
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675557938
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RP1A.200720.009, Sep 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rp1a.200720.009-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682933260
coral-rp1a.200720.009-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682933258
October 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rp1a.201005.004-5e85d0f7.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rp1a.200720.009-factory-boot.img
3. fastboot flash dtbo coral-rp1a.200720.009-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rp1a.201005.004-5e85d0f7.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rp1a.201005.004-magisk_patched-21.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
i5lee8bit said:
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
Click to expand...
Click to collapse
It is safe to update to Android 11 and do a clean install by wiping data (so keep the "-w" in the flash-all.bat file), let the phone reboot into Android 11, setup phone and let it install your previous apps, etc.
Afterwards, install MM 8.01, change settings to beta build, patch boot image AND REBOOT THE PHONE. After rebooting, copy the magisk_patched image file to your adb (it should be 64 MB in size) folder. Proceed with using flashing the patched boot image.
I just updated to October's factory image a few minutes ago and success.
bb709394 said:
It is safe to update to Android 11 and do a clean install by wiping data (so keep the "-w" in the flash-all.bat file), let the phone reboot into Android 11, setup phone and let it install your previous apps, etc.
Afterwards, install MM 8.01, change settings to beta build, patch boot image AND REBOOT THE PHONE. After rebooting, copy the magisk_patched image file to your adb (it should be 64 MB in size) folder. Proceed with using flashing the patched boot image.
I just updated to October's factory image a few minutes ago and success.
Click to expand...
Click to collapse
I'm actually holding off because I'm waiting for a few mods to be compatible with 11, particularly GravityBox. Also, the purpose of my guides are to update without the need to wipe data / flash full clean factory image / seamlessly update with absolutely no additional setup. I know people say it's not so bad these days to set up from scratch, but for me it's still definitely a "ain't nobody got time fo dat" situation. =)
Thanks anyway though.
i5lee8bit said:
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
Click to expand...
Click to collapse
I didn't use your file. What I do is download the full firmware, remove -w and flash, then boot into TWRP and flash the Magisk zip. For some reason this October Update, it wouldn't decrypt my data when booting into TWRP so I patched the boot.img myself. I wanted to let you know that mine also came out to 64mb and after I flashed it to the boot partition, it worked perfectly. So I can "sorta" confirm that it should work.
i5lee8bit said:
I'm actually holding off because I'm waiting for a few mods to be compatible with 11, particularly GravityBox. Also, the purpose of my guides are to update without the need to wipe data / flash full clean factory image / seamlessly update with absolutely no additional setup. I know people say it's not so bad these days to set up from scratch, but for me it's still definitely a "ain't nobody got time fo dat" situation. =)
Thanks anyway though.
Click to expand...
Click to collapse
Seamless update is worth so much. Setting up a phone when its your daily driver is just so much work. No banking pin app will work, you have to set up messangers again, alot of apps will barely work (even with backup services like swift backup or titan) and some apps can't even be backuped at all and will create errors when loading backups.
@i5lee8bit, I just followed your tutorial to successfully upgrade the October patch with the files you provided. Everything is okay. Thanks a lot for your enthusiastic sharing.
WorldOfJohnboy said:
I didn't use your file. What I do is download the full firmware, remove -w and flash, then boot into TWRP and flash the Magisk zip. For some reason this October Update, it wouldn't decrypt my data when booting into TWRP so I patched the boot.img myself. I wanted to let you know that mine also came out to 64mb and after I flashed it to the boot partition, it worked perfectly. So I can "sorta" confirm that it should work.
Click to expand...
Click to collapse
I still haven't bothered with TWRP since the HTC U12+ days, and I actually found that I prefer it that way. Pretty sure TWRP needs to be updated for each (or at least most) monthly update btw. But thanks for the info, looks like 64mb is now the normal way Magisk outputs the patched boot image.
Morgrain said:
Seamless update is worth so much. Setting up a phone when its your daily driver is just so much work. No banking pin app will work, you have to set up messangers again, alot of apps will barely work (even with backup services like swift backup or titan) and some apps can't even be backuped at all and will create errors when loading backups.
Click to expand...
Click to collapse
Yeah, I only backup/restore certain apps (data or apps not on app store) when switching phones because there are always those little glitchy problems and what not if relying on TiBu / Swift too much. I'll use the built in backup/restore for certain apps (like Nova), but other than that when doing a clean install, while Android has better built in features to make it easier to migrate compared to a few years ago, it is still a major PITA.
blue2018 said:
@i5lee8bit, I just followed your tutorial to successfully upgrade the October patch with the files you provided. Everything is okay. Thanks a lot for your enthusiastic sharing.
Click to expand...
Click to collapse
Thanks for the info! Just updated the OP so there isn't a huge scary caution, lol. I figured it would be fine when I tested with August patched with v21.0 and still came out to 64mb, but thanks for the confirmation.
Silly Question Maybe
guys its been a while so pls have patience with my ignorance. I have Xfinity Pixel 4xl and need to use it on T-mobile. Under Developer options,. OEM Unlocking is greyed out and it does not allow me to modify. Am i screwed ?
I tried updating and I can't figure out why it is not working...
Upon boot, I am still on Sept patch with root.
Then eventually it tells me that an update is available to be installed and to reboot to finish.
When I reboot, it says that there was an error.
Magisk no longer has "install after OTA" option. Anyone have any ideas?
xclaim494 said:
guys its been a while so pls have patience with my ignorance. I have Xfinity Pixel 4xl and need to use it on T-mobile. Under Developer options,. OEM Unlocking is greyed out and it does not allow me to modify. Am i screwed ?
Click to expand...
Click to collapse
Sorry about the late response, but maybe this info might help (it's a post I made on slickdeals.net regarding b/l unlocking the P4 series): https://slickdeals.net/f/14385296-x...e-399-free-shipping?p=140865899#post140865899
Also important to note, there is a difference between SIM unlocking (so you can use with T-Mobile) and oem/BL unlocking (so you can modify / root the phone).
tl;dr on my slickdeals post: SIM unlock status controls the oem (bootloader) unlock toggle status. Verizon is known to be the only variant where they fully prevent BL unlocking. XMo is an MVNO off of Verizon. Nobody has reported yet whether it can be done on XMo variants even after SIM unlocking. So you might be screwed.
smithilberry said:
I tried updating and I can't figure out why it is not working...
Upon boot, I am still on Sept patch with root.
Then eventually it tells me that an update is available to be installed and to reboot to finish.
When I reboot, it says that there was an error.
Magisk no longer has "install after OTA" option. Anyone have any ideas?
Click to expand...
Click to collapse
Did you follow the OP / 2nd post exactly? And made sure you're sideloading the correct, Oct 2020 ota zip? Should work fine with the given instructions and links. Make sure you downloaded (or just redownload) all the correct files.
Tbh it sounds like you're just reinstalling the Sept update and boot files.
The November update is out. Anyone here already got the new files?
Morgrain said:
The November update is out. Anyone here already got the new files?
Click to expand...
Click to collapse
I do... not sure if there's a separate thread as this is for the October update.
Side note, I apparently can no longer BOOT to TWRP to flash the Magisk Zip as even the TWRP Coral Beta doesn't decrypt Android 11. So, looks like I'm stuck manually patching the Boot and flashing via bootloader.
GravityBox [R] was pre-released today! Thus, I was able to update, using this very method, all the way from August 2020 thru January 2021. Entire process took only about an hour, with no hiccups. =) =) =)
But luckily, that also means I can actually start confirming again, personally, that everything is working fine. I can happily report everything is working great after this update. SafetyNet is passing with the correct configurations, and January 2021 build is working perfectly so far with Kirisakura 6.6.6 (why @Freak07, why did you have to release as this particular version number?? lol).
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ1A.210105.003, Jan 2021"!
Magisk v21.2 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145709333
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145709334
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145709335
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ1A.201205.008, Dec 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq1a.201205.008-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675600188
coral-rq1a.201205.008-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675600190
January 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq1a.210105.003-ad8d5ecc.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq1a.201205.008-factory-boot.img
3. fastboot flash dtbo coral-rq1a.201205.008-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq1a.210105.003-ad8d5ecc.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq1a.210105.003-magisk_patched-21.2.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
[EDIT 01-13-2021] YET ANOTHER NEW SAFETYNET WORKAROUND (AS OF AROUND JANUARY 12 / 13):
Please see this post: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84285539
Thank you for the update guides as always.
Just wanted to say a quick thanks. Worked like a charm!
Worked like a charm
I'd like to ask someone for help! If you haven't updated yet (i.e. you're still on 2020-12 patch level [non-AT&T]), and NOT using Edge Sense Plus (Active Edge Mod in Magisk Manager and/or EdXposed Manager) NOR any of Tulsadiver's theming mods (3minit / clock / 9tiles / etc), could you please send me your stock SystemUIGoogle.apk file? You can find it, using a root capable file explorer app, under:
(root) /system_ext/priv-app/SystemUIGoogle/SystemUIGoogle.apk
It needs to be the stock, completely unmodified .apk, which is why I'm asking to make sure you're not using any of those mods I mentioned. Or, you could disable those mods temporarily (both Magisk and EdXposed), reboot, and pull the .apk file. Unfortunately whenever I pull it from Google's factory system image always seems to be corrupted. Would just be easier for me if I could get it from someone's up-and-running system...
Thanks!! I really hope someone can do me a solid...
Or, does anybody know if it's safe to "downgrade" to December 2020? Using the full factory image and removing -w flag (and replacing boot.img with magisk patched)? I would think it would work, but I've never tried, nor needed, to flash the previous month's firmware before.
i5lee8bit said:
I'd like to ask someone for help! If you haven't updated yet (i.e. you're still on 2020-12 patch level [non-AT&T]), and NOT using Edge Sense Plus (Active Edge Mod in Magisk Manager and/or EdXposed Manager) NOR any of Tulsadiver's theming mods (3minit / clock / 9tiles / etc), could you please send me your stock SystemUIGoogle.apk file? You can find it, using a root capable file explorer app, under:
(root) /system_ext/priv-app/SystemUIGoogle/SystemUIGoogle.apk
It needs to be the stock, completely unmodified .apk, which is why I'm asking to make sure you're not using any of those mods I mentioned. Or, you could disable those mods temporarily (both Magisk and EdXposed), reboot, and pull the .apk file. Unfortunately whenever I pull it from Google's factory system image always seems to be corrupted. Would just be easier for me if I could get it from someone's up-and-running system...
Thanks!! I really hope someone can do me a solid...
Or, does anybody know if it's safe to "downgrade" to December 2020? Using the full factory image and removing -w flag (and replacing boot.img with magisk patched)? I would think it would work, but I've never tried, nor needed, to flash the previous month's firmware before.
Click to expand...
Click to collapse
Well I have a pixel 4 xl and I've rolled back to android 10 back in October, due to 11's bugs. So in my experience it is safe to roll back to previous updates. Being that I flashed
Suavie103 said:
Well I have a pixel 4 xl and I've rolled back to android 10 back in October, due to 11's bugs.
Click to expand...
Click to collapse
Would you mind sharing what kind of bugs you are facing on 11 please? I was going to update from 10 soon.
Ghisy said:
Would you mind sharing what kind of bugs you are facing on 11 please? I was going to update from 10 soon.
Click to expand...
Click to collapse
No those bugs were when 11 was first released. The January 11 update is perfectly fine imo. You should update
Thanks as always. Works like a charm
I just got the OTA update this week (1-14-2021) and was just wondering if the 1st post is still valid? Right now I am on Android 11 (RP1A.200720.009). Which files do I need to download from Google to go from RP1A.200720.009 to the latest OTA? Thanks in advance!
I am confused on number 8 ( 8. fastboot flash boot coral-rq1a.210105.003-magisk_patched-21.2.img ) where do I get that patched img file from? I am already rooted with Magisk vf5593e05 (4835)
One more small question.... what does DTBO stand for? I have never heard of that?
OMG!!!! I did it!!! Woo Hoo!!! Took me about 30 minutes! I did not flash the " coral-rq1a.201205.008-factory-dtbo.img " because I am not using a custom kernel just straight stock!
It scared me at first because it was taking so long for my Pixel 4 Xl to boot back up but it finally came back on.
I also had to update Magisk to f5593e05 (21401).
I have now went from Android 11 (RP1A.200720.009) to Android 11 (RQ1A.210105.003) and I still have ROOT!!!
Thank you @i5lee8bit for this easy to use guide! I am still a noob using ADB but I am learning more and more!
Oh yea... you said "GravityBox [R] was pre-released today!" where can I get that from? Does it work good?
Is anyone monitoring this thread? I feel all alone!
Perfect write-up. Followed it as instructed, had my phone rebooted with the new update in less than 10 minutes. Even had to double-check that it actually updated since it rebooted so fast!
Thanks!
The February update is out. Anyone got the magisk patched file?
For some reason I'm getting installation error when trying to patch boot image. Tried canary & stable magisk APK. Can someone confirm this?
I got the same, on canary
No issues here. Everything worked first try. Updating phone now, guide will be up soon (assuming no other errors otherwise).
Edit: It's up: https://forum.xda-developers.com/t/...5-004-coral-magisk-stock-boot-images.4227845/
Will also be editing the Active Edge Mod for Edge Sense Plus module really soon, and will be indicated on that thread: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
i5lee8bit said:
No issues here. Everything worked first try. Updating phone now, guide will be up soon (assuming no other errors otherwise).
Click to expand...
Click to collapse
Same here. Working fine with Beta 21.4 on February update.
Hi,
Since I got my phone and rooted it in March I haven't received any OTAs.
From what I gathered, one could easily do so manually, but I did not see a how-to and my knowledge of pixels and recent android stuff is limited.
Could someone perhaps explain how I can do this? Also, should I take the OTAs by order (April and then May) or is it okay to just update to the latest one?
Cheers.
Yeah... My last phone still got offered OTAs when rooted but not this pixel. I guess Google can see that your BL is unlocked, or that you have Magisk and just doesn't allow the normal OTA?
Each month you gotta go fetch the factory image, remove the -w from the script and flash it. Then get Magisk to patch the boot.img and use fastboot to flash it (or boot it and flash from Magisk).
There's a slightly smaller full ota package you can use instead. It is not destructive by default but it takes a bit more work to get the boot.img out (payload dumper).
I see.
Can I install the May update straight away, or should I get the April one first?
Also, what is the name of the script? Is it flash-all.bat? Should I edit it within the zip or extract and rezip?
Ruttix said:
can I install the May update straight away, or should I get the April one first?
Also, what is the name of the script? Is it flash-all.bat? Should I edit it within the zip or extract and rezip?
Click to expand...
Click to collapse
Both full ota and factory are complete upgrades. You can jump straight to the latest version.
The factory image zip expands and has flash-all scripts (.sh or .bat, depending on your os - windows is .bat). That's where you have to remove the -w from (fastboot -w update blah.zip). You install factory images by running the flash-all script.
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
dannyzamora said:
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
Click to expand...
Click to collapse
Make sure you don't have any Magisk mods that may need disabling and updating.
And no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
JonasHS said:
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
Click to expand...
Click to collapse
Yes, that is the procedure I am referring to, the one I have always used, it is strange, as I said, I have followed the same steps as always:
1. Download Factory image of december for Pixel 6a (the last one available in the web).
2. Extract boot.img
3. Patch it with latest magisk app (25.2)
4. Reboot to fastboot
5. Use command "fastboot flash boot magisk-patched.img"
The command is applied correctly but when rebooting the terminal stays in the "Google" logo and after a while it reboots and returns to the same "Google" screen, so in a loop.
Lughnasadh said:
Make sure you don't have any Magisk mods that may need disabling and updating.
An no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
Click to expand...
Click to collapse
I don't have any modules installed, it's a clean install of everything.
It will sound stupid but... I did the steps indicated in the other thread and I have solved the problem, I have root.
I downloaded the december image of the Pixel 7 Pro, extracted the boot.img, patched it with magisk and flashed it with the usual command "fastboot flash boot magisk-patched.img" and it let me boot without problems and working root.
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
G5-User7080 said:
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
Click to expand...
Click to collapse
I know, the truth is that it makes no sense that I have given me this problem because I did not see anyone else with the December update talking about this particular problem, the closest thing was the post I mentioned with the beta, the phone had just arrived from the SAT but I do not think this influenced the problem, it came with the November update and I updated it to the December update.
You mentionned you downloaded the image for the Pixel 7 pro. I assume you made a type and are not flashing a pixel 7 pro image to a pixel 6a? If not then get the right image file.
Otherwise I suggest using the Pixel Flasher software posted in this forum. It's a really good piece of software.
No hassle with manual flashing anymore.
With Pixel Flasher I even update to new security patches with keeping root in like 4-10 minutes, by just downloading the image and then clicking a couple buttons
True to my knowledge, that shouldn't have been the case [ because many have used the Install to Inactive Slot method on their Pixel devices]. But unfortunately, this is what I'm facing for a couple of months. Ever since I rooted my Pixel 6A on the February build, I didn't receive either the March or April update. I have to always take the longer route of using the Factory Image to update my rooted Pixel. So does a rooted phone block the ability to receive OTA updates, at least on the Pixel 6A?
Yes, you cant take an OTA if youre rooted. Its simpler to just manually flash the update anyway.
binary**# said:
True to my knowledge, that shouldn't have been the case [ because many have used the Install to Inactive Slot method on their Pixel devices]. But unfortunately, this is what I'm facing for a couple of months. Ever since I rooted my Pixel 6A on the February build, I didn't receive either the March or April update. I have to always take the longer route of using the Factory Image to update my rooted Pixel. So does a rooted phone block the ability to receive OTA updates, at least on the Pixel 6A?
Click to expand...
Click to collapse
What steps do you take to manually flash these updates and preserve root?
Msninmx said:
What steps do you take to manually flash these updates and preserve root?
Click to expand...
Click to collapse
Disable all modules
Download the latest factory image
Extract Factory Image > Images folder > Boot.img
Patch boot.img via Magisk and send it to the platform tools folder.
Go to extracted Factory Image and edit flash-all.bat file via Notepad++
Change the last line command: fastboot -w update image.zip to fastboot update image.zip
Save the changes.
Transfer the entire Factory Image content to the platform tools folder.
Boot your device to Fastboot Mode
Run the flash-all.bat file and wait for flashing to complete
Once done, your device will boot to OS. Reboot it to Fastboot.
Now boot your device via Magisk patched boot file via fastboot boot file.img
Then use Magisk's Direct Install to get permanent root.
Finally, re-enable all the modules.
I have sent a video of this entire process to you, do refer to that as well [not sharing the video here as self-promotion isn't recommended here.
ctfrommn said:
Yes, you cant take an OTA if youre rooted. Its simpler to just manually flash the update anyway.
Click to expand...
Click to collapse
Just my personal opinion, but doing it via Magisk Direct Install saved me a lot of time and effort in the past. No need for a PC, no need to download the entire firmware, and no need for flashing anything via Fastboot either.
I flash multiple builds a day so it's not an issue for me