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

[Zilla0617]

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

 

[snovvman]

When you use

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:

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:

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]

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]

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 .

 

[Zilla0617]

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.

 

[Pekempy]

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]

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]

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

 

[Zilla0617]

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

Got it. Thank you

 

[m0viefreak]

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?

 

[zee3are0]

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]

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]

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...

 

[m0viefreak]

After "cannot load android system, your data may be corrupt" message..perform a wipe data..if you want to boot...

Sure, I know. But live booting *without flashing boot* used to *not* trigger this on SD1A.210817.015.
It does on SD1A.210817.036.

So that workaround to get temporary root seems not to be working anymore.

 

[zee3are0]

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

 

[Lughnasadh]

Sure, I know. But live booting *without flashing boot* used to *not* trigger this on SD1A.210817.015.
It does on SD1A.210817.036.

So that workaround to get temporary root seems not to be working anymore.

Hmm, that's not a good sign...

 

[snovvman]

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.

 

[Nekromantik]

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?

 

[snovvman]

Did you reboot fastboot after sideloading the OTA?

No, stayed in recovery went to fastbootd. Did not go to bootloader.

 

[Nekromantik]

No, stayed in recovery went to fastbootd. Did not go to bootloader.

hmm maybe you need to reboot and then enter fastboot without booting into android so your in second slot then flash vbmeta and boot