Can't enable OEM Unlocking anymore for anyone that's update their OTA to latest Android Pie (9.x). The security "patches" prevent it, and now the option is 100% grayed out. I have tried the adb uninstall phone option, I have tried multiple factory resets, etc. Will need a new method/app for those stuck with a Pie upgraded 2XL. Mine is perma locked unless someone comes out with a new method. (And yes, I originally bought my unlocked phone from the Google Store directly, but Verizons OTA locked it down).
absolute legend, I got a Pixel 2 today (coming from a Oneplus 6 android Q) process is well delivered and you obviously know your stuff! thanks for your help and keep up these high-quality instructionals (they really are helpful) 😎👍
So damn easy!! I've been working on this for months but kept running into Verizon's locked bootloader. Finally bought a used device that was from Google store. Now I need to remove the ugly "unlocked bootloader" message during reboot. I see a few hits on google search but I am not a very trusting person and wondered if you'd already produced content on this topic? Thanks again, love your channel.
Fantastic to hear that Robert! Pesky carriers at it again. Unfortunately there hasn't been a way to remove that message on boot. It's been like that since the 6P and 5X days.
Thanks Bro! Done rooting my phone! I’ve done install modules and now magisk boot my phone due installed for safety net. Boom! And Now my phone bootloops. And i skip to install TWRP RECOVERY “USE YOUR METHOD” 🤭 just like u said (i don’t like pop up twrp while start) and now ! Boom shakalaka. Bootloop.
Wait so a module bootlooped you? Or installing TWRP did? Either way, try to gain ADB shell access while bootlooping to remove all modules: magisk --remove-modules Or flash the stock boot.img for the time being
Thank you so much the adb sideload didn’t work but thank you for teaching me to unlock the boot loader because I just installed the magisk zip on the phone and flashed it thank you so much 1+ sub
Thanks for your comment Mike! :) For sure, we can take a look at doing that. I can perhaps do a general one, and more specific ones. But basically the steps are usually outlined on the thread. :D
Hello I need help on google pixel 2(smaller one), whenever I type in fastboot flashing unlock, an error pops up saying "FAILED (remote: 'Flashing Unlock is not allowed"If anyone could help me it would be highly appreciated
I have no option to download on Bootloader menu, fastboot command doesn't work... I watched how to install google usb drivers but i don't have the Lemobile ones to begin with....very confusing.. and im not old im 28... someone help
Thanks for this. I managed to learn a few things too and I've been messing with phone rooting for years. One thing however, how does OTA work with this? I assume you can get it, but then do you lose root? Does it just update with no errors? Do you need to do what you have done here (minus unlocking bootloader) for every OTA update?
Depending on what you might do to your phone between rooting it and getting an update, we can use Magisk Manager to help us take the incremental OTAs that get sent to our phones (very handy if you don't want to download 1GB+ every time there is an update, but that requires you NOT to make any modifications to the /system and /vendor partitions as it checks that before flashing the OTA). I will be making a video on this for November. :) You can get an idea of what you might have to do (in case you have done some modification to your /system or /vendor partition) here in my monthly update videos: th-cam.com/video/fgZNOlNIlDM/w-d-xo.html
I'm able to unlock OEM the first time around but when using the flashing unlock command i get an error. I went back to setting and found OEM option grayed out. Factory reset fixes this but I'm unable to get passed this cmd
Hi Armando, it seems like you've got a Pixel 2 that has its bootloader locked unfortunately. I've heard of this particular case where the OEM unlock toggle is available/toggleable, but it doesn't change the state of the bootloader to allow it to be unlocked. If the 'fastboot flashing unlock' command says something along the lines of: OEM unlock is not allowed, and you've already tried toggling the OEM unlock toggle (in the developer options), there's nothing you can do. :( The last workaround for this has already been patched out as of January 2018 I believe.
That would only be the case if you get an update pushed to your phone 🤣, after rooting mine doesn't really do that anymore, I don't actually recall if you can hide those system notifications. You'll be able to update anyways, but just not through OTAs (if you've flashed the TWRP installer).
Thanks a lot for your amazing and organized video, I'm impressed. I learned a lot form it and you have an extra subscriber. My OEM Unlock option is grayed out, my Pixel 2 XL is international version though and it is unlocked, I used sim cards from 5 different countries with no problems. Is there anything to do about this and enable OEM unlocking? Thanks again :)
I can't connect my Pixel 2 XL to my pc, anyone having the same problem ? I get Device Descriptor Request failed. I've looked up everything online nothing helped
Hey, I'm having a lot of trouble getting the serial number to show up when using "fastboot devices". I followed your USB drivers video, but I don't even have LeMobile drivers and when I try to install the USB drivers, Windows says "Windows has determined the best driver is already installed" and shows me 'MTP USB Device' as the driver.
When your device is in the bootloader, there shouldn't be connections via MTP! When your phone is in the bootloader and you see the MTP USB device, try uninstalling the device. Replug your device, and if it automatically installs the MTP device again, you may need to use USBdeview to remove the driver record. Also see if you can choose from an existing list of drivers, rather than pointing to a folder, or letting Windows Update look for newer ones.
Hey there! Unfortunately since past January of 2018, Verizon rolled out an OTA which patched up a workaround. Since then, there have been no new developments to my knowledge. 🙁
Sorry for the late reply! I probably wouldn't go that low with Magisk. Is this your first time rooting? I would try flash the Magisk uninstaller. Boot into Android and then go back into the bootloader, boot the TWRP image and then flash Magisk 18.1. Otherwise, try patching your stock boot image (from the factory image) via Magisk Manager to root.
Hi. Im at the step where I need to set up the bootloader and my device state is locked despite doing everything as you did it. it says FAILED (remote: 'Flashing Unlock is not allowed ') when I try to enter fastboot flashing unlock
Google has implemented hardware based attestation for SafetyNet. There is a way to force it back to basic evaluation by using the MagiskHide Props module (you can get from Magisk Manager). Then SafetyNet will pass for the time being until Google verifies what kind of device we are running.
hello , i need your help. i followed all the steps on my googelpixel xl 2.. i got up to sideload. adb sideload, dragged magisk into the cmd prompt. pressed enter.. it started but then the screen went black... my computer recognises my device but the screen is black on my phone
Uhh haha, wait so were you not able to decrypt your data partition in TWRP to access your internal storage? TWRP does have a screen timeout, but you typically can wake it up from there.
Welcome to team Android. :D There's a large range of benefits, mostly it's down to your own personal needs. Now I understand that you might not know what you need/want, if you don't know what's out there. :) Advantages: systemless mods (fonts, Active Edge Mod (customise the squeeze for assistant)), root/iptable based firewall, some apps have enhanced functionality with root access (depending on the app of course, I can't list them all). Disadvantages: some apps may not choose to work anymore when you are rooted, although Magisk can currently hide itself and bypass SafetyNet (a Google API for detecting system modifications). Monthly updates would need a little bit more manual work, so no more automatic OTA updates for safety of course!
Need Your Help Bro After Updating to android 10 magisk stoped working and root status: sorry root access not properly installed on this device What should i do now
How did you update? You should be able to flash Magisk Uninstaller, then flash the latest version of Magisk. The canary builds seem to work quite well. Is that message from a root checker app? There is really no need for those, Magisk Manager will tell you whether Magisk is installed or it isn't.
Hey Luke! So typically Magisk will enable Magisk Hide for Google Pay, so you should be able to go ahead and add your payment method. :) Of course, you can double check in Magisk Manager as well.
I followed all the steps without issue, but when it comes to sideloading magisk it just doesn't work. I copy across the zip file to the cmd and press enter. It just goes to the next line and doesn't let me do anything else. It does not show the 'serving' line yours does. The phone takes a while to load up and then says sideload failed and brings me back into the phone. Any help much appreciated! TWRP all working fine! (android 9 btw)
@Waffles! Would you be able to try pushing the Magisk.zip (adb push [magisk.zip] /persist) to /persist, and then trying to navigate to that via the Install menu on TWRP? Apologies I no longer own my Pixel 2 so I can't do some testing, but even that happening on Android 9 + TWRP is a little strange. Are you able to do it if you boot from the TWRP.img instead.
@@MaowDroid Hey thanks for the follow up! I actually was able to get my pixel 2 rooted by following this: th-cam.com/video/7T8HnpVLMdg/w-d-xo.html My only issue is my phone is rooted, but since it's a "production" phone, I only have access to "su" over ADB, no access to adb root. There are guides on how to edit my .prop files, but they all are fairly old, and I'm concerned about bricking my device as I'm totally new at this...
@@no1TFKfan ah just patching the boot.img! Definitely the way to go for Android 10+, as I would have thought that TWRP should still work on Android 9 (to be fair, I had issues decrypting data myself, and sideloading would bootloop me!). I'm glad you got it rooted in the end. :D
@@MaowDroid Yup! sideloading would just fail sadly. idk if you might know but I'm having issues sending fast sendevent commands to my phone. I edited the .prop files, but apparently only eng marked builds not user can access true root (adb shell root) not just su access. I spell out more details on what I've tried so far here: stackoverflow.com/questions/62079599/using-sendevent-in-python-to-usb-connected-phone-slow-due-to-su-access
You seem to have a locked model, either activated from Verizon or some other carrier who locks their bootloaders. There is no workaround for that currently. :(
I purchased my pixel 2 xl from Verizon and my oem unlocking button is greyed out. But now I have service through AT&T with the same phone. That won't change the fact that the oem unlocking feature still won't work right?
@@MaowDroid I figured as much. I need to send it in to get a new one so maybe I will get lucky with a refurbished unlocked one. Thanks for the quick response man 👌
Thanks! I'll try this sometime, even though I've never rooted a phone so it'll be a first for me. How hard is it to go back to 100% completely stock? Unrooted, locked bootloader and such.
No worries! Take your time. :D As for going back to stock, it's as easy as Pie (pun intended). You can have a look at what that might look like here: th-cam.com/video/zQmK5KwN5dk/w-d-xo.html
You may want to take a look at this post: forum.xda-developers.com/showpost.php?p=74442342&postcount=2 :) I can look into making a video for this if I can disable tethering on my own phone as my carrier hasn't put that restriction on my phone.
@@MaowDroid A video or advice would be great. I'm not to sure about step3 3 - Edit build.prop adb shell su **(grant permission if phone asks)** mount -o rw,remount /system echo "net.tethering.noprovisioning=true" >> /system/build.prop reboot Do you just type each line and hit enter? What is SU
@@lhamagedon 'su' means superuser. It elevates your current terminal instance. so after you type 'adb shell', you'll see a $. When you type 'su' at that prompt, and accept the superuser request, the $ will turn into a #. Now all commands you run with #, will be run as root. So you would continue with: mount -o rw,remount /system echo "net.tethering.noprovisioning=true" >> /system/build.prop reboot (or whatever the commands were). Hope this helps!
@@anisatawna If you have installed TWRP, just boot into the bootloader, then change the selection to 'Recovery Mode' and press the power button to select it. If you're trying to root the Pixel 2, I would *strongly* advise against using SuperSU. It has effectively been abandoned and probably won't work on recent versions Android Pie. Please use Magisk instead.
Hello there, nice tut seamless and easy, btw can I use temporary twrp to install custom kernel and magisk on pixel 2 / (XL)?. if I installed magisk can I still get ota updates? And why we need to disable automatic system updates what will happen if it updates?.
Hey Mr. Dog. Yes, you can boot TWRP to install a kernel, in fact you can do most things in there if you don't wish to install TWRP. Yes, you can have Magisk installed (although additional steps are required), but not if you had also installed TWRP. The worst case is that you get into a bootloop, but it would just usually result in you updated, and without root. (but re-rooting would be as easy as booting TWRP and flashing Magisk).
Hey there, I am going to buy a refurbished pixel 2 xl. Should I root it right away? or should i wait some time? I am new to this, thanks for your help.
@@shivamghimire400 unlocking the bootloader is in 2 steps: Enable OEM unlock in developer options. Boot into fastboot, run: fastboot flashing unlock Then you must confirm bootloader unlock.
Hay I'm not sure if u still read these comments but if you do pls help I can't tern on oem unlocking it just says connect to the internet or contact your carrier but I'm already connected to the internet and I'm not sure what to do???
Hi beastie, I do try to read my comments regularly, but work has limited that recently. Usually, that means your carrier has decided to block unlocking the bootloader. All the workarounds that I've seen have already been patched out. So there's nothing you can do unfortunately. :(
Have a go at this video: th-cam.com/video/nGkYtP1y58A/w-d-xo.html You dtb may be mismatched for some reason. Ensure that you're using the latest version of TWRP.
Hey Warren, thanks for your comment! OTA updates can be done with a little bit if extra work as described here, using Magisk Manager: topjohnwu.github.io/Magisk/tutorials.html#ota-installation The note there saying you MUST have an non-tampered /system and /vendor partition is quite serious. If you have mounted /system as read-write, you may not be able to take OTAs. I do make monthly videos on using the factory images, which would be safer to use if you have made some /system modifications, or you are unsure. But generally speaking, if you've just rooted using Magisk, installed some modules and haven't used any apps for specifically making system-based modifications, you can with a good chance use the method described above. All you would need to do is to wait for the OTA to get pushed to your phone. :)
@@MaowDroid Here is teh thing, i went to system and updates and it stated it had one and tried to download but of course it could as my phone is rooted, so i paused the download and follow the instructions you outlined to me, when i went back in to resume the down load it stop and stated that Octobers was the latest update for the Pixel 2 XL, which was very strange. Anyway i tried pressing it a few times to try and instigate the download but it wouldst. Tried the procedure a few times and still wouldn't work. Any ideas why this happened? I went and just flashed the factory image anyway,but this way would be better.
@@warrencoakley Yeah it's quite strange. I do recall Google saying that the Check for Updates should now manually get the latest update, so no more waiting or staged rollouts. However, when I tried to do just that for November, it also told me that it was the latest update. Several reboots, and even updates to the latest Google Play Services, still no dice. So, if I do get the chance next month to show this off, I definitely will. 😁
Network unlocked and bootloader unlock capabilities are different. Your phone may have been either activated on a carrier that locks their bootloaders (i.e. Verizon), or it was bought from one of those carriers. There are no workarounds for this unfortunately. :(
MaowDroid bro I just got a refurbished pixel 2 xl just to root it, and then I figure out it was activated by Verizon and now I'm fucked and can't even oem unlock this shit. This is the first time I've ever encountered a problem that even the geniuses on XDA couldn't bypass. Whoever came up with this needs to be shining somebody's shoes tomorrow they don't even deserve a job
Not too sure about this, I've had others having the same issues. You can try patching the boot image via Magisk Manager instead, or try flashing the Magisk Uninstaller and then trying to flash Magisk again.
Hi Özgür, I apologise for not making it clear in the description (although I thought I had), some phones on certain carriers have locked their bootloaders, one example would be Verizon in the US, but I would assume there are other carriers around the world doing something like this. These phones rely on exploits or workarounds for their bootloaders to be unlocked. The last known one was close to December or January last year/earlier this year. Which have been patched. :( But just double check that you have enabled OEM unlocking (that would be greyed out if your phone has a locked bootloader).
Does your device appear in the device manager at all? Anyways, that was only if TWRP was unable to decrypt your /data partition, as that can happen occasionally. I should have mentioned that. So what you can do, is boot back into Android and then copy the Magisk.zip to your phone via MTP (USB for File Transfers), then boot into TWRP again, and flash Magisk.
Thank you, successfully rooted ! 👍 It's normal every time i turned on or reebot my phone got warning bootloader like 11:40 ? is there any way to skip that? Thanks bro I really appreciate that !
Great stuff Jefferson! Unfortunately it's unskippable, but a couple of seconds each time your reboot shouldn't hurt too much ahha. It's been talked about since the Nexus 6P, but no-one has found a way to remove it, but it doesn't bother me anymore :) Just don't relock the bootloader! Unless you return to stock first at least!
ah :( there are certain carriers out there such as Verizon who will lock the device's bootloader. There was a workaround for this, but that was patched almost exactly a year ago. There is nothing you can do for now.
Good Video ands We can earn so many important facts from this article HomeBest Root AppsTWRP adds decryption support for Google Pixel & Pixel 2 on Android Pie|Download TWRP adds decryption support for Google Pixel & Pixel 2 on Android Pie|Download
You must keep your bootloader unlocked once your phone is not 100% stock! (e.g. you have installed TWRP or you're rooted). Also note that you'll be wiping your phone every time you lock and unlock the bootloader.
Depends on the apps. NFC isn't affected by root (on it's own), but then again it would just boil down to the apps you're wanting to use. I don't think Google Pay works currently, it used to for a while. 😢
You won't be able to use TWRP to do so, perhaps have a look at my Oreo root video which will go through using Magisk Manager to patch the stock boot.img to root.
Some carriers lock the bootloader (e.g. Verizon) and currently on the most recent versions of Android on the Pixel 2 series, it's not possible to unlock the bootloader.
Don't worry! If you have the Pixel 2 XL, as it was made by a different manufacturer, it might not have access to Download Mode. Do note that we don't even use it in this video, it's merely a menu option in the bootloader.
You will need to flash the latest Magisk Canary build instead of the stable/beta ones for now. You can download the canary-release builds. forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
:( usually Verizon (or some other carriers that lock their devices) activated or bought devices have locked bootloaders, currently there is no way around this (but ensure that OEM unlocking is enabled).
I don't think it's possible officially. Perhaps you can take a look at these threads: forum.xda-developers.com/nokia-6-2018/how-to/root-nokia6-1-devices-t3831682 forum.xda-developers.com/nokia-6-2018/how-to/guide-how-to-unlock-bootloader-paid-t3822192 There is a paid method of getting the bootloader unlock 'file'.
Thanks Mirza! Usually Google is quite good with handling devices which have their bootloaders unlocked. It's quite hard to brick one (in away, but don't count on it being completely fool-proof). I'd consider what you have to gain when rooting. You might want enhanced adblocking, automation, permissions management or just being able to use Magisk to add modifications to your existing ROM.
@@MaowDroid Newest version. I was trying to boot TWRP after I set up the phone though and booting right after flashing a new bootloader and all that seemed to fix the issue.
![How to Root Pixel 2 or Pixel 2 XL! [EASIEST METHOD]](http://i.ytimg.com/vi/nFD9sa-WdUM/mqdefault.jpg)
![How to Root Pixel 2 or Pixel 2 XL! [EASIEST METHOD]](/img/tr.png)
![How to Root Google Pixel 4 & 4 XL on Android 10 [Walkthrough]](http://i.ytimg.com/vi/S2Ke36U2WqQ/mqdefault.jpg)
![How to Root Google Pixel 3 / (XL) on Android Pie (9.0) [Walkthrough]](http://i.ytimg.com/vi/BgV1xxkcBk8/mqdefault.jpg)
![How to Root Android 10! [Pixel/Pixel 2/Pixel 3/Pixel 3a/Pixel 4/Pixel 4XL]](/img/n.gif)
So easy, im floored! Took less than 10 minutes. You're a beast, subscribed. Best tut on YT
Awesome! I'm glad this helped you out jam. :D
@@MaowDroid hey, rooted my pixel 2 running Android Q the lastest beta with video tutorial. How ever my bootloader was unlocked.
Can't enable OEM Unlocking anymore for anyone that's update their OTA to latest Android Pie (9.x). The security "patches" prevent it, and now the option is 100% grayed out. I have tried the adb uninstall phone option, I have tried multiple factory resets, etc. Will need a new method/app for those stuck with a Pie upgraded 2XL. Mine is perma locked unless someone comes out with a new method. (And yes, I originally bought my unlocked phone from the Google Store directly, but Verizons OTA locked it down).
Hey dude, this worked pretty alright! Took an hour, but I finally got it down. Thank you so much! Super professional tutorial, best on youtube by far.
This was fantastic. I spent hours trying to re-root after updating to Pie. This video finally fixed all my problems. Thanks!
Thank you so much for your comment jluemd! It should have been quite simple, but I'm glad you found this video useful! :)
absolute legend, I got a Pixel 2 today (coming from a Oneplus 6 android Q) process is well delivered and you obviously know your stuff! thanks for your help and keep up these high-quality instructionals (they really are helpful) 😎👍
Thank you Jonathan for your comment! That means a lot! I'm super glad it was good to follow. :) Let me know if you have any particular requests.
@@MaowDroid subs+😀👍 looking forward to watching your catalog of vids .
So damn easy!! I've been working on this for months but kept running into Verizon's locked bootloader. Finally bought a used device that was from Google store. Now I need to remove the ugly "unlocked bootloader" message during reboot. I see a few hits on google search but I am not a very trusting person and wondered if you'd already produced content on this topic? Thanks again, love your channel.
Fantastic to hear that Robert! Pesky carriers at it again.
Unfortunately there hasn't been a way to remove that message on boot. It's been like that since the 6P and 5X days.
This walkthrough was amazing. i have wanted to root for so long but didnt dare! Thanks man!!
Thanks Scott! Have fun with your rooted Pixel now!
Awesome video, rooted my phone in 10 mins. The editing in this video is so clean. The animation style is great. Keep it up 👍
Thank you very much for your comment! :)
I'm glad you have found it useful.
Thanks Bro! Done rooting my phone! I’ve done install modules and now magisk boot my phone due installed for safety net. Boom! And Now my phone bootloops. And i skip to install TWRP RECOVERY “USE YOUR METHOD” 🤭 just like u said (i don’t like pop up twrp while start) and now ! Boom shakalaka. Bootloop.
Wait so a module bootlooped you? Or installing TWRP did? Either way, try to gain ADB shell access while bootlooping to remove all modules: magisk --remove-modules
Or flash the stock boot.img for the time being
Thank you so much the adb sideload didn’t work but thank you for teaching me to unlock the boot loader because I just installed the magisk zip on the phone and flashed it thank you so much 1+ sub
Great to hear! Sometimes we need to fix a few driver issues, etc. but I'm glad you managed to get the Magisk.zip on your phone and flashed in TWRP!
Do you think it would work with other phones but a different twrp zip file that corresponds with the phone ?
Great guide! Thanks mate.
Would be great to see a tutorial for flashing ROMs on the Pixel
Thanks for your comment Mike! :) For sure, we can take a look at doing that. I can perhaps do a general one, and more specific ones. But basically the steps are usually outlined on the thread. :D
absolute perfect guide for the rooting. very easy to understand. take my subscription.
Thank you! :D
saved me a couple of times.... best tutorial i have seen
Thanks for your comment James! I'm glad I was able to help you. :)
Thank you for this excellent and easy to follow guide! Much appreciated!
Hello I need help on google pixel 2(smaller one), whenever I type in fastboot flashing unlock, an error pops up saying "FAILED (remote: 'Flashing Unlock is not allowed"If anyone could help me it would be highly appreciated
Hi Pres! You must have OEM unlocking enabled. And if you can't do that, there's no way around that unfortunately. :(
I have rooted Android 10 using your method. Its so easy
Just curious, did you use Beta or Canary Magisk? And TWRP worked well?
MaowDroid I used TWRP 3.3.0-0 walleye / magisk-v19.3 latest stable
MaowDroid I'm using the pixel 2 I had no issues using TWRP
@@SkinneeBoy awesome thanks! :)
@@SkinneeBoy you also installed TWRP too? No issues decrypting /data?
Great tutorial buddy. Keep going! Nitrogen OS here we go!
:D happy flashing! Maybe I should start looking at some custom ROMs 😉
AMAZING!!! you have yourself another sub!!
Thanks Mr. Cena, if that's what your name is implying ;-)
Seamless process. Thank you for your work!
No worries fifa22! :)
I have no option to download on Bootloader menu, fastboot command doesn't work... I watched how to install google usb drivers but i don't have the Lemobile ones to begin with....very confusing.. and im not old im 28... someone help
Thanks for this. I managed to learn a few things too and I've been messing with phone rooting for years.
One thing however, how does OTA work with this? I assume you can get it, but then do you lose root? Does it just update with no errors? Do you need to do what you have done here (minus unlocking bootloader) for every OTA update?
Depending on what you might do to your phone between rooting it and getting an update, we can use Magisk Manager to help us take the incremental OTAs that get sent to our phones (very handy if you don't want to download 1GB+ every time there is an update, but that requires you NOT to make any modifications to the /system and /vendor partitions as it checks that before flashing the OTA).
I will be making a video on this for November. :)
You can get an idea of what you might have to do (in case you have done some modification to your /system or /vendor partition) here in my monthly update videos: th-cam.com/video/fgZNOlNIlDM/w-d-xo.html
Best video on how to root that I've ever seen.
Thank you Stephen!
I'm able to unlock OEM the first time around but when using the flashing unlock command i get an error. I went back to setting and found OEM option grayed out. Factory reset fixes this but I'm unable to get passed this cmd
Hi Armando, it seems like you've got a Pixel 2 that has its bootloader locked unfortunately. I've heard of this particular case where the OEM unlock toggle is available/toggleable, but it doesn't change the state of the bootloader to allow it to be unlocked.
If the 'fastboot flashing unlock' command says something along the lines of: OEM unlock is not allowed, and you've already tried toggling the OEM unlock toggle (in the developer options), there's nothing you can do. :(
The last workaround for this has already been patched out as of January 2018 I believe.
If i disable automatic system updates will i get the persistent notification that i have a new update? I remember this from before. It was so annoying
That would only be the case if you get an update pushed to your phone 🤣, after rooting mine doesn't really do that anymore, I don't actually recall if you can hide those system notifications.
You'll be able to update anyways, but just not through OTAs (if you've flashed the TWRP installer).
Almost shit my pants but it was worth it. Worked flawlessly.
Thanks a lot for your amazing and organized video, I'm impressed. I learned a lot form it and you have an extra subscriber.
My OEM Unlock option is grayed out, my Pixel 2 XL is international version though and it is unlocked, I used sim cards from 5 different countries with no problems. Is there anything to do about this and enable OEM unlocking? Thanks again :)
I'm having the same issue, oem unlocking is greyed out on my unlocked pixel 2 xl. im using it on sprint btw so it clearly is carrier unlocked...
Worked like a charm for my Pixel 2 XL. Thanks so much! SUB!
Did you do it in Android q beta 5
@@Saad-jn9sc no, I'm still on Android pie
It is very clearly, thank you!
I bought an unlocked google pixel 2 xl to use with sprint, for some reason oem unlocking is greyed out on my device...
I heard if you activate it with a carrier SIM it can lock your OEM unlocking toggle. You may have to contact Sprint.
I can't connect my Pixel 2 XL to my pc, anyone having the same problem ? I get Device Descriptor Request failed. I've looked up everything online nothing helped
Now why did you choose magisk beta and not stable?
It had better support for Pie at the time.
yoo thanks for that cmd command trick
No worries! I was told of that some time ago when I was still holding Shift + Right Clicking for the 'Open Command Window Here' option!
Hey, I'm having a lot of trouble getting the serial number to show up when using "fastboot devices". I followed your USB drivers video, but I don't even have LeMobile drivers and when I try to install the USB drivers, Windows says "Windows has determined the best driver is already installed" and shows me 'MTP USB Device' as the driver.
When your device is in the bootloader, there shouldn't be connections via MTP! When your phone is in the bootloader and you see the MTP USB device, try uninstalling the device.
Replug your device, and if it automatically installs the MTP device again, you may need to use USBdeview to remove the driver record.
Also see if you can choose from an existing list of drivers, rather than pointing to a folder, or letting Windows Update look for newer ones.
Can you unlock the bootloader on a Verizon pixel 2 xl? My oem unlock is greyed out.
Hey there! Unfortunately since past January of 2018, Verizon rolled out an OTA which patched up a workaround. Since then, there have been no new developments to my knowledge. 🙁
Sadly you are fucked. That's what you get from ordering your phone from the scummy red V
@@MaowDroid hi, any word on a workaround recently? #still_stuck. Thanks !
@@brianb2087 hey Brian! Still nothing I'm afraid. :(
Take a look at that: forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
I do not know why in my pixel 2 when flashing the magisk v18.1 he throws me a failed! i try with v17.2 and says me update finished with error 1 :(
Sorry for the late reply!
I probably wouldn't go that low with Magisk. Is this your first time rooting?
I would try flash the Magisk uninstaller. Boot into Android and then go back into the bootloader, boot the TWRP image and then flash Magisk 18.1.
Otherwise, try patching your stock boot image (from the factory image) via Magisk Manager to root.
Hi. Im at the step where I need to set up the bootloader and my device state is locked despite doing everything as you did it. it says
FAILED (remote: 'Flashing Unlock is not allowed
')
when I try to enter fastboot flashing unlock
You probably didn't enable OEM unlock.
@@MaowDroid I did, tried it over like 3 or 4 times and it didn't work. I got a new phone today anyways I just figured it would be fun to try this out.
@@phenomenologicalparadox5216 hmm strange. Would you be able to copy the whole command output?
Also which phone did you get?
Most easy and perfect tut! thank you very much!
Thanks for your comment Ori. :)
I did everythinhg same as you did on my google pixel 2xl but it still did not pass safety net on magisk. Could you help me?
Google has implemented hardware based attestation for SafetyNet. There is a way to force it back to basic evaluation by using the MagiskHide Props module (you can get from Magisk Manager). Then SafetyNet will pass for the time being until Google verifies what kind of device we are running.
hello , i need your help. i followed all the steps on my googelpixel xl 2.. i got up to sideload. adb sideload, dragged magisk into the cmd prompt. pressed enter.. it started but then the screen went black... my computer recognises my device but the screen is black on my phone
nevermind i hard rebooted it, not sure if magicdisk went on oyr not yet.
Uhh haha, wait so were you not able to decrypt your data partition in TWRP to access your internal storage? TWRP does have a screen timeout, but you typically can wake it up from there.
Bro i am new to this stuff i used to be an apple guy bought pixel 2, so what is the benefits of rooting and also disadvantages especially in pixel 2
Welcome to team Android. :D
There's a large range of benefits, mostly it's down to your own personal needs. Now I understand that you might not know what you need/want, if you don't know what's out there. :)
Advantages: systemless mods (fonts, Active Edge Mod (customise the squeeze for assistant)), root/iptable based firewall, some apps have enhanced functionality with root access (depending on the app of course, I can't list them all).
Disadvantages: some apps may not choose to work anymore when you are rooted, although Magisk can currently hide itself and bypass SafetyNet (a Google API for detecting system modifications). Monthly updates would need a little bit more manual work, so no more automatic OTA updates for safety of course!
Need Your Help Bro
After Updating to android 10 magisk stoped working and
root status: sorry root access not properly installed on this device
What should i do now
How did you update?
You should be able to flash Magisk Uninstaller, then flash the latest version of Magisk. The canary builds seem to work quite well.
Is that message from a root checker app? There is really no need for those, Magisk Manager will tell you whether Magisk is installed or it isn't.
I have followed your tutorial exactly. Thank you. Do I need to do anything so that Google Pay works? I know that rooting phones stops that.
Hey Luke! So typically Magisk will enable Magisk Hide for Google Pay, so you should be able to go ahead and add your payment method. :) Of course, you can double check in Magisk Manager as well.
I followed all the steps without issue, but when it comes to sideloading magisk it just doesn't work. I copy across the zip file to the cmd and press enter. It just goes to the next line and doesn't let me do anything else. It does not show the 'serving' line yours does. The phone takes a while to load up and then says sideload failed and brings me back into the phone. Any help much appreciated! TWRP all working fine! (android 9 btw)
Having the same issue
@Waffles!
Would you be able to try pushing the Magisk.zip (adb push [magisk.zip] /persist) to /persist, and then trying to navigate to that via the Install menu on TWRP?
Apologies I no longer own my Pixel 2 so I can't do some testing, but even that happening on Android 9 + TWRP is a little strange. Are you able to do it if you boot from the TWRP.img instead.
@@MaowDroid Hey thanks for the follow up! I actually was able to get my pixel 2 rooted by following this: th-cam.com/video/7T8HnpVLMdg/w-d-xo.html
My only issue is my phone is rooted, but since it's a "production" phone, I only have access to "su" over ADB, no access to adb root. There are guides on how to edit my .prop files, but they all are fairly old, and I'm concerned about bricking my device as I'm totally new at this...
@@no1TFKfan ah just patching the boot.img! Definitely the way to go for Android 10+, as I would have thought that TWRP should still work on Android 9 (to be fair, I had issues decrypting data myself, and sideloading would bootloop me!).
I'm glad you got it rooted in the end. :D
@@MaowDroid Yup! sideloading would just fail sadly.
idk if you might know but I'm having issues sending fast sendevent commands to my phone. I edited the .prop files, but apparently only eng marked builds not user can access true root (adb shell root) not just su access. I spell out more details on what I've tried so far here:
stackoverflow.com/questions/62079599/using-sendevent-in-python-to-usb-connected-phone-slow-due-to-su-access
So, today I followed all of the steps but it did not wipe my phone but it still seems too be rooted.
Stuck At Fastboot
program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing
😭 please help me
You'll need to install the Windows Universal C Runtime.
support.microsoft.com/en-ca/help/2999226/update-for-universal-c-runtime-in-windows
i cant allow Oem unlock it doesnt allow me to. even am connected to internet
You seem to have a locked model, either activated from Verizon or some other carrier who locks their bootloaders.
There is no workaround for that currently. :(
I purchased my pixel 2 xl from Verizon and my oem unlocking button is greyed out. But now I have service through AT&T with the same phone. That won't change the fact that the oem unlocking feature still won't work right?
Yeah it's really unfortunate :( it won't change a thing
@@MaowDroid I figured as much. I need to send it in to get a new one so maybe I will get lucky with a refurbished unlocked one. Thanks for the quick response man 👌
cheers man, worked great
Very clear tutorial
Thanks! I'll try this sometime, even though I've never rooted a phone so it'll be a first for me. How hard is it to go back to 100% completely stock? Unrooted, locked bootloader and such.
No worries! Take your time. :D
As for going back to stock, it's as easy as Pie (pun intended). You can have a look at what that might look like here: th-cam.com/video/zQmK5KwN5dk/w-d-xo.html
Help I got my phone all the way to the end but i cant figure out how to add magisk during adb sideload
What do you mean 'add magisk'? You can just type in adb sideload *drag **Magisk.zip*
thank you so much mate you have made my day!!
Thank you for your comment! :D
Can you make a video on how to disable the carrier tether check for the Pixel 2 and XL?
You may want to take a look at this post: forum.xda-developers.com/showpost.php?p=74442342&postcount=2
:)
I can look into making a video for this if I can disable tethering on my own phone as my carrier hasn't put that restriction on my phone.
@@MaowDroid A video or advice would be great. I'm not to sure about step3
3 - Edit build.prop
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "net.tethering.noprovisioning=true" >> /system/build.prop
reboot
Do you just type each line and hit enter? What is SU
@@lhamagedon
'su' means superuser. It elevates your current terminal instance.
so after you type 'adb shell', you'll see a $. When you type 'su' at that prompt, and accept the superuser request, the $ will turn into a #.
Now all commands you run with #, will be run as root. So you would continue with:
mount -o rw,remount /system
echo "net.tethering.noprovisioning=true" >> /system/build.prop
reboot
(or whatever the commands were).
Hope this helps!
How do I boot into TWRP custom recovery if I have it's already installed with my bootloader unlocked, I want to install SuperSU zip file for rooting
Without a PC
@@anisatawna If you have installed TWRP, just boot into the bootloader, then change the selection to 'Recovery Mode' and press the power button to select it. If you're trying to root the Pixel 2, I would *strongly* advise against using SuperSU. It has effectively been abandoned and probably won't work on recent versions Android Pie. Please use Magisk instead.
Hello there, nice tut seamless and easy, btw can I use temporary twrp to install custom kernel and magisk on pixel 2 / (XL)?. if I installed magisk can I still get ota updates? And why we need to disable automatic system updates what will happen if it updates?.
Hey Mr. Dog.
Yes, you can boot TWRP to install a kernel, in fact you can do most things in there if you don't wish to install TWRP.
Yes, you can have Magisk installed (although additional steps are required), but not if you had also installed TWRP.
The worst case is that you get into a bootloop, but it would just usually result in you updated, and without root. (but re-rooting would be as easy as booting TWRP and flashing Magisk).
failed remote flashing unlock is not allowed
What is Magisk? How do you get it on your android (just drag and drop and initiate install from Files?)
Hey there, I am going to buy a refurbished pixel 2 xl. Should I root it right away? or should i wait some time? I am new to this, thanks for your help.
It shouldn't matter, just depends on how long you're willing to wait ;)
After typing fastboot flashing unlock...it says not allowed
You must enable OEM unlock, if you can't, call your carrier, but generally speaking it's not possible to change on your own. :(
@@MaowDroid i enables it but in bootloader
It says device state locked
Please help.me
@@shivamghimire400 unlocking the bootloader is in 2 steps:
Enable OEM unlock in developer options.
Boot into fastboot, run: fastboot flashing unlock
Then you must confirm bootloader unlock.
@@MaowDroid it didn't work :(
Hay I'm not sure if u still read these comments but if you do pls help I can't tern on oem unlocking it just says connect to the internet or contact your carrier but I'm already connected to the internet and I'm not sure what to do???
Hi beastie, I do try to read my comments regularly, but work has limited that recently.
Usually, that means your carrier has decided to block unlocking the bootloader. All the workarounds that I've seen have already been patched out. So there's nothing you can do unfortunately. :(
Yeah figured that out a bit after but thanks I'm going to buy the pixel 4 from Google hopefully that won't block that
got this error while fastboot boot twrp
FAILED (remote: dtb not found)
Any ideas?
Have a go at this video: th-cam.com/video/nGkYtP1y58A/w-d-xo.html
You dtb may be mismatched for some reason. Ensure that you're using the latest version of TWRP.
Great vid but can you tell me how do i get the OTA updates? Has this been enabled now and good to go?
Hey Warren, thanks for your comment! OTA updates can be done with a little bit if extra work as described here, using Magisk Manager: topjohnwu.github.io/Magisk/tutorials.html#ota-installation
The note there saying you MUST have an non-tampered /system and /vendor partition is quite serious. If you have mounted /system as read-write, you may not be able to take OTAs.
I do make monthly videos on using the factory images, which would be safer to use if you have made some /system modifications, or you are unsure.
But generally speaking, if you've just rooted using Magisk, installed some modules and haven't used any apps for specifically making system-based modifications, you can with a good chance use the method described above. All you would need to do is to wait for the OTA to get pushed to your phone. :)
@@MaowDroid Here is teh thing, i went to system and updates and it stated it had one and tried to download but of course it could as my phone is rooted, so i paused the download and follow the instructions you outlined to me, when i went back in to resume the down load it stop and stated that Octobers was the latest update for the Pixel 2 XL, which was very strange. Anyway i tried pressing it a few times to try and instigate the download but it wouldst. Tried the procedure a few times and still wouldn't work. Any ideas why this happened? I went and just flashed the factory image anyway,but this way would be better.
@@MaowDroid Tried it and it didnt seem to work, be good to do a video on this maybe, this method would seem alot easier to do
@@warrencoakley Yeah it's quite strange. I do recall Google saying that the Check for Updates should now manually get the latest update, so no more waiting or staged rollouts. However, when I tried to do just that for November, it also told me that it was the latest update. Several reboots, and even updates to the latest Google Play Services, still no dice. So, if I do get the chance next month to show this off, I definitely will. 😁
What if OEM unlocking option is greyed out? My phone is already carrier unlocked though
Network unlocked and bootloader unlock capabilities are different. Your phone may have been either activated on a carrier that locks their bootloaders (i.e. Verizon), or it was bought from one of those carriers.
There are no workarounds for this unfortunately. :(
@@MaowDroid aww man. So i can't root the phone then?
Yeah that would be the case unfortunately. :(
@@MaowDroid ah that sucks. Do you have an idea on how to get it fixed?
MaowDroid bro I just got a refurbished pixel 2 xl just to root it, and then I figure out it was activated by Verizon and now I'm fucked and can't even oem unlock this shit. This is the first time I've ever encountered a problem that even the geniuses on XDA couldn't bypass. Whoever came up with this needs to be shining somebody's shoes tomorrow they don't even deserve a job
Im getting stuck at Google Logo after I flash Magisk ! I tried 17.1 & 17.3 beta - same results :/ any idea why ?
Not too sure about this, I've had others having the same issues.
You can try patching the boot image via Magisk Manager instead, or try flashing the Magisk Uninstaller and then trying to flash Magisk again.
@@MaowDroid solution was : flash uninstall magisk zip first and then flash magisk afterwards :p
Nice! I'm glad you got that sorted. :)
@@MaowDroid any other suggestions?
@@seanroy7874 were you unrooted to begin with? And you've tried flashing the Magisk uninstaller?
I have been looking into rooting my Pixel 2 XL as of late and am wondering if this process changes at all as a result of the December Security Update.
Hi Nick! Nope, the process is exactly the same as it was. :)
@@MaowDroid Awesome! Thanks for the info. A definite subscriber now.
@@nickm3569 No worries! Don't hesitate to ask if you have any more questions! :)
FAILED (remote: 'Flashing Unlock is not allowed ')
Unfortunately , PIXEL 2 XL Android Pie November Update
Hi Özgür, I apologise for not making it clear in the description (although I thought I had), some phones on certain carriers have locked their bootloaders, one example would be Verizon in the US, but I would assume there are other carriers around the world doing something like this.
These phones rely on exploits or workarounds for their bootloaders to be unlocked. The last known one was close to December or January last year/earlier this year. Which have been patched. :(
But just double check that you have enabled OEM unlocking (that would be greyed out if your phone has a locked bootloader).
@@MaowDroid Thanks for the kind reply. I tried everything, probably it is unlockable.
Do I disable OEM unlocking option in System settings after Rooting it or do I leave it enabled?
Please leave it enabled. :)
when i do the adb sideload it says no devices found help please
Does your device appear in the device manager at all?
Anyways, that was only if TWRP was unable to decrypt your /data partition, as that can happen occasionally. I should have mentioned that.
So what you can do, is boot back into Android and then copy the Magisk.zip to your phone via MTP (USB for File Transfers), then boot into TWRP again, and flash Magisk.
ok I'll try later on thank you
Wait so I can update my system without anything happening and will work efficiently
Thanks a lot.Very easy and convenient steps.
Thanks Irfan! :) I'm glad you found this to be helpful.
Thank you, successfully rooted ! 👍
It's normal every time i turned on or reebot my phone got warning bootloader like 11:40 ? is there any way to skip that? Thanks bro I really appreciate that !
Great stuff Jefferson! Unfortunately it's unskippable, but a couple of seconds each time your reboot shouldn't hurt too much ahha. It's been talked about since the Nexus 6P, but no-one has found a way to remove it, but it doesn't bother me anymore :)
Just don't relock the bootloader! Unless you return to stock first at least!
does this work as of january 2019? i have a pixel 2 xl and want to use substratum themes by rooting with magisk
Yep it should work just fine. :)
@@MaowDroid my oem unlocking is greyed out. It says connect to the internet or contact your carrier. What should i do?
ah :( there are certain carriers out there such as Verizon who will lock the device's bootloader. There was a workaround for this, but that was patched almost exactly a year ago. There is nothing you can do for now.
@@MaowDroid dammit :( . Thank you for replying
Good Video ands We can earn so many important facts from this article HomeBest Root AppsTWRP adds decryption support for Google Pixel & Pixel 2 on Android Pie|Download
TWRP adds decryption support for Google Pixel & Pixel 2 on Android Pie|Download
perfect tutorial thank you :D
Should I keep Bootloader Unlocked or can I Lock it and only Unlock it whenever I want to install something that requires for it to be unlocked?
You must keep your bootloader unlocked once your phone is not 100% stock! (e.g. you have installed TWRP or you're rooted).
Also note that you'll be wiping your phone every time you lock and unlock the bootloader.
@@MaowDroid I see. Thank you. Great tutorial.
+MaowDroid
Do app updates happen automatically after rooting?
Yep, they should happen regardless of being rooted or not.
Any build number that under the android 9 version will do?
Yeah, there's no real restriction to which build of Android 9. It should even work for Android 10, but I would not flash the TWRP installer.
MaowDroid Alright, will get one and root it! By the way, your tutorial is very clear and easy to understand. Appreciate that lot! *Thumbs up* :D
If I use magisk can I still use NFC and fingerprint for apps?
Depends on the apps. NFC isn't affected by root (on it's own), but then again it would just boil down to the apps you're wanting to use.
I don't think Google Pay works currently, it used to for a while. 😢
sir can i do it same on google pixel2xl running android 10??
You won't be able to use TWRP to do so, perhaps have a look at my Oreo root video which will go through using Magisk Manager to patch the stock boot.img to root.
OEM is currently lock do you know how to unlock it. Its grayed out.
Some carriers lock the bootloader (e.g. Verizon) and currently on the most recent versions of Android on the Pixel 2 series, it's not possible to unlock the bootloader.
Hey by any chance do you have a guide to downgrade from android 10 to 9?
You can follow my unrooting video, just choose the factory image you wish to go to. th-cam.com/video/zQmK5KwN5dk/w-d-xo.html
I have already updated my phone to android 10 is this same process work?
Yep that should be fine. You will have to sideload Magisk when in TWRP (which should be covered in the video).
@@MaowDroid Thank you
@@MaowDroid I did it successfully thank you
Do you know how I can control it from pc?
vnc viewer works? I don´t know best option
You can try something like Vysor, or yes, you can try a VNC server on your phone, or other remote 'desktop' apps for your phone such as TeamViewer.
@@MaowDroid with root, any way to control it from pc remotely ALWAYS, no usb?
Great job!
Thanks Silly Gooes! :D
Please help me how to root Moto G6 Android Pie ;-;
This looks like a good place to start: forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Can you unroot this? Cause I don't want to damage my pixel 2 permanently
Yes you can of course, you should be able to find that video on my channel.
You'll find it quite hard to permanently damage your Pixel. 😉
I can't find Download Mode in Boot loader Please Help
Don't worry! If you have the Pixel 2 XL, as it was made by a different manufacturer, it might not have access to Download Mode. Do note that we don't even use it in this video, it's merely a menu option in the bootloader.
How do u get iPhone emojis wthout root
Magisk also bypasses Fortnite verification.
That's great to hear, especially for those who play haha
What about pixel 2 from Verizon?
Ain't happening chief :( there haven't been any other workarounds since Jan 2018.
does this work with android q?
You will need to flash the latest Magisk Canary build instead of the stable/beta ones for now. You can download the canary-release builds.
forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Can you add exposed framework to Android pie pixels?
Unfortunately, Xposed hasn't been updated to work on Pie yet. By the looks of how Xposed was made compatible with Oreo, it may take a while.
@@MaowDroid thanks I kinda used it for the nodded ig app and a few other things
OEM unlocking is disabled.
:( usually Verizon (or some other carriers that lock their devices) activated or bought devices have locked bootloaders, currently there is no way around this (but ensure that OEM unlocking is enabled).
so if on Verizon were screwed ?
Yup, still nothing for unlocking the bootloader on a Verizon Pixel 2. :(
Yeah man we are screwed. There isn't even a way to downgrade Android for us.
How to unlock Nokia 6.1(2018) OEM bootloader
I don't think it's possible officially.
Perhaps you can take a look at these threads:
forum.xda-developers.com/nokia-6-2018/how-to/root-nokia6-1-devices-t3831682
forum.xda-developers.com/nokia-6-2018/how-to/guide-how-to-unlock-bootloader-paid-t3822192
There is a paid method of getting the bootloader unlock 'file'.
Amazing but I'm worried about voiding my Pixel 2!!!
Thanks Mirza! Usually Google is quite good with handling devices which have their bootloaders unlocked. It's quite hard to brick one (in away, but don't count on it being completely fool-proof).
I'd consider what you have to gain when rooting. You might want enhanced adblocking, automation, permissions management or just being able to use Magisk to add modifications to your existing ROM.
Android 9.0 pie
Fastboot devices
Fastboot flashing unlock
👍👍👍👍👍😊
Hey man, when ever I do the fastboot boot "TWRP" it takes me too a screen of a battery charging icon. I'm on Pie,
Which version of TWRP are you booting?
@@MaowDroid Newest version. I was trying to boot TWRP after I set up the phone though and booting right after flashing a new bootloader and all that seemed to fix the issue.