After rooting, I suggest that you patch the stock boot.img again (the one that's already in your internal storage) so Magisk Manager can make a backup of it. This will be useful if you ever need to use Magisk Manager to update using an OTA. Take a look from 14:15 if you're a bit fuzzy on that. In hindsight, I should have unlocked the bootloader first, then started patching the boot.img, etc.
I have been trying to root my device with Magisk for about 3 days with no success. Each method I tried would end up with a step that either my device or computer was not compatible with. After watching this video and following it step by step I was able to root my Pixel XL seamlessly. This was the most concise easy to follow step by step process I have come across.
Seriously, thank you for making this video. I have gone through so many tutorials and videos only to have to start over and over. Your video was clear and to the point. Yes it's May 2023 and I am just now unlocking my Pixel 4XL. THANK YOU THANK YOU! I can now use VPN passthrough!
It's been a bit of a wild ride, recently an update to Google Play Services started using key attestation when checking Safety Net. If you choose to use the Canary builds of Magisk Manager, it will tell you which kind of evaluation was used to verify. But I've also heard that this was rolled back last month or so (for instance, my Pixel 3 running Android 11 Beta is using the basic evaluation), but this state is inevitable as mentioned by TopJohnWu, developer of Magisk. twitter.com/topjohnwu/status/1237656703929180160
I had to put "Quotation" marks either side of file IMG before I could push it to phone after I dragged it into CMD they where missing like yours...but then I noticed they appeared after you did it using the path copy...but i don't have path availability on my windows 7..just thought I should mention it if anyone struggling like I was... brilliant info thank you so much worked a treat...shame I can't get you Vance's you tube working..
Ah Windows 7, okay, I haven't used Windows 7 in a while, but it should encapsulate the path in quotes if it contains spaces. But I'm glad surrounding it in quotes helped you out in the end. Many thanks for your comment!
@@MaowDroid managed to update my pixel 3a to February update using your brilliant ADB commands...far better to watch on video and pause at each stage than to try and read through with the possibility of the author making a small mistake in the ADB text by seeing it actually working gives me confidence in trying it out. Thank you again for your excellent edited and compiled videos...your a ADB legend.
I guess double check that you've flashed the right boot.img (from the Factory Image) is the matching build. It'll make things easier if you were already on the latest build of Android beforehand! To see if it's a problem with Magisk, you can flash the stock boot.img (the one you got from the factory image) and see if that fixes the touchscreen issue.
@ 14:03 you typed /sdcard/ im a little confused because up until 14:03 there was no mention of an sd card. this makes me think that you saved all these files inside the phone from the computer which is why your directory is listed as f. can you clarify this please. I am at this step and stopped.
so ive scrolled back to 11:41 and see its still on your pc, possibly a file you created and named "storage" so im going to continue in hopes that the /sdcard/ is a magical spell lol
ok so I grew a set (im generally a paranoid person) and just went along. hopefully if anyone else is worried about the same as I was, dont be. just follow along and it works. thank MaowDroid
Hi Stephen, I seriously apologise for not responding sooner, but am I ever glad that you managed to go through with it. Just to clarify these points you've raised up: Storage (F:) is the label for my F: drive on Windows. Usually it's called Local Disk, but I like to name mine. It's no different to doing this on your C: drive, or in your Downloads folder (C:\Users\(username)\Downloads). /sdcard/ in terms of the Android file system is mapped to your internal storage. If you ever view the '/' (root) directory in a file manager, you'll see that the 'sdcard/' folder is a symbolic link to /storage/self/primary. So it's more of a shorthand for your internal storage. Let me know if you have any other questions!
Great guide as usual. I don't know about you but I miss the days when Google phones were developer friendly. There were so many custom ROMs for my old Nexus smartphone and I spent ages trying them all out. Pixels have made custom ROMs challenging, and I wasn't happy when I flashed Android 11 and it broke Google pay for a while until clever Devs made workarounds. It seems Google has forgotten that flashaholics like us are the very people their family and friends go to for advice on their next smartphones. They need to stop making it hard for flashing on their pixels. So many features that have made their way into vanilla Android began life on custom ROMs. A robust dev community is a win-win for Google IMO
YESSS!! Thanks for your comment, and wow yeah what a throwback! I started with the Galaxy Note, but really dug in with the Galaxy Nexus. I guess we've come a long way, and yep, flashing a new ROM every couple of days or even during the day - wow haha. AOKP, PAC ROM, CyanogenMod, PA... just to name a few. And yeah.. all those awesome innovative features, there were the gesture controls (forgot the name of the app), mini-tablet mode in Jelly Bean that was really pushed out in PA, I think it was hybrid mode or something), theming, floating notifications, customisable navigation elements... I could cry. Yeah its a bit unfortunate that we've got all these strings and nets for us to work through to get GPay or even the bloody Macca's app to work haha - perhaps the landscape is moving, I don't even need to recommend Pixels to anyone, they just show up with them haha
Did you ensure that you had downloaded the factory image that matched your phone's build number? And you're not on Android 11 by any chance? You can get your phone booting back up if you flash the stock boot.img that comes from the factory image you had downloaded earlier (assuming that was the correct one).
Really appreciate these videos man. Great work. I kept going back to your videos when I need to return my devices back to a lovely unroot status! Keep up the great content. 💯
Don't have a Pixel phone but thanks to rooting and customs ROMs I was able to resurrect my old beloved HTC One M9 and flash Android 10 AICP 15 ROM with Magisk root enabled🙌🙌🙌🙌🙌🙌 my Note 10 plus has been taking a break for the last 2 weeks.
Oh that's amazing! I loved the HTC M series! Rooting and especially custom ROMs bring life to our older phones, I'm probably going to be sticking with my Pixel 3 for a while now. :)
I ge this error: "FAILED (remote: 'oem unlock is not allowed') fastboot: error: Command failed. " when i type the command fastboot flashing unlock please what do I do?
You must enable OEM unlock as described at the start of the video. If that toggle is disabled, unfortunately you won't be able to proceed further as you've got a model that has the bootloader permanently locked. :( If you have enabled it; but it still says it's not allowed, your device would seem to have a locked bootloader :( usually from a carrier like Verizon.
Hi Sameer, you probably have figured it out but you would just need to flash the stock boot.img to remove Magisk. But for removing the modules, you may have to look for a "Core Mode Only" boot image for the Pixel 4.
Just install the canary Magisk Manager APK over the existing one, or you can choose to uninstall your current version of Magisk Manager and install the canary build.
After the step where It was supposed to install the magisk_patched.img, my pixel4xl now is stuck on the screen of the bootloader, it keeps restarting to the bootloader screen and not loading to the OS at all!! Any help? I tried to open the rescue mode, and now it is stuck on a screen with a dead android and "No command" message
Did you happen to be running Android 11? That requires a different version of Magisk to be installed to the boot image (at least v21 which is in the beta channel right now, or the canary builds). You should try flash the stock boot.img next time; and it should boot up (providing you had downloaded the correct matching factory image based off the build number of Android that was running on your phone).
does anyone know why im stuck on the fastboot image screen.on the bottom of the screen it says "error boot prepare". if anyone know how to fix this. please let me know thank you.
Hi Omar, I would double check that you downloaded the right factory image, remember it needs to match the current version YOU are on! You can try flashing the stock boot.img if you believe you've got the right build of the factory image just in case it's a problem with Magisk patching it. You can check out one of my update videos if you want to update to the latest version of Android 11 (but you'll just have to skip out on patching the boot image for now until you can get booted again).
Thank you sir. That was exactly the issue. I had the correct boot.img installed it still happened. But problem solved. Thank you. Keep the great vida coming. Good bless
Truly impressed; this is the first place where I will ask this question because it seems highly realistic that you'll answer it (and have the knowledge to). My device was rooted with Magisk working. It somehow became unrooted last month, and I get constant notifications that a new Magisk update is available. Anyway to re-root (it shows that magisk manager is installed but not magisk itself) without having to wipe?
Hi Camilo! It should be quite easy to do, yeah sometimes it just unroots itself, sometimes a reboot can bring it back. But in this case, you can flash the same magisk_patched.img that you made back then (provided you haven't updated your phone since patching that boot image (so the build of which the boot.img came from still matches the build number of the system you're on). To be safe, I'd check what your current build of Android is by going to About phone, or it will appear on the expanded quick settings panel (near the bottom). Then seeing if you already have that factory image on your PC (or somewhere), if not download the corresponding one, get the boot.img out of it, and patch it using Magisk Manager. Then flash the new magisk_patched.img like in this video, and exactly how you rooted it in he first place (minus unlocking the booloader as you've done that already when you rooted initially, this is where the wipe comes from), and after that you should boot up and be rooted whilst keeping all your data. (Although you should make a backup in case things do go wrong for whatever reason :) ).
Thank you for the tutorial! Will be using it as soon as I get my Pixel 4XL. Quick question, if I flash the Dirty Unicorns rom, would this tutorial still work on a custom rom? Or would the process be different?
You would have already unlocked the bootloader so no need to do that again, the process is pretty much the same where you'll grab the DU boot.img and use Magisk Manager to patch it; then flash that patched image in order to root. :)
getting stuck after flashing the magisk patched boot image. phone does not want to boot, getting stuck at the "G" loading screen. Any advice on what to do from there? I've already tried reflashing the file and still have the same problem. Any help would be much appreciated
i have the same problem, did followed the procedure again and again ...flashing the patched image bricks me in the G logo everytime and then i reflash the image file so i can boot and try again to patch...and it all started because the safetynet check reported false after rooting...now im stuck in unrooted and many apps not working...what can i do??
Hi Pierre. Are you able to boot up with the stock boot.img? You can flash it the same way as you did the magisk_patched.img (fastboot flash boot [drag in boot.img])? Are you also on Android 11? Currently Magisk v20.4 does not support Android 11 and you're required to use the latest v21 (just released 2 hours ago) which supports Android 11. link.squabbi.com/magisk Be sure to change the update channel in Magisk Manager to beta!
@@MaowDroid Thank you very much! I did end up flashing the stock boot.img file and my phone works normally, I am going to try and use your new Android 11 video to root my phone tomorrow. I think the problem was that I didn't have Magisk v21. Thanks for the videos, keep it up! 😄👍
for me it says magisk not installed after i successfully flashed the patched_boot.img - if i try and flash it to the different slot it also says flashing successfull, but it won't boot - so strange!
You should only need to flash it to the current slot (so no need to suffix the slot). Are you sure you've patched the same boot image (from the Factory Image) with the same build number? If you have doubts, try following through my update video for January.
Did you get the right factory image that matches your phone's current build of Android? Try flashing the stock boot.img just the same way as you had flashed the magisk_patched.img and see if you can boot up. Now that Android 11 is out, are you on Android 11? Because Android 11 requires you to use Magisk Canary builds to root.
Thx for the reply. Yeah I’m on Android 11. Currently Using the RP1A.200720.009 image but not able to boot up. Now showing “no command” with dead android image. In fastboot mode it show my phone is unlocked . Is it because I don’t have the right image or didn’t install properly so it won’t boot up? In simple words, a computer power up without windows install so it won’t run?
I mean it shouldn't have changed much, unless it has swapped slots for you. You should be using the factory image for the Pixel 4 or 4 XL (whichever you have), build number must match what you are currently running. If you're having issues booting up, you can check this video out about flashing the factory images to restore your phone (you probably don't have to wipe the phone so skip that, and skip relocking the bootloader). Then you can try rooting again but use the beta version of Magisk (change the update channel in Magisk Manager's settings) and make sure the latest version it shows is v21.
New Google Play Service does this, almost all modern devices will have this by default now. You can find more information about that on TopJohnWu's Twitter. @topjohnwu
@@MaowDroid Thanks, I solved this by remame and hide magisk manager. but "adb root" doesn't work in terminal on PC, while "adb shell; su" works properly. Do you have any suggestions on this?
did everything as described but when i try to boot the patched file i get bootloop..i did patched twice just for sure from the factory image im on but still no luck.any idea?
Are you certain that the factory image you downloaded matches your build number on your phone? Otherwise flash the factory image boot.img for now and we can sort it out later. I'm going to be away for a while so discord would help. :)
I have the pixel 4 the small one I'm a long time stock Android guy and have rooted phones and ran custom roms before loved the 6p so much ran ressurection remix awesome user experience now I am thinking of rooting the pixel 4 and running dirty unicorns what's your thoughts about it and what rom would you suggest
Sorry for the hugely late reply! I'm currently running Dirty Unicorns on the Pixel 3 and I love it! I've submitted some patches for DU so you'll be getting these new features soon.
i havent instaling roo/twrp for very long time... if my phone is A/B and also my phone have twrp on xda, can i just flash magisk via twrp without doing the boot.img thing ?
If TWRP works on that version of Android (currently it doesn't work well, or at all on Android 10), you can boot the TWRP image and then flash Magisk. It's just that we don't have TWRP for Android 10, so we are up to patching the stock boot.img with Magisk to root.
Hi Humberto, yep it should! I recommend that you stick with the canary builds for now (they seem to have fixed some bugs that are in v21). Especially if you count on hiding Magisk & Magisk Manager.
Can I remove Verizon carrier lock on a google pixel 4 by rooting the phone? I have a Verizon Google Pixel 4 when I check the IMEI lock/unlock status, it says the IMEI is unlock but when I put in another carrier sim card , I get a message stating that the phone is not unlocked. I called Verizon and they said the phone is unlocked but that due to their new locking policy, I might have to wait 60 days to use another sim card on the phone. My question is : Can I remove that lock by rooting the phone? Thank you
Hi Stephane, sorry for the late reply. Even if you could, which to my knowledge I only recall on really early Android phones, rooting the Verizon Pixel 4 is not possible right now due to it having a locked bootloader. You'll probably need to wait those 60 days for the network unlock to complete.
Will you be making a video so we can preserve root and perform December update? Also, I did not make a backup of boot.img, so I'm not sure how to do the OTA update via Magisk without it. Thanks!!!
I may have mentioned that if you just let Magisk Manager patch a boot image again, it will make a backup. Note that the backup is automatic when you choose to patch an image when installing Magisk. Once you do that, you should be able to follow the usual OTA update using Magisk Manager. I was on holiday, so I have some catching up to do 😉
Hi Way. Updates to Google Play Services means that most modern devices won't be able to pass ctsProfile anymore. Check TopJohnWu's Twitter if you want to find out more.
Do you HAVE to do magisk boot.img patching BEFORE you do the oem unlock bootloader? I unlocked the bootloader first thing I got the phone followed your instructions but can't get it to boot.
No, you should be able to do it at any time. Just to double check you got the boot.img from the factory image that is matching your current build of Android? Also did you notice your phone changing slots after flashing that patched image? (usually you start on slot A, but after an OTA, it will change over to B and vice versa).
Hi Silent Whisper, sorry for the late reply, correct me if I have misunderstood. I wouldn't recommend relocking the bootloader once your phone is rooted. Your phone should factory reset (but should retain root access) which would remove your Magisk modules (but theoretically leave Magisk installed). To be honest, I don't really understand your question. :(
Hi Marko, I've recently started Storage Redirect (requires Riru) to ensure that apps don't just roam around my internal storage looking at things (I'm looking at you Ingress). But AdAway + Edge Sense Plus (and Blobmoji), F-Droid Privileged Extension (Magisk Module) are the ones I use. For the Pixel 4, you could try out FingerFace, which allows you to use Face Unlock to pass as a fingerprint reader for those older apps (it didn't work for a few banking apps that I tried to use before).
I've been all over the threads and can't seem to find a system wide font changer with the pixel 4 xl... I'm using font changer right now. Any other suggestions?
There are some Magisk modules that we have to change the fonts, but I guess I'm waiting for custom fonts for the new font changer that we have in the themes menu. I haven't really had a look around about that yet.
I would like to be able to record internal sound like I used to do before; by example: I use AZ recorder to record Whatsapp videos with my family, etc. I notice recently that my videos dont have any sound, I did a quick research and I found that Android removed this feature. Do u know any company that can root my phone for me?.
That should have nothing to do with rooting. Does tapping on that notification not take you to the Play Store to update Google Play Services? You can just flash the original boot.img to unroot too.
It sounds like you're trying to open the boot.img. when you run the command after dragging in the boot.img, make sure the active window is the Command Window before pressing enter.
Hi brother! I want to ask you a question, will the phones which is android 10 out of box won't have twrp? I mean twrp team says it is hard to develop. Is it true that android 10 phones won't have twrp support.
TWRP won't officially support Android 10 currently, with the reasons you have found from the devs, there's been a lot of changes so it'll be a while before they can get it to work fully/properly. However, some older devices are OK, but they probably don't have all the major changes that Android 10 brought.
@@MaowDroid Ahh , appreciate the feedback sir , the reason I asked is because I want to get viper4Android but I don't want to lose my data at the moment. Thanks again for your help in this community ! Cheers !
this is the most detailed step by step videos with no falis , i did follow everything by the minute and got magisk installed as you described in the video...but i dont know how to enable superuser(or do i have to download it separately?) to make it work..cant find modules for the motion sense country restriction...can you help with that?
Hello! Magisk will handle all superuser requests via the Magisk Manager app. You'll get a prompt whenever an app requests root access. You can use MagiskHide Props module to add these props to your build.prop: forum.xda-developers.com/showpost.php?p=80729593&postcount=5 OR you can use Riru + EdXposed to do it: forum.xda-developers.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607 I think adding those props via the MagiskHide Props module/command (you'll need to do that via the terminal) is easier.
@@MaowDroid hi,I added the props via terminal emulator (worked much better than termux) and didn't work...it was so nice to see it working and rebooted just fine,but the motion sense option still grayed out.(I cannot send s screenshot though)
Did this happen after flashing the magisk_patched.img? Flash the stock boot.img for the time being. Was your phone on the latest update before you did this?
Interesting, does booting the stock boot.img help (although it would be temporary). You can try flashing the stock boot.img to both slots (fastboot --slot=all flash boot [insert boot.img]).
Your video is amazing. I try to follow it. My device is a pixel 4 QD1A.190821.007 but this file "10.0.0 (QD1A.190821.007, Oct 2019)" from official google repositorie does not contain any boot.image inside. What should I do? Using 007.A3 or i risk to brick my phone?
Does your phone boot up with the stock boot image? You can flash it the same way you flashed the magisk_patched.img (fastboot flash boot [drag in stock boot.img]). If you're running Android 11, you need to make sure you use Magisk Beta (v21) or the canary builds. Last thing that it could be is that you've downloaded the wrong factory image for your device (you need to make sure you download the matching factory image that matches what you are currently running on your phone).
hi . with you amazing vedio i rooted my device but cant enable motion sense in my country ,, and this is the only reson im looking for root for it ? any help
There was a Xposed module out there that did that. You can have a look at it here: forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917/
Hello, i have a Pixel 1. I rooted, installed twrp some time ago but i think i did an OTA Update or Upgrade to Android 10 and lost ROOT and TWRP. Should i follow this tutorial to regain it back or do other things? (xda is filled with different opinions and people stuck at G logo) Bootloader is unlocked.
@@MaowDroid Thank you. No, im not stuck, im using the phone normally but i just didnt know how to get root properly back. Il just use this tutorial again from flashing twrp as you said. Thank you!
Yep this method is still working! Whether it's worth it, is up to you. If you're interested in some Magisk or EdXposed modules. There are a few ROMs and kernels out for the Pixel 4 if you're keen to try those out, which is always fun to do! Which just require an unlocked bootloader and not root access. However if you're on Android 11, you'll need to use the Canary builds of Magisk Manager & Magisk.
@@saidjamoljiyanhodjaev8918 Ah I see. Just some quick Googling did not reveal anything useful apart from this app: play.google.com/store/apps/details?id=org.js.oledsaver&hl=en_AU It's not something that enables DC dimming. There have been reddit posts requesting the feature around 10-12 months ago and nothing else :( www.reddit.com/r/GooglePixel/comments/dq70ic/request_google_please_include_dc_dimming_option/
You running any custom rom I'm thinking of rooting I have the pixel 4 too thinking of running dirty unicorns not sure though this phone is so smooth and fast already don't know if it's worth it maybe so I can change the font lol that's about it
Got a sweet deal on a 3 month old 4xl ssving this video for when i pick it up :) Ask anyone know if its possible to spoof on pokemon go on ios 11 since magisk now supports 11? Was gonna downgrade to 10 then root.
I know, serials are fine with me (hopefully, please tell me if they're not haha), I was mainly trying to hide my IMEI (unless you can derive an IMEI from a serial number).
also sir Make video how to Apply Substratum Theme In Android 10. Fab/Ethereal Substratum theme is applicable in android 10. as always Root required since 10 is not systemless root.
I was sure Magisk is still systemless on Android 10. I do see that Substratum installs a module for (handling legacy themes IIRC). You should be able to apply them as usual (since the March update of 2018). But I'll have this on the back of my mind. :)
You could unlock the bootloader and flash Magisk. I have a video for the Pixel running Pie, it should be the same. If TWRP messes things up, you can follow this video to patch the stock boot.img to root instead.
you can follow this video basically for every google phone. i did the exact same steps on a nexus 6p with android 10 and it worked fine. just get the boot img from the rom you are using.
There's an Xposed module as well as some build prop mods I believe: www.xda-developers.com/enable-pixel-4-motion-sense-gestures/ Or you can try this without root: mspoweruser.com/want-to-use-pixels-4-motion-sensor-in-any-country-heres-how-you-can-enable-it/ I no longer have the Pixel 4 so I can't show you personally 😓
Yep this'll be fine! Just make sure you download the right factory image. Ensure that it matches your device's CURRENT build number, in Settings > About Phone > Build Number.
Hey! Thanks for Replying! Alright ill do that... I have a pixel 3a as my main phone but I'm not sure if I should or not. If I decide then i will follow this tutorial
@@officialveerbajaj Cool no worries! Think about what you're looking to do with an unlocked bootloader/root access (custom ROMs? changing emojis?). If it eases your mind, you can always revert back to the original state. You'll just have to set up your phone again. :D
I don't have the 5X so I won't be making a video about that unfortunately. But the basics would just be unlock the bootloader and find an Android 10 ROM (something like the Pixel Experience ROM) and follow the installation instructions.
You should be able to tell if you can enable OEM unlock, if it's greyed out then you're out of luck. Generally only Verizon models and T-Mobile have bootloader unlock restrictions (from what I've heard).
Pretty much, except you need to make sure you change the update channel of Magisk Manager to either beta or canary as those versions of Magisk (v21 or greater) support Android 11. You can have a look at my more recent video covering it: th-cam.com/video/sPvnmgon89U/w-d-xo.html
Can you make a video how to install motion sense because my phone not allow to use motion sense in Malaysia. And I know there a lot of people that have same problems as me. I hope you read this comment. Because thus is important Btw thanks for this video it's help me because there have a lot information. 👍👍👍 My phone Google pixel 4xl
Hi! Since Motion Sense works in Australia, I didn't have to use anything to enable it. I have heard of build.prop edits as well as an Xposed module that will enable it. build.prop edits: forum.xda-developers.com/showpost.php?p=80729593&postcount=5 Seems like there is a Magisk module to do it now: github.com/demj1206170/EnableSoli EdXposed module: forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917 Installing EdXposed: forum.xda-developers.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607 I'd recommend getting the latest beta builds of EdXposed from here instead of using the attachments: github.com/ElderDrivers/EdXposed/releases
@@MaowDroid I believe the culprit was me copying apps from my pixel 2 xl. I flashed may 6 build clean and everything is fine. Thank you for this video. I've watched it 100 times to get this stuff down lol.
@@MaowDroid they are not officialy sold in my country. there are few big shops that import them but the price is high, same for oneplus :'( but one day i would like to own one! maybe i will order pixel 4a from germany
Hi Scorned Cripple, sorry for the late reply! I'd put Linux folks up a bit higher to work things out, but I think the trickiest part for Linux users, is to get the platform tools working. I know Ubuntu distros have them available in the package manager, but they're out of date most of the time. I'll look at doing a Linux video soon, just to see how it plays out. :)
@@therealmrstaten1 don't hesitate. the 1st thing to do after buying new phone is to Unlock the bootloader.. incase of System damage / system corrupt after update. if the User dosen't know or no background in Unlocking oem or usb debugging in dev. options you can't flash the fastboot rom since your phone is not visible in Device manager. /fastboot
![How to Root Android 10! [Pixel/Pixel 2/Pixel 3/Pixel 3a/Pixel 4/Pixel 4XL]](http://i.ytimg.com/vi/7T8HnpVLMdg/mqdefault.jpg)
![How to Root Android 10! [Pixel/Pixel 2/Pixel 3/Pixel 3a/Pixel 4/Pixel 4XL]](/img/tr.png)
After rooting, I suggest that you patch the stock boot.img again (the one that's already in your internal storage) so Magisk Manager can make a backup of it. This will be useful if you ever need to use Magisk Manager to update using an OTA.
Take a look from 14:15 if you're a bit fuzzy on that. In hindsight, I should have unlocked the bootloader first, then started patching the boot.img, etc.
One of the clearest, most organized videos I've ever seen. I want all TH-cam videos made like yours!
Thank you Elijah! My intentions exactly, let me know if you've got any other feedback/suggestions.
I appreciate your comment 😊
Yeah I came across him a couple of years ago, I'd have loved videos like his back when I first started flashing
I have been trying to root my device with Magisk for about 3 days with no success. Each method I tried would end up with a step that either my device or computer was not compatible with. After watching this video and following it step by step I was able to root my Pixel XL seamlessly. This was the most concise easy to follow step by step process I have come across.
Seriously, thank you for making this video. I have gone through so many tutorials and videos only to have to start over and over. Your video was clear and to the point. Yes it's May 2023 and I am just now unlocking my Pixel 4XL. THANK YOU THANK YOU! I can now use VPN passthrough!
It stills work in adr 13
I just rooted my new Pixel 4 today. I am getting ctsProfile false. I tried tutorials from TH-cam but have not fixed it. Any help?
It's been a bit of a wild ride, recently an update to Google Play Services started using key attestation when checking Safety Net. If you choose to use the Canary builds of Magisk Manager, it will tell you which kind of evaluation was used to verify.
But I've also heard that this was rolled back last month or so (for instance, my Pixel 3 running Android 11 Beta is using the basic evaluation), but this state is inevitable as mentioned by TopJohnWu, developer of Magisk.
twitter.com/topjohnwu/status/1237656703929180160
I had to put "Quotation" marks either side of file IMG before I could push it to phone after I dragged it into CMD they where missing like yours...but then I noticed they appeared after you did it using the path copy...but i don't have path availability on my windows 7..just thought I should mention it if anyone struggling like I was... brilliant info thank you so much worked a treat...shame I can't get you Vance's you tube working..
Ah Windows 7, okay, I haven't used Windows 7 in a while, but it should encapsulate the path in quotes if it contains spaces. But I'm glad surrounding it in quotes helped you out in the end.
Many thanks for your comment!
@@MaowDroid managed to update my pixel 3a to February update using your brilliant ADB commands...far better to watch on video and pause at each stage than to try and read through with the possibility of the author making a small mistake in the ADB text by seeing it actually working gives me confidence in trying it out. Thank you again for your excellent edited and compiled videos...your a ADB legend.
Great video, still works to this day, very straightforward and does not miss a single point. Great work
I followed exact step but about 22:22, it botted into fastboot mode and can't startup my pixel4; with Enter reason: error boot prepare.
Never mind, I found out that I downloaded wrong Images from Google, I will try again
after I did the rebooting to android part at 22:10 the touchscreen stayed unresponsive but the but buttons working fine, what should I do ?
I guess double check that you've flashed the right boot.img (from the Factory Image) is the matching build.
It'll make things easier if you were already on the latest build of Android beforehand!
To see if it's a problem with Magisk, you can flash the stock boot.img (the one you got from the factory image) and see if that fixes the touchscreen issue.
@ 14:03 you typed /sdcard/ im a little confused because up until 14:03 there was no mention of an sd card. this makes me think that you saved all these files inside the phone from the computer which is why your directory is listed as f. can you clarify this please. I am at this step and stopped.
so ive scrolled back to 11:41 and see its still on your pc, possibly a file you created and named "storage" so im going to continue in hopes that the /sdcard/ is a magical spell lol
it will put it on our sd card... what sd card? the pixel 4 doesn't have an sdcard slot.
ok so I grew a set (im generally a paranoid person) and just went along. hopefully if anyone else is worried about the same as I was, dont be. just follow along and it works. thank MaowDroid
Hi Stephen, I seriously apologise for not responding sooner, but am I ever glad that you managed to go through with it.
Just to clarify these points you've raised up:
Storage (F:) is the label for my F: drive on Windows. Usually it's called Local Disk, but I like to name mine. It's no different to doing this on your C: drive, or in your Downloads folder (C:\Users\(username)\Downloads).
/sdcard/ in terms of the Android file system is mapped to your internal storage. If you ever view the '/' (root) directory in a file manager, you'll see that the 'sdcard/' folder is a symbolic link to /storage/self/primary. So it's more of a shorthand for your internal storage.
Let me know if you have any other questions!
Great guide as usual. I don't know about you but I miss the days when Google phones were developer friendly. There were so many custom ROMs for my old Nexus smartphone and I spent ages trying them all out. Pixels have made custom ROMs challenging, and I wasn't happy when I flashed Android 11 and it broke Google pay for a while until clever Devs made workarounds.
It seems Google has forgotten that flashaholics like us are the very people their family and friends go to for advice on their next smartphones. They need to stop making it hard for flashing on their pixels.
So many features that have made their way into vanilla Android began life on custom ROMs. A robust dev community is a win-win for Google IMO
YESSS!! Thanks for your comment, and wow yeah what a throwback! I started with the Galaxy Note, but really dug in with the Galaxy Nexus.
I guess we've come a long way, and yep, flashing a new ROM every couple of days or even during the day - wow haha. AOKP, PAC ROM, CyanogenMod, PA... just to name a few.
And yeah.. all those awesome innovative features, there were the gesture controls (forgot the name of the app), mini-tablet mode in Jelly Bean that was really pushed out in PA, I think it was hybrid mode or something), theming, floating notifications, customisable navigation elements... I could cry.
Yeah its a bit unfortunate that we've got all these strings and nets for us to work through to get GPay or even the bloody Macca's app to work haha - perhaps the landscape is moving, I don't even need to recommend Pixels to anyone, they just show up with them haha
Looks like I'm back, well done m8. The videos make things a breeze.
Awesome to hear Alec! :) Have fun.
Followed the video and everything went according to plan until I got to 22:00 reboot the device. Stuck on the G loading screen 😕
Did you ensure that you had downloaded the factory image that matched your phone's build number? And you're not on Android 11 by any chance?
You can get your phone booting back up if you flash the stock boot.img that comes from the factory image you had downloaded earlier (assuming that was the correct one).
fastboot error boot partition is smaller than boot image. helppp
After rooting i am stuck on the G logo... What to do?
Did you figure this out?
all you gotta do is flash the megahertz and gigawertz using a tool named fart butt
Yo what the hell was I on when I wrote this
Really appreciate these videos man. Great work. I kept going back to your videos when I need to return my devices back to a lovely unroot status! Keep up the great content. 💯
Thanks for your comment Richard! :)
Now, how to solve this problem: fastboot: error: boot partition is smaller than boot image
Hi I got an error message during the flash (pixel 4xl) remote: 'Failed to write to partition Bad Buffer Size' Please help
Awesome video! Very clear. I can't wait for TWRP and Android 10!
You and me both! Although I've kinda gotten used to all this now haha, but it'll be nice to have for sure.
great video bro, any fix for magisk on pixel 4 it is not working on android 10 atm ?
After Additional Setup, its showing failed as the result. What should I do?
Try uninstalling the Magisk Manager and install it again manually.
Thanks. Finished rooting my Pixel-4 working fine.
Thanks for reporting back with your comment Manoj! :D
Don't have a Pixel phone but thanks to rooting and customs ROMs I was able to resurrect my old beloved HTC One M9 and flash Android 10 AICP 15 ROM with Magisk root enabled🙌🙌🙌🙌🙌🙌 my Note 10 plus has been taking a break for the last 2 weeks.
Oh that's amazing! I loved the HTC M series! Rooting and especially custom ROMs bring life to our older phones, I'm probably going to be sticking with my Pixel 3 for a while now. :)
I ge this error: "FAILED (remote: 'oem unlock is not allowed')
fastboot: error: Command failed. " when i type the command fastboot flashing unlock please what do I do?
You must enable OEM unlock as described at the start of the video. If that toggle is disabled, unfortunately you won't be able to proceed further as you've got a model that has the bootloader permanently locked. :( If you have enabled it; but it still says it's not allowed, your device would seem to have a locked bootloader :( usually from a carrier like Verizon.
So this method works for phones that dont have OEM unlocking able to be turned on ?
After rooting successfully i downloaded a module on magisk and restarted my device ... Now i am stuck on the G logo .. plzzz help
Hi Sameer, you probably have figured it out but you would just need to flash the stock boot.img to remove Magisk. But for removing the modules, you may have to look for a "Core Mode Only" boot image for the Pixel 4.
never mess with magisk. if it works it works. don't update it and don't mess with anything.
I downloaded the wrong version (7.50) and I just found canary how do I update the version?
Just install the canary Magisk Manager APK over the existing one, or you can choose to uninstall your current version of Magisk Manager and install the canary build.
@@MaowDroid I just re did the install part on my laptop. It just updated replacing the old boot.img to the new one...
Can't install Netflix, I've already tried flashing the 3 modules bit still not working
You'll probably need to sideload the APK. You can get it from APK mirror I suppose. Especially if those modules aren't helping you.
After the step where It was supposed to install the magisk_patched.img, my pixel4xl now is stuck on the screen of the bootloader, it keeps restarting to the bootloader screen and not loading to the OS at all!!
Any help?
I tried to open the rescue mode, and now it is stuck on a screen with a dead android and "No command" message
Did you happen to be running Android 11? That requires a different version of Magisk to be installed to the boot image (at least v21 which is in the beta channel right now, or the canary builds).
You should try flash the stock boot.img next time; and it should boot up (providing you had downloaded the correct matching factory image based off the build number of Android that was running on your phone).
does anyone know why im stuck on the fastboot image screen.on the bottom of the screen it says "error boot prepare". if anyone know how to fix this. please let me know thank you.
Hi Omar, I would double check that you downloaded the right factory image, remember it needs to match the current version YOU are on! You can try flashing the stock boot.img if you believe you've got the right build of the factory image just in case it's a problem with Magisk patching it.
You can check out one of my update videos if you want to update to the latest version of Android 11 (but you'll just have to skip out on patching the boot image for now until you can get booted again).
Thank you sir. That was exactly the issue. I had the correct boot.img installed it still happened. But problem solved. Thank you. Keep the great vida coming. Good bless
Truly impressed; this is the first place where I will ask this question because it seems highly realistic that you'll answer it (and have the knowledge to). My device was rooted with Magisk working. It somehow became unrooted last month, and I get constant notifications that a new Magisk update is available. Anyway to re-root (it shows that magisk manager is installed but not magisk itself) without having to wipe?
Hi Camilo! It should be quite easy to do, yeah sometimes it just unroots itself, sometimes a reboot can bring it back. But in this case, you can flash the same magisk_patched.img that you made back then (provided you haven't updated your phone since patching that boot image (so the build of which the boot.img came from still matches the build number of the system you're on).
To be safe, I'd check what your current build of Android is by going to About phone, or it will appear on the expanded quick settings panel (near the bottom). Then seeing if you already have that factory image on your PC (or somewhere), if not download the corresponding one, get the boot.img out of it, and patch it using Magisk Manager.
Then flash the new magisk_patched.img like in this video, and exactly how you rooted it in he first place (minus unlocking the booloader as you've done that already when you rooted initially, this is where the wipe comes from), and after that you should boot up and be rooted whilst keeping all your data. (Although you should make a backup in case things do go wrong for whatever reason :) ).
can i use the same method in this vids to root(magisk) my pixeldust rom (pixel 4) with july factoy image?
You'd need to patch the boot image that comes with the Pixel Dust ROM and you should be good.
Thank you for the tutorial! Will be using it as soon as I get my Pixel 4XL.
Quick question, if I flash the Dirty Unicorns rom, would this tutorial still work on a custom rom? Or would the process be different?
You would have already unlocked the bootloader so no need to do that again, the process is pretty much the same where you'll grab the DU boot.img and use Magisk Manager to patch it; then flash that patched image in order to root. :)
getting stuck after flashing the magisk patched boot image. phone does not want to boot, getting stuck at the "G" loading screen. Any advice on what to do from there? I've already tried reflashing the file and still have the same problem. Any help would be much appreciated
Flash the stock boot.img instead. You might have patched the wrong boot image? Are you on Android 10?
i have the same problem, did followed the procedure again and again ...flashing the patched image bricks me in the G logo everytime and then i reflash the image file so i can boot and try again to patch...and it all started because the safetynet check reported false after rooting...now im stuck in unrooted and many apps not working...what can i do??
Hi I'm getting this message: “Your device is corrupt. It can’t be trusted and may not work properly.” And my device won't boot up...
Hi Pierre. Are you able to boot up with the stock boot.img? You can flash it the same way as you did the magisk_patched.img (fastboot flash boot [drag in boot.img])?
Are you also on Android 11? Currently Magisk v20.4 does not support Android 11 and you're required to use the latest v21 (just released 2 hours ago) which supports Android 11. link.squabbi.com/magisk
Be sure to change the update channel in Magisk Manager to beta!
@@MaowDroid Thank you very much! I did end up flashing the stock boot.img file and my phone works normally, I am going to try and use your new Android 11 video to root my phone tomorrow. I think the problem was that I didn't have Magisk v21. Thanks for the videos, keep it up! 😄👍
for me it says magisk not installed after i successfully flashed the patched_boot.img - if i try and flash it to the different slot it also says flashing successfull, but it won't boot - so strange!
You should only need to flash it to the current slot (so no need to suffix the slot). Are you sure you've patched the same boot image (from the Factory Image) with the same build number?
If you have doubts, try following through my update video for January.
My phone stuck at G logo with loading bar on the bottom side keep running. Any idea how to fix it??
Did you get the right factory image that matches your phone's current build of Android? Try flashing the stock boot.img just the same way as you had flashed the magisk_patched.img and see if you can boot up.
Now that Android 11 is out, are you on Android 11? Because Android 11 requires you to use Magisk Canary builds to root.
Thx for the reply. Yeah I’m on Android 11.
Currently Using the RP1A.200720.009 image but not able to boot up. Now showing “no command” with dead android image.
In fastboot mode it show my phone is unlocked .
Is it because I don’t have the right image or didn’t install properly so it won’t boot up?
In simple words, a computer power up without windows install so it won’t run?
Currently trying to diagnose with “Android Flash Tool” downloading software.
I mean it shouldn't have changed much, unless it has swapped slots for you. You should be using the factory image for the Pixel 4 or 4 XL (whichever you have), build number must match what you are currently running.
If you're having issues booting up, you can check this video out about flashing the factory images to restore your phone (you probably don't have to wipe the phone so skip that, and skip relocking the bootloader).
Then you can try rooting again but use the beta version of Magisk (change the update channel in Magisk Manager's settings) and make sure the latest version it shows is v21.
my pixel stuck in fastboot.. how to fix it?
I met problems of "ctsprofile false" in SafytyNet Check, anyone has the same problem?
New Google Play Service does this, almost all modern devices will have this by default now. You can find more information about that on TopJohnWu's Twitter. @topjohnwu
@@MaowDroid Thanks, I solved this by remame and hide magisk manager. but "adb root" doesn't work in terminal on PC, while "adb shell; su" works properly. Do you have any suggestions on this?
bought in Russia Moscow Google pixel 4 xl Verizon turned out to be a smartphone blocked by Verizon operators I don’t know how to be asking for help
You'll need to talk with the seller! That sucks you got ripped off like that, perhaps the phone was stolen so it's blocked?
did everything as described but when i try to boot the patched file i get bootloop..i did patched twice just for sure from the factory image im on but still no luck.any idea?
Are you certain that the factory image you downloaded matches your build number on your phone? Otherwise flash the factory image boot.img for now and we can sort it out later.
I'm going to be away for a while so discord would help. :)
I have the pixel 4 the small one I'm a long time stock Android guy and have rooted phones and ran custom roms before loved the 6p so much ran ressurection remix awesome user experience now I am thinking of rooting the pixel 4 and running dirty unicorns what's your thoughts about it and what rom would you suggest
Sorry for the hugely late reply! I'm currently running Dirty Unicorns on the Pixel 3 and I love it! I've submitted some patches for DU so you'll be getting these new features soon.
What if I have already unlocked my Pixel XL bootloader, can I just start at the root section to root the phone?
Forgot to say it is a verizon based phone but unlocked.
5:00 video begins
pixel 4xl doesnt have an sd card. im stuck at push using command prompt help
Could you elaborate on the exact issue? Obviously I'm using Pixel 4 as well. The /sdcard/ is mapped to our internal storage so that's fine anyways.
i havent instaling roo/twrp for very long time... if my phone is A/B and also my phone have twrp on xda, can i just flash magisk via twrp without doing the boot.img thing ?
If TWRP works on that version of Android (currently it doesn't work well, or at all on Android 10), you can boot the TWRP image and then flash Magisk.
It's just that we don't have TWRP for Android 10, so we are up to patching the stock boot.img with Magisk to root.
Does the exact method work for android 11? Magisk canary added support for Android 11 in version 21 or no?
Hi Humberto, yep it should! I recommend that you stick with the canary builds for now (they seem to have fixed some bugs that are in v21). Especially if you count on hiding Magisk & Magisk Manager.
Can I remove Verizon carrier lock on a google pixel 4 by rooting the phone? I have a Verizon Google Pixel 4 when I check the IMEI lock/unlock status, it says the IMEI is unlock but when I put in another carrier sim card , I get a message stating that the phone is not unlocked. I called Verizon and they said the phone is unlocked but that due to their new locking policy, I might have to wait 60 days to use another sim card on the phone. My question is : Can I remove that lock by rooting the phone? Thank you
Hi Stephane, sorry for the late reply.
Even if you could, which to my knowledge I only recall on really early Android phones, rooting the Verizon Pixel 4 is not possible right now due to it having a locked bootloader.
You'll probably need to wait those 60 days for the network unlock to complete.
Will you be making a video so we can preserve root and perform December update? Also, I did not make a backup of boot.img, so I'm not sure how to do the OTA update via Magisk without it. Thanks!!!
I may have mentioned that if you just let Magisk Manager patch a boot image again, it will make a backup. Note that the backup is automatic when you choose to patch an image when installing Magisk.
Once you do that, you should be able to follow the usual OTA update using Magisk Manager.
I was on holiday, so I have some catching up to do 😉
I follow your step ,but ctsFile:false,how can I fix it?
Hi Way. Updates to Google Play Services means that most modern devices won't be able to pass ctsProfile anymore. Check TopJohnWu's Twitter if you want to find out more.
@@MaowDroid Thank you！
Do you HAVE to do magisk boot.img patching BEFORE you do the oem unlock bootloader? I unlocked the bootloader first thing I got the phone followed your instructions but can't get it to boot.
No, you should be able to do it at any time. Just to double check you got the boot.img from the factory image that is matching your current build of Android?
Also did you notice your phone changing slots after flashing that patched image? (usually you start on slot A, but after an OTA, it will change over to B and vice versa).
Any videos or tips for cases where a Pixel 4/XL is bricked?
After rooting if I turn off bootloader, will it let me remove magisk modules using adb shell:?
Hi Silent Whisper, sorry for the late reply, correct me if I have misunderstood. I wouldn't recommend relocking the bootloader once your phone is rooted. Your phone should factory reset (but should retain root access) which would remove your Magisk modules (but theoretically leave Magisk installed).
To be honest, I don't really understand your question. :(
So, what usefull apps can I install after rooting? I installed adaway, titanium backup, viper, edge sense plus, what's more?
Hi Marko, I've recently started Storage Redirect (requires Riru) to ensure that apps don't just roam around my internal storage looking at things (I'm looking at you Ingress).
But AdAway + Edge Sense Plus (and Blobmoji), F-Droid Privileged Extension (Magisk Module) are the ones I use.
For the Pixel 4, you could try out FingerFace, which allows you to use Face Unlock to pass as a fingerprint reader for those older apps (it didn't work for a few banking apps that I tried to use before).
@@MaowDroid Thank you!
Can I flash the patched image right after unlocking the bootloader and before restarting the device and setting it up fresh?
I can't think of why not, but if it doesn't work out, try letting it boot up once.
Can I lock boot loader aganie? And restore everything like was at oryginalny stage? Thanks.
Yes you can, you'd want to restore by flashing the factory images first, then relock. I can make a video about it this month.
I've been all over the threads and can't seem to find a system wide font changer with the pixel 4 xl... I'm using font changer right now. Any other suggestions?
There are some Magisk modules that we have to change the fonts, but I guess I'm waiting for custom fonts for the new font changer that we have in the themes menu.
I haven't really had a look around about that yet.
im currently using anaheim Font module. although theres some issue in unicode all font text are replaced by anaheim
I would like to be able to record internal sound like I used to do before; by example: I use AZ recorder to record Whatsapp videos with my family, etc. I notice recently that my videos dont have any sound, I did a quick research and I found that Android removed this feature. Do u know any company that can root my phone for me?.
What phone do you have? If you have the Pixel 4, you're in the right spot. :P
@@MaowDroid I do have a Pixel 4
After the rooting process I get a play services is not up to date, how do I fix this or can I just flash the original boot to undo root?
That should have nothing to do with rooting. Does tapping on that notification not take you to the Play Store to update Google Play Services?
You can just flash the original boot.img to unroot too.
@@MaowDroid will flashing the boot erase anything?
great...what do i do now that I'm 3/4 through this install and my computer is telling me that the boot.img is corrupted?
It sounds like you're trying to open the boot.img. when you run the command after dragging in the boot.img, make sure the active window is the Command Window before pressing enter.
Did it work for you Robert? I'm getting the same.
Gave up. Didn't root.
@@thrdeye Awww man...but did you at least get passed that part?
@@thrdeye when you drag the boot.img on the command window you need to click on the command window again and then press enter.
Hi brother! I want to ask you a question, will the phones which is android 10 out of box won't have twrp? I mean twrp team says it is hard to develop. Is it true that android 10 phones won't have twrp support.
TWRP won't officially support Android 10 currently, with the reasons you have found from the devs, there's been a lot of changes so it'll be a while before they can get it to work fully/properly. However, some older devices are OK, but they probably don't have all the major changes that Android 10 brought.
Hey, is there a way to root my pixel 4XL without wiping my data ?
Unfortunately not, it's a part of the bootloader unlock package :(
@@MaowDroid Ahh , appreciate the feedback sir , the reason I asked is because I want to get viper4Android but I don't want to lose my data at the moment. Thanks again for your help in this community ! Cheers !
this is the most detailed step by step videos with no falis , i did follow everything by the minute and got magisk installed as you described in the video...but i dont know how to enable superuser(or do i have to download it separately?) to make it work..cant find modules for the motion sense country restriction...can you help with that?
Hello! Magisk will handle all superuser requests via the Magisk Manager app. You'll get a prompt whenever an app requests root access.
You can use MagiskHide Props module to add these props to your build.prop: forum.xda-developers.com/showpost.php?p=80729593&postcount=5
OR you can use Riru + EdXposed to do it: forum.xda-developers.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607
I think adding those props via the MagiskHide Props module/command (you'll need to do that via the terminal) is easier.
@@MaowDroid thanks for the prompt reply man,I really can't do it..I tried everything,and no motion sense yet
@@nxsuan Do the props not work and they've been added to the build.prop? Or did you try the EdXposed module?
@@MaowDroid hi,I added the props via terminal emulator (worked much better than termux) and didn't work...it was so nice to see it working and rebooted just fine,but the motion sense option still grayed out.(I cannot send s screenshot though)
Ah I see. Maybe they changed something, have a look throughout the thread to see if there's anything else you can do to enable it!
Is the process exactly the same for a Pixel 3 XL (Just selecting a different boot image?)
Yep! That's right.
Hey you please can help me? my device is down and said "no valid slot to boot" :(
Did this happen after flashing the magisk_patched.img? Flash the stock boot.img for the time being.
Was your phone on the latest update before you did this?
@@MaowDroid No, i want to unroot and now it dont find anything. Sometimes it says "error to boot "boot.img" or now "no valid slot to boot"
@@MaowDroid and it was at the last update yes.
Interesting, does booting the stock boot.img help (although it would be temporary). You can try flashing the stock boot.img to both slots (fastboot --slot=all flash boot [insert boot.img]).
Your video is amazing. I try to follow it. My device is a pixel 4 QD1A.190821.007 but this file "10.0.0 (QD1A.190821.007, Oct 2019)" from official google repositorie does not contain any boot.image inside. What should I do? Using 007.A3 or i risk to brick my phone?
Ok I solved by updating my room to your by using Android flash fool with chrome. Easy.
followed you steps now i get "your device is corrupt" and wont boot up, sits on google screen
Does your phone boot up with the stock boot image? You can flash it the same way you flashed the magisk_patched.img (fastboot flash boot [drag in stock boot.img]).
If you're running Android 11, you need to make sure you use Magisk Beta (v21) or the canary builds.
Last thing that it could be is that you've downloaded the wrong factory image for your device (you need to make sure you download the matching factory image that matches what you are currently running on your phone).
Rooted and fixed
Great to hear! What ended up being the problem?
@@MaowDroid Android 11 seemed to be the issue. Flashed back to 10 rooted and now im all good!
What does bootloader locked in red mean?
hi . with you amazing vedio i rooted my device but cant enable motion sense in my country ,, and this is the only reson im looking for root for it ?
any help
There was a Xposed module out there that did that. You can have a look at it here: forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917/
Hey, how can I unroot & lock bootloader again in my pixel 4. Do u have any video for that.
Not right now, I will probably get around doing that hopefully this month.
@@MaowDroid thanks. Please try to do asap when u free. Waiting for that. I ll appreciate that
Project Mainline worked perfectly in Android 10 with a restart.
Oh that's great to hear! I think you're the first one that's reported back with that. :)
anyone with green tint issue on 90Hz?
I couldn't really recall that on my Pixel 4, but sometimes the greys would look funny.
i think the pixel 4 hass less issues with the screen callibration. It's really bad on pixel 4 XL. Thx for reply :)
Hello, i have a Pixel 1.
I rooted, installed twrp some time ago but i think i did an OTA Update or Upgrade to Android 10 and lost ROOT and TWRP.
Should i follow this tutorial to regain it back or do other things? (xda is filled with different opinions and people stuck at G logo)
Bootloader is unlocked.
Are you stuck at the G logo? If not, you should be able to just flash/boot TWRP and flash Magisk again.
@@MaowDroid Thank you. No, im not stuck, im using the phone normally but i just didnt know how to get root properly back. Il just use this tutorial again from flashing twrp as you said.
Thank you!
Is it still worth to root the phone at this point in time? And is this method still working? Haven't rooted a phone in years.
Yep this method is still working! Whether it's worth it, is up to you. If you're interested in some Magisk or EdXposed modules.
There are a few ROMs and kernels out for the Pixel 4 if you're keen to try those out, which is always fun to do! Which just require an unlocked bootloader and not root access.
However if you're on Android 11, you'll need to use the Canary builds of Magisk Manager & Magisk.
@@MaowDroid Im mostly interested in the fingerprint workaround. And to try the out the motion sense since it's restricted in our country. Thanks tho.
Oh yeah! I saw some workarounds for it! It's crazy all the extra steps some need to get the most out of their devices
Thank you👍 and How do I turn off screen flickering?
I don't exactly get what you mean? :o It's not a feature, that's for sure.
@@MaowDroid I mean DC dimming feature, is there any custom build to solve screen flikering issue in pixel 4xl phones?
@@saidjamoljiyanhodjaev8918 Ah I see. Just some quick Googling did not reveal anything useful apart from this app: play.google.com/store/apps/details?id=org.js.oledsaver&hl=en_AU
It's not something that enables DC dimming.
There have been reddit posts requesting the feature around 10-12 months ago and nothing else :( www.reddit.com/r/GooglePixel/comments/dq70ic/request_google_please_include_dc_dimming_option/
Thank you so much! I just rooted my pixel 4 :D
woohoo, thanks for reporting back Leho! :)
You running any custom rom I'm thinking of rooting I have the pixel 4 too thinking of running dirty unicorns not sure though this phone is so smooth and fast already don't know if it's worth it maybe so I can change the font lol that's about it
Hi. Is this method applicable to the beta 2.5?
Yes it is, but make sure you set the Magisk update channel to canary!
december update is here. can you do a tutorial on the OG pixel xl decemeber update? ( rooted please)
Yes sure thing! I'll put it on my list. :)
Got a sweet deal on a 3 month old 4xl ssving this video for when i pick it up :)
Ask anyone know if its possible to spoof on pokemon go on ios 11 since magisk now supports 11? Was gonna downgrade to 10 then root.
Awesome! Congrats on your purchase! I believe it is reading the SmaliPatcher thread. This post seems to confirm it: link.squabbi.com/vbffot
dude since security is priority blurred out the rumbled numbers/letters besides on Fastboot CMD that's your serial number.
I know, serials are fine with me (hopefully, please tell me if they're not haha), I was mainly trying to hide my IMEI (unless you can derive an IMEI from a serial number).
also sir Make video how to Apply Substratum Theme In Android 10. Fab/Ethereal Substratum theme is applicable in android 10. as always Root required since 10 is not systemless root.
I was sure Magisk is still systemless on Android 10. I do see that Substratum installs a module for (handling legacy themes IIRC).
You should be able to apply them as usual (since the March update of 2018).
But I'll have this on the back of my mind. :)
how do you root a regular pixel xl on android 10?
You could unlock the bootloader and flash Magisk. I have a video for the Pixel running Pie, it should be the same.
If TWRP messes things up, you can follow this video to patch the stock boot.img to root instead.
you can follow this video basically for every google phone. i did the exact same steps on a nexus 6p with android 10 and it worked fine. just get the boot img from the rom you are using.
I have a og Google pixel
Can I root my phone with this method?
Yes you can do so with this method if you don't wish to use TWRP.
Is this method work on Android 13
If magisk doesn't pop up the first time then just reboot...22:42.
Yep that's the trick! Sorry I didn't mention it in the video. Alternatively, you can also install the APK.
Wonderful Video brother!
Thanks Jason, I'm glad you found it useful. 😁
Please do a video on how to enable moition sense in india
There's an Xposed module as well as some build prop mods I believe: www.xda-developers.com/enable-pixel-4-motion-sense-gestures/
Or you can try this without root: mspoweruser.com/want-to-use-pixels-4-motion-sensor-in-any-country-heres-how-you-can-enable-it/
I no longer have the Pixel 4 so I can't show you personally 😓
@@MaowDroid tried adb shell “setprop persist.pixel.oslo.allowed_override true; setprop ctl.restart zygote" didnt work.
@@MaowDroid my phone got fucked while doing root.
please let me know how to fix it. used android 11 beta while doing root
.
@@Kanakapallianurag hey sorry you reply got lost in my notifications... you need to use the canary builds of Magisk to root on Android 11 for now.
does this work on pixel 3a?
Yep this'll be fine! Just make sure you download the right factory image. Ensure that it matches your device's CURRENT build number, in Settings > About Phone > Build Number.
Hey! Thanks for Replying! Alright ill do that... I have a pixel 3a as my main phone but I'm not sure if I should or not. If I decide then i will follow this tutorial
@@officialveerbajaj Cool no worries! Think about what you're looking to do with an unlocked bootloader/root access (custom ROMs? changing emojis?).
If it eases your mind, you can always revert back to the original state. You'll just have to set up your phone again. :D
I want to use substratum and be able to theme my phone more. I am not looking to do much. Should I do it?
Also, would i get googles security updates after rooting
Plz make a video how to install Android 10 in Nexus 5x best method
I don't have the 5X so I won't be making a video about that unfortunately.
But the basics would just be unlock the bootloader and find an Android 10 ROM (something like the Pixel Experience ROM) and follow the installation instructions.
Does this work on USA phones?
You should be able to tell if you can enable OEM unlock, if it's greyed out then you're out of luck. Generally only Verizon models and T-Mobile have bootloader unlock restrictions (from what I've heard).
Is this the same for android 11?
Pretty much, except you need to make sure you change the update channel of Magisk Manager to either beta or canary as those versions of Magisk (v21 or greater) support Android 11. You can have a look at my more recent video covering it: th-cam.com/video/sPvnmgon89U/w-d-xo.html
Thx♥️♥️♥️♥️♥️
Could you please make a video for the oneplus 7t root
If I had the OnePlus 7T in my hands I would. :(
Can you make a video how to install motion sense because my phone not allow to use motion sense in Malaysia. And I know there a lot of people that have same problems as me. I hope you read this comment. Because thus is important
Btw thanks for this video it's help me because there have a lot information. 👍👍👍
My phone Google pixel 4xl
Hi! Since Motion Sense works in Australia, I didn't have to use anything to enable it. I have heard of build.prop edits as well as an Xposed module that will enable it.
build.prop edits: forum.xda-developers.com/showpost.php?p=80729593&postcount=5
Seems like there is a Magisk module to do it now: github.com/demj1206170/EnableSoli
EdXposed module: forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917
Installing EdXposed: forum.xda-developers.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607
I'd recommend getting the latest beta builds of EdXposed from here instead of using the attachments: github.com/ElderDrivers/EdXposed/releases
awesome tutorial. thanks!
Glad it was helpful! :D
Hey, plz make a video for unroot pixel 4. Thanks
Hi Mujibul. Sure thing! I'll take a look at doing that some time soon, hopefully in the next 2 weeks perhaps.
Thank you for your efforts
Thank you Ali! :)
I'm using pixel dust. My camera is broken now that I have root. Annoying man lol
Really rooting on Pixel Dust breaks your camera? You should see if that's been reported in the ROM thread! :O
@@MaowDroid I believe the culprit was me copying apps from my pixel 2 xl. I flashed may 6 build clean and everything is fine.
Thank you for this video. I've watched it 100 times to get this stuff down lol.
wow this video is so gooooood edit: i dont even own pixel device :D
Thanks! :D Are you planning on getting a Pixel?
@@MaowDroid they are not officialy sold in my country. there are few big shops that import them but the price is high, same for oneplus :'(
but one day i would like to own one! maybe i will order pixel 4a from germany
not very useful for linux d: Guess I'll just make a VM or something when I have a day off si i can follow this
Hi Scorned Cripple, sorry for the late reply!
I'd put Linux folks up a bit higher to work things out, but I think the trickiest part for Linux users, is to get the platform tools working. I know Ubuntu distros have them available in the package manager, but they're out of date most of the time.
I'll look at doing a Linux video soon, just to see how it plays out. :)
just do a vfio passthrough vm
watching on my P4 XL
Have you rooted yours yet?
@@MaowDroid no not yet. im honestly thinking about it.
@@therealmrstaten1 don't hesitate. the 1st thing to do after buying new phone is to Unlock the bootloader.. incase of System damage / system corrupt after update. if the User dosen't know or no background in Unlocking oem or usb debugging in dev. options you can't flash the fastboot rom since your phone is not visible in Device manager. /fastboot