• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Status
Not open for further replies.
Search This thread

Utini

Senior Member
Dec 25, 2010
1,161
210
www.whymacsucks.com
www.whymacsucks.com
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 ;-)
 

Az Biker

Sr. Mod / Mod & RC-RT Committees / Shred'r of MTBs
Staff member
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 :p

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 :D

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.
 
Last edited:

roirraW "edor" ehT

Recognized Contributor

93fuelslut

Senior Member
Jul 1, 2012
2,959
441
Nexus 6
So my phone is picked up under "adb devices" and will adb to bootloader, but says waiting for devices when you fastboot nflashing unlock.
 
Last edited:

roirraW "edor" ehT

Recognized Contributor
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.
 
Last edited:

HankMcCoyX

Member
Jul 8, 2016
22
6
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

Forum Moderator
Staff member
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.
 
  • Like
Reactions: roirraW "edor" ehT

HankMcCoyX

Member
Jul 8, 2016
22
6
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

Senior Member
Jul 1, 2012
2,959
441
Nexus 6
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

Senior Member
Jul 1, 2012
2,959
441
Nexus 6
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

Forum Moderator
Staff member
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.
 

V0latyle

Forum Moderator
Staff member
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.
 
  • Like
Reactions: roirraW "edor" ehT
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    Update 12-16-21: As of Magisk 23016, the below is no longer relevant; verity/verification need not be disabled for root.

    For instructions on rooting your Pixel 6 Pro, see this guide.


    This thread will be closed.



    For those of you who are planning on rooting:

    Be aware that Android 12 changed the way boot images are loaded, at least on the Pixel 4, 4a, and 5. We have no reason to believe the Pixel 6/Pro will be any different.

    Two new Verified Boot features implemented in Android 12 will interfere with attempts to root.

    Dm-verity (device-mapper-verity) is a method by which an image on block devices (the underlying storage layer of the file system) can be checked to determine if it matches an expected configuration, using a cryptographic hash tree. If the hash doesn't match, dm-verity prevents the stored code from loading.

    Vbmeta verification is the other half of this - it provides a cryptographically signed reference hash which is used to verify the integrity of /boot, /system, and /vendor partitions. The vbmeta image is only used to verify /boot, while vbmeta-system is used to verify /system.

    This was implemented to prevent persistent rootkits by means of a hardware level security check, to prevent "potentially harmful applications" such as Magisk from evading detection, as such applications residing within the kernel will have higher privileges than the detection applications.

    What this means is that with these two enabled, a modified boot image will cause a verification error when flashed to the device, preventing boot. Interestingly, this check is not performed against "live" boot images loaded via ADB, so with dm-verity and vbmeta verification enabled, a modified image can be booted as long as the image in /boot is intact.


    Dm-verity and vbmeta verification will need to be disabled in order to flash a rooted boot image. Unfortunately, this means that you will have to wait for the factory firmware to be released.

    fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

    We also discovered that a data wipe is required in order to get permanent root; flashing /vbmeta with the disable flags gets you stuck in recovery with "Unable to load Android system, your data may be corrupted" error if you didn't wipe /data when you upgraded. To be clear, this only happens in a specific circumstance:
    * You updated to Android 12 without a wipe, AND
    * You reflash vbmeta with the disable flags


    Here are some threads in the Pixel 5 forum on the matter:
    12
    Cheers for this, much appreciated. I can confirm (yet again) that you have to do disable-verity to root the P6 Pro. It's early enough since getting the phone (literally today) that wiping data isn't too much of a hassle at this stage IMO.

    Factory images are now up, I've just booted a freshly wiped phone with a magisk patch image, transferring stuff again now :)
    9
    1635445408510.png


    Confirmed.
    8
    Alright, so it's possible. Props to @snovvman for linking the vvb2060 repo, because if you read into the bits in English on the telegram, you'll discover that it has MagiskHide still, as an option.

    So:
    Download the latest alpha build from https://t.me/magiskalpha
    Install it by patching the boot image and flashing in fastboot. You might be able to do a direct install, but I patched it manually and checked it booted with fastboot first first to be safe.
    After it boots, you may need to uninstall a hidden Magisk manager if you didn't already - at this point the alpha build will take over, and tell you it needs to install some files and reboot, allow it.
    After rebooting, go into the Magisk settings and disable Zygisk. A magisk hide option will magically appear. Reboot.
    Install Riru and the latest Universal SafetyNet Fix. There's no repo in the build, so you need to get these from GitHub. I also have MagiskHide Props Config installed, but not with any BASIC spoofing enabled, just installed - not sure if that's required. Doesn't seem to be required.
    Reboot.
    Make sure you have Play Services unstable and snet added to your DenyList (it's still called DenyList, but it's Hide)

    Job done!

    1635533860772.png
    6
    The loss of "Hide Magisk" in the lastest release means a few of my apps (banking and work expense) are not going to work if I root my Pixel 6 P. So disappointing. I will miss GravityBox the most, but will learn to live without it.
    Magisk 23010 has DenyList, which works exactly like MagiskHide. However, getting Safetynet to pass is more complicated, as Riru is not compatible with 23010, so you can't use Universal SafetyNet Fix 2.0.0 or newer. So, I went back to Magisk 23001.