Hey guys is there any way to keep vbmeta verity/verification disabled permanently or do I have to redo it every month update?? Thanks
thatsupnow said:
Hey guys is there any way to keep vbmeta verity/verification disabled permanently or do I have to redo it every month update?? Thanks
Click to expand...
Click to collapse
Why are you disabling them?
There is no way to keep them permanently disabled, as they're disabled by using the --disable flags while flashing the partition, so flashing the partition without the flags means they're enabled.
V0latyle said:
Why are you disabling them?
There is no way to keep them permanently disabled, as they're disabled by using the --disable flags while flashing the partition, so flashing the partition without the flags means they're enabled.
Click to expand...
Click to collapse
I'd like to flash different kernels without having to wipe my phone every month for no reason. On my pixel 5 I don't remember having to do a wipe just because I wanted a different kernel
thatsupnow said:
I'd like to flash different kernels without having to wipe my phone every month for no reason. On my pixel 5 I don't remember having to do a wipe just because I wanted a different kernel
Click to expand...
Click to collapse
It depends on the kernel. If it's just the boot image and you're using the stock vbmeta image, then yes you have to disable dm-verity and vbmeta verification. However many kernel developers provide a matching vbmeta image which you'd flash, and IIRC doesn't require disabling verity/verification.
V0latyle said:
It depends on the kernel. If it's just the boot image and you're using the stock vbmeta image, then yes you have to disable dm-verity and vbmeta verification. However many kernel developers provide a matching vbmeta image which you'd flash, and IIRC doesn't require disabling verity/verification.
Click to expand...
Click to collapse
On the Pixel 7 series, you need to disable verity and verification to flash any custom kernel. No one has found a way around this so far.
Lughnasadh said:
On the Pixel 7 series, you need to disable verity and verification to flash any custom kernel. No one has found a way around this so far.
Click to expand...
Click to collapse
Thanks for clearing that up. Just when you think you've got everything figured out, they go and change something.
I'm too old for this crap.
Lughnasadh said:
On the Pixel 7 series, you need to disable verity and verification to flash any custom kernel. No one has found a way around this so far.
Click to expand...
Click to collapse
Thanks guys
thatsupnow said:
I'd like to flash different kernels without having to wipe my phone every month for no reason. On my pixel 5 I don't remember having to do a wipe just because I wanted a different kernel
Click to expand...
Click to collapse
You have to wipe only the first time that you disabling verity/verification...
Then just on every update
fastboot --disable-verity --disable-verification update
cultofluna said:
You have to wipe only the first time that you disabling verity/verification...
Then just on every update
fastboot --disable-verity --disable-verification update
Click to expand...
Click to collapse
But don't I have to wipe every update??
thatsupnow said:
But don't I have to wipe every update??
Click to expand...
Click to collapse
No, as long as you don't boot with the stock vbmeta image. That's why when you do monthly updates you disable verity and verification during the update process (and before you boot) so you don't boot with the stock vbmeta image. Once you boot with the stock vbmeta image you'll have to wipe if you want to disable verity and verification again.
Lughnasadh said:
No, as long as you don't boot with the stock vbmeta image. That's why when you do monthly updates you disable verity and verification during the update process (and before you boot) so you don't boot with the stock vbmeta image. Once you boot with the stock vbmeta image you'll have to wipe if you want to disable verity and verification again.
Click to expand...
Click to collapse
Ahhh I see I see. So when I side load the ota I can then just reboot into fastboot then flash vbmeta to disable it then reboot system??
thatsupnow said:
Ahhh I see I see. So when I side load the ota I can then just reboot into fastboot then flash vbmeta to disable it then reboot system??
Click to expand...
Click to collapse
Yes. You can also update with Pixel Flasher which has an option to disable verity and verification.
Lughnasadh said:
Yes. You can also update with Pixel Flasher which has an option to disable verity and verification.
Click to expand...
Click to collapse
Thank you sir for clearing the air on that
Related
since both available TWRP images don't work on september patch, I tried to decrypt data using magisk and fastboot, I installed magisk with avb and force encryption turned off then I used fastboot format userdata, but it still says it's encrypted, is there any way to decrypt it?
hi I have found a site where that give you a zip. file for disable data encryption "https://www.thec u stom droid.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/" eliminate any space
Sermog02 said:
hi I have found a site where that give you a zip. file for disable data encryption "https://www.thec u stom droid.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/" eliminate any space
Click to expand...
Click to collapse
Yeah, I found it it later on zackptg5.com
Nebrassy said:
Yeah, I found it it later on zackptg5.com
Click to expand...
Click to collapse
Ok, if you have already done can you explain how to use it ? please
Sermog02 said:
Ok, if you have already done can you explain how to use it ? please
Click to expand...
Click to collapse
Go on fastboot,
Fastboot -w
This will wipe everything on the phone, boot twrp, flash the zip then flash magisk
You will no longer be able to receive OTAs
Trying to sideload the December OTA. Rooted with Magisk. Boot into bootloader, select recovery, then I get the google logo (not the red exclamation mark, the Google logo) , but won't enter recovery, just hangs on the logo. Do I need to disable or uninstall Magisk?
Gloff said:
Trying to sideload the December OTA. Rooted with Magisk. Boot into bootloader, select recovery, then I get the google logo (not the red exclamation mark, the Google logo) , but won't enter recovery, just hangs on the logo. Do I need to disable or uninstall Magisk?
Click to expand...
Click to collapse
You need to uninstall magisk and then enable the stock boot.img which is where the recovery resides.
Badger50 said:
You need to uninstall magisk and then enable the stock boot.img which is where the recovery resides.
Click to expand...
Click to collapse
That's new, didn't have to do that with the 3 XL. Do I use the stock boot.img from the currently installed update (december)? Also, how to I flash the stock boot.img, through fastboot?
Gloff said:
That's new, didn't have to do that with the 3 XL. Do I use the stock boot.img from the currently installed update (december)? Also, how to I flash the stock boot.img, through fastboot?
Click to expand...
Click to collapse
Although I never do OTA's, I prefer fastbooting updates, most everything I've read is to uninstall magisk, then restore the stock boot.img which magisk will do for you. So it's either that is causing his problem, or he has an issue with his stock recovery.
Badger50 said:
Although I never do OTA's, I prefer fastbooting updates, most everything I've read is to uninstall magisk, then restore the stock boot.img which magisk will do for you. So it's either that is causing his problem, or he has an issue with his stock recovery.
Click to expand...
Click to collapse
You're talking to the OP. I couldn't update Magisk with the last update, it said installation failed. Should I just flash the stock boot.img?
Gloff said:
You're talking to the OP. I couldn't update Magisk with the last update, it said installation failed. Should I just flash the stock boot.img?
Click to expand...
Click to collapse
Yes
p70shooter said:
Yes
Click to expand...
Click to collapse
I assume the boot.img from December Update, yes?
Gloff said:
I assume the boot.img from December Update, yes?
Click to expand...
Click to collapse
Yes. fastboot flash boot boot.img :good:
Gloff said:
I assume the boot.img from December Update, yes?
Click to expand...
Click to collapse
Yea if you're flashing that one. I would just flash the whole December image using flash all, saves messing around with Ota then but that's me
p70shooter said:
Yea if you're flashing that one. I would just flash the whole December image using flash all, saves messing around with Ota then but that's me
Click to expand...
Click to collapse
I was always worried about wiping my devices, that's why I usually sideload the OTA rather than removing the -w flag.
Gloff said:
I was always worried about wiping my devices, that's why I usually sideload the OTA rather than removing the -w flag.
Click to expand...
Click to collapse
Ah that makes sense, I always double or triple check that I've removed the -w but I have forgotten before lol
p70shooter said:
Ah that makes sense, I always double or triple check that I've removed the -w but I have forgotten before lol
Click to expand...
Click to collapse
Hahahahahaha....I think I remember a couple of those! ?
The Guide should be updated for flashing both slots, I've never been able to get fastboot flash boot --slot all boot.img to work, so I've always flashed both slots individually using
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Is there a new command for flashing both slots simultaneously?
So when updating, do you guys just flash the entire updated factory image when a new update is released? No need to uninstall Magisk, so you don't have to flash the previous update's boot.img?
In other words do you flash new full factory image>patch boot.img>flash magisk_patched> done VS.
Flash old stock boot.img>OTA/Factory image>patch boot.img>flash magisk_patched>done?
This has never been clear to me as far as new updates go. I feel like the guide should have an "I'm rooted and just want to update to the latest security patch" section.
Gloff said:
The Guide should be updated for flashing both slots, I've never been able to get fastboot flash boot --slot all boot.img to work, so I've always flashed both slots individually using
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Is there a new command for flashing both slots simultaneously?
Click to expand...
Click to collapse
Might try this one. Always seems to work for me :good:
fastboot flash boot boot.img --slot=all
Then substitute magisk_patched.img for boot.img when you want to flash the rooted version of the kernel to both slots :good:
Badger50 said:
Might try this one. Always seems to work for me :good:
fastboot flash boot boot.img --slot=all
Then substitute magisk_patched.img for boot.img when you want to flash the rooted version of the kernel to both slots :good:
Click to expand...
Click to collapse
Will try this command after I finish updating to January. Who wrote the guide? They have it as: fastboot flash boot --slot all magisk_patched.img.
They should update it if the order is backwards, since it's never worked for me using the guide's script.
Edit: fastboot flash boot boot.img --slot=all did not work either. I used the boot_a/boot_ b method and it worked fine.
Gloff said:
Will try this command after I finish updating to January. Who wrote the guide? They have it as: fastboot flash boot --slot all magisk_patched.img.
They should update it if the order is backwards, since it's never worked for me using the guide's script.
Click to expand...
Click to collapse
There are few guides, depends on which one your referring too. It's actually not backwards as either will work. Probably just a syntax error or typo :good:
Badger50 said:
There are few guides, depends on which one your referring too. It's actually not backwards as either will work. Probably just a syntax error or typo :good:
Click to expand...
Click to collapse
This Guide: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
I attached my command window log.
Gloff said:
This Guide: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
I attached my command window log.
Click to expand...
Click to collapse
Maybe try the = sign between slot and all
Looks like the one I gave you works though :good:
Badger50 said:
Maybe try the = sign between slot and all
Looks like the one I gave you works though :good:
Click to expand...
Click to collapse
Tried that, middle of the attachment results in fastboot: unknonw option --slot=all
Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
tatico28 said:
Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
Click to expand...
Click to collapse
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Homeboy76 said:
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Click to expand...
Click to collapse
No, I did not, is there a workaround?
tatico28 said:
No, I did not, is there a workaround?
Click to expand...
Click to collapse
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
tatico28 said:
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
Click to expand...
Click to collapse
Hi, what do you mean updating the tools module? tnks
davidvd102dvd said:
Hi, what do you mean updating the tools module? tnks
Click to expand...
Click to collapse
I think he's referring to SDK platform-tools.
Homeboy76 said:
I think he's referring to SDK platform-tools.
Click to expand...
Click to collapse
i though the same but tried without success
davidvd102dvd said:
i though the same but tried without success
Click to expand...
Click to collapse
Ok, then this must be what he is talking about: https://pixelrepair.withgoogle.com/carrier_selection
Yes the SDK Platform- tools, also I had to fastboot flash the boot.img to both a,b slots.
Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
alwynjoshy said:
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
Click to expand...
Click to collapse
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Homeboy76 said:
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Click to expand...
Click to collapse
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
alwynjoshy said:
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
Click to expand...
Click to collapse
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Badger50 said:
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Click to expand...
Click to collapse
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
tatico28 said:
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
Click to expand...
Click to collapse
I tried the way you said but same result. The only thing i didn't do is i flashed only slot A only. But my active slot is A so i think that is not the issue
alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Badger50 said:
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Click to expand...
Click to collapse
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
alwynjoshy said:
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
Click to expand...
Click to collapse
It's a matter of choice really. Many, like myself, like to fastboot the factory images every month to update. Others like the OTA. Functionality is pretty much the same as far as I've seen. However, you can't fastboot an OTA, likewise you can't side load a factory image, and of course, you have to be bootloader unlocked to fastboot the factory images, so keep that in mind as well. I also like using fastboot because you can switch slots to sometimes get rid of errors that occasionally pop up. Good luck with finding your solution whichever way you choose to go. :good:
I think I can be banned for getting fake unlimited google photos storage but im not sure
XDAC1234 said:
I think I can be banned for getting fake unlimited google photos storage but im not sure
Click to expand...
Click to collapse
No it will not be banned
thanks, I already flashed and unflashed pixel experience tho lol, it was kinda laggy
Manjotbenipal said:
No it will not be banned
Click to expand...
Click to collapse
Manjotbenipal said:
No it will not be banned
Click to expand...
Click to collapse
btw do u know if i should install magisk the zip flash way or the patched boot.img way?
I always roo with fastboot method
But remember that you must disable avb before flashing the patched img.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
If you skip disableing avb then you are sure to be stuck in a bootloop coz I have faced it myself.
And if you flash the recovery first then again i recommend you to follow the same step of disabling avb before flashing recovery.img
AND YOU CAN FOLLOW GUIDE IN THIS DEVICE'S FORUM
Btw which miui version are you using?
XDAC1234 said:
thanks, I already flashed and unflashed pixel experience tho lol, it was kinda laggy
Click to expand...
Click to collapse
You can uninstall bloatware with adb once you root your mobile and then install an mtz theme.
You will not even feel like you are using miui after doing that.
Btw should I make a thread on uninstalling bloatware with adb?
Manjotbenipal said:
I always roo with fastboot method
But remember that you must disable avb before flashing the patched img.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
If you skip disableing avb then you are sure to be stuck in a bootloop coz I have faced it myself.
And if you flash the recovery first then again i recommend you to follow the same step of disabling avb before flashing recovery.img
AND YOU CAN FOLLOW GUIDE IN THIS DEVICE'S FORUM
Btw which miui version are you using?
Click to expand...
Click to collapse
[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)
Preamble: After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85). The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG)...
forum.xda-developers.com
You can skip erasing userdata and cache coz it will reset your mobile.
But if you don't want to take any risk and decide to reset then REMEMBER THE PASSWORD OF YOUR MI ACCOUNT
after reset your phone will be locked until you verify your mi account.
Make sure to backup all the data on your phone before flashing
Manjotbenipal said:
You can uninstall bloatware with adb once you root your mobile and then install an mtz theme.
You will not even feel like you are using miui after doing that.
Btw should I make a thread on uninstalling bloatware with adb?
Click to expand...
Click to collapse
If you want to, that thread would be gladly appreciated, I couldnt get debloat (the magisk module) to work in the terminal emulator
Manjotbenipal said:
I always roo with fastboot method
But remember that you must disable avb before flashing the patched img.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
If you skip disableing avb then you are sure to be stuck in a bootloop coz I have faced it myself.
And if you flash the recovery first then again i recommend you to follow the same step of disabling avb before flashing recovery.img
AND YOU CAN FOLLOW GUIDE IN THIS DEVICE'S FORUM
Btw which miui version are you using?
Click to expand...
Click to collapse
huh, I didnt flash vbmeta before and my phone was fine (I had it rooted before pixel experience)
btw im using miui 12.5.6.0 RJOEUXM
SymtaxError said:
huh, I didnt flash vbmeta before and my phone was fine (I had it rooted before pixel experience)
btw im using miui 12.5.6.0 RJOEUXM
Click to expand...
Click to collapse
Then you can try but be careful
Manjotbenipal said:
Then you can try but be careful
Click to expand...
Click to collapse
nah, better safe than sorry (that idiom makes no sense but whatever)
After i do fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img to disable dm-verify inorder to use dsu sideloader my phone goes to bootloop. Although i fix it by flashing stock firmware using miflashtool i still what to know what exactly cause this problem and should i try again
pizzaaaaa said:
Based on the command that you mentioned, you were trying to disable dm-verity on your device. This security feature ensures that the device hasn't been tampered with before booting, and disabling it can potentially cause issues, especially with verified boot.
It is possible that the bootloop occurred due to the disabling of dm-verity, and that flashing the stock firmware resolved the issue. It is difficult to say exactly what caused the problem without additional information about your device and its specific configuration.
If you do decide to try disabling dm-verity again, it is recommended that you proceed with caution and carefully follow instructions from trusted sources. However, please note that tampering with device security features can be risky and may also void the warranty for your device.
Click to expand...
Click to collapse
I want to use dsu sideloader to try out gsi but cannot boot up so i search online and find out i may need to disable dm-verification.I think i will wait after this phone global launch to do any flashing as it should have more user and support i think someone will figer it out. Thanks anyways.
keithsze001 said:
I want to use dsu sideloader to try out gsi but cannot boot up so i search online and find out i may need to disable dm-verification.I think i will wait after this phone global launch to do any flashing as it should have more user and support i think someone will figer it out. Thanks anyways.
Click to expand...
Click to collapse
You don't need to disable dm-verity or vbmeta verification to run a GSI. The only circumstance under which it may be necessary is if you're using a custom kernel. If you're using the stock kernel, reflash /boot and /vbmeta back to stock. If you want root, you can flash a patched boot image. The GSI image only installs to /system.
V0latyle said:
You don't need to disable dm-verity or vbmeta verification to run a GSI. The only circumstance under which it may be necessary is if you're using a custom kernel. If you're using the stock kernel, reflash /boot and /vbmeta back to stock. If you want root, you can flash a patched boot image. The GSI image only installs to /system.
Click to expand...
Click to collapse
thanks
V0latyle said:
You don't need to disable dm-verity or vbmeta verification to run a GSI. The only circumstance under which it may be necessary is if you're using a custom kernel. If you're using the stock kernel, reflash /boot and /vbmeta back to stock. If you want root, you can flash a patched boot image. The GSI image only installs to /system.
Click to expand...
Click to collapse
well now i try to use the stock dsu loader and my phone bootloop but this time it stuck on miui logo instead of just showing redmi.
i think i may uninstall something wrongly on universal android debloater.