Related
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.
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
victor-zorro said:
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
Click to expand...
Click to collapse
Try reflashing it with the factory original firmware using their own flashing tool.
Once you got it working with that, then you can try flashing it with whatever you want.
Till then, there just too many variables with custom ROM.
Hi!
I'd like to get rid of the HTC original firmware on my U12+.
I just tried to flash GSIs of LineageOS 17 by AndyYan then AOSP 10.0 by phhusson, without luck.
I have a factory unlocked HTC U12+ (fastboot mode showing Secure Boot : Development, Secure State : S-Off, Device State : Unlocked(U)) so I went straight to the "flash GSI without TWRP" part of the official XDA tutorial: I factory reset the phone, rebooted in bootloader, then erased system and successfully flashed lineage-17.0-20191117-UNOFFICIAL-treble_arm64_avN.img.
But after reboot, I got a bootloop.
I've wanted to try the TWRP method, but upon launch it asked my password for decryption. While I'm sure of the code I've used and typed, decryption doesn't work, so TWRP didn't help.
Then I've flashed the AOSP GSI via fastboot, but then I got a "This device is corrupt. It can't be trusted and will not boot" error message.
So as suggested on another thread I've used the SD card method to flash a RUU, specifically 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_HTC_Europe_1.30.401.2_Radio_sdm845-000201b-1807311356_release_528103_signed_2_4.zip. It flashed successfully, but then it booted to the static white HTC logo on black background and stayed there for 20 min.
I can still boot to fastboot mode/download mode, but I don't know what to do.
I can't figure what I'm doing wrong, can you help me, please?
After another attempt I've managed to go back full stock using the microSD card method.
Then I've been able to boot TWRP, which first showed a "Mount" "Decrypt data" screen, asking for a password. The 6 digits code I've used previously doesn't work. So TWRP "failed to decrypt data", also was "unable to mount storage" and "failed to unmount /system_root (device or resource busy)". As suggested, I formatted/wiped data to remove encryption.
Then I performed a factory reset, adb pushed system-quack-arm64-ab-vanilla.img to /data, then flashed it successfully to the system partition, as requested in the afore mentioned official tutorial. On reboot I get another bootloop. Bootscreens shows the HTC and Powered by Android wordmarks and also "** ORANGE **" on the top left corner of the screen.
What am I missing?! :-/
After first boot of flashed RUU at the HTC logo reboot the device. Got there myself, rebooted(using power button) and the OS booted up perfectly.
TWRP doesn't decrypt latest Pie with July Patch. So you will not decrypt it. (Wiping does not decrypt).
I used temporary TWRP, flashed permanent (with touchscreen patch), installed Magisk, Rooted, installed LeeDroid from Magisk for example.
Make sure you have a correct RUU for your CID version.
I am not sure how a project treble ROM will work on this device. You still need signed HTC drivers. I don't think we are ready now for 10 on this device for daily use. HTC did quite awful with the Pie update and many bugs are still not fixed after 6 months.
GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
I was unable to determine CID and MID yesterday from fastboot mode or TWRP, so I've downloaded the latest RUU for dual SIM and EMEA model, as my U12+ is dual SIM and I live in Europe.
Now that the phone is back to full stock, I just installed a terminal app right on the phone and executed the following:
getprop ro.cid : 11111111
getprop ro.boot.mid : empty
I understand that the phone is "SuperCID", but I don't really understand what that implies.
Regarding Treble, Treble Info by Hackintosh Five reports (translated from French by me): "Your device supports the old Project Treble version, using VNDK version 26.0."
But the U12+ is listed as supported on phhusson's wiki. A few issues are listed, but I'm fine with them.
I've read a tutorial that asks to "extract the GSI and vendor+boot zips", but then doesn't what to do with the vendor+boot zips. Do you know?
Lastly, do you know what the **GREEN** or **ORANGE** overlay means on the boot screen?
Thank you for your help!
Romano2K said:
GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
Thank you for your help!
Click to expand...
Click to collapse
SuperCID implies you can install any RUU (not specific CID). So you can "transform" your US version into european or asian... for a specific reason. No need to do that. Usually there was a specific base that was needed to install a custom ROM or Custom Recovery or people just wanted a different version because they lived in a different part of the world from where the phone was purposed.
I am guessing the **GREEN*** overlay has smth to do with the RUU (if it's embedded in the Boot animation zip (basically pictures+ sound)) or has smth to do with the nature of your tempering (S-OFF/SuperCid etc.)
with this device and serves as a warning for users/devs/internal testing.
You should find your answers on a different section. More active. I see no activity here. And it's HTC's fault for dying" on us. I myself bought the U12 just to own (probably) the last flaghsip device they make. Here's to the comeback.... but I am not sure it will be real. HTC was one of the fastest to update, for example.. until 2019. We are still with bugs and on the July patch. Right not, in reality I am just hoping for one last Pie update to fix bugs and that's it. Will give this device a 1 year run and buy something better.
So go to the Android general section where you can ask how can you compile your ROM on this device. They should help. I can not offer sufficient knowhow on this topic.
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Interesting. Will look into your tutorial. So thank you. If the boot animation.zip was modified you will find in in root/system/[search for it] -you can lookup up each image that forms the animation to check. I myself modified the ZIP to not include the annoying audio, so i deleted it. )
So is the GSI good for daily use? I would mess around with it until i sell my HTC U11. Still using the U11 as a daily driver for the past 2 weeks. And by selling it i mean practically giving a perfectly good phone away for scrap... because it's old.
Deonix said:
I myself modified the ZIP to not include the annoying audio, so i deleted it.
Click to expand...
Click to collapse
That's clever! The HTC boot sound was annoying when I had trouble booting the bootloader, because of the tactile buttons.
Deonix said:
So is the GSI good for daily use?
Click to expand...
Click to collapse
At this point I have a big problem with AOSP 10.0: brightness is blocked at 100%. There's a workaround involving adb, but for some reason adb isn't working with this firmware, even though I've activated developer options and USB debugging. I haven't had the time to tinker yet, I'll give it a try asap and I'll report back!
Thank you again for your help
Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Did Bluetooth work for you on AOSP? Tried to install a few GSIs over the last couple of days but I cannot get Bluetooth working for calls or media. Apparently it's a known issue but none of the fixes I can find here on the forums seem to work for me. Just wondered what your experience was on another U12. I even tried your guide but still no Bluetooth for me.
Useful post about the GREEN message.
stock rooted pixel4a (from google directly) running root.boot.sunfish-qd4a.200805.003.img iirc.
just hit the upgrade magisk button as i always do (yes, i unhid the app back to normal) but it failed. directly following this, it rebooted and i am now stuck inside fastboot mode without access to ADB. fastboot commands work but ADB do not. is there a way to upload a boot image to get me back to where i was? OR at the least, backup my phone before a full wipe. thanks in advance!
xxTECRAxx said:
stock rooted pixel4a (from google directly) running root.boot.sunfish-qd4a.200805.003.img iirc.
just hit the upgrade magisk button as i always do (yes, i unhid the app back to normal) but it failed. directly following this, it rebooted and i am now stuck inside fastboot mode without access to ADB. fastboot commands work but ADB do not. is there a way to upload a boot image to get me back to where i was? OR at the least, backup my phone before a full wipe. thanks in advance!
Click to expand...
Click to collapse
adb commands don't run on fastboot.
You must flash stock boot.img or magisk patched boot.img using fastboot flash boot "the_boot.img_file_you_want_to_flash"
should i flash this image "root.boot.sunfish-qd4a.200805.003.img"? or do you know where i get a patched magisk boot image? i've looked through magisk github as well as here but i may not be looking for the right stuff. i get the idea of what needs to be done. how i do it exactly is a little stretch, outside the obvious command "fastboot flash boot.img"
little more push in the right direction, please?
EDIT:
reviewing this https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
and this https://forum.xda-developers.com/t/help-access-internal-storage-from-fastboot.4221223/#post-84332187
the fastboot mode screen displays the following for the bootloader version: s5-0.2-6281315 and i do have a bootloader that matches that. going to give that a whirl
making headway but not booting still
xxTECRAxx said:
making headway but not booting still
Click to expand...
Click to collapse
Judging by the screens you've shared, you've just tried to flash bootloader into boot partition. DON'T DO THAT.
If I were you I would just download the complete fastboot ROM and would run flash-all.bat.
In order to retain your data, before running the bat, open it and remove the "-w" you'll see on the update command line.
This will flash the hole ROM and firmware, thus making your device to achieve boot.
Afterwards you may try to root it again.
THANK YOU!
hey @Typhus_ wanted to say thank you again! i was not only able to get back to norm, i was also able to root back to where i was, with the exception of not passing SafetyNet. been reading about it and what all is available to use with HidePropCconfig module. the pixel4a was passing prior to this riggamaroll but not really concerned about that issue at this time.
i just noticed i am not seeing the full 128gb disk. about 6 months ago i had an issue with root and went full retard, re-formatting the phone and throwing commands at it with ADB. i really couldn't tell you exactly what i did as i don't remember but i can confirm i messed with the partitions and this has obviously effected me adversely.
being that you had efficiently helped me with my bootloader and your experience here at XDA, i thought maybe you had some thoughts on the disk not being 128gb and how i might repair that. i have since backed up and in a position to go full retard
please see attached screenshots of disk analyzer, sdmaid, and a windows shared drive mount
xxTECRAxx said:
hey @Typhus_ wanted to say thank you again! i was not only able to get back to norm, i was also able to root back to where i was, with the exception of not passing SafetyNet. been reading about it and what all is available to use with HidePropCconfig module. the pixel4a was passing prior to this riggamaroll but not really concerned about that issue at this time.
i just noticed i am not seeing the full 128gb disk. about 6 months ago i had an issue with root and went full retard, re-formatting the phone and throwing commands at it with ADB. i really couldn't tell you exactly what i did as i don't remember but i can confirm i messed with the partitions and this has obviously effected me adversely.
being that you had efficiently helped me with my bootloader and your experience here at XDA, i thought maybe you had some thoughts on the disk not being 128gb and how i might repair that. i have since backed up and in a position to go full retard
please see attached screenshots of disk analyzer, sdmaid, and a windows shared drive mount
Click to expand...
Click to collapse
That storage space values are just... weird. Can't quite find another word for it.
If I ran into that kind of problem I would completely clean flash the stock ROM again, this time keeping the "-w" flag. You see, that flag completely cleans the user data partition and creates it again as soon as the flashing procedure ends. Most likely, and by doing so, your storage space values will be correct again. Obviously this will wipe everything so, if you decide to do so, please backup manually all your important stuff.
As for SafetyNet fix, you may use kdrag0n module (he made and shared one universal mod that fixes it) or you may flash my addon features module (link on my signature) that, not only, fixes SafetyNet, but also, adds several cool mods.
Cheers!
UPDATE: You can now get root on the Android 10 Umidigi A7 Pro using magisk.zip v25.2 (25200).
See post 10 for more info
----------
to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.
at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom
then...
ive installed the latest Magisk Manager,
copied the original boot image from the stock rom over to the device,
ran the patch operation on magisk
copied patched boot file back over to pc.
load up smart phone flash tool and the stock rom,
selected the patched boot file in the flash tool > boot
pushed to device
ENDS with error notice on flash tool. device goes into bootloop.
resolve by flashing back all of the unmodified stock rom.
multiple attempts, same results
from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.
so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?
ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.
for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.
once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.
thanks in advance everyone!
[reserved]
earlier today i managed to find a link for magisk canary. i dont have the device near me atm, but i believe the manager is v7.5 and magisk itself is v19.X. the output patch file comes out named differently with the older version (newer version appends a unique string behind the name). however, same results as before. boot loop.
one positive note tho: the patched boot file completes with a big green check rather than the runtime error, or whatever it was previously.
i tried pushing the patched boot file over fastboot and via the flash tool. same results regardless.
re-flashed the stock boot image and phone is back up and running. still no root though.
still leaning strongly toward it being a magisk problem, but ive seen mention of disabling some security features dealing with individual partitions, but that was on other umidigi models, so ill have to research further if nothing else pans out
found this tut mentioning vbmeta. otherwise, same process that ive been using with no success. figure its worth a shot. ill post back with results
rooting the umidigi a7 pro (magisk)
rooting the umidigi a7 pro (magisk). GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This guide is for advince users only! better guide comming soon on XDA (I have test this on my own umidigi a7 pro )In order to root your umidigi a7 pro you need to: 1) download device FW --> https://community.umidigi.com/forum.php?mod=forumdisplay&fid=235 (DO NOT download the EEA verison if you are not in Europe!) 2) download sp flash tool in case you brick you phone. --> https://spflashtool.com/ 3) unlock your bootloader --> https://www.getdroidtips.com/unlock-bootloader-umidigi-a5-pro-2/ 2) flash this vbmeta.img file with fastboot in bootloader mode. --> https://mega.nz/file/dnAS3AhD#g5PnSg-0UKFvyhZSZ8Em6gKO2Do7avaUepPmsH75-Bg cmd: fastboot flash vbmeta vbmeta.img 3) extract the boot.img from fw.7z file and patch it with magisk 4) flash your patched_boot.img in bootloader mode cmd: fastboot flash boot boot.img enjoy your rooted phone!!!
nope, the vbmeta thing didnt help. bootloop. i tried using the patch from the latest magisk, and the patch from the older version of magisk. same across the board.
double b26 said:
to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.
at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom
then...
ive installed the latest Magisk Manager,
copied the original boot image from the stock rom over to the device,
ran the patch operation on magisk
copied patched boot file back over to pc.
load up smart phone flash tool and the stock rom,
selected the patched boot file in the flash tool > boot
pushed to device
ENDS with error notice on flash tool. device goes into bootloop.
resolve by flashing back all of the unmodified stock rom.
multiple attempts, same results
from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.
so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?
ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.
for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.
once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.
thanks in advance everyone!
Click to expand...
Click to collapse
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...
So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.
I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.
Cheers... hope you have some luck with what you are trying to achieve.
[RESOURCES]
magisk download archive
Download Latest Magisk zip v23.0 and Magisk Manager 8.0.7 and Root your phone
On this page, we will share the full instructions to download and install Magisk zip on your Android Phone. This tutorial is also for the newbies/noobs
www.getdroidtips.com
19deke55 said:
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...
So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.
I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.
Cheers... hope you have some luck with what you are trying to achieve.
Click to expand...
Click to collapse
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.
> thus far, ive managed to get drivers and all that to mesh.
> bootloader unlock was straightforward... a few command lines
> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)
> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot
rather than reboot, i get boot loop. LOL
everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.
magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.
also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed
if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets
also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.
double b26 said:
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.
> thus far, ive managed to get drivers and all that to mesh.
> bootloader unlock was straightforward... a few command lines
> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)
> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot
rather than reboot, i get boot loop. LOL
everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.
magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.
also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed
if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets
also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.
Click to expand...
Click to collapse
Thanks. The Mediatek side of things is interesting as I have at least one Lenovo tablet that uses them and the Kindle Fire tablet I have also. Such a pain that manufacturers have went down the road of locking bootloaders the way they have. It used to be so easy to install ROMs. Oh well. C'est la vie.
Thanks for the info. I can't see me touching the Umidigi now for a couple of years. It would be more than my life's worth, lol. I'll copy the contents of your post for future reference.
Have a nice day. Hope you have success with your efforts and that your satellite connection improves.
I GOT ROOT !!
Sorry, I forgot to update this thread...
Bottom line is that there was a bug in magisk. It has since been repaired, and root procedure works 'as advertised' using magisk.zip v25.2 (25200)
After having no luck, I gave up. A few months later I tried again after reading about how magisk had a recent bug fix that sounded like it might have been the problem for this Umidigi. So, I grabbed a new build of magisk .zip, followed the tutorial, and it worked as expected. Pretty simple, once you have the resources ready. Not to mention, a windows 10 pc is all you need to get it done.
---------
My Metro by T-Mobile plan is no-cap-LTE, but doesn't have a hotspot allotment. I'm using a 'hotspot unlocker' magisk module to give me access to the hotspot. I believe it stops reporting hotspot activity back to the ISP, but I'm not sure. Regardless, I use a lot of hotspot data every month, but not a peep from the provider.
In conjunction with that, I'm running "VPN Hotspot" to tunnel hotspot traffic thru my phone's VPN connection. Otherwise, tethered data bypasses the VPN. The app is on play store and requires root.
I'm using the phones hotspot to serve data across to an old dd wrt router I have set as a repeater bridge. It runs a virtual wifi network, and other devices sign into that network. From there, behind the router, it operates as a normal home wifi network. Smart TVs, Chromecast, and all your tablet apps work as expected.
----------
I'm also running a few other modules, like viper audio. So far, so good. Really can't complain for a cheap device. It even gets decent battery life when serving data. About 10% per hour, avg running, but can go further if not running a VPN and close background apps .
---------
I'll look on the PC and see if I can compile a list of software, drivers, etc that were needed.