I'm trying to root an Oukitel WP12 with Magisk.
I've downloaded the firmware from the vendor's link and flashed it successfully just like for other Oukitel phones (WP6, WP10).
I could also create a magisk-patched boot image. I followed regular practices: unlocked the bootloader, confirmed by orange state message and flashed the patched boot image.
The phone gets into a boot loop.
This phone differs significantly from other Oukitel phones I saw before. It comes with Android 11 by default, moreover: the device is an A/B device.
Also: apart from vbmeta, it also has vbmeta_system and vbmeta_vendor. I tried flashing a blank vbmeta for vbmeta first and than to all three vbmeta partitions without success.
Anyone came accross with a phone with vbmeta, vbmeta_system and vbmeta_vendor partitions? How I should correctly create blank vbmetas for these partitions?
Note that there's also a boot-debug partition and for several partitions there are partitions with a -verified suffix, like: dtbo-verified, tee-verified, etc.
I think it's probably the wrong vbmeta blanks I'm using causing the boot-loop. Flashing the original images restores the phone - although without magisk root of course...
If you have any ideas or instructions on how to overcome this obstacle, please let me know.
Thanks: Dw.
Unfortunately I can confirm the boot loop. I don't have a solution for now, if you have one, please share!
Hi @Dwokfur,
Finally I managed to root my Oukitel WP12. The recpie you posted is OK, you should only re-flash also the Verified Boot partitions with the proper fastboot flags.
WARNING: the vbmeta* partitions I downloaded from the phone were different from the ones found into the Oukitel firmware zip archive: So I used the one extracted from the phone with the SP Flash Tool v5 program.
After all the final fastboot recipe is:
Code:
fastboot flash boot_a magisk_patched-23000_rgkOP.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_a.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system_a.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor_a.img
wrong thread, ignore, sorry.
Hi,
I had a rooted Oneplus Nord (OOS 11)
I updated the device with the newly released ColorOS 12 update
The root disappeared, so I downloaded the Payload file to root again thru magisk
However, the payload.bin has boot.img, vendor.img files but there is no "vendor_boot.img" file
When I flash the patched boot.img file, the device gets stuck in bootlooop.
I am assuming this is because vendor_boot.img is not patched
Has anyone successfully rooted Oneplus Nord after ColorOS12 update? Can someone help?
Any help on rooting ColorOS 12 updated on Oneplus Nord?
Hi, I am undergoing the same issue. But, sort of have an idea how to fix it. Unfortunately I am a bit worried to try it out. I know there is no vendor_boot image to patch. But isn't it the same thing to patch vendor.img? Could you try patching that and let me know of the results?
I tried patching vendor image. There was an error in magosk.
I'm going to try flashing Twrp recovery on the phone and try installing magisk to root it. Will let you know how it goes
No luck, doesn't work for Android 12. Waiting on some update for rooting the Nord
puru said:
Hi,
I had a rooted Oneplus Nord (OOS 11)
I updated the device with the newly released ColorOS 12 update
The root disappeared, so I downloaded the Payload file to root again thru magisk
However, the payload.bin has boot.img, vendor.img files but there is no "vendor_boot.img" file
When I flash the patched boot.img file, the device gets stuck in bootlooop.
I am assuming this is because vendor_boot.img is not patched
Has anyone successfully rooted Oneplus Nord after ColorOS12 update? Can someone help?
Click to expand...
Click to collapse
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
This worked. I am still testing though.
Link to canary - https://github.com/topjohnwu/magisk-files/blob/canary/app-debug.apk
Mr.Lucky said:
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
Can anyone confirm this does work without having to wipe the entire phone's data?
Thank you
Hi
This works and data is intact.
Mr.Lucky said:
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
How do I patch the boot img ?
Do I use those fastboot commands immediatly after flashing the new rom (reboot to fastboot). No need to install magisk to 2nd slot(after ota) ?
robuser007 said:
How do I patch the boot img ?
Do I use those fastboot commands immediatly after flashing the new rom (reboot to fastboot). No need to install magisk to 2nd slot(after ota) ?
Click to expand...
Click to collapse
Install OOS12, install magisk and patch the boot.img, then boot into the bootloader and type the commands. After an ota, magisk must be installed in the inactive slot.
Does this also work with Magisk v25 released today?
Where can I find those files? I guess I have to move those to the fastboot folder on my pc ?
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
robuser007 said:
Does this also work with Magisk v25 released today?
Click to expand...
Click to collapse
No, I'm not able to have a bootable magisk patched boot image, also using magisk canary release.
After I flash the patched img the Nord goes in bootloop, the only way to have it working is to flash back original boot.img
About the vbmeta.img & vbmeta_system.img I have used the extracted from payload_output folder, I think is correct?!?
Did you manage to solve this ? I really want to upgrade but not loose root.
I rollback to stable Android 11, I have tested the new version for one day and is graphically bugged everywhere, seems they release a beta, not a stable version.
I rollback to stable Android 11 with Orange Fox recovery, Root, safetynet-fix ok, ecc ecc
I have tested the new version for one day and is graphically bugged everywhere, then no recovery, no root, Color OS seems not for me for the moment.
What do you mean with graphically bugged everywhere ?
How can I stay on having root, does it work with latest canary?
robuser007 said:
Did you manage to solve this ? I really want to upgrade but not loose root.
Click to expand...
Click to collapse
I'm also not upgrading because of 'loose of root"
Still not able to find fix of safety net fix for A12..
all method i tried but safetynet is not fix.... CTS profile always FAILED...
nobody has any method which is working...
Now that I have my IMEI numbers restored, I am going to again attempt to flash LineageOS over my stock Android 9.
Let's say I want the latest revision of LineageOS 18, I understand that this is the required system image;
lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img.xz
I also know a vbmeta file is required. This is where I get confused and suspect it's the reason I always get bootloop when flashing.
Do I need a stock vbmeta, a modified vbmeta or a blank vbmeta? I have quite the collection.
Also do I add flags;
--disable-verity
and / or
--disable-verification
Now last, but not least, is my sequence of flashing correct?
fastboot flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot erase userdata
fastboot reboot
I appreciate your time and help.
probably stock vbmeta will work, or get the one in TWRP page for Nokia 2.2
Hello all,
I rooted & unlocked my TMO OP9 using magisk and flashed a stock image.
I'm now trying to install a A13 mod from Pixel Experience. I patched the boot image after running the payload dumper tool. Now I have the patched boot image from magisk copied to my PC. I"m not sure what commands to run now once I reboot into fastboot. Maybe I'm not in the right fastboot (like fastbootd or something)
PS C:\Users\cterr\OneDrive\Desktop\OnePlus9-December2022> adb devices -l
List of devices attached
6bf0a351 device product:OnePlus9 model:LE2117 device:OnePlus9
PS C:\Users\cterr\OneDrive\Desktop\OnePlus9-December2022> adb reboot fastboot
<reboots>
<select fastboot from menu, reboots>
PS C:\Users\cterr\OneDrive\Desktop\OnePlus9-December2022> .\fastboot.exe flash boot .\magisk_patched-25200_aAy2x.img
< waiting for any device >
This fails as fastboot doesn't see my phone. I'm not even sure if I'm supposed to flash to <boot> or recovery.
I remember running this command below for disable-verity in the past but it fails as well. Probably due to a typo. If anyone can confirm that would be great. Do I use fastboot to flash to the boot? Like #fastboot flash boot <magisk_image>. I'm nervous that once I get the fastboot to flash i'll flash it to the wrong place.
PS C:\Users\cterr\OneDrive\Desktop\OnePlus9-December2022> fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
C:\Android\fastboot.exe: unknown option -- disable-verity
Thanks!
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
What device are you talking about ?
f1tm0t said:
What device are you talking about ?
Click to expand...
Click to collapse
Tab p11 4gig
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
f1tm0t said:
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
Click to expand...
Click to collapse
Threr is no twrp sadly
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
mingkee said:
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
Click to expand...
Click to collapse
I tried it i flashed patched boot.img only in fastbootd still boots me in to the bootloader
LSS4181 said:
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
blocky3321 said:
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
Click to expand...
Click to collapse
Which Magisk version did you use? From what I can tell any official Magisk version should work.
I haven't really tested the recent builds of vvb2060's Alpha or huskydg's Delta... so if you're using these versions I can't really help you much...
Additionally, you need to check which slot you are now, and through fastbootd check which slot actually has system, vendor and such. Normally the super partition only has enough size for one slot. You may have entered a wrong slot that doesn't have usable system.
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
Getting Started: What's Your Device ?
Tab p11 4gig
Device->settings->About : Model & Hardware -> Lenovo ??? (Tb-j606f,TB-J616F...) In your case stiker on box or on back.
mingkee said:
who told you to flash vbmeta.img?
Click to expand...
Click to collapse
???