Database Info

Please HELP pixel stuck on loading dots

Hello
I just got a new pixel and I tried rooting it using a video from Max Lee how to root Google pixel and I don't think its working for me since my pixel has been staying on the loading dots for a long time. >30 mins. I have the phone unlocked.
Is it because the pixel has a February security patch and the video has an old method? Please let me know.

Last command was
Fastboot boot boot-to-root.img
And then it instantly rebooted but is still on dots

trizzv said:
Last command was
Fastboot boot boot-to-root.img
And then it instantly rebooted but is still on dots
Click to expand...
Click to collapse
You used an old method. 3rd post in the thread below to flash it back to stock. But get tbe newer google image. Then second to the last post to root it properly.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242

I did that before you responded but thank you anyways!! Glad it worked. Do you know how to root now?
I'm on NOF26V Feb 5 security patch. Unlocked bootloader. I just don't know which method to follow now

trizzv said:
I did that before you responded but thank you anyways!! Glad it worked. Do you know how to root now?
I'm on NOF26V Feb 5 security patch. Unlocked bootloader. I just don't know which method to follow now
Click to expand...
Click to collapse
Same thread, second to the last post. But before you do that get on April so you dont have to do it again.

TonikJDK said:
Same thread, second to the last post. But before you do that get on April so you dont have to do it again.
Click to expand...
Click to collapse
How do I get TWRP after this method?

https://www.google.com/url?sa=t&sou...8c9HsqrcoQJRGmAjA&sig2=Ucuq_6EzplRpNxXXPEBOiQ.

TonikJDK said:
You used an old method. 3rd post in the thread below to flash it back to stock. But get tbe newer google image. Then second to the last post to root it properly.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Which ones do I download?

trizzv said:
Which ones do I download?
Click to expand...
Click to collapse
Do I still download SR3 2.79?

trizzv said:
Do I still download SR3 2.79?
Click to expand...
Click to collapse
Yes. And to your question before this I still use the RC 1 zip and image files.
---------- Post added at 02:56 AM ---------- Previous post was at 02:39 AM ----------
Put the RC 1 image on your computer in the folder with your adb files. Then download the RC 1 zip and the SR3 2.79 zip to your phone.
adb reboot bootloader
fastboot boot path to RC 1 image
It'll boot to twrp and from there install RC 1 zip. Once that's done I reboot back into recovery and flash the SR3 2.79 zip - reboot and prosper. Now if you want, when you reboot to bootloader at the beginning, run the flash all file minus the -W in that file and that'll flash the factory image without erasing data. That's how I do each monthly update. So get the latest image from Google before you start if you use this step.

OTA update with unlocked bootloader

I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?

geicogecko said:
I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?
Click to expand...
Click to collapse
I think you should be able to
Sent from my Pixel 2 XL using Tapatalk

You cannot take OTA updates normally with an unlocked bootloader. The phone will download the update, but the update will fail.
You CAN update manually using either OTA or factory images from here and following my guide here.
To sideload OTA images using either stock recovery or TWRP, follow the instructions here.

Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.

geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.

geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.

socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?

k.s.deviate said:
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?
Click to expand...
Click to collapse
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...

socal87 said:
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...
Click to expand...
Click to collapse
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.

k.s.deviate said:
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.
Click to expand...
Click to collapse
I downloaded the OTA directly from https://developers.google.com/android/ota, then rebooted into TWRP and flashed the zip.
I'm on stock software with the exception of Magisk and Flash kernel, so OTAs always fail. Thus, I have Automatic System Updates turned off in Developer Options.
Regardless of how you do it, the OTA will always overwrite /boot, so you'll lose custom kernel and recovery.

bobby janow said:
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.
Click to expand...
Click to collapse
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.

socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.

geicogecko said:
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.
Click to expand...
Click to collapse
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
socal87 said:
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.
Click to expand...
Click to collapse
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Yes. If you're otherwise stock aside from an unlocked bootloader, you can sideload the OTA zip...or, copy it to internal storage, reboot to recovery, and install it that way.
If you want to keep TWRP, you'll have to boot the TWRP image after installing and rebooting, then flash TWRP. The OTA does not wipe data (obviously); it just returns everything in /boot and /system to stock.

The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Click to expand...
Click to collapse
So I actually took the advice and relocked the bootloader. No issues. I think there was one app that I would've needed root for, but I can't remember what it was. I didn't use Xposed. I don't even know if it works on the Pixel. Like I said in the opening post, I only needed it to enable wifi hotspot, so others may notice it more.

Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.

ychongy13 said:
Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.
Click to expand...
Click to collapse
You should be able to install the latest OTA image using stock recovery:
https://developers.google.com/android/ota

Rooted testers needed for Edge Sense Plus, to customize Active Edge Actions

Mod was already available for the Pixel2.
If you don't know what Edge Sense Plus is, you can check it here: https://forum.xda-developers.com/pixel-2/themes/root-custom-active-edge-actions-edge-t3732368

Just curious but do we know it can be rooted?

krabman said:
Just curious but do we know it can be rooted?
Click to expand...
Click to collapse
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk

Will get pixel 3xl by November 8 9. I am willing to test it for you.

ill have mine by 18th or 19th ill help out if still needed.

Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
j to the 4n said:
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

WisdomWolf said:
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
Click to expand...
Click to collapse
Doing this would be extremely unwise without a copy of the stock boot image. I would advise you to wait till the factory images come out. Which should be soon. If you bootloop, highly likely, you will have a unusable phone until the factory images get posted.

Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Sent from my Pixel 2 XL using Tapatalk

Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.

WisdomWolf said:
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Click to expand...
Click to collapse
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.

I have mine. I'm willing to test whatever/whenever it's safe to do so.
I did enable the "OEM Unlocking" in the developer settings. It didn't come with a USB-C to USB -A cable, so I cannot connect it to a PC anyway.

I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Golf c said:
Your phone comes with a boot image.
Click to expand...
Click to collapse
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).

lensgrabber said:
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
Click to expand...
Click to collapse
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.

sd_matto said:
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
Click to expand...
Click to collapse
There is no "standalone" boot image yet. It comes with factory image. Which should be out soon. The boot image is in your device. You can patch the boot image with Magisk Manager or sideload the Magisk zip. I would not do either of those until you have the factory image. If you bootloop, your device will be useless without factory images

mattj949 said:
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
Click to expand...
Click to collapse
Did you use the "unlock_critical" version of the command or just "unlock"?

Golf c said:
You can patch the boot image with Magisk Manager.
Click to expand...
Click to collapse
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?

sd_matto said:
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
Click to expand...
Click to collapse
No 2 the boot image in the device. Unlock bootloader.
Download Magisk Manager apk. Im about ready to unlock mine right now. In Magisk Manager select patch boot image file. It will save a copy to your device. Transfer to PC.
Fastboot flash boot image. You will bootloop im sure. AVB has changed with crosshatch.
DO NOT attempt this without factory image.
I will be doing this when factory image comes out.

nirenshah said:
Did you use the "unlock_critical" version of the command or just "unlock"?
Click to expand...
Click to collapse
Just "unlock" the other one is not valid for this one. Sorry, I should have mentioned that!

My apologies gentlemen. You do need a separate copy of the the boot image from the factory image to patch in Magisk Manager. Sorry for the wrong info. Actually it makes sense doesn't it.

Golf c said:
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
Click to expand...
Click to collapse
I got my Pixel 3XL last night. Excited to get things going on the Pixel 3XL, coming from a Nexus 6P.
I was sad that the factory image isn't immediately available on google's site for this phone, and I don't want to brick it trying to install Magisk without a factory image to fall back onto.
In any case, woot, woot! Phone looks great and I'm going to transfer over my line today.
Cheers,
B.D.

Android Q Pixel 3 XL ROOT users Q&A

I am starting this thread for us users and experiences while using Android Q. What works, what doesn't. I am not a dev. I am a user. Not here to bash anyone if something doesn't work. @topjohnwu just got root released for this last night.
So one thing I found which I am sure will fixed soon is
SD MAID not working.
Afwall is working.
Systemui tuner working
Button mapper working
I am sure as we go on and they will all work great. But like I said this is just a post what you found thread. If something does work, post it. If something doesn't, post it. Even if someone needs something like an apk. Ask and shall receive. This is a time of helping each other. Not flaming and bashing. Thank you to everyone that has read this and thank you to all the great devs out there and thank you to us users that can exchange information peacefully.

Is it still not possible to write to /system?

w0rdie said:
Is it still not possible to write to /system?
Click to expand...
Click to collapse
Same here. I would think the File Explorer devs would have to update to support Q?

Quickswitch is not working, back button did not work for me with it installed

I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?

kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
I am using a custom kernel so I didn't try to root the stock boot image. But it seems other people are rooting the stock boot image. I would hope they can help you. If I get around to it, I will try and root the stock boot image to see if it works. Someone should be able to help. Custom kernel roots just fine

kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL

Eudeferrer said:
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin

so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kevdog98 said:
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
Click to expand...
Click to collapse
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked

i42o said:
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
Click to expand...
Click to collapse
Custom kernel. Singular is a go. That's what I'm running. I didn't have to flash both slots. That doesn't make sense at all. I am going to get my lazy ass off the veranda and flash the rooted boot image.
Edit: I have Pie in my inactive slot and QBeta 4 in my active slot. If that makes any sense to you guys?

What's the problem? Flashed to active slot only.

Your doing something wrong if you can't root the stock boot image

When I originally rooted Q I did it ota patch inactive slot. Bootlooped. I just went to factory recovery and wiped data. Has worked ever since. I believe mine was looping to modules not being compatible with Q yet. Also if you grab the Q image and pull the boot image. You can patch it that way too. With Q, it is finicky with apps because of isolated storage. Which is weird because zarchiver still sees all files but amaze only sees root directory. Files app I noticed is saying some files I have are folders and not disk images. Zarchiver says it right still. Fastboot -w to manually remove all data too. Sometimes Titan m drive can cause weird things that is why I go to stock recovery and wipe it that way, wipes the Titan m drive too.

Did anybody already try to flash ainur sound mod and can report if it's working? For me the main reason to unlock bootloader again and start root procedure on Q...

kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Same problem here. Already posted the issue at the Magisk thread.

alex1301 said:
Same problem here. Already posted the issue at the Magisk thread.
Click to expand...
Click to collapse
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304

Golf c said:
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Click to expand...
Click to collapse
Yeah, updated everyhting before getting started.

alex1301 said:
Yeah, updated everyhting before getting started.
Click to expand...
Click to collapse
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.

S8rooted&tooted said:
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
Click to expand...
Click to collapse
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.

alex1301 said:
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
Click to expand...
Click to collapse
Click on advanced settings. And make sure when you did patch it, it wasn't checked. It should not be now with 10. With pie it is. Q will not work with it checked. It will double check system to the other partition. And the slot with magisk doesn't match the untouched slot.

Android 11 Release

Android 11 has been released. Anyone upgraded yet on a rooted device?

Subscribing for root results.

I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.

fkofilee said:
I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.
Click to expand...
Click to collapse
I'm curious to know too!

We gots Root!
So far so good root is working

XMayhem2099 said:
So far so good root is working
Click to expand...
Click to collapse
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?

dimm0k said:
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?
Click to expand...
Click to collapse
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?

antiochasylum said:
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?
Click to expand...
Click to collapse
oops, I was hoping to do it via full image rather than OTA

dimm0k said:
oops, I was hoping to do it via full image rather than OTA
Click to expand...
Click to collapse
Probably better to do that lol. My ota is sitting at 1.72gb so it would seem to be a full image.

Did the 1st flash... Didnt boot - Unlocked BL - Looks like nothing flashed to Partition A / Boot A.
Flashing again now ^^

I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Do you use the canary build of Magisk or the stable release?

Anyone got a replacement for overscan?

matekaneve said:
Do you use the canary build of Magisk or the stable release?
Click to expand...
Click to collapse
Canary

Well after redownloading the Core Files and updating ADB - Looks like we are alive...
Checking root now.

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Not working here either, we need to wait for Magisk update, most probably.

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt? Did you flash the full image or OTA? Next step for me (after creating a new patched boot.img) would be to clean flash the full image. Best of luck.

do you have a link to the canary apk?
I tried going to the canary page, but the download link is dead. TIA
v12xke said:
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt?
Click to expand...
Click to collapse

Further down the page youll see it
https://github.com/topjohnwu/Magisk
---------- Post added at 20:29 ---------- Previous post was at 20:27 ----------
Also to add - Magisk Canary outputted a 4MB Boot Image which was wrong - Correctly patched it should be 32.55 MB roughly.
Make sure you pay attention that the boot.img has been patched properly.

I had trouble rooting but eventually got it to work. I deleted all previous boot images and patched images from phone and pc. Reinstalled platform tools. Grabbed fresh boot img from the factory image, patched it then flashed it. And we're in biz