yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
If you went through the guides I sent, you should have all your answers there.

1. The key used by DM-Verity is signed and kept in the vbmeta partition (from Android 8 onwards). Therefore you have to flash a vbmeta that has been signed or an empty vbmeta (that holds no key to do a check) to disable DM-VERITY.

2. vbmeta disables DM-verity and not Forceencryption. The disabler zips disable Forceencryption (and some disable DM-VERITY too). For zips that disable both Forceencryption and DM-Verity, you can use just it and not use the signed/empty vbmeta.

3. Your phone is protected out of the box for your own safety. If you want to take total control over it, you must alert the system by unlocking it (unlocking the bootloader). If you want to give back all the control to your phone, relock bootloader. Note that unlocking/locking bootloader wipes all your data so do backups first.

4. Bootloader is the first step and must be done, if not, the phone won't boot. After bootloader then comes turning off security barriers (DM-Verity, Forceencryption).

5. Though the steps might vary, they usually follow this manner:

• Unlock bootloader. Turn on the toggle in Developer options and then use fastboot to complete the unlocking

• Flash vbmeta to disable DM-VERITY

• Flash TWRP. Though Forceencryption has not been removed yet, TWRP will boot. Now format data in TWRP to temporarily make the phone decrypted. With a temporarily decrypted state, you can access your internal storage to select Forceencryption disabler zip. Flashing the zip makes decryption Permanent.

• You can now reboot or continue flashing other stuff like other recovery, GSI, custom ROM, magisk, etc. Most of them can be done from TWRP itself (the reason you need TWRP in the first place)

• Rooting is optional. You can decide not to root even if you have TWRP, custom ROM, etc. Some apps need superuser privileges to work and you can only use them in a rooted phone (the reason people root their phone). These apps are mostly those that modify the OS. Flashing magisk roots your phone.

Any doubts again?
[Android Q&A, Help & Troubleshooting] TechySkills:
Um, No, Thank you very very very much, You literally fixed all my confusions, I actually bricked my phone and had to go to support office previous month, and pay 2$ (500PKR) to fix it. That is why, I was asking and clearing my confusions. Thank you, Now I am very confident, That, I can now flash my device. Thank you! 💖
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
Good to hear

{Mod edit: Quotation fixed - Oswald Boelcke, Moderator}
[Android Q&A, Help & Troubleshooting] kjisoo:
So, I want to install twrp to install a custom rom, but you said if I want to change from miui to a custom rom, it needs a file called "vbmeta" but after I did a search, the vbmeta file is only needed if the device is running Android 8 and above, whereas my device is on Android 7 | MIUI 10 | Santoni, and it says it only needs DM-verity? What should I do to be able to install a custom ROM?
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
vbmeta was introduced starting Android 8, so no need looking for a vbmeta if you are on Android 7. Starting Android 7, dm-verity had to be strictly enforcing (optional). If this is your case, then you can disable it in Android 7 by using flasher zips. Everything is in this guide.

What Is Verified Boot (DM-Verity) In Android And How To Disable It

Last Updated: February/21/2023 Contents Getting Started What Actually Is Verified Boot And Dm-Verity In Android How Verified Boot And DM-Verity Work In Older Devices (Android 7 And Below) How Verif…

sakophone.wordpress.com
[Android Q&A, Help & Troubleshooting] Slawek_:
@Kenora_I hi, maybe you know. I have Redmi 9 with soft upgraded to android 12.1 and i wanted boot temporary to SHRP. I tried fasboot flash recovery shrp.img and fasboot reboot recovery after but my device did not boot to recovery but started normally into system. May it be problem with vbmeta? My device ia A partition only.
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
PART 1:

Maybe your device lacks recovery partition (common with new and AB slot devices). If this is so, "fastboot flash recovery shrp.img" won't work because there's no recovery partition (recovery now sits in boot partition as boot-ramdisk).

Such devices need two recovery files: img and zip. If you have the two, the ZIP should be in your phone and the img in your PC then first boot the SHRP:

fastboot boot shrp.img

When recovery boots up, locate and flash the ZIP then from SHRP, reboot recovery and enjoy.

NB: I am assuming the name of your img file is shrp.img which might differ.

PART 2:

However, if you are sure your device is A-only, then here you go (make sure the shrp.img is the one for your device and you have the universal vbmeta disable):

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot flash recovery shrp.img

## For AB devices with recovery partition, you can specify slot

fastboot flash recovery_a shrp.img

fastboot flash recovery_b shrp.img

Fastboot reboot

NB: You can choose to boot shrp (instead of permanently install) if you want to use it just now:

fastboot boot shrp.img
[Android Q&A, Help & Troubleshooting] Slawek_:
Hi @Sakodie King TI ,

I tried fastboot boot command but im getting "too many links error."

Treble check saying my phone is A partition only.

I also checked

fastboot flash recovery shrp.img

then rebooting manualy by volume up + pwr but then im getting bootloop while holding these keys.

That is why i asked is this can be caused by vbmeta.
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
Did you flash vbmeta first?

And try "fastboot reboot recovery" after flashing instead of using volume keys
[Android Q&A, Help & Troubleshooting] Slawek_:
I did not flash vbmeta at all. I'm afraid i will brick device.

Shouldn't shrp boot temporary without flashing vbmeta?
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
You have to flash vbmeta first. instead, doing it without flashing vbmeta means you are looking for ways to brick your device.
[Android Q&A, Help & Troubleshooting] Slawek_:
Hey @Sakodie King TI

So i did this:

View attachment 5862953

After reboot recovery i got rebooted to system not recovery.

Also when i'm rebooting to recovery manually, i'm still on old muiu recovery nothing changed.

I took vbmeta from my firmware lancelot_eea_global_images_V13.0.3.0.SJCEUXM_20230111.0000.00_12.0_eea.

In that firmware there are also vbmeta_system.img and vbmeta_vendor.img maybe need to flash them also with --disable-verity --disable-verification parameters?
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
Try this vbmeta https://t.me/skti_group/587

Please take note, after downloading the file, rename it to vbmeta.img
[Android Q&A, Help & Troubleshooting] Slawek_:
Well situation is the same with your file.

I guess my phone after flashing to A12.1 stuck with this stock recovery.
[Android Q&A, Help & Troubleshooting] Slawek_:
OK. I tried different TWRP from here:

https://xdaforums.com/t/twrp-recovery-lancelot-android-11-12.4531485/

And it worked. It seems that SHRP is not working with A12.1 even if its dedicated to my phone.

Above TWRP is messy and imei backup not working but at least its somethink to begin with.
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
Glad to hear that. You ever used the shrp before?

Sometimes we keep thinking things don't work on our phones whereas it is problems with files.
[Android Q&A, Help & Troubleshooting] Slawek_:
Nope I have never tried shrp on my phone before. However i downloaded it from official shrp page and it was dedicated for my phone version.

Last update for this shrp was long time ago, and new MIUI 13 is quite new that is the problem i think.
[Android Q&A, Help & Troubleshooting] Slawek_:
OK. A little update.

I rolled back to MIUI 12 global_images_V12.5.5.0.RJCEUXM and android 11 and now SHRP working like a charm.

So problem was software version.
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
OH!! So what you actually needed was an updated version of SHRP
[Android Q&A, Help & Troubleshooting] Slawek_:
Nope. I needed lower version of MIUI and Android.

For my phone SHRP not working on A12, the same like many others TWRPs.
[Android Q&A, Help & Troubleshooting] Sakodie King TI:
Same thing I am saying that to use SHRP on higher version (12) you needed an updated SHRP.
[Android Q&A, Help & Troubleshooting] jeff862:
If stock rom unavailable on line like xiaoxin pad pro 12.7 2023 ..can i extract vbmeta.img from device?how? Thanks
[Android Q&A, Help & Troubleshooting] TechySkills:
Yes you can, But as its snapdragon, And I am an expert in Mediatek, I cant help you dear, Also the device is relatively new, Please let an year pass by then do any modifications, Otherwise NO ONE would be responsible for the thermonuclear war on your phone.
[Android Q&A, Help & Troubleshooting] jeff862:
How can u extract vbmeta from a device? Please help I need vbmeta.img for my device zui 15 stock rom nof available online... i need to flash gsi rom andrpid 14 vbmeta .img is required for flashing new gsi rom
[Touch Diamond, MDA Compact IV General] maxehret:
Hello, everyone! I just put a horrible scratch into the screen of my mda compact iv. i found out, that the spare parts are similar as for the htc victor, the diamond's brother.

I'm looking for something like this (possibly from Germany?)

can i replace it´on my own? is there a guide for disassembly? found nothing suitable using the search function...

Thanks in advance, everyone,

Max

(Please Help - Victor P3702 Screen - Sorry, didn'zt know how to rename thread)
[Touch Diamond, MDA Compact IV General] gerardo66:
look this

hi my suggestios is this

www.cnn.cn

i already bought parts from them no problem:)

ciao
[Introductions] robert.y9191:
Hello everyone just joined
[Introductions] Kenora_I:
Welcome to XDA! Enjoy your stay here.

Take your time to read the rules and have a good day! :)
[Introductions] robert.y9191:
Thank you
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Qwertyuiop@2004:
View attachment 5364897

ArrowOS

ABOUT

ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.

Website: https://arrowos.net

Github: https://github.com/ArrowOS

Code Review: review.arrowos.net

E-mail: arrowos.contact

WHAT WORKS?

Everything

Including Cast,Video Over LTE(Vilte) etc

WHAT DOESN'T WORK?

You tell ME XD

DOWNLOADS

ROM: ArrowOS

Gapps: NikGapps

Note : Nik Gapps are recommended for Vanilla build.

INSTALLATION INSTRUCTIONS

Vanilla build:

1) Backup Everything (Most Important);

2) Download ROM, Gapps, Magisk;

3) Reboot to Recovery (Orange Fox Recovery is recommended);

4) Wipe System, Data, Cache, Dalvik Cache,Vendor;

5) Flash - ROM, Gapps, Magisk;

6) Once done, wipe the cache;

7) Reboot to System.

SCREENSHOTS

Screenshots are Here

SOURCES

ROM Source: https://github.com/ArrowOS

Device Source: VINCE

Kernel source: Kernel Sources

Information

Device: Vince

Build Type: Unofficial

ROM OS Version: Android 11.0

ROM Kernel: Linux 4.9.273 (Dark Ages)

ROM Firmware Required: Latest Firmware

Based On: AOSP

Version Information

Status: Stable

Current Stable Version: 11.0

SELinux Status: Enforcing

Latest Release Date: 2021-07-17

NOTE:

• This ROM is For Peeps Who Care Mostly About Performance and Battery. (Don't Expect 69+ Customisations), that said, It Has The Necessary Ones.

• So Expect Buttery Smooth Experience and Awesome AF Battery XD.
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Qwertyuiop@2004:
Reserved
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Assassins23:
flashed it yesterday.. no bugs whatsoever yet. i do feel that speaker volume is low here at maximum as compared to pixel extended.. plz do look into it @Qwertyuiop@2004 . other than that ROM is good smooth and as the description says its for people who prefer performance and good battery. :)
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Assassins23:
I can't get some apps on playstore reason is that this ROM is not play protect certified something that playstore uses.. never encountered this before in HavocOs, RR and pixelExtended.. why this ROM isn't play protect certified?
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] dravampire:
Thanks for your work ,I have tried it,but the Google play services keeps crashing even if I cleaned the app data and reboot update
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Qwertyuiop@2004:
It's gonna be in the next update. Sorry for the inconvenience.
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Qwertyuiop@2004:
It's probably a problem with you gapps. Please flash the latest nik gapps.

Also, just flash Rom and gapps.

After rebooting and booting, then flash magisk and other add-ons.
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Assassins23:
😊 Thanks
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] KillMonday:
Riru gives an arror ROMs have incorrect SELinux, how can I solve this?
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Tournibrox:
Thank you for this ROM, I use it for a few weeks and I think I'll adopt it. The ROM is very smooth and battery life is impressive, more than 4 days with my use !

I don't understand why this is not an official ROM, this is the only minor problem which leads to no push updates I think (but it was the same with my precedent unofficial LineageOS Rom).

Please note that last update is from the 12th october and can be found on the official website.
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] drakulaboy:
*edit
[Motorola One Action Themes, Apps, and Mods] Bakarios:
google camera with an ultra-wide functional in motorola one action.

Additional setup: in Mod Settings

put the smartphone as Samsung and restart the app

Link: https://1drv.ms/u/s!AqyQW1E-n_TSj8cEiQyR89i_ZEmQEw
[Xiaomi Mi 11 Lite 4G] aralacikalin:
Hi all,

I have a couple questions.

is it normal that other apps use so much battery? in 24 hours it drains around 650 mah, and in 2 hours it drains around 60 mah or so. I attached screenshots showing this (sorry for bad quality and long screenshot)

and sometimes after charging my phone and unplugging it battery percentage doesn't go down for couple of hours. for example with 20 min of screen on time and 2 hours of idle it should go down about 5 percent or so but it doesn't even go down 1 percent.

Using miui 12.5.1
[Xiaomi Mi 11 Lite 4G] FortMike:
i don't think it's normal at all, I too have noticed excessive battery drain by "other apps" both with the official rom and with xiaomi.eu ROM. I really would like to know what these "other apps" are so that i can disable them because the battery drain is really high on 11 lite.

It's a pity, i like xiaomi.eu ROM but because of the battery drain I decided to change the ROM and now I'm on Xperience ROM who doesn't have this problem but some important features are missing like DT2S and fast charging.

Guys, if anyone has solution for battery drain please share it whis us .

Regarding your problem with the percentage not going down, sorry i can't help you but i never ran into this problem.
[Xiaomi Mi 11 Lite 4G] aralacikalin:
Completely agree with that. Just because of that I started to uninstall apps that I use less in order to see if "other" battery usage will decrease.
[Xiaomi Mi 11 Lite 4G] pratak:
Same problem here, but I don't have any clue which app causes this behaviour. Someone still on 12.0 with the same issue or is ist 12.5?
[Xiaomi Mi 11 Lite 4G] aralacikalin:
after deleting some apps (or after a while) this problem got better. now I have 250 mah in 24 hours on other apps. But now for some reason google play services started to drain much power when not connected to the wifi (or i just realized this now). It drains 1% battery in 1-2 hours when wifi is off but its normal when connected to the wifi. This is an interesting problem as well. any of you encountered it?
[General Topics] ckthunda:
Asking for $400.00 or best offer for mint condition tilt with extras.. Included is Usb Cable, charger and usb headset. ( took me forever to find) Seidio Rubberized Case in black. Authentic Htc Pouch and additional swissgear wallet case. A 2gb Micro sd Card with adaptor.. Phone has custom rom and is in mint condition. Ive made the switch to the iphone sorry guys..

Email me at lynchro@gmail.com for photos or questions.
[General Topics] Black93300ZX:
Disclaimer: I meant this only as a joke, mods, don't hate me. :)
[General Topics] Black93300ZX:
With that avatar picture, I wouldn't be surprised... Creep :-P
[General Topics] ckthunda:
Thanks... Mods.. not selling junk but I know people mess up their phones all the time so i thought i would offer it within the community then sell it to somebody who does not know what they're doing.

Thanks for the hijack... and i'm no newbie been here just as long as some mods..
[OnePlus Nord Questions & Answers] Spinningtop22:
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
[OnePlus Nord Questions & Answers] Kenora_I:
Reflash the rom but erase everything then flash.
[OnePlus Nord Questions & Answers] arturomb:
You needs msmtool to restore the phone to a stock image. Search in xda and follow the steps, its easy
[General Questions and Answers] PokeRekoP:
UPDATE: Changed the Topic as we are getting away from the original question in post 1 to the actual problem: figuring out how to fully root an Onyx Boox Poke3 e-reader running Android 10. "Fully" meaning including full r/w access to /system and /vendor - which isn't straight forward at the moment with "only" magisk-patching the stock boot.img

----------------------

Hi all,

possibly (probably) a "2^32 FAQ" but I can't g**gle it - everything search more or less leads to "how to patch boot img with magisk and flash it (in fastboot or twrp)".

So: Is there a tool (either on android or linux) to apply zips just like in twrp to a "boot.img" or "system.img" file, one after the other?

Why? I have a device for which there's no twrp (yet.... might look into that some day).

I have magisk-rooted it by patching the stock boot.img and then flashing that via fastboot. Rooted yes, Magisk yes, but still a "user-build" / "dm-verity" protected system, so tweaks modifying anything on /system or /vendor permanently aren't successful.

I guess there's a dozen solutions, but I just can't g**gle any (my g**gle foo isn't good enough...)

Anyone?
[General Questions and Answers] Kenora_I:
Disable dm-verity with adb.

You can modify build.prop and change ro.secure to 0 to get adb root.

Then disable dm-verity after that
[General Questions and Answers] PokeRekoP:
I don't get to disable dm-verity, even with adb root (which I installed as a magisk module). Its a "user" build. Or - despite hours of reading and trying - I didn't find the right way to do it (or didn't understand). Or would it be as simple as using Android Image Kitchen to unpack (the patched boot.img), tweak build.prop, repack, re-flash? Now that I think of it...!?

But there's another odd thing here. Magisk App says I don't have a ramdisk. As I don't have the stock "recovery image" (and because I didn't really pay attention to this but followed in the steps of someone with a similar device) I patched the stock boot.img - where really I should have patched recovery.img. However, device behaves fine with the patched boot.img. If I then dd the /recovery partition, I do find ".magisk" stuff in the "ramdisk" folder. Also, in the initial magisk patching log when patching the boot.img, it says:

....
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk32.xz] (0644)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
....

SO, even though the device seems to have no ramdisk in stock boot.img (?) magisk patched it, and the device still runs from it....

Also, could I force magisk to set keepverity=false? In the app, there's no related tickbox available.

Will make all this into a proper howto in the end... a mess at the moment :)
[General Questions and Answers] Deleted member 1890170:
If phone's bootloader is unlocked then you can disable AVB by means of Fastboot:

adb devices
adb reboot fastboot
fastboot reboot fastboot 2>nul
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot reboot
[General Questions and Answers] PokeRekoP:
@jwoegerbauer and @Kenora_I thanks for your responses.

Not sure if I'm on the right track here. I did a "dd" (from within the magisk rooted system via adb, dumping /dev/block/mmcblk0p46) to get the current (stock) vbmeta partition as a vbmeta.img to see what's in there "in stock state". avbtool.py says it doesn't look like vbmeta stuff, and I think it is right after looking at it with a hex editor: it's all zeroes. So, the information to protect /system and /vendor apparently does not come from vbmeta.

I had a look at the stock fimware update zip, unpacked it with superR's kitchen. In /vendor I have build.prop, but that does NOT contain "secure" at all. There is also a file default.prop, but can't see anything related to dm-verity in there, either.

#
# ADDITIONAL VENDOR DEFAULT PROPERTIES
#
ro.vndk.version=29
ro.adb.secure=1
ro.oem_unlock_supported=1
ro.zygote=zygote64_32
ro.logd.size.stats=64K
log.tag.stats_log=I
ro.logdumpd.enabled=0
ro.bionic.arch=arm64
ro.bionic.cpu_variant=generic
ro.bionic.2nd_arch=arm
ro.bionic.2nd_cpu_variant=cortex-a73
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a73
dalvik.vm.isa.arm.features=default

And then there is /vendor/etc/fstab - but it doesn't even list anything that would mount /vendor, only some sub-dirs mounted below that. It only contains "ro" for "/" - should I simply replace that with "rw", re-pack that stock vendor.img and flash it maybe!? With all that AVB/dm-verity stuff around it seems to simple - or not!?

Spoiler content hidden.

Edit: device tree might be the keyword:

From: https://android.stackexchange.com/q...ty-on-android-with-user-build-type-rom/215907

Edit2:

/proc/device-tree/firmware/android/fstab/vendor/fsmgr_flags lists "wait,verify"

/proc/device-tree/firmware/android/fstab/vendor/mnt_flags lists "ro,barrier=1,discard"

SO... seems I have to patch the dtb. Tomorrow maybe...
[General Questions and Answers] Kenora_I:
ro.adb.secure=1

This should be 0 if you want adb root command to function properly.

It shouldnt say adbd cannot run in production builds anymore.
[General Questions and Answers] Kenora_I:
Replacing it with rw, yes would make it read-writeable
[General Questions and Answers] Deleted member 1890170:
According to the changed thread's tite:

Rooting Android means nothing else then adding a matching SU-binary ( AKA root ) to it.

Since Android 6 every Android release comes with ( non-root ) Toybox. What you have to do is to replace this restricted version by a full ( root ) version like Toybox v0.8.5. You can achieve this by temporarily rooting Android, for example by means of copying rooted Busybox to /tmp.