Hello everyone !
I am a realme 7 user and I was trying to root my phone. But when i flashed vbmeta using the command "fastboot --disable-verity--disable-verfication flash vbmeta vbmeta.img " but it says unknown action
I have seen many users solving their problem by using the command fastboot flash vbmeta vbmeta.img
Can can I use the same command to root my device ?
Narayanxtry said:
Hello everyone !
I am a realme 7 user and I was trying to root my phone. But when i flashed vbmeta using the command "fastboot --disable-verity--disable-verfication flash vbmeta vbmeta.img " but it says unknown action
I have seen many users solving their problem by using the command fastboot flash vbmeta vbmeta.img
Can can I use the same command to root my device ?
Click to expand...
Click to collapse
I have also the same problem did you solve it bro?
vassiliszacharis said:
I have also the same problem did you solve it bro?
Click to expand...
Click to collapse
You mean at DELVIK etc? I think the first time I did it yes.
Also I was wondering if I am making a mistake, when I tried to install TWRP, I used this command:
fastboot flash boot path to patched boot img
instead of this
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
as it was not recognised by ADB...
Related
i see 4 potential vbmeta images... anyone know which one is used to disable verity?
AiM2LeaRn said:
i see 4 potential vbmeta images... anyone know which one is used to disable verity?
Click to expand...
Click to collapse
do you have root an a unlocked bootloader?
yes
PopCaps1996 said:
do you have root an a unlocked bootloader?
Click to expand...
Click to collapse
yes
okay download this then grant root
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
back up
vbmeta_a
vbmeta_b
vbmeta_system_a
vbmeta_system_b
once backed up connect phone to pc then go to internal storage of phone then drag an drop PartitionsBackups folder to desktop.
go into that folder extract all file till you get .img then once you have the imgs
reboot to fastboot
do
Code:
fastboot getvar all
to see current bootslot
boot slot_a
Code:
fastboot --disable-verity flash vbmeta_system_a vbmeta_system_a.img
fastboot --disable-verity flash vbmeta_a vbmeta_a.img
boot slot_b
Code:
fastboot --disable-verity flash vbmeta_system_b vbmeta_system_b.img
fastboot --disable-verity flash vbmeta_b vbmeta_b.img
thanks
PopCaps1996 said:
okay download this then grant root
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
back up
vbmeta_a
vbmeta_b
vbmeta_system_a
vbmeta_system_b
once backed up connect phone to pc then go to internal storage of phone then drag an drop PartitionsBackups folder to desktop.
go into that folder extract all file till you get .img then once you have the imgs
reboot to fastboot
do
Code:
fastboot getvar all
to see current bootslot
boot slot_a
Code:
fastboot --disable-verity flash vbmeta_system_a vbmeta_system_a.img
fastboot --disable-verity flash vbmeta_a vbmeta_a.img
boot slot_b
Code:
fastboot --disable-verity flash vbmeta_system_b vbmeta_system_b.img
fastboot --disable-verity flash vbmeta_b vbmeta_b.img
Click to expand...
Click to collapse
well i was going to try this until my main phone dropped and digitizer died. So now this is my main for a few weeks. So quick question, has anyone successfully disabled DM-VERITY on this Nord N200 Phone? i dont want to try this until its confirmed as its now my only phone.
Hello Everyone
Last time i flashed the command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And
fastboot flash boot magisk_patched.img
And my phone was rooted successfully
But i unrooted it again....
And now when i try to root and enter command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img it says unknow option --dm verity ......
Help me out pls
narayan chetri said:
Hello Everyone
Last time i flashed the command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And
fastboot flash boot magisk_patched.img
And my phone was rooted successfully
But i unrooted it again....
And now when i try to root and enter command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img it says unknow option --dm verity ......
Help me out pls
Click to expand...
Click to collapse
RMX2155 or 2MX2151?
OrthodoxOxygen said:
RMX2155 or 2MX2151?
Click to expand...
Click to collapse
RMX 2151 bro
OrthodoxOxygen said:
RMX2155 or 2MX2151?
Click to expand...
Click to collapse
I have the same issue, could you help?
narayan chetri said:
RMX 2151 bro
Click to expand...
Click to collapse
yoboy44 said:
I have the same issue, could you help?
Click to expand...
Click to collapse
Did you make sure that USB debugging was turned on via the developer settings?
Try this guide, maybe:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Lemme know if it works.
Do you use the newest version of adb & fastboot? (older version had problem with the parameter)
Are you sure that verity is not disabled already? (try it without the parameter)
I have the same problem in when i try in Windows Power Shell.
I open cmd as administrator and start working for me .
Hope this can help to someone .
HeiloWorid said:
I have the same problem in when i try in Windows Power Shell.
I open cmd as administrator and start working for me .
Hope this can help to someone .
Click to expand...
Click to collapse
Didn't work for me
KillSkill said:
Didn't work for me
Click to expand...
Click to collapse
Flashing a blank vbmeta does the trick, don't need of a special command.
narayan chetri said:
Hello Everyone
Last time i flashed the command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And
fastboot flash boot magisk_patched.img
And my phone was rooted successfully
But i unrooted it again....
And now when i try to root and enter command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img it says unknow option --dm verity ......
Help me out pls
Click to expand...
Click to collapse
YOU HAVE TO USE FASTBOOT FROM ANDROID PLATFORM TOOLS FOR WINDOWS
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
here's its direct link :
https://dl.google.com/android/repository/platform-tools_r33.0.1-windows.zip
HeiloWorid said:
I have the same problem in when i try in Windows Power Shell.
I open cmd as administrator and start working for me .
Hope this can help to someone .
Click to expand...
Click to collapse
Thank you so much. This actually helped me rooting my Oneplus 7 Pro with Magisk instructions. I was using Powershell, but got the error "unknown option -- disable-verity".
It worked in CMD.
Thanks!
snsgn said:
It worked in CMD.
Click to expand...
Click to collapse
I've always had a sneaking distrust of Powerhell and its pedantic error messages.
I presume that these problems are a case of cmd and PS finding different versions of fastboot.
Just run fastboot --version in both to see if they are different.
A separate topic
In Windows and in Linux the default argument handling is based on the C language.
That means that fastboot flash recovery recovery.img gets changed to an array of 4 strings.
There is quoting and escaping and evaluation going on there too.
Windows has the GetCommandLine() which returns the command line as a single string.
This all sounds good, but a program can be executed in code with an array of strings too and the "command line" has to be manufactured after the fact.
This can lead to some complicated differences.
I think it's best to ignore that GetCommandLine() even exists.
Also, I noticed a peculiarity about GetCommandLine().
In cmd fastboot flash recovery recovery.img gets turned into:
C:\Dir\Subdir\fastboot.exe flash recovery recovery.img,
while PS turns it into:
"C:\Dir\Subdir\fastboot.exe" flash recovery recovery.img
Even when there are no spaces in the path.
Undoubtedly this breaks some Windows programs using GCL.
OTOH, adb and fastboot stick to straight C language handling, so this is not that.
I was trying to rootkit it, but on the last step I got locked in to a fastboot-loop, I eventually got out of it and was able to "install through ADB" through the OTA Oriole software.
Trying to rootkit it again, I messed up and got stuck on the same loop, but when I try to "install through ADB" the OTA file loads up 50% and I get the error "Current SPL 2021-11-05 Target SPL: 2021-10-05 this is considered a downgrade.
Denying SPL because it's SPL downgrade" and it aborts the installation.
Now whenever I try to boot, I get a "your phone is corrupted" message, I press power to continue, I get a message "your phone security is compromised" in orange, than I press power and it hangs on the Google logo on a white screen.
I can still get in to fastboot and all the options.
No idea what to try next.
If I took it to where I bought it, would they send it off to Google and they can fix it? Or do I have a brand new $1150 paperweight?
Thanks for any help.....
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
vbmeta needs to be flashed like this when u are going to want to root. If u already installed the ota there is a thread with the November vbmeta. I think it was on the 6 Pro forums.
sille said:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
vbmeta needs to be flashed like this when u are going to want to root. If u already installed the ota there is a thread with the November vbmeta. I think it was on the 6 Pro forums.
Click to expand...
Click to collapse
Where do I run this from, recovery mode? Do I need any new files?
Glitchedz said:
Where do I run this from, recovery mode? Do I need any new files?
Click to expand...
Click to collapse
In fastboot. As I said. Depends what version you are on. The Oct vbmeta is in the firmware files on the Google image webpage. The November one Is in the 6 pro forums
sille said:
In fastboot. As I said. Depends what version you are on. The Oct vbmeta is in the firmware files on the Google image webpage. The November one Is in the 6 pro forums
Click to expand...
Click to collapse
Sorry, I'm new to this. Do you mean that just have fastboot open on my phone, and type that command into cmd? And where do I put the vbmeta files? Do you have a link to the vbmeta files? I can't find any.
Really really appreciate any help, would love to save the phone.....
Glitchedz said:
Do you have a link to the vbmeta files? I can't find any.
Click to expand...
Click to collapse
Normally you can find the file vbmeta.img inside the "full stock ROM" archive for your phone.
Princip_Loskuta said:
Normally you can find the file vbmeta.img inside the "full stock ROM" archive for your phone.
Click to expand...
Click to collapse
Your reply is 8 months late, but if he didn't figure it out back then he will know now.
Hey sorry,
I have Pixel 6A.
adb shell ls -l /dev/block/by-name shows me that it has vbmeta_a AND vbmeta_b partition.
Would be this right?
fastboot flash boot_ab magisk_patched-[random_strings].img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87413987
Most root-tutorials (except of Magisk-Homepage) for Pixel 6A doesn't even show anything about vbmeta-stuff.
ephemunch said:
Most root-tutorials (except of Magisk-Homepage) for Pixel 6A doesn't even show anything about vbmeta-stuff.
Click to expand...
Click to collapse
That is because, to the best of my knowledge, you no longer need to touch vbmeta in order to root.
hi everyone,
by mistake i didnt reload magisk after ota(RMX2202_11.C.15 GDPR), so i lost my root
now, the situaiton is:
bootloader is working
ive tried to instal twrp but something doesnt wanna work. i guess i installed but the screen is black
then i did manually:
adb.exe shell "twrp install /sbin/Magisk.zip"
Click to expand...
Click to collapse
didnt work.
for 2nd solution i tried
with my rom's vbmeta.img, vbmeta_system.img, vbmeta_vendor.img basicly
fastboot flash boot root.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
Click to expand...
Click to collapse
didnt work either. and now when i try to open the phone, close itself and not always im able to open. now i can use just bootloader which is difficult to reach (need to press 3 buttons)
right now im waiting to finish unroot file.
well, (how) can i boot and root my phone without losing data?
Wow I'm in pretty much the exact same situation just made a thread lol
idk how but after some hours suddenly i saw that it started to work.
i think i changed the slot (like a>b) and flashed .img files on fastboot. at least now it works
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: I didn't test this procedure, I did backup the images from stock Chinese version before installing global version but I didn't flash it back. Please test at your own risks!
1. Make sure your bootloader is unlocked
2. Download the images provided in the link below
3. Boot your device to recovery (hold volume up and power until reboot)
4. Wipe data
5. Boot your device to bootloader (hold volume down and power until reboot)
6. Connect your device to PC (make sure you have installed fastboot on your PC)
7. From windows command prompt cd into the folder containing the images
8. Run the following commands to flash all images
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.
9. You should then be able to boot into system
Stock RMX3300 Chinese images: https://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300 Chinese images (slot B was the correct one when it was backed up): https://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
myogui said:
免責聲明：我不對設備變磚、SD 卡死等負責！
警告：我沒有測試這個程序，我在安裝全球版本之前備份了庫存中文版本的圖像，但我沒有將其閃回。請您自擔風險進行測試！
1.確保您的引導加載程序已解鎖
2.下載以下鏈接中提供的圖片
3.引導您的設備進行恢復（保持音量和電源直到重新啟動）
4.擦除數據
5.將您的設備引導至引導加載程序（按住音量和電源直到重新啟動）
6.將您的設備連接到PC（確保您已在PC上安裝了fastboot）
7. 從 windows 命令提示符 cd 進入包含圖像的文件夾
8.運行以下命令刷寫所有鏡像
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash 元數據 metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
快速啟動 -w
刷新 super.img 時，如果您在 header magic 處收到 Invalid sparse file format 消息，這很好。
9.然後您應該能夠引導進入系統
庫存RMX3300中文圖片：https ://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300中文圖片（備份時槽B是正確的）：https ://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
Click to expand...
Click to collapse
非常感謝你， 我會嘗試
wronkians said:
非常感謝你， 我會嘗試
Click to expand...
Click to collapse
Good luck mate!
myogui said:
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: I didn't test this procedure, I did backup the images from stock Chinese version before installing global version but I didn't flash it back. Please test at your own risks!
1. Make sure your bootloader is unlocked
2. Download the images provided in the link below
3. Boot your device to recovery (hold volume up and power until reboot)
4. Wipe data
5. Boot your device to bootloader (hold volume down and power until reboot)
6. Connect your device to PC (make sure you have installed fastboot on your PC)
7. From windows command prompt cd into the folder containing the images
8. Run the following commands to flash all images
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.
9. You should then be able to boot into system
Stock RMX3300 Chinese images: https://mega.nz/folder/Ilk2CBwb#VMlU6A8wcFJVU0twOD6vTA
All Stock RMX3300 Chinese images (slot B was the correct one when it was backed up): https://mega.nz/folder/d1dxEBTa#nzKU4KuhnDcHjK7MX_D2eA
Click to expand...
Click to collapse
I followed the steps to the letter. Still stuck in a bootloop
Moaz.Magdy said:
I followed the steps to the letter. Still stuck in a bootloop
Click to expand...
Click to collapse
I was stuck in bootloop too when I flashed the global version, try running the last 2 commands or wiping data from recovery then the last 2 commands again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
myogui said:
I was stuck in bootloop too when I flashed the global version, try running the last 2 commands or wiping data from recovery then the last 2 commands again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
Click to expand...
Click to collapse
Thanks! that did the trick. Finally running global version (from your other post) on chinese phone.
SirGustav said:
Thanks! that did the trick. Finally running global version (from your other post) on chinese phone.
Click to expand...
Click to collapse
Great to hear, congrats!
thanks mate
stuck on bootloop for me. i tried to run last 2 commands again, then it still stucks.
Addswes said:
stuck on bootloop for me. i tried to run last 2 commands again, then it still stucks.
Click to expand...
Click to collapse
I am so close tried the same and still bootlooping for me to
Well damn. Switching to the cable from the realme gt 2 pro box fixed it weirdly!
Ok so I now have a brick as it flashed global and tried to lock bootloader. Guess there is no way to fix? EDL mode?
wildlime said:
Ok so I now have a brick as it flashed global and tried to lock bootloader. Guess there is no way to fix? EDL mode?
Click to expand...
Click to collapse
Don't feel bad I made the same mistake. EDL mode is all you can do. In my case I had a person do it for me (unbrick device). Cost me 15 dollars.
robert3892 said:
Don't feel bad I made the same mistake. EDL mode is all you can do. In my case I had a person do it for me (unbrick device). Cost me 15 dollars.
Click to expand...
Click to collapse
What service did you use?
I used the person in post number 8 here:
MSM Downloaf Tool for realme GT 2 Pro
Does anyone know how to access this tool? This is ridiculous, realme has no useful tool to flash their phones and the one that is useful are impossible to access... The only one that I have access was one patched for some especific Oppo phone...
forum.xda-developers.com
wildlime said:
What service did you use?
Click to expand...
Click to collapse
PM me, I'll give you the cheapest one
thank you , any body help me reup to google drive or other
empty.cad said:
thank you , any body help me reup to google drive or other
Click to expand...
Click to collapse
Up, I need it too. @myogui can you reup to GDrive?
Use Mega , 50 GB for free
Can I use this to re-flash my global device? There are some bugs with my phone and a factory reset doesn't seem to fix it.