Database Info

January Patch

Latest update is out on the developer page of Google.

Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
?
I did not have to use a "patched" boot image thirty days ago . . . Normal old boot image did the trick.
.
You have to boot twrp but what do we gain by loading the twrp zip ? . nandroid backups ?

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Have no idea haven't even tried. Didn't know where to get started since I haven't seen anyone say anything about rooting with the January patch.

Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.

The update is good, I see no new features but I noticed big improvements in performances and RAM management

chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Just have to put twrp on and flash through that all good and tested even with swift installer for themes

TonikJDK said:
Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.
Click to expand...
Click to collapse
OK, yes, Magisk v18 worked fine by flashing it on TWRP

Link to download?
Sent from my Pixel 3 XL using Tapatalk

chakra said:
Link to download?
Click to expand...
Click to collapse
January 2019 Update (for Pixel 3 XL aka "crosshatch"):
Factory Image -- https://dl.google.com/dl/android/aosp/crosshatch-pq1a.190105.004-factory-7165155c.zip
Full OTA Image -- https://dl.google.com/dl/android/aosp/crosshatch-ota-pq1a.190105.004-5f23d043.zip

Can you flash via TWRP?

virtyx said:
Can you flash via TWRP?
Click to expand...
Click to collapse
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.

Just came across this bit of vague information but thought some might be interested. Apologies if it's old info, but seems to indicate the upcoming Feb 2019 update.
Feb 19 Various bug fixes as well as support for Optus VoWIFI + EVS codec activation.
Security updates for Android 9.0
Status: Complete
Click to expand...
Click to collapse
https://yescrowd.optus.com.au/t5/Blog/Android-Software-Updates-07-01-2019/ba-p/522497

sliding_billy said:
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.
Click to expand...
Click to collapse
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1

Shaftamle said:
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1
Click to expand...
Click to collapse
It does. Effectively, it does the same thing as the factory image without the -w. It just loads les files. I have been doing the factory image way for years on the OG Pixel XL and now the 3XL. I have done a sideload once just to see the process as well as an OG TWRP sideload once (when it was working) for the same reason. The factory method is the easiest and most reliable IMO. You just need to remember to remove the -w, LOL.

anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp

DrUnkeN_TiGeR said:
anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp
Click to expand...
Click to collapse
Could be a few things. Make sure you have the current fastboot/adb files, flash boot.img to both slots, make sure you have the most recent TWRP and stable Magisk files, verify all of your downloads and start over.

May security update is out

https://developers.google.com/android/images
Still 9.0, but it's starting a new quarterly build so might have some updates. No change log yet
There is this
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."

i did clean install of the recovery image this morning. all seems fine. nothing visually different

Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.

Atomregen said:
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Click to expand...
Click to collapse
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.

sliding_billy said:
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.

208.9mb too! Quite large for just a small incremental update too!

considering locking my BL and clean wiping...
google pay no longer works and its fustrating.

virtyx said:
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
Click to expand...
Click to collapse
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.

Atomregen said:
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck. After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
Click to expand...
Click to collapse
I had some issues getting the May update, TWRP 3.3.0-1, Kirisakura 2.3.0, and Magisk 19.1 to play nicely together. Lots of "rescue party" reboots at the "G" logo of booting after trying to install everything together. I basically did what you did to solve the issue too. Installed the May update (removing -w) then installed TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 18.1 and restarted back to system to make sure it all worked (which it did). After that I upgraded to Magisk 19.1 via the Magisk app and everything seems to be fine now. My temp solution until this was just use TWRP 3.2.3-3 which I had been using up until this point. That worked too and allowed everything to play nice from the initial installation.

Aren't you supposed to boot system before flashing magisk?

Atomregen said:
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
Click to expand...
Click to collapse
wangdaning said:
Aren't you supposed to boot system before flashing magisk?
Click to expand...
Click to collapse
I was wondering the same thing about whether you finished booting before installing Magisk. I completely boot after every step (Image, TWRP, Magisk, Kernel - ElementalX installed with EX Kernel Manager) and don't stack installs in TWRP. Been doing that for years, and it has saved me some time long term despite the couple of extra minutes during installs. My other thought was possibly a bad 19.1 file.
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
sstanton86 said:
208.9mb too! Quite large for just a small incremental update too!
Click to expand...
Click to collapse
Looking at new apps to backup in TB, there were about 7 new system apps that I saw and one that had been removed.

since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Sent from my Pixel 3 XL using XDA Labs

Atomregen said:
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Click to expand...
Click to collapse
I always reboot to the system after the factory image/monthly update is installed and allow it to finish setup. Then I fastboot into TWRP to install TWRP recovery, my kernel, and Magisk via the "add more zips" option in TWRP. I've been doing this ever since I got the device and never ran into issues until this May update. Doing this with the May update, TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 19.1 caused reboots like I described. However, reverting to TWRP 3.2.3-3 instead (my initial solution/fix) or Magisk 18.1 then upgrading Magisk to 19.1 (like @sliding_billy suggested) worked fine. This to me implies a compatibility issue of some type and not an issue with the method of installation.

Tulsadiver said:
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Click to expand...
Click to collapse
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?

virtyx said:
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
Click to expand...
Click to collapse
This is the way Freak recommends flashing his kernel. Did Freak change something?
Freak07 said:
Flash factory image with -w removed (if you want to keep data intact)
Do a reboot
Then you can boot to twrp and flash twrp, magisk and kernel (in that order)
Afterwards all should be fine.
I personally do a reboot after flashing twrp. Then back to twrp and magisk plus kernel...
Click to expand...
Click to collapse

Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
I always flash kernel before magisk. I've never had issues.

Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
not saying either way is right or wrong
but it makes sense to flash magisk LAST.

Anyone try to sideload the OTA? I believe the file is too big to sideload?

lucky_strike33 said:
Anyone try to sideload the OTA? I believe the file is too big to sideload?
Click to expand...
Click to collapse
I sideloaded. Worked fine.

Anyone else unable to root the May update? I installed the update, TWRP, and the kernel I use and everything was fine. After installing Magisk 19.1 the phone boots straight to a "System UI has stopped" dialog box. Substratum overlays were uninstalled before updating and uninstalling Magisk fixes the issue, leading me to believe that it is the cause.
I tried installing Magisk 18.1 instead to see if it would work, but oddly it doesn't seem to install at all. When I boot the phone Magisk Manager was installed, but it claims that Magisk is not installed and no apps can get root access.

Stock Android 11

Just Posted
https://developers.google.com/android/images#sunfish

fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.

I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?

Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs

hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4

I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.

Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.

moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary

@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)

fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik

tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img

Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse

good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints

Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk

Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse

Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk

fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you

mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy

I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?

Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk

Question Android 14 developer preview 1

So, has anyone tried the Android 14 developer preview 1? I have and it runs very well on our phone. Would love to hear your impressions.

I tried it briefly on my Pixel 5. Since Magisk does not appear to fully support 14 yet (Zygisk does not work), I ended up going back to TQ1A and am running the developer preview on an Android Virtual Device instead.

Tried it out just now, magisk doesn't detect root at all of a patched boot image, so its a no go as far as a daily use device for me at the moment

TechX1991 said:
Tried it out just now, magisk doesn't detect root at all of a patched boot image, so its a no go as far as a daily use device for me at the moment
Click to expand...
Click to collapse
You have to use the Pixel 7 boot image to patch and flash, like we did for some of the QPR2 Betas.

TechX1991 said:
Tried it out just now, magisk doesn't detect root at all of a patched boot image, so its a no go as far as a daily use device for me at the moment
Click to expand...
Click to collapse
I do not need a rooted devices, so I just used the Developer Preview to check out the new Android 14 release before it is officially released on my Bluejay.

V0latyle said:
I tried it briefly on my Pixel 5. Since Magisk does not appear to fully support 14 yet (Zygisk does not work), I ended up going back to TQ1A and am running the developer preview on an Android Virtual Device instead.
Click to expand...
Click to collapse
Have you tried Canary 25206? Magisk reports "Zygisk: Yes" (with Zygisk enabled in settings) for me on my Pixel 6 Pro running A14 DP1.

Lughnasadh said:
Have you tried Canary 25206? Magisk reports "Zygisk: Yes" (with Zygisk enabled in settings) for me on my Pixel 6 Pro running A14 DP1.
Click to expand...
Click to collapse
If I can figure out how to get Magisk running on an AVD, I'll try that. Tried patching the ramdisk image, that didn't work.

Lughnasadh said:
You have to use the Pixel 7 boot image to patch and flash, like we did for some of the QPR2 Betas.
Click to expand...
Click to collapse
ohhhhh. So just download the pixel 7 beta, extract the boot.img, patch it and flash it?

TechX1991 said:
ohhhhh. So just download the pixel 7 beta, extract the boot.img, patch it and flash it?
Click to expand...
Click to collapse
Yes

Question OTA wiped root. How to regain?

Hi folks, I am running a Pixel 6A that I rooted with magisk back in December. I stupidly did not disable OTA updates. Last night the QPR2 update came down and wiped root from my phone.
Bootloader is still unlocked and magisk app is installed.
I am confused about the best way to restore root. I see that the QPR2 beta required the use of the pixel 7 boot image. Does that still hold for the stable QPR2?
Also, the magisk app offers a way to choose and patch an image within the app. Can I get the pixel 7 boot image and patch it in magisk, or do I have to use the ADB/ fastboot method?
Sorry for the trouble. I promise I will disable OTA updates in the future. Thanks for any help.

Hello! I am also root user and if it is true that there was an update with the boot 6a not root and I had to use the pixel 7 or 7 pro (I do not remember which was) but if in doubt I would try only with the 6a just in case, the procedure is to download the full rom of the same version you have now, extract the boot.img, patch it with magisk and flash it by adb from the pc, is the method I use in each update and no problems until today, good luck and greetings!

If you are using Magisk Stable 26.1 or Canary 26101, you can use the Pixel 6a boot image to root as the problems mentioned above have been fixed with these versions of Magisk.

Problem solved. Y'all rock.

I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.

RimWulf said:
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
Click to expand...
Click to collapse
Download and open the zip => open "image-bluejay-tq2a.230305.008.e1.zip" => find your boot.img