Related
Wondering if I should update downloaded ota then root or will the update screw things up like locking my boot loader and installing things I don't want or that will make customizing more difficult or impossible? Have had real bad luck with Verizon ota's in the past when it comes to rooting, unlocking, jailbreaking etc... And from what I've been reading on other threads this and other nexus ota updates have been really buggy especially with WiFi and BT. Mine works perfect right now and all I really want is to root it and remove the update file and turn off the update app. Thanks in advance for any advice.
paulsmcin said:
Wondering if I should update downloaded ota then root or will the update screw things up like locking my boot loader and installing things I don't want or that will make customizing more difficult or impossible? Have had real bad luck with Verizon ota's in the past when it comes to rooting, unlocking, jailbreaking etc... And from what I've been reading on other threads this and other nexus ota updates have been really buggy especially with WiFi and BT. Mine works perfect right now and all I really want is to root it and remove the update file and turn off the update app. Thanks in advance for any advice.
Click to expand...
Click to collapse
If you want root, first thing you should do is unlock the bootloader. Second thing you should do is read all the threads regarding root in the SuperSU subforum. Third thing is you want marshmallow because battery life, in my experience, is far better.
I haven't experienced any buggy WiFi or BT with either of my N6s. Just because you had bad luck in the past doesn't mean you'll have the same experience with this phone. The only bad luck you'll encounter would come from your own inexperience.
paulsmcin said:
Wondering if I should update downloaded ota then root or will the update screw things up like locking my boot loader and installing things I don't want or that will make customizing more difficult or impossible? Have had real bad luck with Verizon ota's in the past when it comes to rooting, unlocking, jailbreaking etc... And from what I've been reading on other threads this and other nexus ota updates have been really buggy especially with WiFi and BT. Mine works perfect right now and all I really want is to root it and remove the update file and turn off the update app. Thanks in advance for any advice.
Click to expand...
Click to collapse
Its a Nexus. Even Verizon ota's won't lock it. Update it, unlock the boot loader before or after. Flash back, flash forward, flash sideways. It is all up to you. The entire os/image is downloadable from Google, it is a fully ipen phone.
There are no widespread problems with Marshmallow. It is great. You get that impression because only the people with problems post.
So I would stop reading threads about problems and just read the threads about flashing and customizing.
Take the ota's up to the current version.
Unlock the bootloader.
Flash TWRP.
Flash systemless root version 2.65 from chainfire.
That will get you started.
Thanks for the advice all, did the updates, unlocked the boot loader & rooted. Easiest phone ever to mod !
Howdy guys and gals. Once again, it has been a VERY long time since I have posted. I just received my new Pixel XL today (free warranty replacement from Google for battery issues on my 6P).
Very first thing I did was install twrp recovery and SuperSU, so I could do the Carrier Entitlement mod and have my wifi hotspot. I have a couple of questions:
1. Can I unroot and keep the work I have done to enable my wifi hotspot or will it revert back after I unroot?
2. What can I do to update to 8.0? Honestly, I wouldn't mind losing root via updating OTA, but I don't want to end up with a brick and I don't want to lose my newly added wifi hotspot.
I greatly appreciate any help or input!! Thanks!
EDIT: I did find a tiny bit of info on this topic in the last few posts on this thread (page 2), but I really was hoping for some clarification since it is a bit vague. Link: https://forum.xda-developers.com/pi...ermod-systemless-install-guide-t3501448/page2
jonmike13 said:
Howdy guys and gals. Once again, it has been a VERY long time since I have posted. I just received my new Pixel XL today (free warranty replacement from Google for battery issues on my 6P).
Very first thing I did was install twrp recovery and SuperSU, so I could do the Carrier Entitlement mod and have my wifi hotspot. I have a couple of questions:
1. Can I unroot and keep the work I have done to enable my wifi hotspot or will it revert back after I unroot?
2. What can I do to update to 8.0? Honestly, I wouldn't mind losing root via updating OTA, but I don't want to end up with a brick and I don't want to lose my newly added wifi hotspot.
I greatly appreciate any help or input!! Thanks!
EDIT: I did find a tiny bit of info on this topic in the last few posts on this thread (page 2), but I really was hoping for some clarification since it is a bit vague. Link: https://forum.xda-developers.com/pi...ermod-systemless-install-guide-t3501448/page2
Click to expand...
Click to collapse
1 - If you unroot, the CarrierEntitlement.apk mod will stop working. Assuming you are using the method you linked below. This method on Nougat, relied on placing a modified CarrierEntitlement.apk in the SuperSu (or sbin/supersu directories and then binding that modified app to the original version in priv-app on boot. Essentially replacing the real app with this modified one which short circuits the provisioning check for tethering and allows tethering to work as needed. However, once you unroot those root directories will not exist or won't be accessible and this method will cease to work. Also, once you upgrade to 8.0, this specific method for gaining tethering also won't work. It appears that in 8.0 and above CarrierEntitlement.apk has been deprecated and replaced by TetheringEntitlement.apk. And a similarly modified version of TetheringEntitlement.apk doesn't exist at this point. (I tried and failed to create one.) However, as the posts you linked to indicate, on 8.0 you are able (if rooted) to add the needed line at the end of the build.prop which prevents the provisioning check from running at all. You do need to be rooted to make that build.prop modification. I do not know if making the change while rooted and then unrooting would still allow that build.prop modification to work. I suspect that it would still work since that line would remain in the build.prop even once unrooted, but I have not personally verified this. I would ask why you are so anxious to unroot...if you are wanting android pay to work, safetynet to pass, etc...you can install suhide after rooting and that would solve that problem. The simplest rooting with SuperSu / install suhide instructions I have found are in the OP of Chainfire's suhide post....linked below...
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855
2 - See above. Once you upgrade, you will need to reroot and make the same modifications referenced above in the build.prop.
Good luck!
sb1893 said:
1 - If you unroot, the CarrierEntitlement.apk mod will stop working. Assuming you are using the method you linked below. This method on Nougat, relied on placing a modified CarrierEntitlement.apk in the SuperSu (or sbin/supersu directories and then binding that modified app to the original version in priv-app on boot. Essentially replacing the real app with this modified one which short circuits the provisioning check for tethering and allows tethering to work as needed. However, once you unroot those root directories will not exist or won't be accessible and this method will cease to work. Also, once you upgrade to 8.0, this specific method for gaining tethering also won't work. It appears that in 8.0 and above CarrierEntitlement.apk has been deprecated and replaced by TetheringEntitlement.apk. And a similarly modified version of TetheringEntitlement.apk doesn't exist at this point. (I tried and failed to create one.) However, as the posts you linked to indicate, on 8.0 you are able (if rooted) to add the needed line at the end of the build.prop which prevents the provisioning check from running at all. You do need to be rooted to make that build.prop modification. I do not know if making the change while rooted and then unrooting would still allow that build.prop modification to work. I suspect that it would still work since that line would remain in the build.prop even once unrooted, but I have not personally verified this. I would ask why you are so anxious to unroot...if you are wanting android pay to work, safetynet to pass, etc...you can install suhide after rooting and that would solve that problem. The simplest rooting with SuperSu / install suhide instructions I have found are in the OP of Chainfire's suhide post....linked below...
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855
2 - See above. Once you upgrade, you will need to reroot and make the same modifications referenced above in the build.prop.
Good luck!
Click to expand...
Click to collapse
I greatly appreciate you bringing me up to speed. It has been so long since I have done anything like this. It seems like I'm away for a year or so until I get a new phone, and then I'm back at it again. :laugh:
I used the first method on this link to carry out the deed: https://www.theandroidsoul.com/enab...ing-pixel-and-pixel-xl-verizon-sprint-others/
Really, the only reason I want to unroot is to update to 8.0. I would be totally fine with keeping root (would actually prefer it), but I want to get on 8.0, and I can't find any guides for updating and retaining root and my tethering. It appears as though that won't be an option for now based on your post unless I want to modify the build.prop. I wouldn't mind doing that, but I would need a guide for updating and then another guide for the build.prop, and I'm just not as brave as I used to be with this stuff. Back in the day, I would take some info a run with it, and adapt as necessary. It's almost like I have gotten "old" and haven't kept up with the times and constantly worry I'm going to turn the phone into a paper weight. :laugh:
EDIT: Would I be able to just use the OTA update and it basically undo everything I have done and then re-root myself and then do the build.prop mod, or would I need to get back to a factory state before being able to run the OTA update?
My preferred method of taking upgrades on the pixel xl has been to just sideload the OTA for both monthly security patches and minor releases. I did flash the full factory image for the upgrade to 8.0 (removing the -w from flashall.bat to retain my data). Both methods have worked great for me. In either case, you do need to reroot, reflash suhide, reedit build.prop. But the entire process takes less than 45 min start to finish and had worked well each month since December 2016 for me. When you sideload the OTA or flash the factory image, any changes to build.prop, etc do not prevent the update from completing which is in contrast to what happens if you try to just take the OTA the standard way within android without first restoring to factory stock.
Guides for all of these steps are easily found here on the pixel xl forum. The basic steps for side loading ota/flashing factory can be found at the location they are published on Google's Android image pages.
sb1893 said:
My preferred method of taking upgrades on the pixel xl has been to just sideload the OTA for both monthly security patches and minor releases. I did flash the full factory image for the upgrade to 8.0 (removing the -w from flashall.bat to retain my data). Both methods have worked great for me. In either case, you do need to reroot, reflash suhide, reedit build.prop. But the entire process takes less than 45 min start to finish and had worked well each month since December 2016 for me. When you sideload the OTA or flash the factory image, any changes to build.prop, etc do not prevent the update from completing which is in contrast to what happens if you try to just take the OTA the standard way within android without first restoring to factory stock.
Guides for all of these steps are easily found here on the pixel xl forum. The basic steps for side loading ota/flashing factory can be found at the location they are published on Google's Android image pages.
Click to expand...
Click to collapse
Thanks for the information! I got impatient today and went ahead and updated to 8.0. I tried using the Disable Services app to get rid of the annoying notification to update, but was unsuccessful.
I'm going to re-root tomorrow evening and go through the whole process again to gain the hotspot. Now with the information I received in this thread, and the other links I emailed myself today at work, I'm starting to ease back into the modding world.
jonmike13 said:
Thanks for the information! I got impatient today and went ahead and updated to 8.0. I tried using the Disable Services app to get rid of the annoying notification to update, but was unsuccessful.
I'm going to re-root tomorrow evening and go through the whole process again to gain the hotspot. Now with the information I received in this thread, and the other links I emailed myself today at work, I'm starting to ease back into the modding world.
Click to expand...
Click to collapse
Nice work! Welcome back to the fun! Good luck!
I found this guide to rooting[NOTE: see below]. And then I just heard the news that the Moto G6 is confirmed to get a Pie upgrade. A couple of questions:
If I want to root, should I do it ahead of the Pie upgrade? Will my rooting be preserved? Will rooting cause trouble with the upgrade?
Will the upgrade likely break the rooting method?
Thanks!
NOTE: Apparently this forum censors Droid Views links. I inserted a space in the URL so the whole thing doesn't gets *'ed. The page title is "How to Unlock Bootloader, Install TWRP and Root Moto G6" in case you just want to Google it.
Updating will not keep root and will probably break things if you have root while updating. In fact, you'll definitely not be able to install an update if you've got TWRP installed in place of stock recovery.
If you've got the patience to wait for Pie to come through, I'd say wait for it.
After the update to Pie, will the same rooting process work? Or will there be a new process?
Is the update to Pie something I have to approve or initiate? Or could I wake up in the morning and find out my phone already updated?
Thanks so much for the help!
komi_9 said:
After the update to Pie, will the same rooting process work? Or will there be a new process?
Is the update to Pie something I have to approve or initiate? Or could I wake up in the morning and find out my phone already updated?
Thanks so much for the help!
Click to expand...
Click to collapse
The same rooting process should work in theory, granted root solutions such as Magisk have been updated to support Pie.
You usually have to recieve the notification and then initiate an update on any Android phone, but I can't tell you about this one in particular because I haven't received any sort of update since I got it.
Sounds good. I am planning to update to Pie (whenever that comes), and then I'll worry about rooting. But I was worried that down the road when we get to Q that it would auto-update and break my phone because it was incompatible with TWRP or something. But so long as I have the chance to decline it, I will hopefully be good.
Root now with magisk. When p comes you can flash the magisk Uninstaller and unroot. Then after you update to p you can boot a twrp.img again and flash magisk again.
Sent from my moto g(6) plus using Tapatalk
Hi
I will have my N960F/DS in a couple of weeks. I prefer not to root it for at least a couple of months in case of any warranty issues. However, by then it should have upgraded to Pie. Does anyone know whether the current root methods will work under Pie? Do they work under the current beta?
If your phone has an unlocked bootloader, pie won't change that. You're probably thinking about the exploit days that new updates patched.
So yes, it will be rooted as soon as the devs build twrp.
Great! Thanks!
Similar problem
I have a brand new N960FD and im have the "only official released binaries are allowed to be flashed" because i installed twrp and tried to do so with no-verity-encrypt and RMM state bypass. but now im stuck and i don't know what to do to root my new phone... (with magisk, which didn't work as well....)
I just want pie with root and no trouble.
Anyone can help me ?
J_O said:
I have a brand new N960FD and im have the "only official released binaries are allowed to be flashed" because i installed twrp and tried to do so with no-verity-encrypt and RMM state bypass. but now im stuck and i don't know what to do to root my new phone... (with magisk, which didn't work as well....)
I just want pie with root and no trouble.
Anyone can help me ?
Click to expand...
Click to collapse
read carefully Dr.ketans post in the general discussion. its pinned.
nothing anyone can do for you that you can't do by yourself by reading. i would also suggest you to read throught Docs whole pinned thread(user comments) and then do the same thing with the twrp thread in the dev section.
all issues and questions have come up sooner or later. you just need to want to take time and read.
down the line, you'll have also more questions and these answers would probably answer themselves after those 2 reads.( might be a lengthy read but sure beats having a phone that is not operating like you want it to)
Samsung account problem
I have the same model, n960fd, rooted with magisk tests checked, everything is fine, but when i want to connect to a samsung account, it loops and ask me again for the password, non stop.
Is there any known solution ?
Please help
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
paul_cherma said:
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
Click to expand...
Click to collapse
1- Probably not usually the root or recovery will block OTA updates from installing, even if they download.
2- If you lose root, you can USUALLY re-root assuming the same root method wasnt patched. If it was patched, a new root method (though probably still through magisk) will be needed. If this is the case, its up to the dev to find that method, you might be without root for a while.
3-if you debloat, and receive an OTA, your will probably need to de-bloat again, thought I havent personally had experience with this.
Why are you rooting? Just to de-bloat? If so, root isn't really necessary...
As someone who's been in the rooting stage for many years, i can answer your questions.
1. You can not update your phone through OTA updates after rooting the device, as the device was modified in an unauthorized way. And since you own a galaxy phone, the e-fuse within the motherboard will blow and knox will be permanently blown. You can no longer use samsung pay, google pay, and any other app that uses the safetynet api, even after you unroot the device.
2. You will lose root every time you update. You will need ODIN on your PC in order to properly update your firmware and to re-root your device by following the procedure again that you used to root your device, unless samsung patched the method you used to root your device. You can always check what bootloader version you're on within the firmware. For example, on the galaxy S8, the firmware version is N950U1UES5CRG9. The 5th to last number of the firmware will tell you. In this case, N950U1UES5CRG9 is the 5th bootloader version. Keep this in mind once samsung starts to update your phone often.
3. You will have to debloat again from scratch. In order to fully update your device through ODIN, you need to download the full firmware file containing an AP (Firmware), BL (Bootloader) , CP (Modem), and CSC (Carrier File) and manually flash them.
Do keep in mind, it is possible to soft brick or even hard brick your device, so back up your data frequently if you decide to tinker with your device.
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
paul_cherma said:
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
Click to expand...
Click to collapse
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
HighOnLinux said:
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
Click to expand...
Click to collapse
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Twodordan said:
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Click to expand...
Click to collapse
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
HighOnLinux said:
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
Click to expand...
Click to collapse
I mean xprivacy on xposed was the must have killer feature for any android device to turn your device into anything other than a privacy nightmare. If we can't do that any more we are f'd.
[EDIT] Looks like the new version of xprivacy, xprivacyLua is still supported for android 11, with magisk and EdXposed or LSPosed:
[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
XPrivacyLua Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy). Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data...
forum.xda-developers.com
XPrivacyLua/README.md at master · M66B/XPrivacyLua
Really simple to use privacy manager for Android 6.0 Marshmallow and later - XPrivacyLua/README.md at master · M66B/XPrivacyLua
github.com