I am a constant user of Android Pay, and I don't want to fuss with trying to keep root and keep Android Pay working. I have been reading up a bit on these different profiles such as "butterfly" that many have seem to have had success with and I was wondering if this were possible to achieve without root? I am hoping for a file I could edit in terminal editor or a flashable zip I can edit or use. I have TWRP installed and am using the latest iteration of the ElementalX kernel.
Thanks, and sorry if this has been answered before.
Related
I'm sure this has been asked somewhere, and I tried to find out for myself but I haven't been able to get a definitive answer and I'm rather careful with my phone so that is why I am asking here. I have the Sprint GNote 2 with Android version 4.1.1 and I rooted using CF Auto Root. I have installed a bunch of root programs (Busy Box, Triangle Away, etc.) and made some system modifications and simple sound file changes... now my device wants me to update to a new version of Android. So before I do that, I am assuming that I just go ahead and do the update and then go through the CF Auto Root process again... is that going to affect any of the mods I have made, do I need to keep track of what I've done so I can make the changes after each system update? I'm still learning, so any help is appreciate and sorry for the n00bish question.
Thanks.
~ Sorcerer Merlin.
I rooted for the first time and it is good to go. When googling, I just find articles of "must-have" apps for rooted phones.
My question is, though, what apps do I need.
I see TWRP and Xfusion (or something like that) a lot. I also seen about some app that saves root when upgrading to 12B (I had to downgrade from 12B -> 10B).
So, are there any apps that are neccessary that aid in saving root, managing root access, etc. that is recommended?
Flash TWRP and then flash some custom ROM if you want.
d1zzylol said:
I rooted for the first time and it is good to go. When googling, I just find articles of "must-have" apps for rooted phones.
My question is, though, what apps do I need.
I see TWRP and Xfusion (or something like that) a lot. I also seen about some app that saves root when upgrading to 12B (I had to downgrade from 12B -> 10B).
So, are there any apps that are neccessary that aid in saving root, managing root access, etc. that is recommended?
Click to expand...
Click to collapse
Rooting just depends on what you want to do. Rooting allows you to:
Flash TWRP, as stated above, to flash custom ROMs.
Install apps that require root. Just depends on what you want to do. TiBu allows you to backup and restore your apps and their data which you cannot do without root.
Between rooting and TWRP, you can flash custom kernels which allow overclocking and other enhancements.
Root allows you to re-enable writing to the external SD card which was limited under Kit Kat.
Again, we can't really tell you "must-have" apps. It all depends on the user. You'll just have to research around and look. Not trying to be mean about it, it's just that it's such an open-ended question and it varies from user to user and what their wants and needs are.
I had hard time with finding how to root this phone but I might did this. Can you tell me if I discovered something or just really ****ed up?
I found this site. http://techglen.com/2015/02/14/how-...3-14-4-a-0-157-android-4-4-4-kitkat-firmware/
Downloaded the .ftf files. Flashed the .108 kernel and then just used the root option from flashtool. Flashed .157 back.
Everything is working. Root Checker says that I have root. I was able to hid the softkeys compeletly.
But couldn't find anyone using this method on here so.. Was I blind or just done something wrong?
People don't use your exact method , but in esence thats the way everyone roots on locked bootloader: flash an old stock kernel that is known to have a root exploit, root using that exploit(with flashtool or some other way) and after that flash the latest stock kernel that you will use. It's been this way for a long time for all the xperia devices.
Thanks for the answer. I'm so happy I finally got this phone. Been waiting for months! Earlier had to use ****Phone and even with jb it felt so bad. Maybe I'm an android fanboy. But with iOS I got that claustrophobic feel..
Even though I used the same guide and got root,the latest Root Explorer cannot seem to be able to open panel_id text file located in sys/devices/blahblah folder for example. Nor can it copy it to sdcard1. I get a message that I need root even though I've granted permissions to the app. Titanium seem to work OK. So what's the matter? Any ideas? How do I make sure I have full root access?
Not sent by me!
hey sorry been a bit off lately. download root checker app from Google play store. this should tell you if you're rooted or not. or try to use root browser app
Root Explorer eventually can have root permissions off by default.
Check it's settings.
I reflashed XZDR 2.8.3 and SuperSU 2.48 beta and everything is fine. Maybe try the same.
Not sent by me.
Hello
I have a Lenovo P2a42 UK version on 3 mobile.
I haven't rooted a phone before and would like to know how to root my phone.
Firstly, should I root to stock android first and then consider other ROMs?
Secondly, should I root from the UK version (SO56) to the ROW version (S232)?
Finally, what is the best way of rooting to LineageOS in a secure way? What is the best site to download the necessary files?
Sorry for all the questions but any help would be really appreciated.
Thanks in advance!
Firstly, should I root to stock android first and then consider other ROMs?
A. My opinion move to custom rom unless you need led notification light.
Finally, what is the best way of rooting to LineageOS in a secure way? What is the best site to download the necessary files?
A. see the comment 1,2,3,4 on any custom rom thread or simply download aad on su from :- https://download.lineageos.org/extras
and flash it using twrp (remember change data to ext4 otherwise root may not work)
Secondly, should I root from the UK version (SO56) to the ROW version (S232)?
A. i didnt understand what is rooting s056uk to s232
Hit thanks if i've helped
Sent from my Lenovo P2 using Tapatalk
Entirely up to you, but I'd upgrade to the newer stock ROM for now rather than using a custom ROM. You will lose VOLTE support and some other features, like the battery saving switch / LED notifications.
If you do plan on rooting, use the guide in the TWRP post here on the Lenovo P2 forums. However, it'd be wise to read up on what you can actually do with root. Myself, I rooted in order to install a custom boot animation (tricky and not the standard method on Lenovo stock ROM), change fonts (a little frivolous considering you're losing warranty for it), and mainly to add a hosts file for system wide ad blocking. You can use magisk to root (there's a forum dedicated to it) but I have had quite a few problems with it.
Also, if you root, you lose access to some apps such as android pay, and lose access to features in certain apps (banking apps for example). Magisk claims to work around these problems, but it's tricky to install and upgrade and doesn't always work. I almost got stuck in a bootloop using the default uninstaller, and had to modify the installer by hand in order to get newer versions to install. On top of that, the magisk module system doesn't seem to work, at least on my device.
Whatever happens, let us know what you choose to do and how you get on.
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Nblufire12 said:
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Click to expand...
Click to collapse
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
sb1893 said:
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
Click to expand...
Click to collapse
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Nblufire12 said:
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Click to expand...
Click to collapse
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
sb1893 said:
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
Click to expand...
Click to collapse
is your build.prop edit still working on oreo for og pixel xl 1?
Nblufire12 said:
is your build.prop edit still working on oreo for og pixel xl 1?
Click to expand...
Click to collapse
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
I've been considering switching to the Pixel XL or the 2XL and this is a critical factor for me. From what I gathered from the 2XL forum, this wasn't working. I'm going to see if I can track down if the same Magisk tether module exists for the 2XL. If anyone knows ahead of time, I'd like to know.
Nblufire12 said:
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
Click to expand...
Click to collapse
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
sb1893 said:
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
Click to expand...
Click to collapse
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Nblufire12 said:
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Click to expand...
Click to collapse
I'd recommend following one of the many guides found on XDA. Here is the one I used to get up and running on magisk...you will need to determine which portions of the guide are relevant to your situation and needs.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Good luck!
S
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
scoobysnack said:
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
Click to expand...
Click to collapse
Interesting. I am unable to edit build.prop with Root Explorer (which does have Root Privs). Whenever I open the file for edit in Text Editor within Root Explorer, it allows me to edit the file, but when I "Save Changes and Exit" or "Save Changes" and then exit...those changes are not retained. The timestamp on the build.prop file is unaltered as is the file size. I wonder what the difference is that allows you to edit your build.prop but prevents me from changing mine...I have poked around on the forums and the magisk threads and haven't been able to figure it out. I stopped researching when I discovered the ability to insert those settings at boot time via the magisk modules and decided that was a viable solution (maybe better as it leaves build.prop stock and unchanged.)
Thanks,
S
I click "Save Changes" then I click "Save and Exit" it will say the original file is name .bak