update your fastboot /adb, download latest version
update your fastboot /adb, download latest version
you are on fastbootd mode? from fastboot reboot fastboot and test if commands now works
corrupted Dm-verity
. This is an unusual situation...Redmi Note 10 5G EEA | Stable | Fastboot |
Hi.Hi, @FrranciscoM
I've noted, your phone is now rooted, so try another fastboot choose your os version... this is the latest r31.0.3 at this time. After that, try as mentioned at this heading thread, if your issue is not solved, backup all you personals data, images... and flash a new stock rom (official) and proceed again for rooting your device.
Your story is really strange, without any modification your device shows acorrupted Dm-verity
. This is an unusual situation...
Hope this help.
Edit1: To flash a rom, I don't use software like spflashtool or others (I can't get them to work properly), I do it using the bash script included in the large stock rom, in my case:
Be sure to choose fastboot version.
Redmi Note 10 5G EEA Stable Fastboot
After unpack, you will find the files: flash_all.sh, there is a flash_all.bat for you too. These allow you to completely overwrite your previous installation. This is my modest recommendation.
Edit2: for 3rd party apps and more backup , I recommand: Migrate - ROM data backup: 4.0 & his companion Migrate flasher since the marvelous Titanium Backup (root needed) does not work very well with android 11.
About
and look at the row version MIUI
, on mine i got:the important part is in red bold RKSEUXM (europe) for me. this is for the full flash solution.
corrupted Dm-verity
message, have you try the method from the 1st post with vbmeta.img given on first post?$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
boot.img
provided by a fastboot
stock rom.vbmeta
and maybe boot
imagesOfftopicEdit1: To flash a rom, I don't use software like spflashtool or others (I can't get them to work properly), I do it using the bash script included in the large stock rom, in my case:
boot.img
is delivered with its rom and must be used only with it. It contains a lot of redundant information that is present in the rest of the files that correspond to it, such as the brand, the model, the version of the rom and many others... If you use a boot.img
from another rom, even if it is the same model, you may encounter unwanted problems.vbmeta.img
and boot.img
'the version modified by the magisk root operation'). There are some Xda members (see posts on this thread) who provide the boot.img
file already patched corresponding to a specific version of the rom, you can certainly use one of them if you don't want to do it yourself but pay attention to the version and the region.Couldn't you just use MagiskHide to conceal it from your game? Works for me with two different banking apps.reason i want to unroot because my game detect magisk or it safe to uninstall magisk ?
yeah, i just figure out how to hide magisk after ask my questionyeaCouldn't you just use MagiskHide to conceal it from your game? Works for me with two different banking apps.
You probably need to hide the Magisk App so it shows up in the app drawer under a different name (e.g. Settings) - I can see from the third screenshot that this hasn't been done. Also, if the apps requested root access, did you reject them? Banking apps would usually refuse to run if they can obtain root.Hi all! Can someone help me please? I am unable to hide magisk from 2 banking apps . BT and BRD. They say that the system is compromised , rooted.
Did that now.. named it aaaaaa . Tried a reboot and the apps still say that I am rooted. The banking apps never requested toot access. Also tried to uninstall the banking apps, and reinstall them. (You probably need to hide the Magisk App so it shows up in the app drawer under a different name (e.g. Settings) - I can see from the third screenshot that this hasn't been done. Also, if the apps requested root access, did you reject them? Banking apps would usually refuse to run if they can obtain root.
You did add the apps to the Magisk Hide list again after reinstalling them? I think you would probably also only have to clear the app data rather than reinstalling in order to try again. There are suggestions for a different banking app in this thread although I didn't have to do any of those things myself.Did that now.. named it aaaaaa . Tried a reboot and the apps still say that I am rooted. The banking apps never requested toot access. Also tried to uninstall the banking apps, and reinstall them. (
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_a' OKAY [ 0.000s]
fastboot flash boot boot.img
fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.524s]
Writing 'boot_a' OKAY [ 0.224s]
fastboot reboot
This is know issue. You have "lite" version of adb/fastboot. The version with bigger files will support all parameters.with one exception, in point 8 I used this command:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta vbmeta.img
The correct flashing vbmeta.img should fix this problem.