yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Guides, News, & Discussion] Eejcloud:
Thanks, figured it out. I have to use Canary version of Magisk Manager but the Stable version of Magisk itself and it works fine. Tulsadiver's Clock and Navbar swap mod was causing bootloops initially until I removed them.
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
Tulsadiver has updated his modules for June update.

Pixel 3
[Google Pixel 3 Guides, News, & Discussion] finesse:
Thank you for this, very helpful.
[Google Pixel 3 Guides, News, & Discussion] NickEspo:
Need magisk_patched.img for Pixel 3 (blueline) June 2020 update

Got a big ask from anyone: Can someone please post the magisk_patched.img for the June 2020 update for the Pixel 3 (blueline)? Or any 2020 update?

I might have put in a bad file, but whatever the reason after I fastboot-flash-booted my file, my phone's screen no longer responds to touches. Which means I cant try to re-patch the file. So if anyone has one, it would be REALLY appreciated!
[Google Pixel 3 Guides, News, & Discussion] robocuff:
Extract the stock boot.img from the factory image you downloaded and flash that with fastboot. That should get you going again.
[Google Pixel 3 Guides, News, & Discussion] NickEspo:
Thanks. I'd tried that, but everything was bricked. I figured out how to factory-reset (without recovery) using only buttons, but even after that the screen was still non-responsive. I ended up using fastboot to switch active partitions (it looked like B was corrupted) and did a flash-all on the entire (non-OTA) factory image into A. That worked.
[Google Pixel 3 Guides, News, & Discussion] schalacker:
If you're still looking for Blueline June 2020 (blueline-qq3a.200605.001) Magisk_Patched.img:

https://file.io/oyxBOc4p

That worked for me and was patched via MM 7.5.1 (267).
[Google Pixel 3 Guides, News, & Discussion] big in japan:
Hey all, I just soft-bricked and eventually was able to rescue my Pixel 3. I want to take another stab at installing Magisk but would appreciate someone confirming to me the order of operations. Currently, I'm running the June 2020 PixelDust CAF, and everything is working.

1) On phone: Install Magisk Manager

2) On desktop: Download Magisk patched boot image (https://sourceforge.net/projects/pixeldustproject/files/ota/blueline/magisk_patched.img/download)

3) Boot into Fastboot mode and flash magisk_patched.img - "fastboot flash boot magisk_patched.img"

4) Reboot phone - "fastboot reboot"

5) Profit (or the opposite, since I'm adding Magisk to use Google Pay.)

Many thanks, want to be sure I avoid another bricking!
[Google Pixel 3 Guides, News, & Discussion] big in japan:
Nevermind, answered here (in case it's helpful to whomever encounters this next): https://xdaforums.com/showpost.php?p=82825551&postcount=46
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
I've been out of the loop a minute. Can someone confirm the latest update? My system shows the March 5, 2020 as the security update, build number QQ2A.200305.002. That's not the latest is it? System update is saying it is when I run the update check, but I thought I read Google released another.
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
Well, they are released monthly, so obviously it is not the latest. For some reason you are not getting the OTA. Just dl the google factory image.
[Google Pixel 3 Guides, News, & Discussion] big in japan:
I've got another Magisk question: When I try to switch my Google Fi active device from my backup (a Pixel 3a) to my rooted Pixel 3 (running PixelDust), I get error code E0x30003 and a message: "Unfortunately, your Google Fi service can't be switched right now."

Searching for the error code has turned up nada. Is anybody familiar with this? Is it something that can be fixed with Magisk?
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
And I have to go in order, correct? No skipping?
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
Not sure if you try to ota, but with full factory image you can skip. Remove the -w from the flash-all.bat to prevent data loss.
[Google Pixel 3 Guides, News, & Discussion] Nedhsa Demixe:
Will give it a try. Thanks
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
I am getting an error when trying to update using the factory image. Running the flash-all.bat begins to flash, then it gives me the following error.

--------------------------------------------
Bootloader Version...: b1c1-0.2-6374987
Baseband Version.....: g845-00107-200409-B-6382632
Serial Number........: 8CPX1S072
--------------------------------------------
archive does not contain 'android-info.txt'
fastboot: error: could not read android-info.txt
Press any key to exit...

Any idea what I'm missing?
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
android-info.txt is in the image-blueline-qq3a.200605.001.zip file that is inside the factory image zip file. Do you see the following files in the directory from which you are executing flash-all.bat? Do you see android-info.txt in image-blueline-qq3a.200605.001.zip? Unzip it to make sure the zip is not corrupt.

boot.img

bootloader-blueline-b1c1-0.2-6374987.img

flash-all.bat

flash-all.sh

flash-base.sh

image-blueline-qq3a.200605.001.zip

radio-blueline-g845-00107-200409-b-6382632.img

Also, make sure you are running the latest platform tools. A new version was released in April. https://developer.android.com/studio/releases/platform-tools
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Yeah, all of the files are in there with the boot.img being the renamed patched image. The android-info file is in there as well. Could it be erroring because the system wants me to go month by month with the updates instead of skipping to the current?
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
If you are flashing the factory image, you don't need to go month by month. I'd try it with the original boot.img, not the patched boot.img. You can flash the patched image after the update. That's what I do for the monthly updates.
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
So what would be the appropriate sequence and coding that you use? Do I still modify flash-all.bat?
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
You still remove the -w from flash-all.bat. Your phone will be wiped if you don't remove the -w. This is what I do (I'm using Linux):

adb reboot bootloader

./flash-all.sh

adb reboot bootloader

fastboot flash boot magisk_patched.img
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Much obliged. That did it. :good:
[Google Pixel 3 Guides, News, & Discussion] Robshr:
Is there a way to write to the build prop with root in Android 10

Thanks in advance
[Google Pixel 3 Guides, News, & Discussion] Wout2426:
You still remove the -w from flash-all.bat. Your phone will be wiped if you don't remove the -w. This is what I do (I'm using Linux):

adb reboot bootloader

./flash-all.sh

adb reboot bootloader

fastboot flash boot magisk_patched.img[/QUOTE]

Just flashed the July update, no problems
[Google Pixel 3 Guides, News, & Discussion] 0v3rdr1v3:
i have followed step by step, but unfortunately i get stuck in the fasboot after the 8 step. Can anyone help me please?

i know my mistake now. i have downloaded an old firmware:eek:
[Google Pixel 3 Guides, News, & Discussion] dvquest:
Adb reboot bootloader
[Google Pixel 3 Guides, News, & Discussion] lee_enfield:
Does this work with Android 11?
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
Magisk Canary should work with Android 11. See the Magisk thread at https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
[Google Pixel 3 Guides, News, & Discussion] mhrussell1:
FWIW, the patched boot image would not load on my Pixel 3. Stuck on bootloader screen. I also could not revert to 10.
[Google Pixel 3 Guides, News, & Discussion] rczrider:
Anyone having trouble with magisk_patched.img and the September update?

I'm not new to this, so it (probably) isn't anything I'm doing wrong. It updates to the September just fine, only the Magisk-patched boot.img doesn't take. Bootloops into fastboot; restoring stock boot.img gets me back into Android without issue. I've done a combination of flashing stock boot.img, magisk_patched.img, reboot into bootloader, etc. Nothing works.

Using the latest Magisk Manager 7.5.1 (267).
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
You're not using the latest canary build. 7.5.1 is either stable or beta. Last I checked, the canary should look to install 20424.

FWIW, using the latest canary, I can patch my boot.img, and the phone will boot, but once I get into the actual OS (after entering security PIN), the whole phone freezes completely. Hard reboot via hold power button is the only thing that works. Had to reflash original boot.img to get back into the phone. Someone else reported this on John's Twitter thread, and there have been other mixed results reports for the Pixel 3.
[Google Pixel 3 Guides, News, & Discussion] Ipeacocks:
Tried to root Pixel 3 on Android 11.

So far unsuccessfully. If you try to flash patched boot produced from stable Magisk manager version - you will get bootloop. For fixing that flash original boot image from ROM archive via fastboot.

I've also tried to to flash patched boot produced from canary Magisk manager version. But it leads to non-working recent apps screen in any launcher.
[Google Pixel 3 Guides, News, & Discussion] rczrider:
That's correct. I didn't see anything in this thread suggesting I should use Canary for the September update of Android 10...

...except that I'm an idiot and didn't notice that September's update is actually 11. Derp :p
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
For using this method on the latest A11 update:

You must use the latest Magisk Canary build (currently 20425).

If you have systemless hosts enabled (primarily for adblocking) in Magisk before updating to A11, it is possible your Pixel 3 will freeze after your initial security login after flashing the patched boot.img. If this happens, get your phone back to fastboot (power + vol down should work) and run this command from your computer:

adb wait-for-device shell magisk --remove-modules

The cmd prompt should then wait for you to reboot your phone. When your phone reboots and adb comes active, that command will manually disable your modules. Currently, it appears at least the systemless hosts is causing the freeze, but it's possible other modules may cause it as well.

The disable code comes from the Magisk troubleshooting wiki here:

https://www.didgeridoohan.com/magisk/MagiskModuleIssues

The freeze issue started in 20424, and I have tested it to be persistent in today's Canary release, 20425.

A couple folks have brought this issue up in John's Twitter feed (he's the one who made us aware of the adb line), so I would guess he's working on a fix, but again, that fix does not appear to be present in today's release.
[Google Pixel 3 Guides, News, & Discussion] rczrider:
Thanks for passing this along!

Does this mean you could just remove the modules prior to flashing the patched boot image, boot up, then reinstall? Or is it that the modules can't be installed at all?
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
Magisk Manager doesn't offer the module options until the patched boot is flashed and Magisk itself is live on the device. And, of course, the device freezes before you can get into the Magisk app to disable once installed. If you updated from A10 without disabling the modules, they'll be persistent into A11 when Magisk is reinstalled, with no way in the Magisk app to remove them. Hence, the adb command.

At this point, it does not appear the modules, at least the systemless hosts, can be used.
[Google Pixel 3 Guides, News, & Discussion] JustinChase:
I had to uninstall Magisk Manager in order to install the Android 11 upgrade (Manager was stuck on loading screen). I'm now running Android 11, and have installed the latest Manager 2eb00187 (299) (10)

But it fails to patch the boot image blueline-rp1a.200720.009-factory-145e4cc4.zip

Where have I gone wrong, and what can I do to proceed?

thanks
[Google Pixel 3 Guides, News, & Discussion] mhrussell1:
Dumb question, but did you unzip the above zip file until you get to the image.../ directory that has a file called boot.img? That is the file to copy to the phone and let Magisk mgr to patch.
[Google Pixel 3 Guides, News, & Discussion] JustinChase:
I hope it's not a dumb question, because the answer is no, I didn't. I see nowhere in any of the guides I found that says to do this, and Magisk seems to work with the zip file, but ends up failing.

I'll unzip and put just the boot.img file on the phone and try again.

Thanks!
[Google Pixel 3 Guides, News, & Discussion] joomax:
Can confirm guide works perfectly for me on my pixel 3, September release of A11.

Used Canary build of manager, no hiccups.

Google Pay doesn't work yet though... SafetyNet fails everything :(
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Tried searching but xda produced pages upon pages of results...

Is there a quick guide somewhere for switching regular Magisk to the Canary build or do I just need to back everything out?
[Google Pixel 3 Guides, News, & Discussion] Chezbel:
If you go to Magisk Manager settings under the Manager section is an option for "update channel". I think that is what what you want.
[Google Pixel 3 Guides, News, & Discussion] mhrussell1:
This link allows GP to work on rooted Magisk Pixel3 phones. I did not have to re-edit the file going to A11.

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

Mark
[Google Pixel 3 Guides, News, & Discussion] josh4trunks:
I updated to android 11 using the built in updater and everything worked fine. I obviously lost magisk so today I tried tackling re-installing it. I patched the boot.img found in "blueline-rp1a.200720.009-factory-145e4cc4" and tried installing that; that got stuck on boot since I didn't use a canary build of Magisk Manager.

I tried fixing things by using "fastboot flash boot boot.img", but every time I reboot it eventually brings me back to Fastboot Mode with the reason "reboot bootloader". I see in my terminal I have flashed boot.img to both "boot_a" and "boot_b" so I am not sure what the issue is?

Any help would be appreciated. Need my phone for work and family =[

####

Checksums of boot.img are below...

md5 - 3d4d8854cbb2adb655dd5a091dfddcaf

sha256 - 48ad963af211403bf5079d2b62657cfb3b4b3031318049c432452ad62bf01a13

Production revision: blueline MP1.0(ROW)

Bootloader version: b1c1-0.2-5672671

---------- Post added at 03:44 PM ---------- Previous post was at 03:09 PM ----------

I ended up recovering using the steps in flash-all.sh. I didn't realize that would wipe my data... guess I'll need to re-set this phone, but that's ok. I usually do that when there is a new version of android anyway.
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
The current stable version (20.4) of Magisk does not work with Android 11. You must use Canary or wait for version 21, which should be released very soon.
[Google Pixel 3 Guides, News, & Discussion] Muledeer:
Magisk install Oct update Android 11

vers 21000 does not work you need to use vers 21004

I just completed a clean install from unlock all the way to patching Oct update android 11 (Pixel 3)

Magisk is working - Only issue is I cant install an APK to system\priv-app - keeps failing (same for system\app

Any ideas?

thanks

Mule
[Google Pixel 3 Guides, News, & Discussion] Pakabidu:
Flashed clean Android 11 and then rooted by pathcing boot with canary manager. SafetyNet fails, but GooglePay works fine (had to change dg.db values again though) and AdAway is also working, so I'm happy.
[Google Pixel 3 Guides, News, & Discussion] dadu1257:
Same problem, how did you solve it?
[Google Pixel 3 Guides, News, & Discussion] Jcxmt125:
I did exactly that, but now my phone refuses to boot. It says there aren't any valid slots to boot. could you please help? BTW I fixed it by flashing my phone with factory image but I still want root. I am on android 11(R)
[Google Pixel 3 Guides, News, & Discussion] Pakabidu:
I had the same issue, fixed by flashing both slots (flash boot magisk_patched.img flashes only slot A)

fastboot flash boot_a magisk_patched.img

fastboot flash boot_b magisk_patched.img
[Google Pixel 3 Guides, News, & Discussion] mhrussell1:
[post deleted] I think I spoke too soon. Looks like GPay and safety net still working.
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Been holding out hope that we'd get a stable magisk release so I would have to switch. Looks like going canary is the only way to go to get to Android 11.
[Google Pixel 3 Guides, News, & Discussion] mhrussell1:
Canary has been rock solid for me.
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Has it? I read it was still having Google Pay and SafetyNet issue.
[Google Pixel 3 Guides, News, & Discussion] mhrussell1:
Gpay works great. I had to do the dB SqlLite hack but it was a one-time thing back on A10. The only other thing I really want to work is AdBlock antd that works also.

Mark
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Systemless?

Also, where's the info on the GPay hack? Is it in the Magisk thread?
[Google Pixel 3 Guides, News, & Discussion] fyrmd:
Phone not connecting

I cannot for the life of me get my phone to connect to my computer. I have tried different cables, checking all of the settings I can think of, updating platform tools.

Device manager says "Device Descriptor Request Failed" and code 43. The phone shows up fine on my chromebook, although there is a problem with Linux there so that is not an option, but that lends me to believe this has something to do with my Win 10 computer. I am Android 11 September update, unrooted. The phone says it is up to date, will not load October or November update so possibly an issue with the September update?

Any direction would be appreciated-thanks!
[Google Pixel 3 Guides, News, & Discussion] mhrussell1:
Yes, systemless.

GPay Workaround

Mark
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
So, Magisk is now pushing 21.2 as the latest stable version. Is this the one that will allow us to upgrade to Android 11? I never got around to installing Canary.
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
Yes, Magisk 21.2 works fine with Android 11.
[Google Pixel 3 Guides, News, & Discussion] mitch_ruth:
Did you get this to work? I also tried flashing both slots and still no change. Haven't tried a clean install yet.
[Google Pixel 3 Guides, News, & Discussion] klemi71:
Can you please tell me how to apply updates? OTA dosn´t work any more since magisk can´t be installed to inactive slot any more. I downloaded latest factory image and ended up in wiping my phone. :-(
[Google Pixel 3 Guides, News, & Discussion] miggsr:
Number one typically you would need to provide a little bit more information regards to what device you're working with that way everyone here can understand more or less where to direct you to find the right information to resolve your issue.

Number two if you've already wiped your device then you've successfully installed the update there's nothing that can be done after you've already wiped your device unless you made a backup on your computer then you can restore that data back to your device and you should be okay now that you have the updated software / firmware and your data is restored back to device

Number three if it is a Google pixel that you have then if you download the original factory image there is a file that you can edit using Notepad++ there is a line that you need to remove two items save the file and then run it. The file that you will be editing or will need to edit is called "Flash All.bat" The line you edit if you are using Notepad++ you will need to look for line 23 it starts fastboot -w ..... That "-w" that you see just delete it and save the changes made.

If your edit is done correctly when you run that file to update your device to the latest firmware software your device will not be wiped and you will have successfully installed the latest firmware software.

BARE IN MIND THAT WORKS ONLY WITH GOOGLE PIXEL DEVICES!!
[Google Pixel 3 Guides, News, & Discussion] klemi71:
It's a Pixel 3 and I had a backup, already restored. Before flashing I extracted boot.img and patched it with magisk to flash it in fastboot to keep root. I modified FlashAll.bat and removed "-w", so far everything successful.

But my phone stuck in fastboot mode and I wasn't able to flash anything, so I used recovery mode to wipe and get access again.

So before running modified flashall.bat, do I have to uninstall magisk and restore boot.img?

Reroot from the beginning after update is applied?
[Google Pixel 3 Guides, News, & Discussion] klemi71:
In addition I'm on Android 11, January. Recovery is stock as so far there is no working TWRP.
[Google Pixel 3 Guides, News, & Discussion] miggsr:
That I am aware of no you don't need to reroute if you want a pixel 3 that is even easier there is a chance that one of your partitions might not be cleaned correctly so you might have to wipe both partition a and partition b to get the device up and running correctly I would say don't delete the backup you had saved and also a side note there is in fact a working twrp for Pixel 3. if you go to twrp.me go to devices your should find the recovery there.

Now to wipe the partitions on your device...

FORMAT PARTITIONS

Type ---> fastboot erase system_a

fastboot erase system_b

Or

fastboot format system_a

fastboot format system_b

So I'm going to recommend this find the default "flash all.bat" copy that back to the folder because you're going to run Android 11 update with that file so your device will be back to stock after you wipe the partitions that I have listed above. I don't recommend that you use twrp going forward nothing against it it's just that makes things much much easier. Anytime you need to do a update you will need to do the update following the method in the previous post that I listed with removing "-w"

So to summarize this post here

1. Wipe your partitions

2. Run default Flash all.bat

3. Load device

4. Restore your data.

5. Install magisk apk.

6. Patch boot img.

7. Reboot to bootloader.

8. Flash magisk patched boot img.
[Google Pixel 3 Guides, News, & Discussion] klemi71:
I'll give that a try! Maybe slot b is really corrupted.

Thanks a lot for your patience.
[Google Pixel 3 Guides, News, & Discussion] miggsr:
I don't think slot is corrupted but I can't say that doing an update incorrectly can cause an issue with the partition it doesn't exactly corrupt it but the easiest method to get your device to be able to do updates easy and to have the device functioning as it should without any issues would be just following the methods I've provided. A year ago I experienced some issues and with those steps I was able to start fresh with no issues since.
[Google Pixel 3 Guides, News, & Discussion] zedomax:
Getting error in fastboot "Enter reason: error boot prepare". Not working for me, on the latest 10 firmware like you.

---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------

My bad wrong boot.img...

---------- Post added at 08:05 AM ---------- Previous post was at 07:36 AM ----------

works fine thx OP!

---------- Post added at 08:43 AM ---------- Previous post was at 08:05 AM ----------

Thanks OP! I have just rooted my Pixel 3 XL using this method, works fine.
[Google Pixel 3 Guides, News, & Discussion] shrtrnd:
If I may ask, why is this only relevant for mac users? I didn't do this on windows and my phone won't boot up after flashing the patched img. Could this be the solution?
[Google Pixel 3 Guides, News, & Discussion] AndroidGX:
Theres nothing new in the steps described in this how-to. Those steps was known since many months ago, this is the classic and best way to flash root and keep the official updates warning from our Pixel phones.

I made a little ".bat" flashing script (for Windows) few months ago, I might share it if anybody is interested