I use Aignes Website Watcher on the computer asking with the Website Watcher app that syncs with it through DropBox, to let me know when certain webpages have new material.
You can only root a phone if you can unlock the bootloader. Verizon phones have always come Carrier unlocked from the start, but you can't unlock the bootloader. It's either always been like this or been like this for so long (since before my first Android phone in 12 years ago).
If I called and requested for Verizon to carry your unlock my phone since I'm in Canada a country that doesn't Have Verizon as a carrier. Could that provide me some leverage with them or the representative being able to do it?You can only root a phone if you can unlock the bootloader. Verizon phones have always come Carrier unlocked from the start, but you can't unlock the bootloader. It's either always been like this or been like this for so long (since before my first Android phone in 12 years ago).
There have been a few lucky ways around it on some Verizon devices but it's nearly impossible anymore unless you just get lucky.
The simple answer is no, you can't do this with a Verizon device. Now if you buy a factory unlocked (meaning unlockable bootloader) and happen to use it with Verizon, then yes, you can still root it since you'll be able to unlock the bootloader.
Folks with the T-Mobile variant of the P6P are also lucky. They just have to talk to the right person in customer service to get their phones permanently carrier unlocked, and by chance that also enables their ability to unlock the bootloader as well.
No. Verizon phones are already carrier unlocked like I said. You don't have to use the Verizon phone with Verizon. You can use it with a carrier in Canada. You just can't unlock the bootloader. Verizon never allows bootloaders to be unlocked.
So I have not rooted since my old Nexus 6P but with losing the fabricated overlays with January update I finally pulled the trigger. Unreal how the process has changed since then.Never have I used magisk or done any of this before. Back in the day it was , unlock, flash twrp, flash SuperSU and bobs your uncle. I think I'm good to go now. And next I gotta see what kind of tinkering I can do. I may have to revive some of my old subs themes or something else.
View attachment 5510199View attachment 5510201
estoy en rom el 36 de noviembre
yo era root, asi que vea la imagen de arranque de noviembre para perder la raiz
Actualicé a enero por ota adb, falló 7 en 47%
Al reiniciar, perdí las opciones de desarrollador y tocando 7 veces en la compilación no abre las opciones de desarrollador.
como puedo recuperarlos
Edito, por ota en android tampoco se actualiza
No sé cómo, pero he logrado actualizar siguiendo esto
actualice el zip completo y actualice el gestor de arranque antes de actualizar todo
[GUÍA] Rootear Pixel 6 "oriole" con Magisk
The latest Canary does as well. It was tested by someone on the Pixel 5a and 6 with success, but we'll probably have to wait until February for a 100% verification.
I plan to try February update ota with the 23018 version. Since I already have the January update, I cannot do it.
If your OEM Unlocking is greyed out, it is most likely because you do not have the option to unlock the bootloader, regardless of whether or not your device is carrier unlocked.My phone is fully paid off. That's not the issue. It's carrier locked because that's just their policy and they apparently just carrier lock everything and refuse to change that until you've been using it, active, for 40+ days. Because they suck.
Yes, I know that carrier locks are not the same thing as bootloader locks, my phone is carreir unlocked and the OEM Unlocking option is grayed out and my understanding is that the OEM Unlocking option is grayed out because the bootloader is only meant to be unlockable once the carrier lock is removed.
Sounds like you're on T-Mobile US.......Is it impossible to root / unlock the bootloader for a carrier-locked device? My Pixel 6 is carrier locked and I'm getting the impression that I'd have to actually use the device for 40 days and get an official carrier unlock before I could unlock the bootloader, and I'd need to unlock the bootloader to root.
Unless I'm mistaken carrier unlock and bootloader unlock are two completely separate animals.Is it impossible to root / unlock the bootloader for a carrier-locked device? My Pixel 6 is carrier locked and I'm getting the impression that I'd have to actually use the device for 40 days and get an official carrier unlock before I could unlock the bootloader, and I'd need to unlock the bootloader to root.
To add: Once you pay off your device, they can carrier unlock your phone, and also make it possible to enable OEM unlocking (so that you can unlock the bootloader). Many, many others on T-Mobile have reported doing that.
Oh, you wanted to wipe, lol. My misunderstanding. Yeah, what @Az Biker said.Right, I wanted to wipe. It's a brand new phone that was on .036, and not yet activated. I'm wondering if I did wipe, with the --disable-verity --disable-verification into the .bat file, am I good to go ahead and install Magisk, and from now on, not wipe on future updates, or do I have to do this extra step after (fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img)?
The Magisk Repo has been removed from the Magisk app. You can use this instead...
Root has been achieved, thank you for your time & assistance, it's much appreciated.You shouldn't need to flash to both slots. So you can just do fastboot flash boot <nameofpatchedbootimage.img>.
You should be able to rename the patched boot image (although I have never done it). I usually just put it in a labeled folder and copy and paste the name into the command prompt.
You should be patching the boot.img that you extracted from the factory image. It's located in the image-raven-sd1a.210817..037 zip file within the factory image (assuming you are on build .037).
If you are still having problems, then 2 things to check:
1. Make sure your Platform Tools are up-to-date. Latest I believe is 31.0.3
2. Make sure you have the correct (and latest) USB drivers installed on your computer... https://developer.android.com/studio/run/win-usb
EDIT: Oh, one very important thing. Make sure you are using the latest Canary version of Magisk.