[Moto G Power Questions & Answers] FakedKetchup:
libpng-12 is a dependency of the program, probably for the Welcome tab which is made out of pictures instead of a mark language elements...

In regards to the recovery partitions, i found out it is because on devices with A/B partitions, the recovery is merged into the boot.img file. Im not aware of any custom recoveries made for it.

Patching it for root is as straightforward as installing older version of Magisk App on any android phone, copying the stock boot.img anywhere on the device, then patching the file from the app and flashing using SP Tools.

I patched the boot.img from the stock rom. I also managed to successfully execute the bypass script. It used to throw out Missing Default Config error, but i found the default config on github (exploits-collection; attachments) and used that just fine - copy the contents of the archive into the root folder of the bypass utility:

View attachment 5892949

So, in order to unblock the protection, one needs to SOLDER the two pins, any other method was extremely unreliable. On Windows, install LIBUSB drivers from the attached file or from sorceforge. Do it in such a way that you run the installer and you'll get to this popup:

View attachment 5892951

then click next

View attachment 5892953

and youll see bunch of devices. Now plug in the phone with unplugged battery and shorted pins, then wait till a new device pops up, could be called MTK Device or anything like that. You select it and install the libusb library to it. Unplug the phone.

CD into the Bypass Utility folder via CMD/Terminal and run as root: python3 main.py, but install the requirements beforehand (sudo) pip install pyusb pyserial json5 ( running the program as root, the dependencies may not carry over so install them as root as well)

If you did everything right, you should see a prompt saying "Waiting for device"

Then you keep the 2 pins shorted and plug in the phone, if all goes right you should see this output:

View attachment 5892965

On linux, you need a custom patched kernel, either get the patch or get a prepatched kernel or live boot a FireOS iso.

from the README file:

As long as you keep the phone plugged in, the protection is off, however i found myself often needing to re-run the script before each action that utilizes the bootrom.

Using the mentioned scatter file throws out errors. I tried to first remove the protection and then immediately run the NVRAM readback but it failed

View attachment 5892981

Full guide https://xdaforums.com/t/guide-how-t...d-flash-in-edl-with-no-auth-for-free.4229683/

I tried to make my own scatter file by using MTK Droid Tools, but this utility only supports MTK65xx and below CPUs, so it isnt possible in our case. I also tried a generic MTK6765 scatter but that didn't work either. Without the scatter file, the tool doesn't kow where to write the boot.img and thus its a dead end. I'll try to do this on a different PC see if anything changes but i highly suspect its just a wrong scatter file. I got it from this allegedly stock rom.

What i stumbled across is this mirror site, where basically every ROM this device ever had is uploaded, so i think ill start there.

HUGE EDIT:

Accidentally i didnt load up the scatter file from the ROM directory but instead from a different location, tus it didnt load all the other necessary parts. It seems like you have to flash everything, not just one part like recovery or bootloader. Or maybe you can flash a single thing and that is what the square checkboxes are for lol

View attachment 5893083

Thus i can happily announce that i successfully flashed the boot.img, after which Root Checker wstill reported NON-ROOT. I installed MAGISK APP once again and it asked me to reboot to finalize, then it rebooted, i entered the Magisk app and rooted directly from the app. -and the phone is rooted !

Technically it could be possible to flash a custom ROM using this exact tool, although i can only imagine few of the hardware actually working without manually fixing ACPI etc.

It is certainly one of the most difficult root procedures, but nothing unusual in the world of reverse engineering