Related
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to 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 G3/4, 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 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. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
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. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
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. 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.
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.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
I have an at&t variant HTC m8, I recently stitched to cricket wireless. SIM swap went fine. I've been wanting to gain root to remove att bloatware. I'm on android version 5.0.2. My main issue is I've gotten nowhere unlocking boot loader using a pc. Tonight I resorted to using kingroot from Google play,which worked on third attempt. However supersu said it needs an update.
So basically I'm lost and trying to find away to gain root without a computer if possible.
I've never used kingroot. What happens if you try to update the root binary?
May be a bit irrelevant. I think you'll need to unlock the bootloader to do what you want (delete bloatware). I don't think kingroot alone will get it done. Reason being, you can't modify the system partition with root alone. You need kernel mod wp_mod, which is flashed with custom recovery TWRP. And you need an unlocked bootloader to flash custom recovery.
What issues did you have exactly when trying to unlock the bootloader?
I believe my main issue was that my pc is out of date running an unauthorized widows 7 lol. I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution. I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Lewis715 said:
I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution.
Click to expand...
Click to collapse
Not sure what "unable to obtain adb" means if you don't explain what happens exactly, where you are trying to get the files, etc. So all I can do is assume, and hope that I don't suggest you do things you already tried.
If you want an adb/fastboot installer, the following should work, and decently up to date: http://forum.xda-developers.com/showthread.php?t=2317790
Otherwise, there are other adb installers if you just type "easy adb" into the XDA search function.
No such thing as TWRP files that can help you unlock the bootloader. By definition, you can't install custom recovery until the bootloader is unlocked, and TWRP is a custom recovery. So nothing can be done with or by any TWRP files until you unlock the bootloader.
Lewis715 said:
I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Click to expand...
Click to collapse
Again, can't really help with what is "conflicted" unless you give some specific details.
Its understandable that a lot of the threads may be confusing, as the info is often outdated. This is getting to be an old device, and a lot of folks that wrote the various guides have moved on, and not updating the guides.
The following is a pretty good AT&T specific guide: http://forum.xda-developers.com/showthread.php?t=2799796
But as mentioned, some things are outdated:
1) The driver package is old. You can get updated drivers by downloading HTC Sync from the HTC website. After installing (which will also install HTC drivers) you can uninstall Sync, but keep the drivers; if you don't want Sync (but I haven't had any problems keeping it).
2) I believe the Dropbox link for adb installer is dead, but I already gave an alternative above.
3) The TWRP version is really old, don't use it! Get TWRP 3.0.2 from here: https://dl.twrp.me/m8/
The exception might be in the stock Android version on your phone is old, but if you tell me what it says for OS number on the bootloader screen, I can advise more specifically.
4) TWRP version is old, again, don't use it! v2.76 is the latest "stable" version, and you can get it here: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Everything else in the guide should still apply.
Vomer's guide is also a good one:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Again, the TWRP version is out of date (use the current one linked above).
You only need to do Sections 0 and 1, as the remainder of the guide (S-off, SuperCID) doesn't apply for what you are doing (unlock bootloader, custom recovery, and root).
Also, highly recommended to make a TWRP backup of the stock ROM, before you root.
After root, flash wp_mod with TWRP to enable system partition changes to stick (and deleting bloatware is a system change). What wp_mod depends on your Android version. But for Marshallow, the wp_mod can be found here (you just need the zip wp_mod, not the whole ROM): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Lewis715 said:
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Click to expand...
Click to collapse
Of course, the vast majority of us don't have any real need to mess with the device. But we do, nonetheless!
I'm creating this thread because I saw no mention of how to get Pixel Launcher installed as a system app without root. I've tried this using npf10c on the 6p but it will probably work with 7.0 and other phones supported by FED-patcher.
These are the simple steps to follow in order to get it done:
1. Flash factory image from Google (latest image can be found here https://developer.android.com/preview/download.html).
2. Flash TWRP 3.0.2-3 This is very important, the latest official release will NOT work so you have to use this unofficial version (Download: https://idlekernel.com/twrp/nexus/)
3. Flash FED-Patcher v8. This is basically the key thing. What this does is patching the boot.img so that all the changes you make are not erased when you reboot from recovery into android. This is something is done during the installation process of root, and also when a custom kernel is flashed. But if we want to avoid those two scenarios, Fed Patcher is the way to go. Here is the link to the thread: http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
4. Flash Pixel Launcher zip and tweakprop in order to get the assistant.
5. Reboot.
6. Enjoy! :good:
Works!!! Finally!
I have tried all options with teh non-root Nexus6p.
The ONLY way to get GA on non-root Nexus 6p is this!! Thank you!!
Dont use the flash method with this.. Just edit the build.prop using adb.
fr33duhm said:
I have tried all options with teh non-root Nexus6p.
The ONLY way to get GA on non-root Nexus 6p is this!! Thank you!!
Dont use the flash method with this.. Just edit the build.prop using adb.
Click to expand...
Click to collapse
Glad It helped!
The twrp...
The site link provided here (idlekernel.com..) never seems to open. Any other way to grab that version of twrp recovery..? I have searched a lot but couldn't find it.
agpt8 said:
The site link provided here (idlekernel.com..) never seems to open. Any other way to grab that version of twrp recovery..? I have searched a lot but couldn't find it.
Click to expand...
Click to collapse
I found this (TWRP 3.0.2-3) in a google search and used it. Sorry for the weird link, I have less then ten posts so XDA prevents me from posting to avoid spam. This seems legit though and I used it myself successfully: androidfilehost.com/?fid=312978532265371415
This bloke on youtube thinks he has it rooted.. maybe fake though..
The fact that the video says that you cannot update Magisk as the bootloader is still locked makes me think it might be legit..
Considering it is all done within the Android OS it is probably safe to try.. you might just have to factory reset if it causes issues.
Another option?
{Mod edit: Link removed}
Looks interesting, this phone would appeal to me more if I could root it.
If the root does work then how could you unroot it or would installing updates get rid of it and you need to root again?
I think root is possible, but until now I have not been able to find out exactly whether the Fastboot is locked or not. it is my first OPPO and so I have no experience with OPPO. even if it's BBK. it's not an OP 8. We can only hope that someone might want to open it here. But from the root on youtube and other websites I would be careful. I also couldn't find any firmware for the flash via MSM tool or download tool ... so at the moment with an unbrick it is not possible to restore it.
__NBH__ said:
Looks interesting, this phone would appeal to me more if I could root it.
If the root does work then how could you unroot it or would installing updates get rid of it and you need to root again?
Click to expand...
Click to collapse
Factory reset should revert if the apps dont have revert option.
I'd like to see them show rooting an X2 Pro, rather than an A5s (CPH1909)
ordered one anyway... first phone without root in 11 years.. i hope i made the right decision.
It depends what you root for I guess. For me I currently root for adaway, viper, substratum themes and to change my font plus I recently run a module for various tweaks.
I used viper for my old wireless earbuds, I recently got new ones which sounds great without viper. Lots of apps now have a dark mode and I hear this phone has a beta mode that can turn other apps dark. Not changing font I can live with and the tweaks module is fun but not essential. Adaway I will miss. But for the first time in a while I'm not so fussed about root. I understand some people like it because you can flash ROMs when the device gets older. I survived for 18 months with a Samsung S8 plus without root so I know I can do it!
I need to decide whether to pre order the phone today or I miss out on the pre order bonus, I like it but don't think I can trade in my 7 pro, I love it a bit too much.
First and foremost adblock though you can do that without root. Second Sony Music magisk module for Android Auto. Third to debloat. 4th for some advanced Tasker tasks. I'm pretty sure I can get workarounds for most
Sage said:
This bloke on youtube thinks he has it rooted.. maybe fake though..
The fact that the video says that you cannot update Magisk as the bootloader is still locked makes me think it might be legit..
Considering it is all done within the Android OS it is probably safe to try.. you might just have to factory reset if it causes issues.
Another option?
{Mod edit: Link removed}
Click to expand...
Click to collapse
I don't see how this can be legit. The video shows a different device and also the rooting tool is for mediatek based devices. The Oppo find x2 pro is based on Qualcomm chipset.
Can anyone confirm if VMOS work this phone? It may be the only way to use root.
Never heard of vmos sounds interesting!
Yeah VMOS is like running VMware or Parellel on Mac. It's easier than rooting an actual android device, but it also gives more battery drain and less intuitive. I have it on my Mate 20 pro, does anyone know if it works on find x2 pro?
Videos been removed. I really wish this phone had working twrp and magisk it'd be literally the ideal phone
I'm just waiting for a oneplus phone with a periscope camera, that will be the one to get as it will be like this phone but with working root.
Yeah miss root. First phone in a decade I have bought without it. Though mostly I use it for adblock though private DNS works very well
Really missing root on this phone. I wish it were available considering the Snapdragon processor
EE
So far, i have been able to Enable USB Debugging and OEM Unlocking, this on the EE Network. Seems there is no TWRP Build Avail for the X2 Pro Yet. And i am unaware of any other way of Flashing the Magisk Zip Safely any other way.
I have also patched the boot IMG with magisk but there is no way to flash the file.
The recovery accepts only ozip files?
bhomie28 said:
I have also patched the boot IMG with magisk but there is no way to flash the file.
The recovery accepts only ozip files?
Click to expand...
Click to collapse
How did you manage to Patch the Boot IMG?
Thanks Man!
I download the OTA ozip file from oppo. Decrypted the ozip, extracted the boot image & patch it with magisk manager:laugh:
Easy going but how I can flash the file:crying:
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
S1nPur1ty said:
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
Click to expand...
Click to collapse
You basically have 3 choices to acquire the boot.img:
1. Payload Dumper
2. TWRP and adb
3. Download the stock boot.img for your version of Hydrogen OS (if it exists)
There are "auto root" tools out there, but not sure how they are. I personally used #2, but payload Dumper works quite well too.
Pretty sure the auto root tool on here works on any version of ROMs. But keep in mind that when you wanna perform a OTA update after root using the restore image method, the auto tool backed up the extracted stock boot image on our pc rather than letting Magisk does its normal job and store in our phone the way Magisk wants. What I mean is that we essentially lose root first and need to re-run the auto tool after each OTA update. I'm just lazy to get perform the normal methods, so I just double click on that auto tool each time and let it does its job each time I lose root after each OTA update. I remember it actually worked flawlessly and let Magisk back up the stock boot image at first, but then after some OTAs later when I messed up and reset factory settings in recovery and had to re-root my phone using the tool, magisk acts weird and stopped storing a back up boot image in the phone.
S1nPur1ty said:
Downloading through the website doesn't work, because I recently updated my firmware through OTA and I bought my OP 7T Pro in Shanghai. I am trying to root my device by using this tutorial:
watch?v=VGjYuvoBpPA <-- YouTube URL
However, I am not sure if this is the only way or if there are better ways of rooter OP 7T Pro devices without needing the payload data as described in the YouTube video. Any help is appreciated!
Click to expand...
Click to collapse
I did eventually unbrick my device, because for some reason I ended up not being able to call anymore. When unbricking, I installed the EU version and everything seems to be working fine now. However, I regret for not backing up the root data; because the Chinese version has Oneplus Roaming option where you can use internet in any country without having the need for any sim card. Also, you can record any conversations without any third party apps needed, so it's unfortunate. I wish I could install the Chinese version again, because they really were a big help in the past.
S1nPur1ty said:
I did eventually unbrick my device, because for some reason I ended up not being able to call anymore. When unbricking, I installed the EU version and everything seems to be working fine now. However, I regret for not backing up the root data; because the Chinese version has Oneplus Roaming option where you can use internet in any country without having the need for any sim card. Also, you can record any conversations without any third party apps needed, so it's unfortunate. I wish I could install the Chinese version again, because they really were a big help in the past.
Click to expand...
Click to collapse
I'm Chinese, and I can help you to download last version H2OS.