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
Related
Hey Guys,
I've done reading about this issue but I did not find an answer specifically to the Nexus 7 device.
I bought my mother-in-law the Nexus 7 and she loves it. However, she will be going back home (which is far) and I was wondering if an OTA update comes, will she be able to update? Will it mess with the system itself if updated over?
Do I have to unroot first, then OTA update, then reroot?
I will not install any custom rom. I will just have it rooted that is it.
Thank you
I unlocked my bootloader and manually rooted [superuser zip in CWM], then I installed the system update that updated it to 4.1.1 [JRO03D], and I still had root, so I'm pretty sure the updates on the N7 will keep the root.
However, you can always try "OTA root keeper" in the play store, it's supposed to restore root, in the event that an OTA update unroots it.
I downloaded it before updating because I thought I'd lose root with the update, but I didn't have to use it at all.
But I'm no longer on the stock rom, I switched to the ParanoidAndroid rom, it's excellent.
I see. Do I need to unlock the bootloader in order to root? Is it true that unlocking the bootloader is only needed if I want to install custom ROMs right? Can I just have root?
Thanks again!
You have to unlock the bootloader in order to root.
keplenk said:
I see. Do I need to unlock the bootloader in order to root? Is it true that unlocking the bootloader is only needed if I want to install custom ROMs right? Can I just have root?
Thanks again!
Click to expand...
Click to collapse
Unfortunately no, because there is no known exploit for loading an insecure boot image, in which case you could use 'adb' to push Superuser to /system/.. But unlocking the bootloader isn't a big deal, except for the fact it erases all the data. There are ways to back it up via adb, and I think the N7 Toolkit has backup & restore options.
I'm looking to root my phone but I don't want to flash any new bootloader or custom roms. I'm under the impression that I'll still be able to get OTA updates if I do this. My question is if I download and install an OTA update will I still have root on the phone or will it remove root? Thanks!
psyphris said:
I'm looking to root my phone but I don't want to flash any new bootloader or custom roms. I'm under the impression that I'll still be able to get OTA updates if I do this. My question is if I download and install an OTA update will I still have root on the phone or will it remove root? Thanks!
Click to expand...
Click to collapse
I was still able to receive and apply the OTA after rooting, but the OTA did cause me to lose root. But re-rooting was pretty painless.
Its sure than rooting phone you receive OTA and can install it?? If yes, I want to root my phone, only root, i dont want to change anything more for receiving OTAs.
How can I do? just only root, any link to the safest way?
Is the same way when I receive an OTA and i have to root again?
many thanks.
1. You can use an app called OTA Rootkeeper. Use it to hide root before you accept an OTA, then use it to restore root after.
2. Yes, you can use adb commands (possibly the Nexus 4 toolkit as well) to temporarily flash clockwork recovery and obtain root. You will need to unlock the bootloader though, and that will factory reset your device.
http://forum.xda-developers.com/showthread.php?t=1993331
Nospin said:
1. You can use an app called OTA Rootkeeper. Use it to hide root before you accept an OTA, then use it to restore root after.
2. Yes, you can use adb commands (possibly the Nexus 4 toolkit as well) to temporarily flash clockwork recovery and obtain root. You will need to unlock the bootloader though, and that will factory reset your device.
http://forum.xda-developers.com/showthread.php?t=1993331
Click to expand...
Click to collapse
Good advice for OTA Rootkeeper! If I head down this path I'll make sure to use that. I'm still looking around for the best way to root without unlocking the bootloader or factory reseting.
Superuser contains a built in 'try and preserve root' function which worked well when I updated to 4.2.1
A new update is out for the 6p with monthly security updates. I have two questions:
1. I'm assuming Google is going to break systemless root. Does this update do that or does it still work?
2. Now that we're seeing monthly updates, keeping root is going to be a pain. What is the least painful process to update? I've searched around and have not been able to find a good guide.
1. I downloaded the new MMB29P image today. I flashed the system and vendor partitions via fastboot. Systemless root is still working.
2. See #1
1. It still works
2. Not painful at all. Fastboot the relevant updated factory images and reflash SuperSu. 2.66 is working perfectly and the existing guides/stickies are still valid.
Did this. Lost root.
@gthing can you be more specific on what you actually did and that will help for advice.
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.
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.