Database Info

[GUIDE] [clark] How to root Pure/Style on Marshmallow or correct a bad root attempt

It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section to root, or "Do the prep" section to fix a bad root.
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting update UPDATE-SuperSU-v2.82-20170528234214.zip (version 2.82) is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
Do the prep:
Note that the hidden Do the prep section is ONLY for repairing a bad flash, SuperSU has been updated and as of version 2.79 the hidden section should no longer be needed for general purpose root on a working device, you just flash SuperSU. If you flashed an older version and are bootlooped, perform this section and continue.
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, when you have your backups and are ready to root, first go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press ENTER (there is no confirmation returned). You can verify this worked correctly by entering 'cat /data/.supersu' in the terminal and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again. Now press exit/back and press the HOME key.
After you have successfully entered the command in the TWRP Terminal you may continue
How to do it:
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
Again, this is somewhat dated information and only applies to fixing a bootlooping device when improperly rooted.
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
NOTE: I no longer own this device, but will help where I can and will keep this thread open to assist users where ever possible, but I no longer have a device to test/verify things with.

Alternate Method #1
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 98% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.

Reserved - FAQ (oops, guess I already did that)

I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true

Jorinde123 said:
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Click to expand...
Click to collapse
Find the latest rom image for the version you have installed, and flash the radios with fastboot.

acejavelin said:
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
Click to expand...
Click to collapse
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.

Jorinde123 said:
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Click to expand...
Click to collapse
Because you are not on 49-18, if you were on the latest OTA for 6.0 you were on 49-18-4. Pre-flash validation failure confirms your using the wrong version. Look in my sig for the return to stock thread, there are links to current roms and discussion of the 'preflash validation error'.

Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.

Got the Moto X Pure a few days ago. It came with 6.0. This procedure works. Thank you!

ban.codrut said:
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Click to expand...
Click to collapse
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not

Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated

SouthernEvo said:
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
Click to expand...
Click to collapse
It is not a known issue... Where are you storing the backup, internal storage or SD card?

acejavelin said:
It is not a known issue... Where are you storing the backup, internal storage or SD card?
Click to expand...
Click to collapse
Was backing up to the SD Card . Been messing with it and now its working for some weird reason . I appreciate your quick response though

I used windroid to unlock the bootloader and install twrp( don't reboot system but rather boot into recovery to make twrp stick) , from there I just flashed supersu and I was good to go. Many methods out there but this worked for me.

Thank you so much for this guide. I have to say, as a new Motorola user coming from Samsung phones exclusively, this whole process made me feel like a real noob again.
I made the switch from iOS to Android back when the Galaxy S2 came out because I grew tired of the jailbreak cat and mouse games on the iPhones and iPads. Learning to root and flash ROMs on all my subsequent Samsung devices was fairly simple and very enjoyable. This Moto X Pure though was a real tasker for me. I honestly never knew about the extra steps you had to take to unlock, twrp and root this phone. I really wish manufactures would help us make this much easier.
Anyway, thank you again for your help. I'll be seeing y'all around the forums as a new MXPE user!

acejavelin said:
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Click to expand...
Click to collapse
Thank you for clarifying a misconception I had on systemless root
(I intentioned to reply to you earlier, but the mad busy week made me forget about my intent )
I'm going to try right now the latest stable with systemless method (rather than flashing the older version) on a full wiped clean stock to see if it works. (Even tho I see lots of feedbacks here inspiring me to believe it would)

In what order?
acejavelin said:
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting SR4-SuperSU-v2.78-SR4-20161115184928.zip is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. You can verify this worked correctly by entering 'cat /data/.supersu' and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again.
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Click to expand...
Click to collapse
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt

Iglooian said:
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Click to expand...
Click to collapse
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.

acejavelin said:
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
Click to expand...
Click to collapse
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.

Iglooian said:
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Click to expand...
Click to collapse
Fair enough... I will edit the "How to do it" section to make it more clear.

[GUIDE] MY HUAWEI MEDIAPAD M5 SUCCESS STORY - Unlock, Root, TWRP, ROMs, µg (microG)

This guide is for folks who want to turn their stock Mediapad M5 SHT-W09 (C567) in to a rooted, ROM-flashing-friendly device. All credit goes to those listed below, without whom I would have not had a clue how to proceed. The real purpose if this post is to, essentially, get all the steps in to one, comprehensive, guide for all those folks who were unfortunate enough to have purchased their BOOT-LOCKED, ENCRYPTED, FUNKY-AS-HELL Huawei device.
This is my first (and last) Huawei device because of those things. My previous (and any future) devices will not have a locked bootloader, or will at least be easily unlocked. Lesson learned—do your research before spending your money. That being said, let's proceed.
CREDITS
@stinger4321 For link to online bootloader unlock service.
 @Apo11on For rooting guide.
@Zackptg5 For DM-Verity, ForceEncrypt, Disk Quota Disabler.
@schwabe93 For TWRP & ROM [LOS 15.1 Unofficial]
@Setialpha and the NanoDroid team for µg (microG) via NanoDroid.
@TiTiB [me] For debloating guide.
In order to keep this guide as brief as possible, I am not going to mention any alternative, nor unsuccessful methods—only those that worked FOR ME. Do some "re/searching" and you may find something that works best FOR YOU.
UNLOCKING BOOTLOADER [GRRRRRR ] Thanks to @stinger4321
AFAIK as of this writing, 18 Dec 18, you will have to pay to unlock the bootloader. I used the online service found here:
https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275/page19
It took about 10 hours for me to get the code, so be patient.
ROOTING Thanks to @Apo11on
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
It is a Magisk rooting solution, but once rooted you can change to another type, if you wish.
TWRP [3.2.2-1 Unofficial] Thanks to @schwabe93
https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
Not everything is functional, but hey, you'll have TWRP.
ROM [LOS 15.1 Unofficial] Thanks to @schwabe93
https://forum.xda-developers.com/mediapad-m5/development/rom-lineageos-15-1-t3813826
DM-Verity, ForceEncrypt, Disk Quota Disabler @Zackptg5
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Read the instructions, and pay attention to the order of the steps, "This zip should be flashed after anything that modifies your boot img"
Easily the most stable ROM I've ever used! And I've used, probably, 70 or 80 over the years.
µg (microG) via NanoDroid Thanks to @Setialpha and the NanoDroid team
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
LOS 15.1 [Unofficial] does not, thankfully, include GAPPS. µg (microG) is "A free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries." that allows for most functionality that would otherwise require Google's crap.
GSI PROJECT TREBLE ROMS Thanks to @mishaal Rahman, Editor-in-chief on the XDA-Developers Portal for the "How to flash a Generic System Image (GSI) on Project Treble supported devices" guide.
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
I played around with four different GSI ROMs, but came back to LOS. I highly recommend trying them out tho because in my experience, using the adb method [link and commands below], I never lost any apps/data/settings—everything was still there, just with a new ROM to play with.
ADB COMMANDS [assuming already installed/authorized/plugged in, etc.]
adb fastboot bootloader >>>BE SURE THAT "PHONE" & "FRP" BOTH SHOW "UNLOCKED" BEFORE PROCEEDING<<<
fastboot erase system
fastboot -u flash system [name of system image you downloaded]
fastboot reboot
Disconnect device and play with new ROM.
>> DEBLOAT <<
This device is not a phone. I don't do any phone-like things with it. My debloat list is not for everyone—I'm very aggressive in my approach. Use your favorite search engine to find "bloatware safe to remove", and proceed with your own brain. You now have a rooted device with TWRP so why not do a backup and have fun debloating? That's how I figured out what to, and most importantly, what *not* to delete. BTW, I have used logcat readers to analyze the errors caused by my aggressive deleting of system assets, and am okay with the few errors that are caused—mostly the device trying to do "phone things" and not finding the required assets.
My method is to delete files/FOLDERS of those things I don't want—you have a rooted device, why use a "system app uninstaller" that might not fully do the job? The folders in which I do my deleting are, in order, /data/data, /system/app, /system/priv-app, immediately followed by a reboot, without which all bad things are possible.
I use the awesome MiXplorer (available for free, here on xda) for many functions—including root exploring/deleting, so I get rid of the ROM's included:
html viewer, gallery app, PDF viewer, text viewer/editor, et. al.
Below items are from LOS 15.1 [UNOFFICIAL]
⫸ /DATA/DATA
"Tele" "phone" "call" "cell" anything, blockednumber, dialer, carrier, stk, ctsshim, egg, mms, gallery3d, live wallpaper picker, and live wallpapers (noisefield, music vis, et. al.), dreams
⫸ /SYSTEM/APP
WAPPushManager, Stk, messaging, LiveWallpapersPicker, EasterEgg, CtsShimPrebuilt, CarrierDefaultApp, BasicDreams
⫸ /SYSTEM/PRIV-APP
"Tele" everything, WeatherProvider, MmsService, ManagedProvisioning, Gallery2, EmergencyInfo, Dialer, CtsShimPrivPrebuilt, CellBroadcastReceiver, CallLogBackup, CarrierConfig
I may have missed a few, and every ROM is different, so you may find more things to debloat.
If you found this guide to be useful, please hit the "Thanks" button ?

Unnecessary post deleted by poster

I am going to document my experience with unlocking, rooting and custom rom'ing my device.
I have an SHT-AL09, MediaPad M5 LTE. Country code is C00 (China). I don't know why my experience is quite different from @TiTiB; it could be the fact that mine is LTE device. But the fact is Huawei has MediaPad M5 8.4" (WiFi or LTE), MediaPad M5 10.8" (WiFi or LTE), MediaPad M5 Pro. That's at least 5 variants, and I suspect the ROM'ing procedure won't be the same.
Going back to stock
Firstly, I found myself bricking the device a couple times. But the eRecovery feature saves the day. As soon as you unlock the bootloader, the boot screen would tell you that the device is not safe, and you can run eRecovery to reset it (pressing volume Up for 3 seconds). That feature can connect to WiFi outside of Android, download the ROM specific to your device, and reset the whole thing. I had to do it twice, and I think it took about 45 minutes. It works flawlessly, and everything is reset (except the bootloader still stays unlocked.) So, I would say, don't be concerned about bricking it. Unless you plan to replace the bootloader, then I can't advise you.
Important key combo
As you install TWRP and ROM, you will need these key combination handy.
• Reboot - hold down the power button.
• Fastboot - As soon as it boots, and just before the mediapad screen, hold the volume down button WITH the USB cable connected.
• Recovery - Hold down the power button and volume up WITHOUT the USB cable connected.
Credit to @pyarle on https://forum.xda-developers.com/showpost.php?p=77238982&postcount=31
Choice of TWRP
This is important to know. I found two TWRP's advertised for MediaPad M5.
• From @schwabe93 https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
• From @Pretoriano80 https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
The first one can boot even if the data is encrypted. But it cannot decrypt data, nor can it flash any LineageOS ROM (even the one posted by @schwabe93 here https://forum.xda-developers.com/mediapad-m5/development/rom-lineageos-15-1-t3813826 )
The second one cannot boot if the data is encrypted. But, it can boot just fine if the data is unencrypted, and it could flash the LineageOS image from https://openkirin.net/
You can switch between them; it's a matter of flashing the right image in fastboot. Sadly, not one TWRP can rule it all, but that's the way it is today.
My success story
Here goes how I got LineageOS on my MediaPad M5 LTE
Download ROM and zip file
• This is the ROM I used. https://openkirin.net/builds/openkirin_los_beta5.img.xz
• Unzip it, then copy it to the external SD card.
• For DM-Verity, ForceEncrypt, Disk Quota Disabler @Zackptg5 See https://forum.xda-developers.com/and...crypt-t3817389
• Download the zip file, and copy it to the external SD card as well. You will need to decide whether to disable encryption or not. See the ROM section below. But if you decide to keep the data encrypted, rename the file to Disable_Dm-Verity_12.16.2018.zip before you copy it to the SD card.
Unlock the bootloader
• https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275
• I ended up paying $22 to get an unlock code. https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
• If your device has not been updated to a new Huawei ROM, you might have luck with a $5 solution with dc-unlocker. Otherwise, don't bother with downgrading. I tried for days; I just couldn't get it to work.
Root
• This is straightforward. https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
TWRP
• Install this first. @schwabe93 https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
• Don't forget, after the fastboot flash command and fastboot reboot, you have to boot to recovery right away. Otherwise the stock ROM might remove TWRP. Don't forget your key combo.
• Boot to recovery. Do a normal wipe (aka. Data, Cache, and Dalvik). (It won't be able to wipe /Cache.) Then do a "Format Data".
• Boot to Bootloader, and flash the second TWRP @Pretoriano80 https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
• With the data partition not encrypted, the second TWRP will boot. It can wipe /Cache.
Install ROM
• Hopefully, you have the LineageOS ROM from openkirin downloaded onto the SD card already.
• Still running @Pretoriano80 TWRP, flash the ROM. It already has google apps.
• You will be flashing the ROM as an IMAGE (to the "system" partition.)
• Here comes an important decision you have to make. Would you like to encrypt your data partition? If so, no TWRP can flash anything onto the device again, so you better figure out all the zip files you'd like to install.
• After you make your decision, rename the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip file if necessary, and flash it. (TWRP has a file manager for you to rename files).
Should I encrypt or not encrypt?
• This is a personal decision. If you keep it unencrypted, your life would be easier. You can stick with @Pretoriano80 TWRP and boot to it, and flash whatever zip files you'd like down the road.
• If you encrypt it, you will have to flash @schwabe93 TWRP next time you'd like to run TWRP. And all it could do is to format data, so that you can flash @Pretoriano80 TWRP again and flash. You would have to backup data with TitaniumBackup in Android, and restore it after the fact. You see the inconvenience?
• But, you know, if you lose your device, you would hate yourself for not encrypting your device.
Hope this helps anyone who has an SHT-AL09. The LineageOS rom runs really well, and I love the screen and sound.

Thanks @pazzu, especially for:
"Going back to stock
Firstly, I found...I would say, don't be concerned...". This makes me feel even more adventurous.
And the stuff about TWRP. I have decrypted my device since my first attempt at using @Pretoriano80's TWRP, so I'm going to try it out again. Flashing .img files via TWRP is quicker and easier for me than doing it with PC and adb.
Good stuff, mate! Thanks
EDIT: Now running @Pretoriano80's TWRP! No success with Havoc GSI—won't boot. More researching...
Sent from my SHT-W09 using XDA Labs

@TiTiB The fact is you have an SHT-W09 and I have an SHT-A09, I don't know if there are differences when it comes to custom ROMs. I can share a failed story though; I installed Magisk-v18.zip by installing it in TWRP. That was an epic failure that I had to recover using eRecovery. Good luck!

TiTiB said:
UNLOCKING BOOTLOADER [GRRRRRR ] Thanks to @stinger4321
AFAIK as of this writing, 18 Dec 18, you will have to pay to unlock the bootloader. I used the online service found here:
https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275/page19
It took about 10 hours for me to get the code, so be patient.
Click to expand...
Click to collapse
I got my M5 Monday and went to that site yesterday but it had no codes left for the wifi only version. Has that happened before? Does this mean they will never get any more? It will be very depressing if I can't get my shiny new M5 unlocked and rooted.

thecdn said:
I got my M5 Monday and went to that site yesterday but it had no codes left for the wifi only version. Has that happened before? Does this mean they will never get any more? It will be very depressing if I can't get my shiny new M5 unlocked and rooted.
Click to expand...
Click to collapse
I encourage you to do your best to stop any firmware update from Huawei, and try the dc-unlocker service. It seems that as long as your tablet is not upgraded to a certain build, dc-unlocker service would work. See https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275

pazzu said:
I encourage you to do your best to stop any firmware update from Huawei, and try the dc-unlocker service. It seems that as long as your tablet is not upgraded to a certain build, dc-unlocker service would work. See https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275
Click to expand...
Click to collapse
What @pazzu says is very true—don't do any upgrades! Also, look around here on xda for unlocker services other than dc-unlocker & global-unlocking. I remember anecdotal stories about such-and-such service that "worked when others didn't", so don't give up hope.
Sent from my SHT-W09 using XDA Labs

TiTiB said:
What @pazzu says is very true—don't do any upgrades! Also, look around here on xda for unlocker services other than dc-unlocker & global-unlocking. I remember anecdotal stories about such-and-such service that "worked when others didn't", so don't give up hope.
Click to expand...
Click to collapse
Yeah, the don't upgrade thing lasted about 5 minutes after I opened the box. I'm geeky about devices, upgrading it was as natural as breathing
Tried ministryofsolutions and they said no. Tomorrow I'll give dc-unlocker a go but I'm not optimistic. It's still a beautiful device, I guess I can live with it unlocked/unrooted.

The latest firmware is not DC-unlocker compatible yet, but it's not the end of the world. There are other services who send you a bootloader unlock code although they are simply more pricey ($30-60).
As for TWRP, I recommend TWRP for P10 because it's compatible with MediaPad M5 and capable of handling encrypted data partition and ADB.

thecdn said:
I got my M5 Monday and went to that site yesterday but it had no codes left for the wifi only version. Has that happened before? Does this mean they will never get any more? It will be very depressing if I can't get my shiny new M5 unlocked and rooted.
Click to expand...
Click to collapse
Responding to my own post...
I emailed the service unlock bootloader service in question tonight about ever getting more wifi unlocker codes and they replied, "Yes we will, We are currently testing the service"
So, that sounds hopeful.

Hellow Pazzu. I am a chinese man .I am very interesting in rooting android and install AOSP on my devices. But I am studying in
junior school so I have not a very known for android , Linux and English. The transformer software is not reliable . I have some questions about your article.
Frist why were you install TWRP twice .Whats the problem with the log of TWRP,if I wont do this what will happened?
Second once in a while I was wipeing the data suddenly the power was off .Than I cant reboot my devices.But it can boot into fastboot.
Then I used ADB to write system.img recovery.img boot.img it still cant working .I had write that 3 imgs why cant working?

Having a CMR-W09 with testpoint and Potato NV the bootloader unlocked but for almost one week was trying to get rid of the FRP lock . Ended up getting rid of the lock by flashing CMR-W09_hw_eu with Android 9.0. now I have the TWRP vtr3.2.1.0-v0.4. At least for me this recovery remained even after flashed the Android 9. Dont forget the button combinations.
Put official ROM on SD card in folder dload , turn tablet off keep Volume up and Volume down pressed together with Power botton. When Huawei logo comes up, release Power button and the ROM will be flashed.
Few tips when in TWRP you get failed to mount '/vendor '/cust '/odm etc. Get to Wipe in TWRP >Advanced Wipe >Repair or Change File System and select the partition can not be mounted >Change file system> select EXT2 > after that select EXT4, now that partition can be mounted again. The only you can not repair here ist the '/odm . For that solution is Huawei Update Extractor found here >https://forum.xda-developers.com/t/...updated-v0-9-9-5-open-source-library.2433454/ Extract the ODM.img from original ROM into the ADB folder and flash it on fastboot > fastboot flash odm ODM.img
One tip.... you dont have to use command > fastboot reboot , just keep volume up and power button> release power when Huawei logo comes up, so you will not have the custom recovery replaced with erecovery. That especially when you dont have all workj done in custom recovery and you dont want to lose it.

RobZen77 said:
Having a CMR-W09 with testpoint and Potato NV the bootloader unlocked but for almost one week was trying to get rid of the FRP lock . Ended up getting rid of the lock by flashing CMR-W09_hw_eu with Android 9.0. now I have the TWRP vtr3.2.1.0-v0.4. At least for me this recovery remained even after flashed the Android 9. Dont forget the button combinations.
Put official ROM on SD card in folder dload , turn tablet off keep Volume up and Volume down pressed together with Power botton. When Huawei logo comes up, release Power button and the ROM will be flashed.
Few tips when in TWRP you get failed to mount '/vendor '/cust '/odm etc. Get to Wipe in TWRP >Advanced Wipe >Repair or Change File System and select the partition can not be mounted >Change file system> select EXT2 > after that select EXT4, now that partition can be mounted again. The only you can not repair here ist the '/odm . For that solution is Huawei Update Extractor found here >https://forum.xda-developers.com/t/...updated-v0-9-9-5-open-source-library.2433454/ Extract the ODM.img from original ROM into the ADB folder and flash it on fastboot > fastboot flash odm ODM.img
One tip.... you dont have to use command > fastboot reboot , just keep volume up and power button> release power when Huawei logo comes up, so you will not have the custom recovery replaced with erecovery. That especially when you dont have all workj done in custom recovery and you dont want to lose it.
Click to expand...
Click to collapse
How did you unlock the bootloader? I'm exploring different options, but not sure which route to go. My m5 is on emui 9.1. If I can down it to 9.0 or 8 (maybe using hisuite?) I think I can brute force it at least (there a few promising projects on github). But I just don't know is the honest answer. Grateful if you would elaborate. I'm reading up on testpoint atm. Looks promising.

Vortex SYNQ Dev Thread (TWRP Image & Bootloader Unlock!!!)

During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
UPDATE: We now have enough people to really get the ball rolling for some development for this phone, so as we accomplish more things we'll post them here

Anything you try from here, you do so at your own risk. This may void your warranty, break your device, etc.
HOW TO UNLOCK THE BOOTLOADER
Go to Settings>About Phone>Build Number and tap this a lot really fast to enable developer mode
Go to the new developer mode option in the Settings menu, check the switch that says Allow OEM Unlock
Plug your phone into your computer, enable ADB Debugging, open up a terminal on your computer, and initiate an "adb reboot fastboot" to put the device into fastboot mode
In your computer terminal again, type in "fastboot oem unlock". If it fails, run it again. If it fails again, reboot to fastboot one more time and try a couple more times. Eventually it should work after a couple tries, it did for us
Confirm the device unlock on the phone (pressing volume up at the prompt I believe), and wait for the phone to reboot. Note that it's not stuck in a bootloop at this point, it's just factory resetting after the unlock, so give it time to work
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 1
Pull a recovery image from the phone with SPFT using a proper mtk6739 scatter file which I can't exactly find
Port TWRP to the phone from another device's mtk6739 TWRP image with carliv image kitchen tool, and flash it back to the phone with SPFT
Flash Magisk in TWRP, reboot, profit
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 2
Pull a boot image with SPFT
Use the Magisk APK to inject magisk into the boot image
Flash the boot image back with SPFT (or maybe fastboot), reboot, profit
HOW TO FLASH TWRP TO THE PHONE (STILL EXPERIMENTAL)
Download the TWRP image from here
Reboot to the bootloader
Assuming you unlocked the bootloader from before, just do "fastboot flash recovery [imagename]" to get it on there
If fastboot complains about it not being able to flash, try running the command one more time
CUSTOM ROMS FOR THIS PHONE
This phone came with 8.1 Oreo, so that means it has to be Treble enabled. I'm no expert with Treble stuff but I believe GSIs made for arm a-only partitions SHOULD work on here. We haven't tested this for ourselves yet though
Like mentioned before, feel free to drop by and leave a message if you're willing to help us out on our endeavors. I also want to try and get 'Thew a working recovery on his phone again if possible, since for some reason when we try to flash back the image we pulled (with our "best guess" mt6739 scatter file) it didn't work

i might have one.. i will check as soon as i get to the shop

jasonmerc said:
During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
Unfortunately during our testing, he seems to have messed up his recovery image and is unable to restore a stock one on there. If there's any other owners out there willing to help us out (and maybe willing to risk their device for some test builds of TWRP too) I beseech thee to make yourself known.
Click to expand...
Click to collapse
i have one .. if you need

desbloqueokings said:
i have one .. if you need
Click to expand...
Click to collapse
Check your PMs on here, just sent you something

So the other 6739 scatter files we found didn't exactly work for this phone, so we pulled our own with a tool we found on Hovatek. This isn't a "port" from another phone, this directly came from the Synq itself.
Give major thanks to @desbloqueokings for pulling this for us!

The group we had seems a bit inactive now, so I'll post my new creations up here for all you guys here to test and tell us all if it works or not. One is a patched boot image that contains Magisk, all you'd need to do for that is flash the boot image and install a Magisk APK and you should be good to go for root. The other is a dirty port of TWRP Recovery I did from another MT6739 phone. It was hard finding an image to port from, so I want to give a huge thanks to @lopestom who sent me a 6739 image he had that I could port from
PLEASE BE AWARE THAT THESE ARE TEST IMAGES. I DONT HAVE THIS PHONE MYSELF AND CANT TEST IT MYSELF, SO IM NOT SURE IF THESE WILL WORK OR NOT. PLEASE MAKE A BACKUP OF YOUR CURRENT BOOT & RECOVERY IMAGES WITH SPFT USING THE SCATTER FILE ABOVE BEFORE TRYING ANY OF THIS. WHAT YOU DO TO YOUR OWN PHONE IS YOUR OWN RESPONSIBILITY. WHILE I WILL TRY TO HELP YOU IF SOMETHING BREAKS, IM NOT RESPONSIBLE FOR WHAT YOU CHOOSE TO DO
With that being said, here's the Mega folder containing the boot and recovery images. You can either flash these through SPFT like most people do with mediatek phones, or through fastboot, whatever you can get working. I'd also recommend you unlock your bootloader using the method posted above before doing any of this
Let me know if this stuff works or not, if you choose to flash it

Our victory was bittersweet, but a victory nonetheless
We got a working recovery image from @lopestom that seems to work fine on the surface, but when we need to flash the zip that disables dm-verity (disables force encryption) it supposedly breaks the /system partition on the stock ROM. My recommendation would be to take a backup of your /system directory in recovery before trying to flash anything. But since this is a Treble-enabled device, that means GSI ROMs could also work when flashed.
Here's a link to the recovery image we were using. We flashed it in fastboot with an unlocked bootloader but I imagine it would work just fine in SPFT too. I was told by the person that made the image that it's apparently not a good idea to flash the disable-force-encryption zip on a dirty port of a TWRP image like this (and to also never wipe /data). While you should be able to use this TWRP to flash something like Magisk, don't do those other two things for now.
Here's some screenshots from @Matthew702 to show the phone booting to TWRP (we made the mistake of trying to wipe /data and trying to flash the disable-encryption zip, please do not do this):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thank you!

You guys are amazing.
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx

xAlimorAx said:
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx
Click to expand...
Click to collapse
Yeah it showed up in Russian for our tester too. Not sure why it does that, but otherwise it should still work fine

Need your assistance
Season greetings to you my friend, I ended up formatting my vortex synq using Sp flash tool, after attempting to root, now I have black screen only vcom for sp flash tool works but I need preloaded files and others to unbrick, it was gonna be a Xmas gift for my aunt, but I messed it up, wont turn on just vcom when connected to PC, I have the files stckboot and recovery but sp tool needs pre-loader error, plz help me

Please back up vortex synq
Good I ask for a help to see if someone will have or could make a back up for this vortex synq cell phone since some of us have problems in the firmware when modifying it and we do not have a previous backup if someone can collaborate, it would be infinitely appreciated.

I know this post is old but if somebody can backup the firmware from this it would be awesome, because i am trying to restore my vortex snyq (its hard bricked) but i can't find the preloader for this phone anywhere, when i tried to flash the preloader with sp flash tool it gives me this: STATUS_DA_HASH_MISMATCH, the preloader has to match this phone, if anyone has a backup of the firmware feel free to post it here or dm me, but yeah just wanted to post here.

also need firmware having the same issue ages now
any help much appreciated
safe 2021-2022

use this to unlock bootloader and backup fw https://github.com/bkerler/mtkclient

Making this post to do a dump of the Vortex Synq stuff I had on Mega. XDA allows us to upload large files to here now, and my Mega account is getting pretty full, so I want to transfer everything I have that's Vortex Synq related from there to here. That means any download links pointing to my Mega will be broken, but all of that stuff previously linked by me can be found in this zip.
disclaimer
Feel free to use any of my stuff in any way you see fit. The only thing I ask is that if you do improve on something, share it with everyone else and don't just keep it for yourself. Keep it going for the good of the community/public.
Also, know that it's been a long time since I've messed with this phone, so I don't remember what mods/images/etc in my Mega repo are functional or not. Anything contained within this zip, FLASH AT YOUR OWN RISK.
/disclaimer

[CLOSED] Delete Thread.

Due to the disrespect of certain members I will no longer share the tutorials.

Wait does this mean you finally got my script to work?

lebigmac said:
Wait does this mean you finally got my script to work?
How about a little feedback in my project thread? Is that too much to ask for?
Did the latest fix work for you or not? Hello?
Click to expand...
Click to collapse
I said you were working on it. LOL. If it worked I'd be writing a Guide for that!

Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root

mingkee said:
Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root
Click to expand...
Click to collapse
Exactly. Definitely made a note of that in the guide since that is why the frozen touchscreen issue happens.

Articul8Madness said:
.This tutorial is for people like me than ran into problems rooting the Moto One 5G Ace XT2113 (MetroPCS Qualcomm Variant) running on stock Android 10. I got this phone literally last week brand new in the box. This is a hand holding guide for the Noobs that really are intimidated by rooting their device.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
I want to thank @mingkee and @sd_shadow for pointing me in the right direction. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this; I did achieve root out the starting gate but initially lost touchscreen functionality. The issue was that you have to use the boot.img of your firmware to patch into Magisk; if you do this with your phone out the box you really don't know which firmware was used and that is where the bungle happens. This will clear up all those potential freakout moments.
Thanks to Android 10 being System As Root with all these new super partitions running amuck, you cannot get Write access in the actual system files. So even when you achieve root, you can't do much. @lebigmac is working on that as we speak. Drop by his thread on R/W access and beta test his script so he can get more knowledge about how our phone works.
Introduction/Preparation
First, go and prepare by READING EVERYTHING. Very important. This is the Qualcomm variant and NOT the Mediatek variant. Flashing does make a difference between the two. Last thing you want to do is brick the device because you flashed the wrong firmware to the wrong processor, or you flashed other software for the other similiar Moto One 5G and it bricked.
Second, unlock the bootloader. All T-Mobile and their subsidiary variants can be unlocked by Motorola as well as International and Motorola factory variants; go to their bootloader official unlock site and follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). It is HIGHLY ADVISABLE to do this in Waterfox or Chrome (I used Waterfox). And yes, you may have to request the code 3x to get it to send to your email depending on their server traffic. When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
Verizon and ATT Variants CANNOT BE BOOTLOADER UNLOADER UNLOCKED.
***NOTES SO YOU DON'T FREAK OUT***
1. I did NOT see the motorola post screen telling me it was unlocked. I had to find this in fastboot's menu.
2. The only way to restore the phone if something goes wrong is by flashing it via fastboot. The way to get to fastboot is turn the phone off and press Volume Down and Power. The Motorola tool will NOT work. That's normal.
3. You will see a cute message that you've unlocked the bootloader and that the phone software integrity is compromised when you boot the phone up every single time after the bootloader unlock. It will also say press the power button to pause. This is normal. Give it a minute, you havent broke it.
4. OEM Unlocking should already be activated and greyed out in the Developer Options once the bootloader is unlocked; you can't access it anymore.
Files
You will need an SD card for root. You will also need other apks to successfully help you pull off root ready to install. Pull ALL the necessary files you will need.
1. Get Minimal ADB and Fastboot (it's easier).
2. Download the Motorola Drivers from their site if yo don't already have them (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (Very important, its hard to know your hardware without this).
4. Magisk v22.0.apk (They no longer have a separate Magisk Manager)
5. Root Explorer.apk (This software helps navigation better but you can use any Explorer of your choice).
6. Root Checker.apk
7. Stock Firmware XT2113-3_KIEV_RETEU_10_QZK30.Q4-40-62_subsidy-DEFAULT_regulatory-XT2113-3-EU-SAR_CFC.xml (This is important if you mess up the boot image trying to root). You can get the firmware of your choice at Motorola Official Firmware For Kiev.
8. Patience (and a good movie keeping you going).
As of now this device as no TWRP, so you have to do this the old fashioned way to root. And just so you know, I used Windows 7 for all of this.
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. Everytime you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and tries to push an update. Just take the silver key thing and pop it out. You will have to push it back in and out in a second, but start with it out.
3. Make sure your wifi is OFF.
4. Make sure your SD is in and mountable and all files you need are on the card.
5. Make sure you Save boot.img to your SD Card from your firmware files. This is very important for root.
6. Make sure your developer options are activated.
7. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
8. Make sure to check CPU-Z for your hardware specs so you download the right files for the phone and avoid potential problems.
9. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device).
10. Make sure you have the STOCK CABLE that comes with the phone. Like most Motorolas this model is funky about using other cables.
11. Make sure you back up all your calls, texts, pics, etc. Flashing the firmware is the ultimate factory reset and you will lose all your files on the phone. SMS Restore is a good software to backup Calls and Text logs and it supports keeping MMS.
12. Make sure you have the internet. It is necessary for some steps.
Rooting
1. Make sure all the firmware files are extracted into your Minimal ADB and Fastboot folder (or whatever ADB folder you're using for this).
2. Open FlashFile.xml in Notepad. This is located among the firmware files you put in the Minimal ADB and Fastboot folder.
3. Cut, copy, and paste everything from the FlashFile that is shown and then paste it in an online Flash file Converter. I used Online Flash File Converter here.
4. Convert the text by pressing the bar below where you pasted the text. It may be in Spanish or Portuguese but is should say something like Cerar Commandos.
5. Copy the text by hitting the two pieces of paper icon in the corner after it's converted. Or just cut copy and paste manually.
6. Turn the phone completely OFF.
7. Plug your phone via USB cable into the computer.
8. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY).
9. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your firmware files are in the Minimal ADB directory or it won't work.
10. Paste the contents of the flashfile converter into Minimal ADB and Fastboot. This should start the process of the flashing.
11. When the entire flash is complete, boot the phone and disconnect phone from the computer. Ignore the bootloader unlock error.
12. Wait. Sometimes this takes up to 3-5 minutes on a new flash. You should see the boot animation of Motorola.
13. Push your Sim Card back into the phone.
14. Start setting up your device on the screen. Sim Card must be in or it will give you a message your phone is Network Locked.
15. Once you make it to the Wifi Setup screen take the Sim back OUT the phone. Do not connect to Wifi.
16. Once you are done with setup, go to Settings>About phone.
17. Go all the way down to Build Number and press it until you unlock Developer Options.
18. Go to Settings>System>Advanced>Developer Options. Advanced is a pull down tab that will reveal Developer Options.
19. Disable Automatic System Updates. I know this is hard for some people, but a forced OTA update may cause problems and prohibit root.
20. Enable USB Debugging. Disable Verify bytecode of debuggable apps. Disable Verify apps over USB if it is highlighted. Exit.
21. Put your SD/Sim card back into the phone.
22. Go to the Files folder and install Magisk first, then Root Explorer and Root Checker.
23. Open Magisk. You will see Magisk and App. Hit Install by Magisk (a fingerprint looking icon is to its left).
24. Allow Magisk to access photos, media, and files if it asks.
25. Select option "Select and Patch A File."
26. It will take you to a screen where you can select your explorer to navigate to your SD card where you saved the boot.img. Go there and select it.
27. Magisk will save it as magisk_patched.img. Once you get it patched, find where it saved, make sure it's on your SD card and then turn off the phone.
28. Plug your phone via USB cable into the computer.
29. Press Volume Down and Power to boot into fastboot mode.
30. Open up a fresh Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure you transfer the magisk_patched.img that Magisk patched off your SD card into this folder.
31. Rename your original boot.img to "boot.img original" or whatever distinct name you want to give it in your Minimal ADB and Fastboot folder.
32. Rename your magisk_patched.img to boot.img.
33. In Minimal ADB and Fastboot type "fastboot flash boot boot.img" and hit enter.
34. If all goes well it should flash to the partition before it says done and in how many seconds.
35. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
36. Wait for the bootloader cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
37. Open Root Checker and confirm root. You can uninstall it after confirmation if you like.
38. Open Root Explorer. A prompt asking you to grant permission should pop up.
Congrats. You should be rooted now.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. You're asking for bootloop hell if you do as your boot.img that Magisk patches needs to match that particular firmware you used.
2. While it hasn't happened to me, You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. While you won't lose anything just flashing boot.img, you will lose everything having to flash ALL the firmware over. Keep backups of all your important stuff.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, follow my guide on restoring the firmware on the phone. And don't worry - it won't relock the bootloader. You can find my guide here: The Complete Noob Guide to Flashing via Fastboot MetroPCS Moto One 5G Ace XT2113 [Qualcomm Version]
Hope this helps my fellow TMobile and subdiary acolytes and othoers. I have flashed and reflashed my phone with different variant roms trying to force Write status and beta testing scripts for @lebigmac on our device so it's pretty straightforward now.
I will try and answer questions if I can or point you in the right direction.
Click to expand...
Click to collapse
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset

bobbyp1086 said:
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset
Click to expand...
Click to collapse
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.

Articul8Madness said:
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.
Click to expand...
Click to collapse
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.

bobbyp1086 said:
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.
Click to expand...
Click to collapse
If your bootloader is unlocked the only way you should have gotten the corruption is if you flashed an incompatible firmware. Mine came with MetroPCS but I've flashed RETUS and RETEU well. I'd stray from any VZW or ATT software just because you can't trust their firmware won't lock down the bootloader.
Or maybe the software just didn't download well. Try re-downloading it . I've had a bad download mess up a flash before.

I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch

bobbyp1086 said:
I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch
Click to expand...
Click to collapse
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.

Articul8Madness said:
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.
Click to expand...
Click to collapse
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and fix file permissions, it's in settings

bobbyp1086 said:
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /View attachment 5279427View attachment 5279429View attachment 5279431View attachment 5279433 and fix file permissions, it's in settings
Click to expand...
Click to collapse
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.

I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?

I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked

bobbyp1086 said:
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.
Click to expand...
Click to collapse
Android 10 is very challenging. It is easy to root but it is a trickable root with a false sense of root since Google locked all Android 10 and newer as Read Only on the System with this super partition crap trying to be Apple.

Skel40 said:
I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?
Click to expand...
Click to collapse
Check my guide. I posted link to where the repository is.

Skel40 said:
I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked
Click to expand...
Click to collapse
You will not pass safety net because you've rooted it and Android 10 will block it. It isn't necessary, especially if you delete all Google stuff and their tracking Covid crap.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
Hi @Articul8Madness. Thanks for mentioning me
There's a Motorola user who recently got my script to work using the troubleshooting repair script that I posted here
It turns out the lpmake arguments that are auto-generated by the original script were flawless and were not the root cause of the unidentified lpmake error that some Motorola users were experiencing at the end of the original script. According to @Xiaoleng the error was most likely caused by some kind of new Motorola security feature that prevents the terminal command from executing if the arguments are too long. Go figure.
And he was even able to fastboot flash the super_fixed.bin in one piece without having to first split it up into chunks. That's a huge surprise to me. I always thought Motorola users can only fastboot flash super sparsechunks?!
Please feel free to give it a try and report back your results. Thanks. Good luck!

[ROM][UNOFFICIAL][11][ARM64] LineageOS 18.1 for Amazon Fire HD 10 (maverick/9th gen)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
Code:
/*
* Your warranty is... still valid?
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are the one choosing to make these modifications.
*/
IMPORTANT
This ROM is only for the Amazon Fire HD 10 2019 (maverick) Do not try to flash it on any other device.
This ROM requires the temporary bootloader unlock found here. Read the instructions carefully and come back once you have a working temporary unlock.
This thread will be updated should another unlock method be available.
This ROM requires that you be on the 7.3.1.0 launch firmware. If you have temp unlocked your device, you should already be on this firmware.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
This is a custom build of LineageOS for the Amazon Fire HD 10 9th generation (maverick) which is 64-bit, allowing you to run 64-bit applications and benefit from better performance, unlike the stock OS which is 32-bit.
Working
Audio
Bluetooth
Camera
DRM L1 (playback not tested)
DT2W (double-tap-to-wake)
Media Playback (Hardware OMX)
Sensors
SDcard
USB (MTP, PTP, etc)
Wi-Fi
Not Working
SELinux is Permissive
Deep Sleep (?)
Hotspot
Notes
The stock gallery app has some issues playing media which is higher than 1920x1080, if you face this issue please try a third-party gallery app.
If you have flashed GApps, you should wait for the device to "settle" after completing setup wizard. During the first 10-ish minutes of use, the tablet could heavily lag and freeze.
Since this is a beta build, you should be prepared to face bugs and issues, along with possible stutters and lags.
You are free to use any recovery to flash this ROM, however, I recommend using the attached recovery (Lineage Recovery) to flash this ROM in order to avoid any potential issues.
How to Flash?
Spoiler: Flashing Instructions
It's important to note that you will have to boot your device with mtkclient every time you reboot!
First of all, boot the device into fastboot mode. Once you see something like => FASTBOOT mode... appear on your devices display, you can flash the Lineage Recovery image with the following fastboot command:
Code:
fastboot flash recovery lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick-recovery.img
fastboot reboot recovery
This flashes the custom recovery to the devices recoverypartition, and then tells it to reboot into recovery mode.
To make sure the device boots into recovery upon the next reboot, hold the volume up button on the device after sending the preloader again with mtkclient.
DO NOT let the device boot back into FireOS at this point, as it will flash the old recovery back to the device, and you will need to start from the beginning again.
The unlocked LK indicates which mode the device will boot into, you should see something like lk boot mode = 2 on the devices display, meaning it is booting into recovery mode.
Once in Lineage Recovery, tap on "Apply Update", and then tap on "Apply from ADB". There are also options to apply updates from external storage if you wish.
Now, it's time to actually install the ROM. We are going to sideload the Lineage ZIP to our device using adb with the following command.
Code:
adb sideload lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick.zip
At this point, all you need to do now is wait for the flashing process to complete.
Once finished, you will be brought back to the apply update menu. Simply press the back button to go back to the main menu.
Now, tap on factory reset and tap on the option Format data/factory reset. This is going to erase all of the old FireOS userdata from the device.
If you do not wish to install GApps, skip to the finishing up process below the GApps flashing instructions.
Optional: Flashing GApps
To install Google Services to your new ROM, you will want to start by downloading the recommended GApps package (see Downloads section).
Once downloaded, you can follow a similar process that you did for installing the ROM ZIP.
Tap on "Apply Update" again, and "Apply from ADB".
Once you have done that, you can sideload the GApps package with the following command:
Code:
adb sideload MindTheGapps-11.0.0-arm64-XXXXXXXX_XXXXXX.zip
If you wish to install other addons (e.g. Magisk), repeat the same steps, substituting the GApps package file name with the Magisk zip file name.
Finishing Up
Once you have done everything you need to do in Lineage Recovery, it's time to boot into the new ROM.
It's important to note that the reboot system now option does not work correctly, so follow these steps to workaround it.
Tap on Advanced, and then tap on Reboot to bootloader.
Once you see => FASTBOOT mode... on the devices display once again, type the following fastboot command to reboot.
Code:
fastboot reboot
After a short while, you should see the LineageOS boot animation on your device. First boot usually takes 5-10 minutes, especially if you have installed Google Services.
Wait for the device to boot and you should be presented with the setup wizard. Enjoy!
Downloads
ROM
Recommended GApps
Source Code
Device
Kernel
Vendor

Screenshots attached below.

Reserved #3

Amazing job.

@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
The device tree is currently private for whatever reason. I will let bengris know through Telegram.

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
Hey, currently the new device tree is not open source yet, I will make it open source once I fix the remaining issues (mainly getting SELinux Enforcing). Kernel tree is open due to the GPL license.

Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?

I will pay $1,000 or more to anyone who can open bootloader to the new systems amazon

jasonjohn95 said:
Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?
Click to expand...
Click to collapse
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.

Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate

ＤＥＭＯＮ said:
Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate
Click to expand...
Click to collapse
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...

Michajin said:
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...
Click to expand...
Click to collapse
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?

ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....

ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
that being said, i hope you have updates disabled, because there might be another root option coming.

bengris32 said:
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?
Click to expand...
Click to collapse
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops

Michajin said:
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....
Click to expand...
Click to collapse
Thank you very much for your answers, I don't know when I bought the Tablet, I forgot, but I imagine that it is possible to downgrade to Fire OS 7.3.1.0 in some way which I don't know, apart from I don't understand the tutorials that I found on XDA, I really have 2 days and my head hurts a lot because I do not understand the explanations of the users, if there was even the slightest possibility that you could contact me and tell me step by step what I should do and I will show you with screenshots how I progress and do everything to have a guide, I promise to pay you if I succeed in installing this ROM by PayPal

jasonjohn95 said:
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops
Click to expand...
Click to collapse
Let's try to dump pstore from the device when it's trying to boot then.
Wait for the device to reboot after being on the amazon logo, immediately on the next boot up, go into recovery mode. Then, enable ADB.
You can dump pstore with the following adb command (adbd should run as root in recovery):
adb pull /sys/fs/pstore
Hopefully there should be some logs in there which you can attach here, if not, keep retrying until you get something in there. If you are 100% nothing is being dumped to pstore, just let me know.
As a side note, I am using the kernel source and blobs from the 7.3.2.7 firmware, so I'm not sure why it's not seeming to boot on later firmware.

bengris32 said:
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.
Click to expand...
Click to collapse
It works!
Completed a Lineage build using the info on "amazon-mt8183-devs" repo - now installed & working fine.
Many Thanks