Recent content by Senpy

Good question. I think I didn't modify the manifest completely and it uses the wrong name/doesn't show. Either that or the process doesn't complete.

I don't see why it wouldn't, but it's not necessary. If you remove/disable the injector, tricky store will function as expected. The dynamic nature was added shortly after I added the module. Of course, for old ROMs before Igor added the change, it'd still be needed to get strong.

You do know that no one here is from Xiaomi, so saying that doesn't mean anything and also, plenty of people say that on the official forums and they also don't care... The rom used here isn't typically Global HyperOS. The xiaomi.eu devs usually start with CN version and customize it from...

The only benefit of TWRP is updating the ROM. Rooting is done once per ROM update. ViperFX and other modules can be installed within your root manager. Not sure how TWRP is more convenient for this as you need to reboot into recovery, flash, and then reboot vs install and reboot. Took me less...

You don't need TWRP to get root. Just patch init_boot or boot like magisk/apatch/kernelsu want and flash it in fastboot

If the changes are the same, then yes. I haven't tested it on any devices besides my own.

even when there's an issue, the home launcher is fine. the only potential issue is some functionality issues like saving to internal storage, which you can check by trying to download a file or install an apk. if there's an issue, just uninstall or disable the module.

Shouldn't be that much different from normal. It's just a file mapping the original framework.jar with the modified version rather than found any computations. I still get all-day battery on my 14 ultra

That's probably due to some incompatibility from modifying the framework.jar. I had that happen when I manually attempted the mod. More details about the system + a copy of the original framework.jar would be helpful.

You can't dynamically unmodify something. Rather the devs are putting in a branch, so if inject is found, do one thing and if inject is not found, do something else. In this case, the do something else is the original action.

You'll still need PIF, tricky store, and a key box that can pass strong. This module just messes with the stuff xiaomi.eu devs put in to handle droidguard.

Decided to modify FrameworkPatcherGo to disable the droidguard check in framework.jar. I'm not an android dev, so YMMV. Should be safe, but do your own research and use at your own risk since I'm just a random person on the Internet. Module found here: https://pixeldrain.com/u/9GmWzNe2 Edit...

if you have a chinese version, you have to use a paid service to unlock the bootloader unless you meet the criteria that xiaomi has for unlocking chinese versions, but that's unlikely. it's not just xiaomi being more restrictive about bootloader unlocking and also threatening to not purchase...

Go to folder you extracted rom. Run: ``` fastboot erase misc fastboot flash boot_ab images/boot.img fastboot flash init_boot_ab images/init_boot.img fastboot reboot ``` These are the commands I usually use to fix boot issues.

It's not going to the rom, so changing that won't do anything. Phone on -> boot mode -> {rom, recovery, fastboot} Right now it's set to boot to recovery, so you need to unset that. Set active won't change anything since you most likely flash to both A and B slots. If erase didn't fix it...