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.
Related
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
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
Hello all,
I have a P2XL but my previous phone was a N6P. I am lending it to my brother for a bit until he gets his own P2XL, I have the phone back to stock and have relocked the bootloader but am curious to know if I can root the phone so he can install Substratum, V4A and AdAway and still receive OTAs. He knows to disable the Substratum OTAs and uninstall V4A before OTA but I'd have to teach him how to sideload OTA if he wouldn't be able to receive the typical method OTA via Google/carrier.
The N6P is Google bought, being used on Tmo.
Thanks!
cwburns32 said:
Hello all,
I have a P2XL but my previous phone was a N6P. I am lending it to my brother for a bit until he gets his own P2XL, I have the phone back to stock and have relocked the bootloader but am curious to know if I can root the phone so he can install Substratum, V4A and AdAway and still receive OTAs. He knows to disable the Substratum OTAs and uninstall V4A before OTA but I'd have to teach him how to sideload OTA if he wouldn't be able to receive the typical method OTA via Google/carrier.
The N6P is Google bought, being used on Tmo.
Thanks!
Click to expand...
Click to collapse
Most likely not. Over the air updates do checks for that kind of thing including root unlocked bootloaders and modifications to the system partition. Unless you know how to go into the Manifest and override this I would suggest you leave it at full stock if you plan to use OTAs
Sent from my Nexus 6P using Tapatalk
Actually, when you do systemless root and do not modify system partition in any way (changes done via Magisk do not count), then OTA may go through, but it will remove root since it replaces boot partition with its own (and systemless root modifies boot partition instead of system). Because of this, you would have to root again after OTA.
Instructions for applying OTA if rooted using Magisk: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
back when engineermode exploit backdoor 'thing' whatever you want to call it, was still a thing i seized to opportunity to gain root access, however since then magisk hide has begun failing me and i would like to either find a way to update magisk from v14.0 safely, or to unroot completely (preferably without wiping) as this has started being problematic. I am on the latest oxygenOS update and i used this guide to root (i originaly linked it here but apparently i cant do that, it was on github, called OneplusRoot by a fella named aldur.)
If anyone can help id really appreciate it.
Thanks in advance
Since One Plus removed engineering mode I'm surprised you were able to update OOS and maintain the exploit. Why don't you just unlock your bootloader and root the proper way? Your phone won't melt if you do.
I would like to avoid wiping if possible. I too am surprised at the persistence of root after at least 3 OTAs. At this point I no longer really need root and would rather my phone run smoothly without some applications crashing or not running due to root.
bump?
gbesh said:
bump?
Click to expand...
Click to collapse
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
manor7777 said:
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
Click to expand...
Click to collapse
Well my system doesn't boot with root. I have to manually mount something and start the magisk service.
Which is why I'm not sure how to update as I've been told the updated version has a different file structure that the one I'm on.
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
yohouse2 said:
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
Click to expand...
Click to collapse
no unfortunately i am still waiting for a solution.
gbesh said:
no unfortunately i am still waiting for a solution.
Click to expand...
Click to collapse
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
yohouse2 said:
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
Click to expand...
Click to collapse
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
gbesh said:
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
Click to expand...
Click to collapse
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
yohouse2 said:
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
Click to expand...
Click to collapse
After one of the recent updates, magisk hide started working again and my apps are no longer crashing. It is strange but i guess this situation has turned out favourably after all.
I have a stock xt1766, which I use primarily as my kid's Pokemon Go phone. That app is often updated to detect root (despite Magisk), so I need to remain unrooted. But I need to install one app as a system app.
Is there a way to do this without rooting, or, if I do root the device and install my system app, is there a way to de-root and retain the system app? I recall there was a method called "kingo root" or something, but not sure if it's trused of effective on this device...
Currently on NCQS26.69-64-5, getting prompted to install NCQS26.69-64-8.
Thanks for any advice!
Mike
resarfekim said:
I have a stock xt1766, which I use primarily as my kid's Pokemon Go phone. That app is often updated to detect root (despite Magisk), so I need to remain unrooted. But I need to install one app as a system app.
Is there a way to do this without rooting, or, if I do root the device and install my system app, is there a way to de-root and retain the system app? I recall there was a method called "kingo root" or something, but not sure if it's trused of effective on this device...
Currently on NCQS26.69-64-5, getting prompted to install NCQS26.69-64-8.
Thanks for any advice!
Mike
Click to expand...
Click to collapse
You might be able to root with magisk, install your system app, then use fastboot to flash the stock boot.img. which could unroot your phone. But it may not be able to boot because of dm verity or even forced encryption. Kingroot will not work on this device, and is most certainly not to be trusted since it sends your device info to unknown Chinese servers. The only way to successfully unroot, that I know of, is to flash the stock firmware. Which, of course will remove any system changes.
So, short answer, not likely.
madbat99 said:
You might be able to root with magisk, install your system app, then use fastboot to flash the stock boot.img. which could unroot your phone. But it may not be able to boot because of dm verity or even forced encryption. Kingroot will not work on this device, and is most certainly not to be trusted since it sends your device info to unknown Chinese servers. The only way to successfully unroot, that I know of, is to flash the stock firmware. Which, of course will remove any system changes.
So, short answer, not likely.
Click to expand...
Click to collapse
I suspected as much, thanks for confirming.