yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Guides, News, & Discussion] ibolito:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
[Google Pixel 3 Guides, News, & Discussion] gmmurphy:
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
[Google Pixel 3 Guides, News, & Discussion] Oberbergler:
Thanks man :) Everything was right but I forgot to update adb and fastboot. Now I have root :D
[Google Pixel 3 Guides, News, & Discussion] thach562:
ignore me -- im idiot.
[Google Pixel 3 Guides, News, & Discussion] qtotter:
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
[Google Pixel 3 Guides, News, & Discussion] shrtrnd:
So I have a problem, maybe someone can help me with.

Back in March I made the following post:

"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/

Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/

Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.

So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "

After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)

So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.

I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.

Any idea what I could do? Can't run the uninstaller and can't reroot... ???

thanks!
[Google Pixel 3 Guides, News, & Discussion] ibolito:
Have you checked if your patched boot.img matches the firmware on your phone?
[Google Pixel 3 Guides, News, & Discussion] shrtrnd:
Well it's the same one I used to flash the firmware.

I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.

Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
[Google Pixel 3 Guides, News, & Discussion] GohanBurner:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
[Google Pixel 3 Guides, News, & Discussion] acidspider:
I had it working before I bodged a magisk module install
[Google Pixel 3 Guides, News, & Discussion] Lagarde:
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.

- Latest magisk canary

- Used the same firmware

- No errors anywhere along the way
[Google Pixel 3 Guides, News, & Discussion] rickthecabbie:
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img

To get the patched image over to my phone. It worked out great. I was able to reboot,

and see the root in Magisk Manager.

YMMV
[Google Pixel 3 Guides, News, & Discussion] wokija:
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
[Google Pixel 3 Guides, News, & Discussion] coachmarino:
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Ok. Read through the thread and want to make sure I'm not missing anything since this is my first time rooting a Pixel (rooted other devices before)...

Are we not required to install TWRP in order to root?
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
As far as I know, if you're on Android 10 with a Pixel, you can't install TWRP. Can't even use it as a temporary recovery.
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Wow. That is interesting to see. Gonna see if I can read up more on it. Times have truly changed from the days when CWM was the big dog of custom recoveries, followed by TWRP. Now, seeing I don't need/can't use either is interesting to say the least.
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
Yeah, they put out a public notice back in October, addressed more or less to Android 10 Pixel users, saying don't hold your breath. They were working on it, but it wasn't going to be an easy fix. That October letter was the last official thing I've seen on it, and I've done quite a bit of research.
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
Yeah. I read their post on their website and it leave me with this question:

According to their blog, the issue only affects Pixels that shipped with Android 10. Mine actually shipped with Android 9 (Christmas present I'm just opening and setting up). However, I've completely installed all of the current updates, including the December release. Does this guide still work for me since I was technically Android 9 to start and then upgraded to Android 10 before unlocking and rooting, or should I be using this one (the newbie guide)?
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
You cannot install TWRP on a Pixel 3 running android 10.
[Google Pixel 3 Guides, News, & Discussion] WIMPHunter:
Magisk root wipes Pixel on Android 10

Just so you know... I did this today on a spare Pixel (not a 2,3, etc) and it indeed rooted the phone. BUT it wiped everything, including installed apps, photos, texts etc. Caveat flashor.

Also, a minor quibble with the instructions. It would be nice to know how you intend people to download and extract boot.img ON A PHONE. I did it on a linux PC and used adb push to put the file on the phone in a place where Magisk could find it.

But Thanks for the root anyhow!
[Google Pixel 3 Guides, News, & Discussion] gatharot:
Did anyone try rooting whilst updating?

For instance:

1. Extract boot.img

2. Patch it

3. Zip it back to `image-blueline-qq2a.200305.002.zip` (march update)

4. Run flash-all.sh (with '-w' removed form last line to prevent factory reset)
[Google Pixel 3 Guides, News, & Discussion] Wout2426:
Did you try this method, or not yet ?

I'm rooted, on February, but still didn't get the ota notification via settings....
[Google Pixel 3 Guides, News, & Discussion] gatharot:
Not yet sadly, as my pixel3 is my daily driver and the last factory reset was one too many... I would rather do Magisk's rock-solid OTA update but I did not receive any notification since january now

So... I am looking for options without recovery installation but I dread doing it myself ^^
[Google Pixel 3 Guides, News, & Discussion] Wout2426:
Same here..

Maybe someone here can tell what's the most save way to flash the march ota manually, without loosing root.

Edit:

- In magisk app: Uninstalled magisk, back to stock boot.img

- Reboot, root is gone

- Downloaded march full update, removed the -W from te .bat file

- Used the flash-all command

- reboot

- Patched the march boot.img in magisk and flashed it to get root again

All worked fine, no loss of data or apps.

Link: https://xdaforums.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117 no.4
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Manually check for ota in settings, system, advanced. Use this, but read closely before doing anything. Pay attention when you can reboot. https://topjohnwu.github.io/Magisk/tutorials.html
[Google Pixel 3 Guides, News, & Discussion] Wout2426:
Thx for your answer. I did check manually, it said your up to date, February 5th.

I edited my post, I'm on March update now.
[Google Pixel 3 Guides, News, & Discussion] gatharot:
Manual check in System > Advanced > System update > 'Check for update' does not work anymore... I used to update this way before

[MENTION=1454401]Wout2426[/MENTION] : No need to go back to stock boot.img then, just uninstall/disable modules that potentially cause bootloops (such as active Edge) and then flash all without -w. You loose root upon update anyway
[Google Pixel 3 Guides, News, & Discussion] Wout2426:
I did, thx.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
My pixel 3 must be special then.
[Google Pixel 3 Guides, News, & Discussion] qualitymove13:
Patched Boot Image

Can someone post the March patched boot image for me? Once I click the install button to patch the image in Magisk Manager, the app closes. Ugh. TIA!

Edit: Running latest canary
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
Use latest stable magisk manager and patch.
[Google Pixel 3 Guides, News, & Discussion] luizffgarcia:
Yep just had the same issue, uninstall canary and use stable, it works
[Google Pixel 3 Guides, News, & Discussion] GrandAdmiral:
I'm already on the March update, but see the link in the OP is the original image for Android 10. I assume I can't use that one so can someone point me to the factory image for the March update?
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Google pixel factory image.
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
Factory images - https://developers.google.com/android/images

OTA images - https://developers.google.com/android/ota
[Google Pixel 3 Guides, News, & Discussion] gatharot:
Back here! So.. I actually got impatient and tried my luck to save the extra step of reinstalling Magisk after update and rebooting. There is already too many threads opened for updating in android 10 so this slightly specific way too update will be left here for your eyes only. Here goes...

Monthly update w/o losing root (for those ignored, like me, by OTA notifications):

Requirements :

- an already rooted device with Magisk Manager

- magisk modules known for causing bootloops uninstalled (active edge for instance)

- a plugged-in device on 'File transfer/Android Auto' and with USB debugging enabled

- the latest and greatest adb/fastboot binaries, get them there : https://developer.android.com/studio/releases/platform-tools#downloads

- a fresh backup of your system or a pair of eyes to cry if anything goes awry

1- Download latest image file from https://developers.google.com/android/images

2- Unzip the contents of the zip into your folder of choice (some might say the abd/fastboot folder though it works anywhere)

3- Unzip the boot.img from the inner archive (for march 20 update: `image-blueline-qq2a.200305.002.zip`)

4- Copy the boot image to your phone, then in Magisk Manager press Install > Install > Select and patch file > boot.img

5- Once Magisk is done patching, get the resulting magisk_patched.img back to your updating folder. If you cannot find it use the following command: `adb pull /sdcard/Download/magisk_patched.img` (*)

Interlude - Your folder should look like this:

.

├── blueline-qq2a.200305.002-factory-d7814508

│ └── blueline-qq2a.200305.002

│ ├── boot.img

│ ├── bootloader-blueline-b1c1-0.2-6085603.img

│ ├── flash-all.bat

│ ├── flash-all.sh

│ ├── flash-base.sh

│ ├── image-blueline-qq2a.200305.002.zip

│ ├── magisk_patched.img

│ └── radio-blueline-g845-00096-200114-b-6134206.img

└─── blueline-qq2a.200305.002-factory-d7814508.zip

Now back to the fun parts.

6- Rename magisk_patched.img to boot.img. Delete the original one, it has served its purpose

7- Update the inner archive boot.img to the patched one

8- Open the flash-all.sh/flash-all.bat depending on your OS and remove the '-w' from the `fastboot -w update image-blueline-<your_latest_image>.zip` line. This is what wipes your phone clean, so make sure to save the file once modified.

9- Double check requirements #2 and #3.

10- Run the command: `adb reboot bootloader` (*)

11- Run your modified flash-all script.

Hopefully, you are done and your phone is up-to-date and still rooted.

12- Reinstall your magisk modules, you missed them too much already.

(*) If you get an error here, try running it from the adb/fastboot folder.
[Google Pixel 3 Guides, News, & Discussion] codygs83:
Has anyone had problems running Tasker or modifying system files? Magisk shows I'm rooted. It grants permissions when I run the apps. But Tasker fails to run commands and file explorer fails to modify system files. Am I missing something?

Flashed patched IMG with no problems. Magisk shows I'm all good. I dunno what else I missed. ?*♂️
[Google Pixel 3 Guides, News, & Discussion] kancrutt:
anyone has stock backup of February boot.img? I've tried to restore images via Magisk to update OTA (March) but failed "stock backup does not exist!"
[Google Pixel 3 Guides, News, & Discussion] codygs83:
Does the patched IMG need to be flashed on both slots?
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
Normally it is flashed only to the slot that will be booted next. If you are having boot problems, sometimes flashing both slots will resolve the problem.

https://topjohnwu.github.io/Magisk/install.html
[Google Pixel 3 Guides, News, & Discussion] codygs83:
Yeah not so much boot problems, but root problems. Can't use Tasker or write to storage. Magisk shows I'm rooted. And grants the apps permissions. But still no root access when using apps
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
You cannot directly modify system on android 10. Only way to make changes is to do so systemlessly with magisk.
[Google Pixel 3 Guides, News, & Discussion] codygs83:
How do I do that? And would Tasker work after that?
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
Tasker should work anyway, unless you are running a script to change /system or something. To make a module read up on the magisk forums. There are too many variable for me to be able to explain.
[Google Pixel 3 Guides, News, & Discussion] SilvrDrgn:
Dirty flash of March image over working rooted Feb image fails

My Pixel 3 is already at Android 10 with Feb updates and rooted with Magisk. Trying to dirty flash the March image. Log from my command prompt is attached in "flash_failed.txt" file. At the point of the "extracting super_empty.img (0 MB) to disk... took 0.000s Rebooting into fastboot OKAY [ 0.057s]", the device does reboot, but it reboots into a "fastbootd" screen that I have seen before, but it doesn't appear to be the correct screen/mode for the phone to be in for the flashing to continue to work properly. That fastbootd screen has a volume up/down menu on it with reboot system, enter recovery, reboot to bootloader , and power off options. Anyone else get this issue? How do I get through this?
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
What type PC are you using to do the flashing? I have those same symptoms trying to flash from a Linux container on my Pixelbook. Linux looses the USB connection when the Pixel reboots, which causes the Pixel to reboot into the fastbootd screen. Try a different PC. Also make sure you have the latest platform tools. https://developer.android.com/studio/releases/platform-tools
[Google Pixel 3 Guides, News, & Discussion] SilvrDrgn:
I'm using a Win-DOHS 10 Home laptop, and I do have the latest platform tools installed. I downloaded fresh copy of those right before I attempted all this. Win-DOHS makes it's usual beeping noise during the Pixel 3 reboots as the USB connection goes away and comes back. The USB connection definitely comes back during the "extracting product.img (1984 MB) to disk... took 12.009s" step and before it actually tried to send the product image.
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
If you can't try from another PC, try to sideload the image. This thread concerns a similiar problem (with a chromebook) that was resolved by sideloading it. https://xdaforums.com/pixel-3/how-to/please-help-flashing-incomplete-t4070059

If nothing else works, you can boot Linux from a USB stick and flash from it. I've had good luck with this https://xdaforums.com/android/software-hacking/live-iso-adb-fastboot-driver-issues-t3526755

I don't know how recent their platform tools are, so you may need to update platform tools first.
[Google Pixel 3 Guides, News, & Discussion] SilvrDrgn:
Tried sideload, but kept getting invalid footer error. Tried USB stick, but it wouldn't boot. So, last resort - another Win-DOHS machine. Man, Win-DOHS really does suck. I tried it on another Win-DOHS machine (one that had never had my Pixel 3 connected to it before), ran the flash and it worked fine. So, I suspect it's something to do with the Pixel 3 USB drivers on the machine that has the issues. Thanks for the suggestions. Any idea how to get the Pixel 3 USB drivers updated on my machine that has issues?
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
Sorry, I quit using Windows over a decade ago. Google "allintext: adb windows driver", and you'll find plenty of suggestions. Beware of downloading drivers from a flaky site, though. That's a good way to get malware.

I don't know what Win-DOHS is, but if you have a government/corporate issued laptop there are likely security restrictions on use of the USB port.
[Google Pixel 3 Guides, News, & Discussion] SilvrDrgn:
OK, no worries. Thanks for your help.

Regarding "Win-DOHS" have you ever seen the animated TV series "The Simpsons?" Win-DOHS is my take on Homer Simpson saying "DOH!" all the time, because Windows makes me say "DOH!" all the time. :)
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
That's exactly why I quit using Windows. :laugh: Linux is much less irritating.
[Google Pixel 3 Guides, News, & Discussion] djetouch:
Hey guys i'm new on Android ! So i need your help ..

(Pixel 3 on Android 10)

I followed the guide, i have magisk installed and i think i'm rooted ! But when I've installed my first module i have to reboot and when i opening magisk again, it was not installed (20.4 stable) ...

I try to reinstall everything again and it's working but when i reboot it seems magisk is not installed !

It's normal ? I mean you need to do this everytime you rebooting your phone ?!

Thanks for the guide btw i hope someone can help me !
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
It sounds like you are using "fastboot boot magisk_patched.img" instead of "fastboot flash boot magisk_patched.img"

The first will only be a one time boot into magisk, the second will permanently flash it.
[Google Pixel 3 Guides, News, & Discussion] djetouch:
Thanks for the reply.I have reading all of the thread again and find the solution!

For some reasons "fastboot flash boot magisk_patched.img" don't work for me. (failed with partition)

"fastboot boot magisk_patched.img" work fine but after i have to reinstall magisk from magisk manager and reboot for permanently flash it !

Everything is ok now ! Rooted with magisk installed
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
Just to follow up, for future reference. If fastboot flash boot fails this would suggest your adb/fastboot is out of date. There is no reason it should fail other than that really. Glad you got it working either way.
[Google Pixel 3 Guides, News, & Discussion] unibombz:
Hello,

I have flashed both boot.img and magisk_patched.img

I am suck in fastboot no matter what. I cannot get back to the OS.

fastboot reason: reboot bootloader

i have tried slot a and b with no success

whenever i reboot it goes back to the fastboot screen. Any ideas?

EDIT:

I wonder if this is the concern

pixel 3 (blueline): The Pixel 3 and Pixel 3 XL come with a Snapdragon 845, Pixel Visual Core (PVC)

pixel 3a (sargo): The Pixel 3a and Pixel 3a XL come with the Snapdragon 670 chip

EDIT 2:

I was using sargo, and needed to use blueline - noob mistake

Thanks for the posts, it put me down a path to resolve this concern. All pixel users make sure you know the variant you're on :)
[Google Pixel 3 Guides, News, & Discussion] Echosen:
I did the same thing I think cause I'm stuck on the bootloader but I don't know

which Android 10 img to flash, there are several. I'll just tussle through them until

I find a compatible variant for Android Q

Edit: After patching 4-5 different pixel imgs I finally found Pixel 3 variant blueline. :eek:

didn't lose any data - it just paused the boot because of the incompatibility.

once the right variant is flashed the boot will continue as is.

I had such a stressful yet adventurous time finding the correct boot.img

I want to make it easier on others with my firmware

This is the boot.img for Pixel 3 Android Q2A.200501.001.b2

NOTE: go into settings before anything on Android version

and know what variant you are on before anything

For those of you that are stuck in fastboot before this, this variant is the OTA of May 20th 2020

so if you updated your phone to Android Q around that time this is the variant you're going to use

Link to Pixel 3 Android Q May variant:

https://drive.google.com/file/d/1JbX6r3pHnruOiMTuDL_mAxNlFDal9YQt/view?usp=sharing
[Google Pixel 3 Guides, News, & Discussion] Eejcloud:
Don't seem to be able to get this working on the June update, anyone else?
[Google Pixel 3 Guides, News, & Discussion] eriks0n:
I just tried with the June update. When I reboot I lost the screen's ability to sense touches!?
[Google Pixel 3 Guides, News, & Discussion] kondroid:
flashed the full package without wiping data, flashed the patched magisk boot, all working fine for me.
[Google Pixel 3 Guides, News, & Discussion] Wout2426:
Same here, no issues.
[Google Pixel 3 Guides, News, & Discussion] ShadowJP88:
After june update, in my case, the touchscreen didn't work after patching boot.img with magisk
[Google Pixel 3 Guides, News, & Discussion] eriks0n:
Oh, I'm not alone! We need to figure out why this is working for some and not others.

I'm using a Pixel3 - are you guys as well?
[Google Pixel 3 Guides, News, & Discussion] ShadowJP88:
Yes I'm on a pixel 3 too.

Luckily, I always only boot with the patched_boot. I use the Magisk app to flash the boot itself.

---------- Post added at 11:26 PM ---------- Previous post was at 10:56 PM ----------

I've install the canary build of magisk and that do the job, pixel3 rooted again :D
[Google Pixel 3 Guides, News, & Discussion] eriks0n:
Yup, I tried with the latest Canary build of Magisk Manager and it worked! Thanks [MENTION=6653950]ShadowJP88[/MENTION] !
[Google Pixel 3 Guides, News, & Discussion] Eejcloud:
Trying with the Canary build and the touch screen still doesn't work, feel like I'm doing something wrong. I'm assuming you're using the canary build of the manager and magisk itself? 20415?
[Google Pixel 3 Guides, News, & Discussion] eriks0n:
So when I first tried the canary release, it didn't work for me. I had the same no touchscreen problem.

So I ...

Delete the boot.img from the phone

Delete the patched boot.img from the phone

Reinstalled the latest factory image (wihtout wiping data)

Grabbed the boot.img from the latest factory image

Used the Canary Build of Magisk Manager to patch the boot.img and generate the patched.img

The applied the patched image

It worked

So it's possible you might be using the wrong version of boot.img, triple check you're using the right version from the factory image on your phone and it should work.