Question [CLOSED] Read this before rooting your Raven ***OBSOLETE***

[Utini]

Yes and no. With an unlocked bootloader and vbmeta disabled, someone could grab your phone and flash their own boot image to try and compromise your data...but they'd still have to get through device encryption. It's honestly more statistically likely that you'd download a malicious app and grant it root access.

Thanks, I feel safe with disabling it then ;-)

 

[Morgrain]

Thanks, I feel safe with disabling it then ;-)

To be honest here, if you have someone that has unwanted physical access to your phone & wants to get into your phones files with a custom boot image, you have far greater problems than the Porn Search history that might get leaked. So, uhm, I agree.

 

[Az Biker]

i can't take it anymore. So, why does everyone feel the need to "update" every month? I can see if Google decides to release some "Revolutionary" camera update or something. But just for a security update? lol what a joke that's been running for about 3 years or better

Because I'm lazy, I update every other month, or every third month (unless the new update includes quadruple battery life), but I don't fault those who want, like, or feel the need to update monthly.

As crazy as it sounds, some users just ENJOY tinkering, flashing, and messing with their devices and a fresh, new monthly factory image is the perfect excuse to do just that.

I used to be one of those! I also used to underclock CPUs, GPUs, lower screen brightness, keep a 98% dark wallpaper, and Greenify everything app under the sun JUST to increase my SOT by 30 minutes

But like the monthly factory update, I am now too lazy and no longer care about having to plug my device in once a day

As for those who still squeeze every drop of life out of their battery, who enjoy updating the factory image every, single, month; good for you, keep on enjoying your device the way you prefer.

For those, like me, who are too lazy or no longer care about living on the developmental razor's edge, good for us.

 

[Flawn]

Maybe update OP Post? Permanent root is working...

 

[roirraW "edor" ehT]

Maybe update OP Post? Permanent root is working...

It seems to me that the OP is specifically about disabling verity and verification. I don't think there's anything about the OP that is wrong. The same user has a more detailed thread about the subject here: ****READ THIS BEFORE UPDATING!*****

 

[93fuelslut]

So my phone is picked up under "adb devices" and will adb to bootloader, but says waiting for devices when you fastboot nflashing unlock.

 

[roirraW "edor" ehT]

So my phone is picked up under "adb devices" and will adb to bootloader, but says waiting for devices when you fastboot nflashing unlock.

I know you said in the other thread that you updated the drivers, but I just wanted to share that when I used adb on the phone while it was fully booted up, I didn't have to install any drivers in Windows. When I was booted into recovery mode, I then had to install the latest Google drivers.

I'm only mentioning in case it shows in Device Manager that it doesn't have a driver installed after you boot to recovery.

Also, you're using the latest official Google platform tools? Sorry if you already mentioned it.

 

[HankMcCoyX]

I followed the steps to root and am in a bootloop. If I try to enter recovery I get the android with a red triangle and exclamation with no command listed underneath.

Any tips on how to fix this?

Thanks!

 

[V0latyle]

I followed the steps to root and am in a bootloop. If I try to enter recovery I get the android with a red triangle and exclamation with no command listed underneath.

Any tips on how to fix this?

Thanks!

Bootloop, as in continuous? Or the device reboots to Rescue Party?

To enter recovery, you have to use the key combo - when you get the image of the Android with the red triangle, hold down Power and click Volume Up to enter the menu.

 

[HankMcCoyX]

Bootloop, as in continuous? Or the device reboots to Rescue Party?

To enter recovery, you have to use the key combo - when you get the image of the Android with the red triangle, hold down Power and click Volume Up to enter the menu.

Turns out the phone was unhappy with the cable I was using. I had several flashes of the factory image fail when trying before I realized to try a different one.

After reflashing I got the correct events to happen.

 

[93fuelslut]

I know you said in the other thread that you updated the drivers, but I just wanted to share that when I used adb on the phone while it was fully booted up, I didn't have to install any drivers in Windows. When I was booted into recovery mode, I then had to install the latest Google drivers.

I'm only mentioning in case it shows in Device Manager that it doesn't have a driver installed after you boot to recovery.

Also, you're using the latest official Google platform tools? Sorry if you already mentioned it.

Yeah I installed the latest Google drivers but still isn't listed in device manager on my PC. I'll have to check which platform tools I'm running

 

[93fuelslut]

Incorrect. DM verity and vbmeta verification MUST be disabled to run a patched boot image. This is true regardless of whether it's the 12 Beta or the public release.


Remove Magisk via the Uninstall option within the app; first use Restore Images, then use Complete Uninstall. This will restore the boot image, so you don't have to. It will then reboot the phone.

At that point, yes, you would install the older version of Magisk, then root as usual by patching the boot image.

So I think I'm on the latest a12 so hopefully it's not beta. If I'm not rooted, I can just download an older version of magisk and install that normally? As in just patching the boot image

 

[V0latyle]

So I think I'm on the latest a12 so hopefully it's not beta. If I'm not rooted, I can just download an older version of magisk and install that normally? As in just patching the boot image

Magisk 23001 and older doesn't seem to work to patch the Pixel 6/Pro boot image; you have to use 23010 or newer.

Many modules are going to be ported to Zygisk anyway so I'd recommend just using the latest Canary, 23015.

 

[93fuelslut]

Magisk 23001 and older doesn't seem to work to patch the Pixel 6/Pro boot image; you have to use 23010 or newer.

Many modules are going to be ported to Zygisk anyway so I'd recommend just using the latest Canary, 23015.

So if I want root, I have to follow the OP guide?

 

[V0latyle]

So if I want root, I have to follow the OP guide?

This is an information only thread, and as such, there is no guide. However, here is the guide I wrote for the P6/P6 Pro.

 

[Dragon Kumera]

Been rooting and roming since Nexus 4. I'm really starting to wonder if it's even worth it anymore.

Using ssd boost app and adaway plus custom bootanimation are really the only reasons I root.

 

[V0latyle]

Hello mate, I updated to the OTA but not bothered about losing data. Which instructions am I best following for permanent root?

Many thanks

Which instructional steps would you suggest I use for being on the latest update and not bothered about losing data, to get permanent root (not lost on reboot)?

Please don't ask the same question twice. It will be answered eventually.

Update to Magisk 23016. If possible, do this from within the Magisk app. If you are using the Alpha, you will need to remove it, then install 23016.

After doing so, you can update however you want, and root normally by patching the boot image. Disabling verity/verification is no longer necessary with Magisk 23016.

I am unable to update to the day 1 Nov firmware .36 update. I initially was on .19 rooted tried to update to .36 after removing Magisk but it didn't work. So I factory reset my phone and tried to perform ota install but it fails to install. How can I install .36 ota?

Update to Magisk 23016 first. See above. Then, dirty flash the factory image; I recommend using Android Flash Tool, as this is easiest.

Probably need to re-enable these, might have to reflash again after.

(these are the OP's instructions to disable them. Adjust accordingly to re-enable:

There is no need to re-enable verity/verification if disabled. Just don't worry about them at next update.

 

[V0latyle]

Given that most of this information is now irrelevant, this thread will be closed. Please move discussions to this thread.