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

Status
Not open for further replies.
Search This thread

Zilla0617

Senior Member
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:



You already asked this question just a few posts up from this. :) Wait for an answer.
That sucks I hope i don't have to wipe my phone again when the images come out
 
  • Like
Reactions: roirraW "edor" ehT

snovvman

Senior Member
Jun 6, 2008
1,530
511
When you use
Code:
fastboot boot boot.img
ADB sends the boot image via USB to the phone, and the phone loads it instead of what's in the /boot partition. Therefore if you boot a patched image, you should have root.

However, following the instructions above, you'll still have to wipe. There is an as yet unidentified issue with rooted boot images tripping something (probably the kernel) into thinking data is corrupted.

Here is something you can try however:
1. Download the OTA and the factory image to your computer
2. Patch the boot image from the factory zip
3. Sideload the OTA:
Code:
adb reboot sideload
adb sideload ota.zip
4. When the update completes, you will be in recovery. DO NOT REBOOT.
5. Select "enter fastboot"
6. Flash vbmeta and boot:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash boot magisk_patched-23xxx_xxxxx.img
7. Reboot your device

If you have just unlocked your bootloader and have not done anything else, you should be able to boot a patched image for temporary root, if you don't want to lose data.

If you FLASH the patched image (and disable verity/verification) you have to wipe data, or the phone will boot into Rescue Party.

The only possible alternative is to sideload the OTA EXACTLY as I posted above, meaning you have to flash vbmeta and boot in fastboot.

If you flash the images in bootloader, you will have to wipe.

These two posts contain very important information for those who want to update future patches without wiping. At this time, it's probably the best chance we have. @V0latyle, to date, have you observed success with these procedures in avoiding the need to wipe? Thank you.
 

V0latyle

Forum Moderator
Staff member
These two posts contain very important information for those who want to update future patches without wiping. At this time, it's probably the best chance we have. @V0latyle, to date, have you observed success with these procedures in avoiding the need to wipe? Thank you.
It's hit or miss honestly.
 

mkhcb

Senior Member
Nov 2, 2012
305
313
After reading through this thread, I have 2 dumb questions.

If you use this alpha build that has safety net working, will you always have to format your data with the monthly security updates, to maintain root?

Is there a dummy proof, step by step guide on how to root with this alpha build?

Thanks in advance!

I am a step above the average Joe when it comes to tech. Way below avg compared to you folks .
 

Pekempy

Senior Member
Aug 22, 2011
660
318
UK
Google Pixel 6 Pro
So I just finished setting up my phone, to confirm should I flash or boot the alpha magisk patched boot image? My verity/verification is already disabled from my previous root.
If you boot, you'll have temporary root until you restart your device. This is useful for either testing the boot image works, or you can then use "Direct install" from magisk manger.
If you flash, it should give you root which persists between reboots.

Either one should work.
 

Zilla0617

Senior Member
If you boot, you'll have temporary root until you restart your device. This is useful for either testing the boot image works, or you can then use "Direct install" from magisk manger.
If you flash, it should give you root which persists between reboots.

Either one should work.
I'm a little confused. When you say direct install, do you mean after I flash in bootloader go back to Magisk manager hit "install" select the direct option and the let the system reboot again?
 

Pekempy

Senior Member
Aug 22, 2011
660
318
UK
Google Pixel 6 Pro
I'm a little confused. When you say direct install, do you mean after I flash in bootloader go back to Magisk manager hit "install" select the direct option and the let the system reboot again?
If you boot the image from bootloader (fastboot boot x.img) you'd need to use Direct install in Magisk to keep root.

If you fastboot flash boot x.img, you won't need to do the direct install
 

m0viefreak

Member
Jan 25, 2012
5
5
I cannot get live booting for temporary root to work on SD1A.210817.036 anymore:

  • stock vbmeta / stock boot + Normal start:
    -> Phone starts
  • stock vbmet + 'fastboot boot boot-patched.img'
    -> Does not boot at all, screen turns off for a second, then I am back in the bootloader.
  • vbmeta patched + 'fastboot boot boot-patched.img'
    -> Recovery / 'Cannot load android system. your data may be corrupt'.
Was working fine on SD1A.210817.015

Anyone else seeing this behavior?
 
Last edited:
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)?
Sorry I took so long to reply. I'm not an expert and shouldn't be considered one, but I've gotten so much help from XDA forums over the years I feel bad not contributing if I've got even 1% knowledge to help.

So, here's what I did...

1. Download factory image from Google, Riru & USNF from GitHub and MagiskAlpha from Telegram.
2. Unlock bootloader (and factory wipe; all the developer mode, USB debugging and adb/fastboot + Google USB driver information applies as normal)
3. Install MagiskAlpha, patch the factory boot.img
4. fastboot flash with verity first, then fastboot flash boot the MagiskAlpha modded boot img, then reboot.
5. You've now achieved root and have the ability to use MagiskHide. Do so, add all of Google Play services to the deny list, hide MagiskAlpha, install Riru module, reboot.
6. Add USNF module. Reboot.

should now have persistent root and pass SN. Add your DRM and banking apps to the deny list as necessary. May have to clear your Google Play data.
 

dr_rick13

Senior Member
Apr 15, 2011
1,184
618
OnePlus 6
OnePlus 6T
Sorry I took so long to reply. I'm not an expert and shouldn't be considered one, but I've gotten so much help from XDA forums over the years I feel bad not contributing if I've got even 1% knowledge to help.

So, here's what I did...

1. Download factory image from Google, Riru & USNF from GitHub and MagiskAlpha from Telegram.
2. Unlock bootloader (and factory wipe; all the developer mode, USB debugging and adb/fastboot + Google USB driver information applies as normal)
3. Install MagiskAlpha, patch the factory boot.img
4. fastboot flash with verity first, then fastboot flash boot the MagiskAlpha modded boot img, then reboot.
5. You've now achieved root and have the ability to use MagiskHide. Do so, add all of Google Play services to the deny list, hide MagiskAlpha, install Riru module, reboot.
6. Add USNF module. Reboot.

should now have persistent root and pass SN. Add your DRM and banking apps to the deny list as necessary. May have to clear your Google Play data.
Hey man thanks for this write-up. Can you clarify step 4 "fastboot flash with verity first" I get the second part but don't completely follow here. Can you elaborate please?
 

cultofluna

Senior Member
Nov 25, 2015
3,950
1,984
Google Pixel 6 Pro
I cannot get live booting for temporary root to work on SD1A.210817.036 anymore:

  • stock vbmeta / stock boot + Normal start:
    -> Phone starts
  • stock vbmet + 'fastboot boot boot-patched.img'
    -> Does not boot at all, screen turns off for a second, then I am back in the bootloader.
  • vbmeta patched + 'fastboot boot boot-patched.img'
    -> Recovery / 'Cannot load android system. your data may be corrupt'.
Was working fine on SD1A.210817.015

Anyone else seeing this behavior?
After "cannot load android system, your data may be corrupt" message..perform a wipe data..if you want to boot...
 
Hey man thanks for this write-up. Can you clarify step 4 "fastboot flash with verity first" I get the second part but don't completely follow here. Can you elaborate please?
Yeah, I mean run the command:

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

Then:

fastboot flash boot your_magisk_alpha_modded_boot.img

Then:

fastboot reboot
 

snovvman

Senior Member
Jun 6, 2008
1,530
511
I'm cross posting this from another thread because it contains relevant discussions to this thread.

Using @V0latyle's procedure, I have been testing by factory flashing to A4, root, then sideload OTA to C2, flash vbmeta and patched boot while in fastboot (not bootloader). Twice now, the phone boots fine but no root. If I go back to fastboot and re-flash vbmeta and patched boot, I get corrupted data.

From what I can tell, after sideloading OTA, flashing vbmeta, the fastboot flash boot command flashes the patched boot to the inactive slot. This is why I don't have root. Trying again, I used the --slot all switch, but got an error when flashing to the other slot. After rebooting the phone and going back into fastboot, fastboot flash boot automatically flashes the active slot but triggers a need to wipe.

Clear as mud, I know, but it's what I am seeing so far.
 
  • Like
Reactions: roirraW "edor" ehT

Nekromantik

Senior Member
Apr 1, 2010
6,723
931
London
Google Pixel 6 Pro
I'm cross posting this from another thread because it contains relevant discussions to this thread.

Using @V0latyle's procedure, I have been testing by factory flashing to A4, root, then sideload OTA to C2, flash vbmeta and patched boot while in fastboot (not bootloader). Twice now, the phone boots fine but no root. If I go back to fastboot and re-flash vbmeta and patched boot, I get corrupted data.

From what I can tell, after sideloading OTA, flashing vbmeta, the fastboot flash boot command flashes the patched boot to the inactive slot. This is why I don't have root. Trying again, I used the --slot all switch, but got an error when flashing to the other slot. After rebooting the phone and going back into fastboot, fastboot flash boot automatically flashes the active slot but triggers a need to wipe.

Clear as mud, I know, but it's what I am seeing so far.
Did you reboot fastboot after sideloading the OTA?
 
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.