Related
Any issues or new bugs?
I have Magisk, but no TWRP. I plan to flash-all with the -w removed to preserve data.
Has anyone else done the update with that process?
Yup, flash-all minus -w worked like a charm.
Me too, had no issues. I later booted twrp just to install magisk and youtube vanced, as always.
I flashed it, only prob I had is that the patched magisk boot image did not work and I lost root, however booting twrp and flashing magisk again fixed this
Link contains factory boot, and patched images, bootloader and radio from stated release
August 2020 (canary): https://drive.google.com/drive/folders/1SpBngNA35CnCCF57jK8wjhRUQEeyyCHG?usp=sharing
Tulsadiver module disabler: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867 (i think magisk canary disables modules if you boot into safe mode https://github.com/topjohnwu/Magisk/commit/a5d7c41d209527fe7b45a2ef7d031add9b6fad24 )
Way to update without flashing: https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md
here is a guide for getting root: https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
platform tools were updated in july 2020: https://developer.android.com/studio/releases/platform-tools
and a guide for google pay with root: https://forum.xda-developers.com/ap...7-1-22-pie-t3929950/post79643248#post79643248
Hide Google pay, Google play services, Google services framework, clear Google pay data after update and apply module.
old factory and patched images:
July 2020 (canary patch): https://drive.google.com/folderview?id=16-XxwJbT5VIIT1cbDTXIffdOuqwx3XCH
Feb 2020 (beta patch): https://drive.google.com/open?id=1WZ2-tza0IB3oICGFCHuj1GJKJr0nd8a3
Jan 2020 (canary patch): https://drive.google.com/open?id=1_zNt1i2uqbGhfEiWn0O716v9noJdR4uJ
Dec 2019(canary patch): https://drive.google.com/open?id=1JHc86ZOHkyNA0uJ6r43eLqG4oe6KBfGy
nov 2019(canary patch): https://drive.google.com/open?id=14GA7qrPITZ_-jYNDAFuC0bJiaKwGmqRP
oct 2019(canary patch) : https://drive.google.com/folderview?id=16bbXgyWwi8TmJNaih_UvdtXxB8fC5W0t
note: i think you can go into recovery mode to disable modules with canary magisk if you have trouble.
updated OP with nov images
one report of nov 2019 update breaking google pay
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
if you can push the magisk uninstall zip to your device, then fastboot booting into twrp then flashing the magisk uninstall zip that should do the trick.
swieder711 said:
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
Click to expand...
Click to collapse
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
jd1639 said:
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
Click to expand...
Click to collapse
Thanks for the pointer. I wasn't sure if that Disabler would work with the November image.
I ended up reflashing the factory default and than reapplying the correct files. I now have GravityBox running on the Nov Image!
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
ffchampmt said:
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
Click to expand...
Click to collapse
OP updated to show 19.5.
Had the same issue and ran into the problem getting the modules disabled. Glad you were able to get it up and running.
Sent from my Pixel 3 XL using Tapatalk
i think doing a full uninstall of magisk (removes modules and settings) might be best until twrp or something else comes along...
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
chinesecooler said:
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
Click to expand...
Click to collapse
wait no more!
Woop woop, time for my bi-annually update
dipstik said:
wait no more!
Click to expand...
Click to collapse
Which version of Magisk did you use to patch the boot image? I tried using stable and canary to patch the stock boot image when I updated earlier, but each time it would just reboot straight to bootloader.
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
dipstik said:
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
Click to expand...
Click to collapse
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Face_Plant said:
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Click to expand...
Click to collapse
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
comady25 said:
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
Click to expand...
Click to collapse
It is working for many and not for others. My wife's P3 rooted fine with canary.
jlokos said:
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Click to expand...
Click to collapse
I used this method and it worked with no issues. It was only the second time i used this method but with others having issues with the factory image and patched boot image i thought I'd give it a try.
In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
These files are to install Magisk. Please only flash it if you are already on March update. This is not March OTA!
Link courtesy of @i5lee8bit; March OTA patched with Magisk 20.4 https://www.androidfilehost.com/?w=files&flid=306923
Dear Mushtafa, great thanks to you! I've been looking for this all day. Thank you!
mushtafa said:
In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
Click to expand...
Click to collapse
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.
onlyguynamedniles said:
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.
Click to expand...
Click to collapse
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?
mushtafa said:
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?
Click to expand...
Click to collapse
No I'm still on January, I never got the Feb OTA and didn't bother to try manually since it didn't seem significant enough but I wanted this March update because of the new Pixel drop feature set.
You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware
mushtafa said:
You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware
Click to expand...
Click to collapse
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.
otrobruno said:
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.
Click to expand...
Click to collapse
You flashed the March boot.img on your February firmware? Why?
mushtafa said:
You flashed the March boot.img on your February firmware? Why?
Click to expand...
Click to collapse
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?
otrobruno said:
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?
Click to expand...
Click to collapse
If you're not getting the March OTA, you need to download it from Google and sideload it. https://developers.google.com/android/ota
There is a thread here somewhere which shows how to do this.
The boot.img I shared above is for people who need it for Magisk and saves them downloading the ~2GB factory file.
Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?
wonderlander17 said:
Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?
Click to expand...
Click to collapse
Affirmative :good:
dang is it that hard to understand . if youre build number does not look exactly like this QQ2A.200305.003 then do not use these boot.img's
its that simple this is not to upgrade you to the march sec patch with root this is for people already on the march sec patch to use to gain root
FIXED IT!! After taking the March update I flashed this patched img the phone boots up to a black screen. If you use the power button it brings up a White menu with "power off" "restart". So then I turn the phone off and load fastboot and flash the stock boot img and everything works again. Any ideas? Figured it out.... Magisk modules that were running.
Can you flash any of them without the use of a computer?
mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Nope. TWRP or any other recovery is not yet compatible.
mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Yes with ex kernel manager it's possible
Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923
i5lee8bit said:
Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923
Click to expand...
Click to collapse
Added to OP, cheers
[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.
Hello guys!
Something wrong happened with my blujay, I need ur help...
So here's the complete story:
1) since december I didn't have OTA update, I don't know why, and the system was telling me it was outdated everyday but up to date in the update menu. so I decided to download the latest OTA bluejay-ota-tq1a.230205.002-1ec64b58.zip and apply it.
2) that worked nice, it booted up updated to this version. But proposed me another security update to get me to march 2023 security update.
3) Allright, security update done, but without root. So I donwloaded the full image corresponding to the OTA i made, bluejay-tq1a.230205.002-factory-1b04ccc9.zip, extracted the boot.img, patched it with magisk 26.1, then flashed it through fastboot.
4) this is where things get naughty, I had bootloop. I imagine this boot.img was correponding to my OTA update, but then another update was done, and the boot.img was wrong for this one.
5) I tried to reflash the patched and original boot.img, same. I tried to reapply the OTA, same, still bootloop.
6) I just tried to patch the full image, removing the -w from the flash-all.bat to not wipe my data (the whole point is that I can't loose all that), and still the same, I have a screen from android recovery saying it cannot load the system and proposing me to wipe, which I don't want.
What should I do ? Save me please!!
You updated from the Feb 2023 patch to the March 2023 patch in step 2. You then downloaded and patched the Feb 2023 boot.img file and applied it, with the system being at the March 2023 update. This is where the issue is. You need to download the March 2023 image and flash the boot.img from this. It is possible though, that you are at the April 2023 patch if you did this very recently.