Any root method for the Moto G4 yet? - Moto G4 Questions & Answers

Is there a working root method for the Moto G4 (Running Android 7.0) yet?
And I'm not talking about the G4 plus...
I desperately want to break my phone free.
There must be one by now.

TheTechnoToast said:
Is there a working root method for the Moto G4 (Running Android 7.0) yet?
And I'm not talking about the G4 plus...
I desperately want to break my phone free.
There must be one by now.
Click to expand...
Click to collapse
G4 and G4 plus use the same method, flash TWRP then elemental x kernel and then you can root it With super su or magisk.
Enviado desde mi Moto G⁴ #StayUnbeaten

syverman said:
G4 and G4 plus use the same method, flash TWRP then elemental x kernel and then you can root it With super su or magisk.
Enviado desde mi Moto G⁴ #StayUnbeaten
Click to expand...
Click to collapse
Thanks for the reply! Is there a guide to do this?

TheTechnoToast said:
Thanks for the reply! Is there a guide to do this?
Click to expand...
Click to collapse
I wanted to try it but I have a problem with the bootloader that I can not unlock because my computer is the amazon version that no one could remove said ads in the latest security update NPJ25.93.14.5, if anyone knows of any solution I will be grateful .

TheTechnoToast said:
Thanks for the reply! Is there a guide to do this?
Click to expand...
Click to collapse
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting

echo92 said:
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting
Click to expand...
Click to collapse
Thanks for this. Yes, I'm okay with all of this (I've rooted my previous phones), I'm aware of the risks and stuff. I'll give this a try ?

flako72 said:
I wanted to try it but I have a problem with the bootloader that I can not unlock because my computer is the amazon version that no one could remove said ads in the latest security update NPJ25.93.14.5, if anyone knows of any solution I will be grateful .
Click to expand...
Click to collapse
Um... Could you ask questions in your own forum please? This forum is for rooting help for the Moto G4.

TheTechnoToast said:
Um... Could you ask questions in your own forum please? This forum is for rooting help for the Moto G4.
Click to expand...
Click to collapse
I think he is asking about the Moto G4 Amazon version. So he is in the right forum.

Caxref said:
I think he is asking about the Moto G4 Amazon version. So he is in the right forum.
Click to expand...
Click to collapse
Oh, okay. But even still - I think he should be asking the question individually. Not only would he get more help from people but it wouldn't detract from my post.

echo92 said:
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting
Click to expand...
Click to collapse
Thanks so much! Worked perfectly on the Moto G4.
Consider the question closed

Related

Stock update with unlocked bootloader

I have an unlocked bootloader. (Because I will probably want to root the phone in the future and want to be able to keep user data. However I don't want to root it right now because then my children will not be able to catch pokemons.) What I was not aware of is that unlocking has disqualified me from any official updates. So the question is: how can I get the latest stock version into my phone? Preferably with intact user data.
Sony seems to have pretty good support for unlocked devices. You'll just have to use an alternate route to update stock. This might help: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Edit: You could also try flashing the latest Magisk, 10.2, which provides systemless root. Delete your system su binaries and you can probably have root + PoGo. But there's another thread for that.
I was able to update with xperifirm + flashtool with intact user data.
Although the first attempt resulted in a soft brick. But I had better luck with the Linux version. Might be a driver issue I guess.
Bigfoot987 said:
I was able to update with xperifirm + flashtool with intact user data.
Although the first attempt resulted in a soft brick. But I had better luck with the Linux version. Might be a driver issue I guess.
Click to expand...
Click to collapse
Glad to hear it worked. If you look into the newest Magisk for your root solution, you should have no problems running Pokemon Go.
OK, I'm a newbie to Sony devices, so here is my question:
Let's say XC phone is on Nougat, BL unlocked, TWRP + custom Kernel installed, rooted as well. Now Sony releases a new February security update. Of course I can't install the OTA. So if I head to Xperifirm and Flashtool for a firmware upgrade, how do i proceed to preserve the custom recovery, custom kernel? I know how to keep the userdata, but i suppose root will be gone. I would like to upgrade the firmware with the least hassle, am I on the right track or is there a better/faster way?
On my z5c i flashed new firmware without any wipes, than flashed custom kernel. That's all.

Root not sticking! Need professional help.

Good evening ladys and gentlemen,
hoping you can help me with my root-not staying-problem.
I have the A2017G B09 version. I already managed to unlock my device and I had root with xposed installed.
Sounds good so far, right?
Well my problem is that after the restart that is needed to activate my xposed modules, my root went away and I couldn't get it back. After that I tried to do it again but root wouln't stick no matter what.
And yes, I did use the "reboot disemmcwp" command.
I tried to root by flashing the newest chainfire supersu 2.79, since I have newest twrp 3.0.3-1.
It would be great if you would be able to help me on my journey and maybe explain to me the difference between systemless and normal, and what magisk is since I saw that op up a few times.
Oh and please tell me from where I should start if I want to work on everything android related (roms, kernel, apps) since my semsester is nearing its end.
Thanks in advance.
Systemless root means that the /system partition is not modified, however the boot image is altered. There is much hype on this, however there still are many mods out there requiring modifications of /system. I personally do not see any advantage of it, probably because I have been using custom ROMs for years, and custom ROMs has many alterations to the /system compared to stock or pure CM or AOSP roms. However it is clear that the future goes that way and eventually most of the mods will be systemless. The advantage is that you will supposedly be able to flash OTA upgrades, however if the OTA is also modifying the boot partition, then it doesn't matter, you will not be able to flash the OTA upgrade. So the benefits of systemless mods are arguable.
Magisk is an open root. it is systemless from the beginning and any module under Magisk framework will be systemless. So far no official Magisk release (latest at this time is v10.2) is compatible with the Axon stock ROM. However, the latest v10.3-beta2 seems to fix the root injection problem. It is included in the Bad Boyz custom ROM.
There are some apps not working on root devices. They use a SafetyNet procedure to check for that, such as Android Pay or Pokemon Go. However there are ways to overcome this security check and you can enjoy root and SafetyNet compatibility either using SuperSU or Magisk, system or systemless root. the issue becomes a little tricky when adding Xposed mod framework to the mix, since the procedures to have all 3 (root, SafetyNet and Xposed) working is not that straightforward. However this is possible in the Axon 7. You can find one of my guides in the links in my signature.
Enjoy!!!!
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Try reflashing supersu don't reboot, then use terminal in TWRP to do reboot disemmcwp and see if it works. I usually use root Explorer to see if I can change /system to r/w. If it did not work go back to terminal in TWRP and try again. I have had to do it a few times to get it to work. Using adb terminal seems to work first time, terminal apps have not worked for me.
Yuujinz said:
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Click to expand...
Click to collapse
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Oki said:
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Click to expand...
Click to collapse
Wouldn't it brick my european device?
Yuujinz said:
Wouldn't it brick my european device?
Click to expand...
Click to collapse
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Oki said:
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Click to expand...
Click to collapse
Ok thanks I'll do it this evening
Or maybe not, to risky.

Moto x play rooting problem.

I have been thinking to root my Moto X Play for a long time now but I have been thinking about some things lately which are as follows:
1. Can I just Unlock the Bootloader and get root from one click root apps like Kingroot?
Cause I am afraid that TWRP or SuperSU can go wrong and bricking my phone.
2. If no, then what is the use and work of TWRP recovery and SuperSU?
3. Will I get official OS updates, like nougat update is just around the corner.
Please help me out in the above mentioned thing, any help will be appreciated.
1. Kingroot is more likely to brick your phone than TWRP and SU taken together
2. TWRP gives you some extras, like it lets you backup the whole system or flash new roms. SuperSU is under constant developement so it's generallly safer to use than one-off roots like Kingroot
3. No. Official updates (OTAs) are only available for pure stock firmware
Thanks
Can I install stock firmware after rooting?
Flamester said:
Can I install stock firmware after rooting?
Click to expand...
Click to collapse
Sure, but you will loose root. You can't have modified and unmodified firmware at the same time

Most Simple Way to Upgrade to Nougat? + Other Questions

I'm currently sitting on the stock 6.0.1 B29 ROM for my 2017U A7, which is BL unlocked, rooted (SU 2.79-SR2), Xposed, with RootSwitch working, and TWRP.
What's the most simply way for me to upgrade to Nougat while maintaining those things listed above (aside from Xposed which I know doesn't support Nougat yet)?
Would I be forced to wipe my phone after installing Nougat in order to get everything working optimally?
Are there any issues or potential problems when upgrading that I should be aware of?
Read the nougat thread in general.
lafester said:
Read the nougat thread in general.
Click to expand...
Click to collapse
I have seen this thread: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
But I was wondering there was a more simple or directly method which doesn't involve EDL mode?
Edit: Nevermind, I don't know why I was expecting a more simple method, nothing on the A7 is more straightforward than that. I'd still like to know if I should be expecting any issues and if a full wipe is needed. For that matter will my phone be wiped anyway if I install that ROM?
Cyrus D. said:
I'm currently sitting on the stock 6.0.1 B29 ROM for my 2017U A7, which is BL unlocked, rooted (SU 2.79-SR2), Xposed, with RootSwitch working, and TWRP.
What's the most simply way for me to upgrade to Nougat while maintaining those things listed above (aside from Xposed which I know doesn't support Nougat yet)?
Would I be forced to wipe my phone after installing Nougat in order to get everything working optimally?
Are there any issues or potential problems when upgrading that I should be aware of?
Click to expand...
Click to collapse
I don't see any reason that you couldn't flash the universal bootstack and modem for the U variant from the Lineage thread, and then flash the stock Nougat ROM that's posted in the BadBoyz Magisk thread. Or just flash the bootstack and modem, then flash that ROM, being that it's stock and should still allow you to pass SafetyNet.
bluestudy said:
I don't see any reason that you couldn't flash the universal bootstack and modem for the U variant from the Lineage thread, and then flash the stock Nougat ROM that's posted in the BadBoyz Magisk thread. Or just flash the bootstack and modem, then flash that ROM, being that it's stock and should still allow you to pass SafetyNet.
Click to expand...
Click to collapse
I would assume that it'd overwrite TWRP and I'd have to reinstall that again, and considering all the steps overall, that's not really any faster than jcadduono's EDL mode method.
Basically I was hoping there was a method that could just allow one package to be directly flashed and get it all done in one simple go to prevent any possible mistakes.
I said screw and installed the necessary program and drivers to flash the package with the Nougat bootloader + ROM + TWRP in EDL mode, it appears to detect properly, but I don't know if I want to go through with it until Xposed arrives. Between YouTube ads or grinding my face with a belt sander, I think the latter is less painful and horrific.
On the topic of SafetyNet, I currently pass it if I switch root off, yet Nintendo games won't install on my phone. They show as "incompatible with your device" the same as if they detect I have root. I have SUHide installed as well, but I have no idea how to check on that (where it is or how it functions for that matter). Installing the APKs from an alternate source just results in them crashing on start-up. Nintendo REALLY don't want root users playing any of their games.
Cyrus D. said:
I would assume that it'd overwrite TWRP and I'd have to reinstall that again, and considering all the steps overall, that's not really any faster than jcadduono's EDL mode method which installs the bootstack + ROM + TWRP from one package and can recover a brick.
Basically I was hoping there was a method that could just allow one package to be directly flashed and get it all done in one simple go so I don't have to do a song and dance every time I want to change my ROM. But I don't know if I can just do that with jcadduono's package because IIRC TWRP doesn't automatically install things to where they should be, you have to manually select it (recovery, etc) and that package needs to be installed to multiple locations. Or maybe I have no idea what I'm talking about it.
I said screw and installed the necessary program and drivers to flash the package with the Nougat bootloader + ROM + TWRP in EDL mode, it appears to detect properly, but I don't know if I want to go through with it until Xposed arrives. Between YouTube ads or grinding my face with a belt sander, I think the latter is less painful and horrific.
On the topic of SafetyNet, I currently pass it if I switch root off, yet Nintendo games won't install on my phone. They show as "incompatible with your device" the same as if they detect I have root. I have SUHide installed as well, but I have no idea how to check on that (where it is or how it functions for that matter). Installing the APKs from an alternate source just results in them crashing on start-up. Nintendo REALLY don't want root users playing any of their games.
Click to expand...
Click to collapse
Have been able to play Pokemon Go (my son, lol) and Fire Emblem on several Lineage based ROMs using Magisk. Can also get Android Pay to work (except for my bank currently not supporting it, but it doesn't show that I'm running any third party ROM or have my bootloader unlocked.) So, that might be the way for you to go, if you decide to try it out. As far as the EDL method, I've never tried it, but it does seem like an extremely useful tool.
Sorry went back and edited my post. It seems I was mistaken and I'd have to at least flash 2 packages by the EDL method, the TWRP package isn't the full ROM, just the bootloader and recovery. The only thing I can get working is Pokemon Go if I switch off root. Is Magisk working on the stock Nougat ROM as well?

Modifying Host File Without Root

I just ordered a Moto G5 Plus and expect delivery next week. I am not sure if I really want to root. I would be happy if I could just modify the host file to prevent ads. Is it possible to change the host file without root and still accept OTA updates? Any guidance in doing so is appreciated.
This is not possible as the hosts file lives in somewhere in the root folder or in /su
Your best bet would be to just root which is really no big deal, or use your home wifi router to block ads somehow.
MrTooPhone said:
I just ordered a Moto G5 Plus and expect delivery next week. I am not sure if I really want to root. I would be happy if I could just modify the host file to prevent ads. Is it possible to change the host file without root and still accept OTA updates? Any guidance in doing so is appreciated.
Click to expand...
Click to collapse
Or root and still apply OTA using FlashFire
GopalKaul said:
Or root and still apply OTA using FlashFire
Click to expand...
Click to collapse
I did not know it was possible to flash an update to a rooted stock ROM. With my Moto G3 I was restoring pre-root ROM, accept OTA, re-root, then re-flash rooted ROM data. Modifying the host file is my primary reason to root. I will search the G5 forum for FlashFire instructions.
MrTooPhone said:
I did not know it was possible to flash an update to a rooted stock ROM. With my Moto G3 I was restoring pre-root ROM, accept OTA, re-root, then re-flash rooted ROM data. Modifying the host file is my primary reason to root. I will search the G5 forum for FlashFire instructions.
Click to expand...
Click to collapse
It is hit and miss using Flashfire on Moto devices... sometimes it works and sometimes it doesn't, depends on what you had changed with root. Some people used it with the G 2015, but it often failed. I can't speak to the viability of it on this device though.
There is no way to modify the host file without root, period... You can use something like Adblock Browser or another browser with build in ad blocking though.
You can import host files without root with Netguard: https://github.com/M66B/NetGuard/blob/master/FAQ.md
Dunno if it can accomplish what you want though.
MrTooPhone said:
I did not know it was possible to flash an update to a rooted stock ROM. With my Moto G3 I was restoring pre-root ROM, accept OTA, re-root, then re-flash rooted ROM data. Modifying the host file is my primary reason to root. I will search the G5 forum for FlashFire instructions.
Click to expand...
Click to collapse
If you only get Adblock, fine... But if you remove system apps , then it surely wouldn't work
acejavelin said:
It is hit and miss using Flashfire on Moto devices... sometimes it works and sometimes it doesn't, depends on what you had changed with root. Some people used it with the G 2015, but it often failed. I can't speak to the viability of it on this device though.
There is no way to modify the host file without root, period... You can use something like Adblock Browser or another browser with build in ad blocking though.
Click to expand...
Click to collapse
Can TWRP be booted (not flashed) on the G5 like the G3?
MrTooPhone said:
Can TWRP be booted (not flashed) on the G5 like the G3?
Click to expand...
Click to collapse
Yes. If you have twrp.img it's just
Code:
fastboot boot twrp.img
while you are booted into the bootloader.
Excellent news. Looking forward to my new phone.
MrTooPhone said:
Can TWRP be booted (not flashed) on the G5 like the G3?
Click to expand...
Click to collapse
Yes, but as with the G3 the Bootloader must be unlocked. Remember, that simply unlocking the Bootloader will cause SafetyNet API checks to fail in Nougat without rooting with Magisk, thus breaking OTAs as well.
acejavelin said:
Yes, but as with the G3 the Bootloader must be unlocked. Remember, that simply unlocking the Bootloader will cause SafetyNet API checks to fail in Nougat without rooting with Magisk, thus breaking OTAs as well.
Click to expand...
Click to collapse
If SafetyNet API check fails, understand no OTAs, what about playstore access and updates? With the G3, even though an unlocked bootlader makes the device uncertified, the device still has full access to the playstore. I am thinking some day Google will be shutting down playstore to uncertified devices and those that fail SafetyNet API checks.
MrTooPhone said:
If SafetyNet API check fails, understand no OTAs, what about playstore access and updates? With the G3, even though an unlocked bootlader makes the device uncertified, the device still has full access to the playstore. I am thinking some day Google will be shutting down playstore to uncertified devices and those that fail SafetyNet API checks.
Click to expand...
Click to collapse
SafetyNet failure itself won't stop OTAs, but just about any modifications to boot, system, or recovery will cause a failure.
Apps will install and update, however, some apps check SafetyNet and will not function if it fails... Pokemon Go, Netflix, Android Pay, Snapchat, and most most banking and financial apps come to mind, but there are plenty of others.
I am in agreement that eventually devices that are not certified will not be allowed Play Store access, someday... But SafetyNet is only part of device certification.
I can not find a way to do it.
Overwriting the hosts file on the system with twrp does not work.
Install a zip using twrp with the hosts file, either.
There really is no way to do it without having to root?
Did you try Netguard?
Knutselmaaster said:
Did you try Netguard?
Click to expand...
Click to collapse
Using PIA with Mace enabled works as well.

Categories

Resources