I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
doveman said:
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
Click to expand...
Click to collapse
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
NOSS8 said:
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
Click to expand...
Click to collapse
Yeah, I downloaded the correct ROM (miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip) and extracted the boot.img from that.
Renaming magisk.apk to magisk.zip and flashing it just installs the app doesn't it, it doesn't root the phone as far as I'm aware.
I followed the instructions here, which say that you should only tick the "Patch vbmeta in boot image” option when patching the boot.img in Magisk if the device does NOT have a separate vbmeta partition. The Poco X3 does have a separate vbmeta partition,, so I didn't tick that option.
Installation
The Magic Mask for Android
topjohnwu.github.io
I've tried the "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" command with four different versions of fastboot that I've got, dating from 2016 to 2020, and they all reject the "--disable" switches as an "unknown option".
I tried it without those options, so I flashed the patched boot.img and then did "fastboot flash vbmeta vbmeta.img" but after rebooting Magisk still shows that root is not installed.
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot
Size: 5.3 GB
Release Date: 2021-11-09
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz
NOSS8 said:
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot
Size: 5.3 GB
Release Date: 2021-11-09
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz
Click to expand...
Click to collapse
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
doveman said:
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
Click to expand...
Click to collapse
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Check:
https://forum.xda-developers.com/t/...n-vendor-dynamic-partition-enable-rw.4238807/
https://forum.xda-developers.com/t/q-h-safety-way-to-unlock-bootloader-flash-recovery-root.4198719/
NOSS8 said:
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
doveman said:
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
Click to expand...
Click to collapse
What happens if you try to root from the Magisk app?
NOSS8 said:
What happens if you try to root from the Magisk app?
Click to expand...
Click to collapse
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
doveman said:
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
Click to expand...
Click to collapse
No functional TWRP for this device.?
NOSS8 said:
No functional TWRP for this device.?
Click to expand...
Click to collapse
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
doveman said:
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
Click to expand...
Click to collapse
Strange case as strange as the number of threads has this subject for this device.
NOSS8 said:
Strange case as strange as the number of threads has this subject for this device.
Click to expand...
Click to collapse
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
doveman said:
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
Click to expand...
Click to collapse
This phone is rootable, surely an oversight or an error somewhere.
NOSS8 said:
This phone is rootable, surely an oversight or an error somewhere.
Click to expand...
Click to collapse
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
doveman said:
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
Click to expand...
Click to collapse
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
NOSS8 said:
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
Click to expand...
Click to collapse
I've already got TWRP recovery flashed. I guess I'll have to flash the ROM again and start from scratch.
I tried flashing super.img but that didn't fix it. In the end, going into ADB Sideload mode in TWRP and flashing the 2.7GB recovery version of the ROM with
"adb sideload miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" fixed it without losing any data.
I still can't root it though. I've tried the "install Magisk (root)" option in TWRP and renaming magisk.apk to magisk.zip and installing that in TWRP, but it still shows "Installed N/A" in Magisk and Root Verifier says "Root permission not granted or Superuser App Missing" but then it says "Superuser App: 25.25:MAGISKSU", so it's the root permission that isn't granted.
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
NOSS8 said:
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
Click to expand...
Click to collapse
I thought so but I've reflashed the patched boot.img and done
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
and
"fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img"
in case it needed that too, but Magisk still shiows "Installed N/A"
I tried installed SR5-SuperSU-2.82 zip from TWRP to see if that would get it rooted,, but it couldn't even install that, it just gave some error.
Related
Hi
Anyone give me service of Root my mobile Online?
OnePlus 8T ?
I'm teird to Root my mobile, please help
4lielion said:
Hi
Anyone give me service of Root my mobile Online?
OnePlus 8T
I'm teird to Root my mobile, please help
Click to expand...
Click to collapse
Hey there,
Try this link: https://forum.xda-developers.com/oneplus-8t/how-to/guide-how-to-root-oneplus8t-kb2001-t4178675
I don't know how this work.
4lielion said:
I don't know how this work.
Click to expand...
Click to collapse
Read, then read some more, and then read some more.
There are literally too many threads on how to root this phone.
Sent from my OnePlus8T using XDA Labs
sharkie405 said:
Read, then read some more, and then read some more.
There are literally too many threads on how to root this phone.
Sent from my OnePlus8T using XDA Labs
Click to expand...
Click to collapse
Been out of the game for a while. Just a question.
The purpose of python and dumploader is to extract the boot.img?
And then let magisk patch it and flash it via fastboot?
ddaharu said:
Been out of the game for a while. Just a question.
The purpose of python and dumploader is to extract the boot.img?
And then let magisk patch it and flash it via fastboot?
Click to expand...
Click to collapse
You can get all ".img" you need, of course including boot.img.
You can also get boot.img by using modified recovery with ADB function.
Like this:
https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/
Not recommend directly flash modified boot.img, try "fastboot boot boot.img" first, if it can successful boot in system, then magsik patch local boot.img. This way you can avoid flash error/broken boot.img.
ULTRAJC said:
You can get all ".img" you need, of course including boot.img.
You can also get boot.img by using modified recovery with ADB function.
Like this:
https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/
Not recommend directly flash modified boot.img, try "fastboot boot boot.img" first, if it can successful boot in system, then magsik patch local boot.img. This way you can avoid flash error/broken boot.img.
Click to expand...
Click to collapse
THANKS MAN! THIS PERSON PATCHED THIS boot.img. PROVIDING THAT IT'S THE CORRECT IMAGE, I CAN JUST UNLOCK THE BOOTLOADER AND THEN "fastboot boot boot.img" FOLLOWED BY INSTALLING ON MAGISK AND THAT SHOULD BE IT?
Dopamin3
Sunday at 3:05 AM
#497
I was able to temporarily boot TWRP to backup the kernel from 11.0.9.9. Instead of a boot.img file it gave a boot.emmc.win but I flashed it back with "fastboot flash boot boot.emmc.win" and it worked fine. I also tested the Magisk patch and it booted with working root access. I have North American KB2005.
Stock 11.0.9.9.KB05AA boot.emmc.win (NA): https://drive.google.com/file/d/1LS7ZL9ib9PqszQL_KW_BASQox8nOAKJX/view?usp=sharing
Magisk patched 11.0.9.9.KB05AA boot.img (NA): https://drive.google.com/file/d/15OS1wx7u7P6yc9ggDguWtVm-9Y6s8H1d/view?usp=sharing
ddaharu said:
THANKS MAN! THIS PERSON PATCHED THIS boot.img. PROVIDING THAT IT'S THE CORRECT IMAGE, I CAN JUST UNLOCK THE BOOTLOADER AND THEN "fastboot boot boot.img" FOLLOWED BY INSTALLING ON MAGISK AND THAT SHOULD BE IT?
Dopamin3
Sunday at 3:05 AM
#497
I was able to temporarily boot TWRP to backup the kernel from 11.0.9.9. Instead of a boot.img file it gave a boot.emmc.win but I flashed it back with "fastboot flash boot boot.emmc.win" and it worked fine. I also tested the Magisk patch and it booted with working root access. I have North American KB2005.
Stock 11.0.9.9.KB05AA boot.emmc.win (NA): https://drive.google.com/file/d/1LS7ZL9ib9PqszQL_KW_BASQox8nOAKJX/view?usp=sharing
Magisk patched 11.0.9.9.KB05AA boot.img (NA): https://drive.google.com/file/d/15OS1wx7u7P6yc9ggDguWtVm-9Y6s8H1d/view?usp=sharing
Click to expand...
Click to collapse
"fastboot boot boot.img" is temporary use the boot.img in your ADBTOOL folder, next reboot will return to ROM boot.img, so after you boot in system, you also need to magisk patch local boot.img before any reboot, and that should be it.
ULTRAJC said:
"fastboot boot boot.img" is temporary use the boot.img in your ADBTOOL folder, next reboot will return to ROM boot.img, so you also need to magisk patch local boot.img before reboot, and that should be it.
Click to expand...
Click to collapse
Sorry I'm not sure what you mean.After I do all of that and the phone boots up, go to this area of magisk and patch the same boot.img from ADBTOOL?
Sorry for my limited english…
After the phone boot up, patch the current boot.img like this:
"fastboot boot" command didn't really flash that boot.img, just temporarily boot it once.
Hello.
I had root in beta 1 by flashing a modified boot image patched by magisk (after wiping my device and disabling verification on vbmeta with fastboot). I was able to boot into the system no problem and root was achieved.
Now that I have flashed Beta 2, I'm not able to root. I tried flashing disable verification with vbmeta but it won't go past the Google logo. It says the data is (damaged). I tried flashing just the modified boot image of Beta 2 (from magisk) and it says it's not able to verify the boot image. I also tried booting into the boot image, flashing magisk directly through the app, but when it reboots, it gives the same error.
The only thing I haven't tried is factory reset my data.
Any help would be appreciated, thanks.
Don't use the beta. That's why it's a beta there's always bound to be issues
thatsupnow said:
Don't use the beta. That's why it's a beta there's always bound to be issues
Click to expand...
Click to collapse
Will I have to wipe my data after flashing the modified vbmeta?
Machuda said:
Will I have to wipe my data after flashing the modified vbmeta?
Click to expand...
Click to collapse
I would just to be sure that all traces are gone
I ran into the same problem until I used the flash tool and disabled verity and verification. If you don't do this, you'll be unable to boot if you have a modified boot image.
To root Android 12 you have to flash the beta image and than do this:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
And I think when you do a update, its broke the disabled verity & verification.
I find this and you can to update with this command
fastboot update --disable-verity --disable-verification image-redfin.zip
Click to expand...
Click to collapse
but I don't know I its work.
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...
Hello,
how can I root my phone with magisk 25.2?
My bootloader is already unlocked.
Thank you very much!
t0bM said:
Hello,
how can I root my phone with magisk 25.2?
My bootloader is already unlocked.
Thank you very much!
Click to expand...
Click to collapse
First,
Find the boot.img of your firmware
Patch it using magisk app
Find a patched vbmeta of your phone's version
Move those to your pc and into the folder where fastboot is found
Reboot to fastboot mode and connect it to your pc
Type fastboot devices to check if it is connected
Type fastboot flash boot nameoffile.img(the boot file name)
Type fastboot flash vbmeta nameoffile.img(the vbmeta file name)
Restart the phone either manually or using fastboot reboot
you should also put this command to avoid bootloop or any problem with booting your phone
fastboot --disable-verity --disable-verification flash vbmeta nameoffile.img(vbmeta file name)
The easiest method is by downloading magisk latest apk from the github and rename it to Magisk.zip and flash it with your custom recovery
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
???