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.
Just in Time for The New Year I would like to show Everyone How to root there Canadian variant LG V20!
Current Known issues
- No Service From Carrier
- Seems VERY Laggy (Can be Fixed with using a Kernel)
Other Information
- Yes you can Restore to factory Settings with this Method (So Don't worry if you screw up)
- Sorry far I Only know This works on the H915 however the Restore should work with all LG Models
- This will give you a Bootloader to have access to fastboot Commands
- Working TWRP Recovery
So After Reading the No Service Part many are mostly not going to be interested... I uploaded this Thread anyway to see if anyone could find a fix to this issue. (When one is found I will update this with the fix)
So If you still want to Root your Canadian LG V20 Let's do it!
DOWNLOAD THE ZIP FILE HERE
https://mega.nz/#!ABZV0AZZ!8LBGgpjiGT1ij6scshWTQO4tGhUb9GMUcTHtKLLhfW0
- I DO NOT TAKE ANY RESPONSIBILITY FOR YOU BREAKING YOUR DEVICE
- I HAVE NOT CREATED ANY OF THESE FILES I ONLY PUT EVERYTHING INTO ZIP FOLDER FOR YOU TO DOWNLOAD AND MAKE THINGS CONVENIENT AND SIMPLE
- PLEASE THANK THE ACTUAL DEVELOPERS WHO CREATED THESE FILES (LISTED BELOW)
FILES USED/THANK THESE PEOPLE
@me2151 Dirty Santa Files (Boot2.img, Step 1.bat, Step 2.bat and RUNMEFIRST.bat) -
HTML:
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
@jcadduono recowvery and dirtycow exploit (used with Dirty Santa)
HTML:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Stock Images for LG V20 H915 you can find those here
HTML:
http://lg-firmwares.com/lg-h915-firmwares/
(You will need to be flashed on H91510d for this to work however you could try 10e if you wanted)
@autoprime UPPERCUT for LGUP (This is what allows the LG V20 to be read and will allow you to downgrade to 10d if needed and will let you restore to stock using Download Mode at any time! This will only be used for you if you mess up with the root and need to flash back to stock or you need to upgrade or downgrade to the 10d firmware)
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
@Chainfire SuperSu v2.79 SR1
HTML:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
WHAT DO YOU NEED BEFORE YOU START
- A Copy of LGUP
- An LG V20 H915 Running the 10d Firmware (if you need help flashing this firmware read below before Step 1)
- The Zip File I Listed above to Download
- ADB and LG Drivers
- A Windows Computer
HOW TO UPGRADE/DOWNGRADE TO FIRMWARE VERSION 10d
Step 1 - Boot Your Device into Download Mode (Turn the phone off hold the Vol + Button and plug in your device to the Computer)
Step 2 - On your Computer find the Zip File (extract it) and Open Uppercut.exe (This should launch LGUP and Make sure your Phone is Connected to your Computer)
Step 3 - In LGUP Select the Upgrade button (even if you are downgrading it will still work) then find the Firmware .kdz file for 10d
Step 4 - Flash the KDZ back onto your device
ROOTING THE DEVICE!
Step 1 - Install a Terminal Emulator App to your Device
Step 2 - Verify your device is plugged in and that ADB sees the Device (adb devices)
Step 3 - On your Computer Open the RUNMEFIRST.bat (do not close this window)
Step 4 - After loading up RUNMEFIRST.bat run Step1.bat (if you see permission denied on the files Flatland and Flatland64 this is normal)
Step 5 - Once the shell prompt opens in the step 1.bat window type "run-as con" (without quotations then hit enter) then type "chmod 0777 /storage/emulated/0/*" (yet again not in quotations and then hit enter)
Step 6 - Once that has finished on your phone open the Terminal app you downloaded earlier and type in id (if untrusted_app is displayed continue if not redo the steps)
Step 7 - In the Terminal Emulator type applypatch /system/bin/atd /storage/emulated/0/dirtysanta then watch the RUNMEFIRST.bat to see when it tells u to open Step2.bat (when it tells u to open Step2.bat open it)
Step 8 - You should now Be into a Somewhat usable bootloader on your device... now we Stop using DirySanta and Start to do things manually by ourselves open up a Command Prompt and type "fastboot flash boot boot.img" this will flash the boot2.img used in the Dirty Santa Exploit
Step 9 - After that finishes type "fastboot flash recovery TWRP.img" This will put TWRP (For the H918 Variant) on your device
Step 10 - Boot into TWRP (Remove battery then put it back in hold the Vol - Button and the Power Button Once LG Powered by Android Logo Appears Release the Power Button then Hold it Again, A White screen should come up say yes to both screens then should boot into TWRP)
Step 11 - Now that you are this far I recommend you backup everything so that you can start from this point if you mess up any upcoming steps that way you do not have to reflash the stock image and start from step 1 again....
Step 12 - Select Wipe from the Main menu then go to Format Data then type yes and enter (This will remove the password lock currently enabled on the device)
Step 13 - On the Main Menu select Install browse to your SD Card where you put your SuperSU.zip File onto and flash that to the device
Step 14 - Once that is completed return to the main menu select the Wipe menu again go to Format Data then yes again
Step 15 - Go back to the Wipe Menu and go to Advanced and select Dalvik, Data and Cache then slide to wipe after this finishes reboot to the system
Step 16 - Once in the System complete the Android setup and enable USB Debugging again then type adb reboot recovery (if your device does not boot into Android this is when u go back into TWRP by doing the remove battery method and holding those buttons down as I stated before and you Restore your Backup you made in Step 11 and you try doing those Steps again)
Step 17 - Once Back into TWRP (you may make another backup here if you would like) select Install then Flash SuperSU to your device again... Go back to the Main Menu Select Wipe then Advanced and Select Dalvik and Cache then Slide to Wipe and reboot into the System
Step 18 - Once back into Android you should see SuperSU on your device and you may download a Root Checker app of the Play Store to Make sure your Device is Fully Rooted and Working!
Please inform any Issues in the Replies below and I will add them to the List for People to Know before they Attempt rooting... If anyone finds a Fix for the Modem file to get service working on the LG V20 H915 while rooted please reply and i will Add that to the guide BELOW!
I DID NOT MAKE ANY OF THESE FILES SO PLEASE THANK THE CREATORS (LISTED ABOVE) FOR THEIR HARD WORK AND EFFORTS!
I THINK I BRICKED MY DEVICE/ THE ROOT DID NOT WORK/ I WANT TO GO BACK TO STOCK
Step 1 - As Stated Above to this all we need to do is Enter Download Mode (Remove Battery reinsert battery hold Vol + and plug in the Device) and then run the UPPERCUT.exe File
Step 2 - Select Upgrade browse over to your kdz file and select it then flash it to your device! Your Device Should boot up into Android (I Have Bricked my LG V20 Many Times Removing TWRP and the Bootloader and having nothing but the LG Logo and the Download Mode and I could Still get into the Device after doing this so it should work for you! However any problems should be dealt with the developer on his forum listed here
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
)
Anyone willing to Try installing things like Kernels and ROMs I would assume you would be using H918 Supported Files For those as thats what TWRP is running in.....
Will be adding a Zip File will all the Files need in a Couple of Minutes....
There seems to be a hidden settings menu on our Devices in which we can play around with the Modem Settings among other things.... you need to open the Phone App and Type in *#546368#*915# and the menu should come up.... Maybe somebody can figure out how to get Service running.... All Credit for this goes to @KedarWolf in his post listed here https://forum.xda-developers.com/v20/how-to/access-hidden-menu-h915-t3515098
Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet
markbencze said:
Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet
Click to expand...
Click to collapse
Yes the Wind H915 still haven't got it figured out yet hopefully someone will soon then we will have an official working root for the Canadian Variant
I would have jumped on the Freedom Mobile (formerly Wind) deal ($30 for 6GB for the first 10 months) if the H915 had been root and has an unlocked bootloader. LG's track record of offering unlocked bootloader is looking very bleak for the H915.
@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.
Emilius said:
@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.
Click to expand...
Click to collapse
Sorry i should mention that a Kernel fixed this issue for me!
TheDantee said:
Sorry i should mention that a Kernel fixed this issue for me!
Click to expand...
Click to collapse
Service issue or laggy part?
Emilius said:
Service issue or laggy part?
Click to expand...
Click to collapse
Laggy Part
Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,
SHABBA JOTS said:
Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,
Click to expand...
Click to collapse
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....
TheDantee said:
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....
Click to expand...
Click to collapse
So SuperSU messed the service reception? Not bootloader?
Emilius said:
So SuperSU messed the service reception? Not bootloader?
Click to expand...
Click to collapse
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?
TheDantee said:
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?
Click to expand...
Click to collapse
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?
Emilius said:
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?
Click to expand...
Click to collapse
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol
TheDantee said:
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol
Click to expand...
Click to collapse
He he, I am an Nexus person. I am so afraid to mess up my V20. With Nexus it is so easy, in 2 steps you are done. I miss that part I mast say.
Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?
markbencze said:
Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?
Click to expand...
Click to collapse
It's look like H915 dues not have bootloader at all.
Emilius said:
It's look like H915 dues not have bootloader at all.
Click to expand...
Click to collapse
Well it has to have a bootloader. It's just locked right. Like if we pulled apart the stock kdz we should be able to find it and my theory is we could use flashfire to flash stock recovery and also flash thr bootloader since twrp can't to my knowledge flash bootloaders. We would be left with root but no recovery. I could be so far from being right but who knows. This could be the only way to have root and a working phone.
Hey guys,
I've backed myself into a corner here a little and I hope you can guide me to get a working phone again.
I was on Ephemeral Mate 8 for a while now and decided it was time to upgrade. The new ROM I wanted to try mentioned I should have at least firmware version B3XX to flash it, so I thought the easiest way to get there would be to flash a stock ROM again and let the system update function do it's work. I updated from NXT-L29C432B180 to B192 to B560 to B581 (no B3XX offered in between) and somehow managed to get the phone rooted again. Yet I noticed some things (like Bluetooth) not working quite properly anymore (for whatever reason) and so wanted to downgrade again.
Tried to restore one of my old backups from Ephemeral Mate 8: it failed. The backup from stock B581 I made before: no idea where it was stored, but I can't find it anymore and may have accidentally deleted it by now. Currently it seems I don't have any OS installed anymore.
I still have an unlocked bootloader and can access it by pressing power + volume down and can flash a custom recovery via Fastboot (the one I'm currently trying with is this one). However, no ROM I try to flash or backup I want to restore will work anymore, they just fail with varying errors like error 7 or invalid zip file. At some point I tried to wipe almost anything I could before every new try to flash anything (probably a very bad idea), because I thought a clean start would somehow resolve some of the various errors TWRP was throwing at me - obviously it hasn't. I also tried installing the same stock ROM like the first time via dload method, but it always says there is an incompatibility with my current version (probably that I don't have one anymore by now) and fails.
Sadly, I can't remember anymore what everything I tried to flash in between to try and get it working again or where I found it, because it simply is too much. But I'm willing to provide any information I'm able to achieve and try any steps you tell me to get it working again. I'd be very grateful for any help on this and already thank you in advance for any advice.
Sooo... in the meantime I followed this guide and got my phone working again. However, I'm facing another problem now:
When I try to flash TWRP I always get this error and can't find out what it means and how to fix it:
Code:
target reported max download size of 471859200 bytes
sending 'recovery' (17280 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.454s
Maybe it's related to that somehow the Serial Number of my device has changed in the process? It's now just '0123456789ABCDEF'. I read about fixing it with HCU Client tool, but when trying to repair the Serial Number it just gives me this error:
Code:
2017-06-23 13:11:36.503 Autodetect COM port and phone type start!
2017-06-23 13:11:36.509 Compatible COM ports not found!
2017-06-23 13:11:36.513 ERROR!
Phone not found !
I don't know how to proceed, but don't want to be stuck with stock rom. Any suggestions?
Okay, image verification error obviously had something to do with the B320 rom I flashed. Tried B192 now and recovery flash with fastboot goes through with OKAY... Just that the phone doesn't boot into recovery - it just sits there stuck on boot screen.
Would still be thankful for any hints.
Patneu said:
Okay, image verification error obviously had something to do with the B320 rom I flashed. Tried B192 now and recovery flash with fastboot goes through with OKAY... Just that the phone doesn't boot into recovery - it just sits there stuck on boot screen.
Would still be thankful for any hints.
Click to expand...
Click to collapse
I read somewhere that once you are on EMUI 5 you can't go back to 4. The rollback works to 4.1 which is where I am now with C636B330 but that's it. No further. I was advised to use the DC Phoenix tool and go to 330 which thankfully worked! Do the same and you should be ok I guess.. 4.1 or 5.
I think I'm just going to have to wait for someone like kang to do a Rom based on one of those before I try custom. Unless there already is one? Next time I flash a phone I should really research the pitfalls. That would avoid a week of using a different device!
Bearded_1 said:
I read somewhere that once you are on EMUI 5 you can't go back to 4. The rollback works to 4.1 which is where I am now with C636B330 but that's it. No further. I was advised to use the DC Phoenix tool and go to 330 which thankfully worked! Do the same and you should be ok I guess.. 4.1 or 5.
Click to expand...
Click to collapse
Thanks for the reply! I'm now back on C432B180 with EMUI 4.0 flashed with DC Phoenix and finally managed to flash a TWRP using SRK Tool.
Anything with B3XX or B5XX still just gives me the 'image verification error' mentioned above for any custom recovery and I doubt it would be any different with SRK Tool since it also just makes use of fastboot as it seems to me. So I'm staying with B180 for the moment unless someone has a suggestion on how to get rid of this error.
I'll now try to flash Ephemeral Mate 8 again, since it was the first (and last) custom ROM that worked for me before. I know it's discontinued, but it's the only one I can currently find that doesn't mention to go to B3XX first - which wouldn't work for me.
What worked and didn't work so far:
Tried flashing EM8_41816_SIGNED.zip, which failed without warning and rebooted to fastboot mode mid-process which showed some error involving the word 'panic'.
Managed to root the stock B180 again with SRK Tool, but will continue to try earlier versions of Ephemeral 'cause I really need the Kang Tools. Will update on how that worked out.
Suggestions still welcome on:
How to get rid of 'image verification error' on B3XX and B5XX' so I can try flashing a non-outdated ROM.
Other still available pre-B3XX ROMs I could try.
Any root apps to achieve navbar and status bar modifications similar to Kang Tools, so I could do without a custom ROM and stay with currently achieved rooted stock ROM.
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.
YEEESSS!!! :victory:
Tried flashing EM8_40416_SIGNED.zip now and went through without errors. Took a few seconds to reboot and it works! Just B170 now it seems, but hey...
My quest to upgrade may have failed graciously, but at least I got a working rooted phone again with Kang Tools - what more can I ask for? And unless someone, somehow, somewhen has a hint for me about this damned 'image verification error' (at least I now know a foolproof way to fix it if I mess anything up again) I'm taking this cautionary tail to heart and won't touch this damned phone's firmware again 'til it turns to dust under my fingers.
And now, as common courtesy commands, my exact steps - from having completely messed up with nothing save stock recovery and fastboot mode working anymore to functioning phone again with root, cutom ROM and Kang Tools - for the sake of the poor souls of the future who may (hopefully not) follow in my footsteps facing the same problems (no guarantees or responsibility whatsoever on my part, just what worked for me):
1. Reboot your phone into fastboot mode (bootloader) by pressing and holding power + volume down together (don't forget to connect the phone to a PC before!). As always, make sure you have enough battery power left before each step! If you don't at this point, try booting into stock recovery by holding power + volume up and charge your phone, then continue.
2. Download:
2.1: DC Phoenix from here. Found here via here.
2.2: File with partition rework and factory firmware from here. Found here.
2.3: NXT-L29C432B180 stock ROM from here (you may need a different version depending on your device!). Found here. (Stock ROMs B3XX or higher may work too, but didn't for me - see above).
3. Buy 15 credits here to use DC Phoenix (it's worth it!), unpack and start DC Phoenix and login with your DC-unlocker credentials. (Edit: If you want to try the new guide mentioned below from step 5 onward, you should consider buying the 'DC-Phoenix + HCU timed license' option for 19 bucks instead.)
4. Follow this guide. You find the mentioned 'UPDATE.APP' file in the stock ROM ('update.zip') file you downloaded before.
5. You should have unbricked your phone and have a working stock ROM again by now. :fingers-crossed: Now on to getting a custom ROM again:
(Edit: I fiddled around with my phone a bit more in the meantime, so if you prefer flashing a TWRP on a B5XX-based stock ROM and finding your way from there, you may want to follow this new guide instead.)
6. In the settings of your phone enable 'Developer options' -> 'USB debugging' if you haven't already (and 'Enable OEM unlock' too just to be sure, don't know if it's necessary, but I did it). If you don't see 'Developer options', tap on 'About phone' -> 'Build number' a few times. Connect phone to your PC.
7. Downloads:
7.1: SRK Tool from here. Found here via here.
7.2: Ephemeral Mate 8 from here. Found here via here. (Later version or other ROMs may work for you, but didn't for me.)
8. Move 'EM8_40416_SIGNED.zip' file (or the one you want to flash) to the external sdcard of your phone.
9. Unpack and start SRK Tool.
10. Select '3. Install Recovery 6.0' -> '2. Huawei Mate 8' -> '2. Install Mate 8 TWRP for Marshmallow (EMUI 4.0)' (may depend on the stock ROM version you flashed before). Confirm requests and follow the instructions.
11. Your phone now reboots. Remove the USB cable connecting it to the PC and press and hold power + volume up to boot into the newly flashed custom recovery.
12. Select your language (it was chinese later on for me, when I didn't!) and press 'Cancel' if asked for a password. When asked to allow changes to system, do it (don't know if necessary, but I did).
13. Select 'Wipe' -> Swipe to Factory Reset'.
14. Go back and 'Format Data' -> type 'yes' and confirm. Reboot the phone and enter custom recovery like before. Factory Reset again. (Don't know if this step is necessary, but I did it.)
15. Go back and select 'Install' -> select and flash the zip file you moved to sdcard before. If no errors occured, reboot your phone. Let it reboot, it may take a few seconds. If you get errors, try starting with step 1 or 11 again (depending on how badly you messed up...) and try a different custom ROM (Follow the instructions there and be aware of prequisites and warnings!). If that doesn't work either, note your errors and ask for help - good luck!
16. Congratulations, you should have a working phone again with Ephemeral Mate 8 custom ROM with Kang Tools, it should be rooted already. :good:
17. Maybe buy the guys, who developed and wrote the mentioned tools and guides to help you on your way, a coffee - they surely deserve it.
Hint: If you only want a rooted stock ROM, reboot your phone after step 12, start SRK Tool again, select option '4. Root' and follow instructions.
Patneu said:
Thanks for the reply! I'm now back on C432B180 with EMUI 4.0 flashed with DC Phoenix and finally managed to flash a TWRP using SRK Tool.
Anything with B3XX or B5XX still just gives me the 'image verification error' mentioned above for any custom recovery and I doubt it would be any different with SRK Tool since it also just makes use of fastboot as it seems to me. So I'm staying with B180 for the moment unless someone has a suggestion on how to get rid of this error.
I'll now try to flash Ephemeral Mate 8 again, since it was the first (and last) custom ROM that worked for me before. I know it's discontinued, but it's the only one I can currently find that doesn't mention to go to B3XX first - which wouldn't work for me.
What worked and didn't work so far:
Tried flashing EM8_41816_SIGNED.zip, which failed without warning and rebooted to fastboot mode mid-process which showed some error involving the word 'panic'.
How to get rid of 'image verification error' on B3XX and B5XX' so I can try flashing a non-outdated ROM.
Any root apps to achieve navbar and status bar modifications similar to Kang Tools, so I could do without a custom ROM and stay with currently achieved rooted stock ROM.
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.
Click to expand...
Click to collapse
Isn't the FRP related to the 'enable oem lock' option? Glad it's sorted! I might follow this thread in the future to go back to pre EMUI 4.1, but I like the camera options so willing to stick with it for a while!
Hey, I didn't realized, I have the 0123456789ABCDEF serial number too, I'm on B330, after unbricking it with DC phoenix (flashed directly from the "Factory_firmware.." for unbrick it, to B330). Did you solve that?
I think I cannot do much now because I'm waiting for the 14 days using my HW account to request de bootloader unlock code. Altough, my phone says I have the bootloader unlocked (that's because the DC phoenix tool did something). But I've never formerly unlocked my phone.
Don Kronos said:
Did you solve that?
Click to expand...
Click to collapse
Well, sort of... I'm still on this fake ABC... Serial Number, but as you can read above, I at least managed to flash a TWRP again and also to install a custom ROM, if only a B1XX based. Better than nothing, though. Didn't encounter any other downsides of the changed Serial Number 'til now.
If you have a hint concerning the 'image verification error' I'd still be glad to hear, but otherwise I'm fine now.
Patneu said:
If you have a hint concerning the 'image verification error' I'd still be glad to hear, but otherwise I'm fine now.
Click to expand...
Click to collapse
Patneu said:
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.
Click to expand...
Click to collapse
The FRP (Factory Reset Protection) prevents some "writing" commands of ADB to be executed, thats the reason of the "image verification error". It is the homologue to an iCloud protection of iPhone, but using Google Account. I don't know why it gets locked.. but the DC phoenix can crack that protection.
Don Kronos said:
The FRP (Factory Reset Protection) prevents some "writing" commands of ADB to be executed, thats the reason of the "image verification error".
Click to expand...
Click to collapse
Sounds right, aside from the fact that my FRP doesn't seem to be locked. When I flashed B320 via DC Phoenix or flashed B1XX and updated to B560 via OTA and booted into fastboot mode, it said there "Phone unlocked" and "FRP unlocked". I shouldn't get the 'image verification error' then, right? But I do. If I flash B1XX via DC Phoenix, it says nothing about FRP, whether locked or unlocked, just "Phone unlocked" and I don't get 'image verification error'.
I remember getting a TWRP to flash when I updated from B180 (flashed with the TWRP I had before) to B581 OTA before I used DC Phoenix (even if it threw errors like nothing good), but I don't remember if it said anything about FRP then.
Don Kronos said:
I don't know why it gets locked.. but the DC phoenix can crack that protection.
Click to expand...
Click to collapse
Yeah, it seems so, but it can't flash a custom ROM, can it? Only 'UPDATE.APP' of stock ROMS as far as I can see.
Patneu said:
YEEESSS!!! :victory:
And now, as common courtesy commands, my exact steps - from having completely messed up with nothing save stock recovery and fastboot mode working anymore to functioning phone again with root, cutom ROM and Kang Tools - for the sake of the poor souls of the future who may (hopefully not) follow in my footsteps facing the same problems (no guarantees or responsibility whatsoever on my part, just what worked for me):
Click to expand...
Click to collapse
You just saved my fuc**ing ass bro. Thanks a lot for such detailed steps. I was another prick who got his device bricked. I also fhashed a buch of things and lost track on the number of solutions tried until I came across your post:fingers-crossed: Now i feel solid again and want to continue flashing and messing up with my device. That´s the beauty of android, you can recover your device from almost any state. Thanks a lot. You made my day!
The process really work and it's really easy. Those 15 bucks are worth every penny!
juanq214 said:
The process really work and it's really easy. Those 15 bucks are worth every penny!
Click to expand...
Click to collapse
Glad, I could help you and yeah, they surely are.
Just a few remarks I discovered in the meantime:
- If you want to further mess with your phone after that, be sure to not mess up so badly as to having to use DC Phoenix again, unless within the next 72 hours or you'll have to pay the 15 bucks again (as mentioned here). Other claims made there about "lifetime" are not legit.
- Tried EM8_41816_SIGNED version of Ephemeral Mate 8 (based on B180) again and it works, too. The failure and mid-process 'panic' reboot at first try was caused by unrelated battery (hardware) problems of my device (which I think already started before messing with the firmware), which caused me to think I had more power left than I actually did. :silly:
I solved the battery problems by replacing the battery using this guide, ruining some cheap repair kit, made of too much plastic, in the process and paying altogether around 40 bucks for it and for now, everything runs fine again. :good:
Patneu said:
Glad, I could help you and yeah, they surely are.
Just a few remarks I discovered in the meantime:
- If you want to further mess with your phone after that, be sure to not mess up so badly as to having to use DC Phoenix again, unless within the next 72 hours or you'll have to pay the 15 bucks again (as mentioned here). Other claims made there about "lifetime" are not legit.
- Tried EM8_41816_SIGNED version of Ephemeral Mate 8 (based on B180) again and it works, too. The failure and mid-process 'panic' reboot at first try was caused by unrelated battery (hardware) problems of my device (which I think already started before messing with the firmware), which caused me to think I had more power left than I actually did. :silly:
I solved the battery problems by replacing the battery using this guide, ruining some cheap repair kit, made of too much plastic, in the process and paying altogether around 40 bucks for it and for now, everything runs fine again. :good:
Click to expand...
Click to collapse
I successfully got OTA for L29C432B581. I don't really care much about xposed or magic, all I needed was Nougat update. The only downside is that fast charging is gone, but that is not because of the brick but rather a bug related to the update.
Everything fixed.
Ok, so I'm a little late on this, but because some recent circumstances forced me to mess with my phones firmware again - despite my former new-found resolutions :angel: - I dug into this mess again and finally found the solution for the last unsolved problem I encountered: the dreaded 'image verification error'. So I thought, I'd share it with anyone else out there, who may still be struggling:
If you followed my original instuctions, maybe you got stuck at the same point I did: I originally wanted to install a more recent custom ROM based on Android Nougat, but couldn't for the hell of it flash a working TWRP, because of 'image verification error', when I was on a stock Nougat ROM (B5XX-based) and finally settled for my old B1XX-based Ephemeral Mate 8 ROM once more.
So here's what I did to get a working TWRP flashed with a B5XX-based stock ROM (again, no guarantees, just what worked for me):
1. Depending on how badly you messed up before or at what point you currently are, first you may want to follow some of my original instructions 'til step 5. (All links are still working, as far as I can see.) You then should be good to go with a working B1XX-based stock ROM as a basis for what where going to do now. :fingers-crossed: If you already are, great. :good:
1.1: Attention! If you don't already have a working B1XX-based stock ROM, you may want to slightly differ from my original instructions: instead of buying the 15 credits for DC Phoenix in step 3, you could directly choose the "DC-Phoenix + HCU timed license" option for 19 bucks, so you're already set for everything we're doing later and can mess with your phone as much as you want for the next 72 hours - it may come cheaper in the end and it's easier in any case.
1.2: You may notice afterwards, that if you start adb and type 'adb devices', that the serial number of your device changed to something generic like '0123456789ABCDEF'. We'll fix that later on, along with the 'image verification error', but be sure to note your devices original S/N! You can find it on a sticker at the side of the box your phone came in or in the phones 'Settings' -> 'About phone' -> 'Status' -> 'Serial number'. I don't know where else to recover it, if you lost it.
2. Once you have a working B1XX-based stock ROM as a basis, update it to the latest B5XX-based one (was B582 for me) via 'Settings' -> 'System update'.
2.1: Attention again! You may want to check 'Developer options' -> 'Enable OEM unlock' first, since it was greyed out (while still checked) for me once I updated to B5XX. Don't know if it's necessary to have it enabled, but better safe than sorry so you don't have to start over. (If you don't see 'Developer options', tap 'About phone' -> 'Build number' a few times.)
3. Download:
3.1: HCU Client from here. (Thanks Petr S. for putting me on the right track!)
3.2: Unofficial TWRP for EMUI 5.X from here. Found here. (Official TWRP versions may work for you, but didn't for me.)
4. If you didn't already, buy a sufficient number of credits (don't know how much it will be) to use HCU Client from here or directly choose the "DC-Phoenix + HCU timed license" option for 19 bucks to get the all-round carefree package.
5. Unpack and start HCU Client and login with your DC-Unlocker credentials.
6. Connect your phone to your PC and enable 'Developer options' -> 'USB debugging' (don't know if necessary, but I did).
7. As instructed by HCU Client, type '*#*#2846579#*#*' (minus the quotes) into your phones dialer and select '1. Background Settings' -> '2. USB Port Settings' -> 'Manufacture Mode'. If your phone should be rebooting somewhere in the process, you may need to do this again.
8. Now click 'Read phone info' in HCU Client ('Autodetect' should be checked already) and wait for it to complete. (If you didn't buy a sufficient number of credits or the mentioned license before, HCU Client will simply get stuck instead of just telling you - which I found a little odd. )
9. Click 'Repair UMTS' (acknowledge the warning) and type the original serial number of your device (not the '0123456789ABCDEF' one!) into the 'SN' textfield, check it and hit 'Repair'. (I also retyped the 'IMEI' and 'IMEI 2' numbers, but I guess that was unnecessary.)
10. If now you hit 'Read phone info' again, all the textfields under 'Repair UMTS' (except 'WiFi MAC' and 'Bluetooth MAC') should be filled with the right values. Then click 'Unlock' -> 'Read Bootloader code', note the bootloader code. Your phone will shutdown.
11. Power up your phone again, make sure 'Settings' -> 'Developer options' -> 'USB Debugging' and 'Enable OEM unlock' are still checked and bring it into fastboot mode, then open a command prompt and cd to where your 'Minimal ADB and Fastboot' (or whatever you're using) is installed, if you didn't already, and type 'fastboot devices'. You should see your device with the original serial number again.
12. Unlock your device again with the command 'fastboot oem unlock ' followed by the bootloader code you noted before. Now you should be able to flash the unofficial TWRP you downloaded with 'fastboot flash recovery twrp-3.1.1-1-next.img' (assuming you copied the TWRP image file to your 'Minimal ADB and Fastboot' directory for convenience and didn't rename it).
13. Type 'fastboot reboot' and immediately bring your phone into recovery mode. You should now have a working TWRP with a B5XX-based stock ROM and should be able to flash anything you'd like. :fingers-crossed::good:
You should also be able to flash a Nougat-based custom ROM now, though I didn't try that and settled for the stock ROM rooted with Magisk for personal reasons.
A last word of warning: Be sure to frequently make backups in TWRP before you flash or change anything important like installing or updating Magisk or Xposed modules, because I noticed my system to be a little... wonky at this point.
Don't know if that's related to the way I unbricked my phone with all these DC-unlocker tools or just using Magisk or whatever, but several times after changing something important and rebooting, my phone kind of crashed into fastboot mode with some warning about 'native_boot_fail' and wouldn't boot again until I made a factory reset in recovery and started all over (the first time while writing this guide :silly. Not so bad, as it doesn't happen randomly as long as I don't make any major changes to the system, but you wouldn't want to retype your Google password and setup your system again everytime like I had to do, would you? So, yeah, just make a backup in TWRP before you change anything root-related - and tread a little lightly, as in: don't make to many changes at once - and you should be fine.
Hi guys
Hope all are well. I really really need someone to help me with a todo guide to get this done.
I phone is currently using the latest June security Patch (Odin Flashed) One UI 2.1
I am so confused about the instructions on various sites and youtube. The Videos on there is about 6 months old. I tried installing TWRP via a guide i saw online, but could not get it done.
Now when my phone starts i get a bootloader unlocked warning message. This is fine. it still boots into Android 10, and is perfectly usable. Can someone who did this, please point me in the correct direction? I tried last night for hours, could not get it done.
The sequence of events etc are all different on the sites, and some does not make sense.
I hope i can actually do it on this version, as i see alot of the threads are April 2020'ish,
Thank you so much guys!
Hi guys...
No one? I will be so grateful
^^rac said:
Hi guys...
No one? I will be so grateful
Click to expand...
Click to collapse
Me too, have asked in here before but no takers. As someone who is new to android I just new a plain step by step guide too. I have same device as you on latest June update.
Sent from my SM-G970F using Tapatalk
^^rac said:
Hi guys...
No one? I will be so grateful
Click to expand...
Click to collapse
I just stumbled across your question by mistake, you need to search and ask questions in the appropriate threads and you will get help.
Lineage s10
https://forum.xda-developers.com/ga...rom-lineageos-17-1-beta0-s10e-update-t4076585
Magisk
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
Twrp
https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
Philnicolls89 said:
I just stumbled across your question by mistake, you need to search and ask questions in the appropriate threads and you will get help.
Lineage s10
https://forum.xda-developers.com/ga...rom-lineageos-17-1-beta0-s10e-update-t4076585
Magisk
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
Twrp
https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
Click to expand...
Click to collapse
Thank you. I have seen instructions OK but they all assume that reader has a basi understanding of jargon and steps to take. I want to root, I guess it's called, but just need a step by step of what to do.
Sent from my SM-G970F using Tapatalk
17-apg said:
Thank you. I have seen instructions OK but they all assume that reader has a basi understanding of jargon and steps to take. I want to root, I guess it's called, but just need a step by step of what to do.
Sent from my SM-G970F using Tapatalk
Click to expand...
Click to collapse
Check out this guide from the TWRP thread, it might be good to read the first page or two of the twrp thread aswell so that you dont miss any important info. Also make sure that you get the right TWRP file for your specific firmware version. Good luck
PiCkLeS said:
By clicking on the button below you will get a set of instructions, step-by-step, on how to install Ians excellent work with TWRP as a recovery for your device and John Wu's root via Magisk.
This is not the fastest or most uncomplicated tutorial to do this. It is, however, made to make sure as many as possible succeed. So if you feel that a step or two is uncessesary, this tutorial is probably not for you since you most likely already know enough to just go by Ians more direct instructions. So dont PM me with tips on how to simplify these steps, I already know about that and that is not the point of the tutorial.
The instructions are intended for:
The user that either is completely new to this world but have managed to get an unlocked bootloader beforehand
The user that just want to have some instructions to follow to not forget a step in the process
Please note that the tutorial should work just fine for the S10E-device, but there might be another set of key combinations for your device, please take care to understand what you need to do in specifics to do the same presses of buttons.
It is strongly encourage to flash lates stock firmware and do a complete clean system install before using this tutorial. However, if you know what you are doing, it will work fine with an already rooted system as long as you have the latest Canary build (both magisk and magisk manager) on your device when patching the TWRP-image and the firmware AP-file per instructions below.
Where ever you decide to start, know that your device will be wiped and you need backups for your relevant data before you begin.
These instructions are ...
.. an "add-on" till John Wu's Magisk solution that will make your device rooted with Magisk and having Ian Macdonalds TWRP-recovery
.. for those who have already an unlocked bootloader - DO NOT attempt this without first making sure you have "OEM Unlocked" enabled
Step-by-step guide:
A) Follow John's instructions HERE until you get to step 5, then return here
B) Download latest TWRP-image by Ian Macdonald for your type of device in the first post in this thread
C) Download latest multidisabler-zip by Ian Macdonald and copy it to your SD-CARD - download here
D) Copy the TWRP-image to your device and do the same as you did with the AP-file in Magisk Manager (Install->Install->Patch file and choose the TWRP-image)
E) Copy the patched TWRP-image and magisk_patched.tar to your computer
F) Rename the patched TWRP-image to "recovery.img" on your computer
G) With your own choice of program on your computer, open the "magisk_patched.tar"-file, remove the existing recovery.img and replace it with your newly patched recovery.img and save the tar-file
H) Boot your device to download mode
I) Go back to John's instructions and IGNORE step 6 and DO step 7 and come back here!
J) We now need to factory reset our device:
-> Press Power + VolDown for a few seconds to get out of download mode
-> AS SOON AS THE SCREEN GOES BLACK: Press Power + Bixby + VolUP and HOLD THESE KEYS FOR A LONG TIME until you see the bootlogo of TWRP, then release the keys
K) In TWRP, install your downloaded multidisabler-zip from your SD-CARD and DO NOT REBOOT
L) In TWRP, format data (not only wipe, choose specifically "Format data" and write "yes" and go ahead and after DO NOT REBOOT
M) In TWRP, go back to the start screen - choose "Reboot" and choose "Recovery" AND NOTHING ELSE - DONT touch any keys on the device
N) Go back to John's instructions and begin from step 12
O) All done - you know have a rooted device by Magisk, with TWRP as recovery - enjoy and be sure to thank Ian Macdonald for the help with TWRP and John Wu for Magisk root!
Click to expand...
Click to collapse
And here comes another I bricked my phone 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!