I already flash android 11 lolinet ROM on my XT-1970-2 and it worked fine, I have wish to have TWRP and root with Magisk, but I don't know how to flash vbmeta.img file with adb.
With which tool they patch the vbmeta.img . And it works the same twrp-3.3.1-v4.img Magisk and edXposed work on android 11 for e moto one vision xt1970-2 ??
Can serve the above file used in android 10 = vbmeta_patch.img ?????
Related
Hello I come from this thread and downloaded the patched magisk boot image for stable android 10 BA but it break the wifi (iirc it mean it's for AA which have different firmwares). I already asked in the thread if there are a patched img for BA but I ask here in case someone already have a rooted stable BA Android 10 terminal because I really need root.
Thx
https://forum.xda-developers.com/showpost.php?p=80643311&postcount=158
You can also fastboot boot TWRP (unofficial built -70), then just flash Magisk and it will patch boot.img automatically, and obtain root.
Hi, I am trying to flash magisk. I patched my boot.img and flashed it via fastboot. But it didn't work, Magisk app was still showing as not installed. Then, I tried the Recovery method (flashing the magisk zip), it tells that magisk patched to the boot.img file but this method didn't work too. But it said magisk patched to the boot.img. What can cause it?
My rom: Xiaomi.eu 21.12.8, Android 12
My device: Xiaomi Mi 10T (apollo)
CaganAgabey said:
Hi, I am trying to flash magisk. I patched my boot.img and flashed it via fastboot. But it didn't work, Magisk app was still showing as not installed. Then, I tried the Recovery method (flashing the magisk zip), it tells that magisk patched to the boot.img file but this method didn't work too. But it said magisk patched to the boot.img. What can cause it?
My rom: Xiaomi.eu 21.12.8, Android 12
My device: Xiaomi Mi 10T (apollo)
Click to expand...
Click to collapse
Flashing the Magisk patched boot.img only installs the necessary binaries to gain root access, you have to manually install the Magisk Manager app to take advantage of the binaries that it installs. Flashing the patched boot.img does not automatically install the Magisk app on your device as part of the flashing process.
Here is the actual way to ROOT the most recent OTA SPA2.220405.003
This requires a full data wipe, so you have been warned.
1) copy the vbmeta.img and vbmeta_system.img from the OTA to your working directory
2) download the twrp.img from here: https://dl.twrp.me/redfin/ [version twrp-3.6.1_11-0-redfin.img only] to the same working directory with vbmeta.img and vbmeta_system.img
4) rename the recovery to "twrp.img" for simplicity sake
5) copy the boot.img from the OTA to your internal storage
6) install the latest Magisk app
7) patch the boot.img from the OTA
8) copy the patched boot.img from internal storage to the same working directory with vbmeta.img and vbmeta_system.img and twrp.img
9) rename the patched boot.img to "root-boot.img" for simplicity
10) reboot into the bootloader with adb from your working directory
11) run these commands exactly as typed below:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
fastboot flash boot root-boot.img
fastboot boot twrp.img
12) in twrp, wipe all userdata
13) reboot system and confirm it boots and that you have a working cellular radio.
Enjoy.
There are not proper root directions anywhere else for the Pixel 5 latest OTA, other than these. I've looked and this is the only way I have found that works 100% of the time for me.
Killed it!! Appreciate you
ghost9640 said:
Killed it!! Appreciate you
Click to expand...
Click to collapse
appreciate you!
Hi thank you, will this work to root lineage 19 (android 12)?
Edit: all done and rooted. no wipe required, Lineage 18 root, upgraded to Lineage 19 (lost root) and now regained root.
nrd\ said:
Hi thank you, will this work to root lineage 19 (android 12)?
Edit: all done and rooted. no wipe required, Lineage 18 root, upgraded to Lineage 19 (lost root) and now regained root.
Click to expand...
Click to collapse
These instructions should work for nearly any device with the same or similar partition scheme with an unlocked bootloader.
mainly, both vbmeta and vbmeta_system require verity and verification disabled, not just vbmeta which is where most people get it wrong and then wonder why their radio/system/root doesn't work right.
This is the official way to root going forward, until the partition scheme changes or a new bootloader/verity computation is released
Just to clarify do you have to disable verity and verification every single flash / update / new rom / re-root?
nrd\ said:
Just to clarify do you have to disable verity and verification every single flash / update / new rom / re-root?
Click to expand...
Click to collapse
Not sure for every ROM that is or will be available, but going forward with any OTA, yes. Again, that is until the partition scheme changes or a new verity measure is created in the bootloader and/or lk [little kernel]
Been a while since I last rooted any of my devices. I am currently on the April update to Android 12. What I want to do is root my Pixel 5 and roll back to Android 11. Should I follow these instructions, and then how to get to Android 11. Thank you for any help.
wmdunn said:
Been a while since I last rooted any of my devices. I am currently on the April update to Android 12. What I want to do is root my Pixel 5 and roll back to Android 11. Should I follow these instructions, and then how to get to Android 11. Thank you for any help.
Click to expand...
Click to collapse
I don't provide support.
And your questions have already been answered a thousand times over
wmdunn said:
Been a while since I last rooted any of my devices. I am currently on the April update to Android 12. What I want to do is root my Pixel 5 and roll back to Android 11. Should I follow these instructions, and then how to get to Android 11. Thank you for any help.
Click to expand...
Click to collapse
YouTube it
I would like to install a GSI on my A22 5G but I'm using the Android 12 Firmware and I can't downgrade to Android 11 due to Rollback protection. The problem is that the bootloader verifies the system image with vbmeta and I don't have a blank vbmeta for Android 12.
Yes ive tried it and it works fine with all the features.
i have experience about flashing , i flashed roms before
Read through this thread.
Root OnePlus 9
This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll...
forum.xda-developers.com
OEM unlock, using Fastboot.
Use the readback function of the MSM tool to get a copy of the boot.img file from the active slot.
Patch that with Magisk 25.2 (26.1 didn't work for me).
Fastboot to the patched boot.img file
Install Magisk directly.
Update Magisk to the latest version.
gotaug said:
OEM unlock, using Fastboot.
Use the readback function of the MSM tool to get a copy of the boot.img file from the active slot.
Patch that with Magisk 25.2 (26.1 didn't work for me).
Fastboot to the patched boot.img file
Install Magisk directly.
Update Magisk to the latest version.
Click to expand...
Click to collapse
can you explain how to copy boot.img from msm tool ?