Can Magisk Manager actually create a patched boot image without root? Didn't know that. Btw, thanks for doing all this work!Root is possible. The way I achieved it is first to follow the official bootloader unlock method given by Motorola. Then install Magisk Manager V 7.5.1 (latest as of today). After that have magisk patch the boot image and recovery image, and flash them both through fastboot. It will say the boot partition is signed but when you Flash it to the recovery partition it will tell you the image is either not signed or corrupt. Don't worry about this, it does not affect loading back into system or back into the bootloader or recovery. Remember, after this you will have to boot through recovery every time you reboot or you will not have root until you do. Unfortunately I am still trying to work on TWRP, and it is going rather slow as this is my first attempt at compiling a custom recovery and I am no developer, and am learning as I go... Hope I helped!!!
Sorry, I know this is a thread for moto e6 plus, but do you guys know what is the command to unlock Moto e6 play XT2029-3 bootloader, I tried fastboot flashing unlock_critical but it returns that its a unknown command, my phone got bricked after this last OTA update and its giving me red state warning and its stuck in bootloop, its a second hand phone so no warranty, if you guys could help me I would really appreciate it...
Al parecer también hablas español, el problema es que al reinstalar la rom oficial desde lmsa me dice que esta en desbloqueo ilegal, solamente pongo ese comando y se arregla ese problema? O debo hacer algo mas?
Is there any way to root / unlock bootloader / install TWRP in the European 64GB Dual-SIM version, XT2025-2?
I have the stock rom with August 2019 patches and tried using multiple ways described here to unlock it, but didn't get anywhere.
First I tried fastboot flashing unlock_critical, didn't work. Tried installing latin american version via the Recovery Tool, didn't work. Tried to install TWRP with same tool, nope either. Then I tried the mtk-su tool, got error 4 even thought it should in theory be compatible. Kinda losing hope. Anyone got any tips or ideas what I could try?
In my Country we only have the 64/4g model and plus its been rebranded as the Lenovo K10 [Not Note or Plus] It has the Same fastboot Screen and the same recovery and the same Motorola update services the only that has change is that it has a MTK-8000 series chip and the Splash screen is different is this a different model? And can i flash Root or TWRP on it?
I have been using AOSP 10 arm64 AB for months now, the phhusson one, it works amazing in my 4/64.
Today i tried to install AOSP 11, same arm, same developer. But it ended in bootloop.
I've tried everything, permissive, reinstall it after formatting data, anything worked.
Has anyone tried android 11 with this device? can anyone give me a stable GSI?
I had to flash it in a very specific way, because with sp flash tool you need to have the auth file and the specific Download agent to write to this phone and I looked everywhere how to flash this thing and I couldn't make it flash any file in any way.
But then I discovered that the official Lenovo tool uses SPFlashTool to flash mediatek devices, so I messed around with it for a while and found out how to flash files to this phone
What I did was download the Lenovo MOTO Smart Assistant for Windows, went into the flash tab, selected rescue; then selected MOTO device, i chose my specific device model (which is Moto E6 Plus XT2025-1 4G/64G) and clicked in the download button to download the latest firmware.
After it finishes downloading, you can go into the software's downloaded tab, and in the bottom there's an option to open the default download directory. In there are all the files for rescuing the smartphone (Full ROM, Lenovo's provided spflashtool (which i guess is the one Lenovo MOTO Smart Assistant uses to flash this phone), Some Download Agents for SPFlashtool, and among other things).
So, what i did at this point is I closed the tool, got into the Firmware's folder, grabbed the Boot.img and modified it with Magisk's android app (there is no root needed if you don't intend to flash the file to the actual device) and afterwards, replaced the old boot.img in the tool's download folder with the new one generated by Magisk (of course, after renaming it to boot.img) and opened the tool again and went into the same tab, selected again my device, clicked in the rescue button instead of the download one, and followed instructions on screen. It seemed like everything went fine, but when I started the phone, bootloader stated that the system integrity was changed (because I wrote to flash that new boot.img) that's when i realised that the dm-verity is not disabled in boot.img on Oreo -> + devices, but at least i knew that we could flash files to the device.
At that point I tried everything to disable DM verity and other verification: Using kitchens (In windows and in Linux) , using python scripts, Manually searching where to disable it, but i couldn't get any software to correctly disable it and /or to unpack any of the img files of the Firmware (system.img and some others unpacked but i didn't find anything there) so if anyone can help with this it would be very appreciated.
Yes! please upload the oficial ROM if you can. It will be always be very helpful have that files here in the forum.
I've been trying to make a full backup of this device, but I couldn't figure out how to do it properly. I've found a possible root solution here https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213/amp/ but I don't want to take any risks without backups.