Related
I Finally Got Temporary Root On The AT&T Samsung Galaxy Note 4 (and yes it is SuperSU, bit it does require KingRoot)
I Did It
can you post the software info page with the build for verification of which device it's on?
Like you want the build number?
BTW here is how to do it
https://youtu.be/Xr_2LQimK9I
This is temporary root which means that once you reboot you're going to lose root... Sadly not much new...
Sent from my SAMSUNG-SM-N910A using Tapatalk
Meh, I know but it's better than nothing
Well if this is true it is new because it's on 5.1.1 and not 4.4.4. Going to give it a shot...
So I've tried twice now to root using Kingroot 4.8.0 on Android 5.1.1 and twice my phone has rebooted at the very end when I was trying to download SuperSUMe from the Playstore (did look like root was successful). Might have better luck if I factory reset my phone, but I'm not that interested in getting root.
I can verify that this indeed does provide a temp root on at&t note 4 v5.1.1
BUT! It causes the system to slow down and lag alot and the keyboard no longer works untill the phone is rebooted and when you reboot the samsung startup screen shows a padlock that says custom. So the guys at kingoroot have manged to find a small crack but it is to unstable to use at this time.
I did test out the root permissions on a few apps
1: es file explorer. (I was able to set rw permissions and move files from the internal to ext sd card and see root folders and files in the system)
2: lucky patcher (it was able to gain root and modify installed packages on the fly)
3: es task manager (i was able to acess the root features but changes did not stick)
My hope is maybe someone can learn from this and make the temp root more stable even if temporary (i kinda doubt it since gaining temp root seems to freak the system out causing glitches and stutters)
I obtain temporary root indeed the only I could achieve is, wipe bloatware and change font lol.... So far so good
Well remember, with Samsung changing the system on Android 5.1.1 now requiring a custom kernel to root one of their devices and knowing that AT&T locked the bootloader, this is the best we can get as of right now. Give the developers of KingRoot time because they have tried to root the note 4 without needing a custom kernel. I know it doesn't seem like a lot but give them time. We have wait this much for root. Why not wait a little bit longer for the root to stabilize?
Btw guys I rooted my note 4 on KingRoot v4.8.1, they haven't released this version on their website yet
And supersume pro probably won't work on this
I use the terminal emulator and a root script
DAKILLER29 said:
Well remember, with Samsung changing the system on Android 5.1.1 now requiring a custom kernel to root one of their devices and knowing that AT&T locked the bootloader, this is the best we can get as of right now. Give the developers of KingRoot time because they have tried to root the note 4 without needing a custom kernel. I know it doesn't seem like a lot but give them time. We have wait this much for root. Why not wait a little bit longer for the root to stabilize?
Click to expand...
Click to collapse
There is a bounty regarding it, if they achieve completely root, 8,000 dollars are waiting for anyone achieving it
4.8.1 does stabalize things a little but i can guarantee just aboit that they are using a hole in the stock keyboard to obtain temp root i am going to experiment with non stock keyboards and see what happens from there. I also noticed that the phone gets hot when rooted
Does this temporary root allow the 910A to act as a wifi hotspot?
I was just about to list my Note 4 on Swappa. I can get by without root most of the time but when I need a hotspot, I really need it so I'm back on my Z2 for the moment.
terryowen said:
Does this temporary root allow the 910A to act as a wifi hotspot?
I was just about to list my Note 4 on Swappa. I can get by without root most of the time but when I need a hotspot, I really need it so I'm back on my Z2 for the moment.
Click to expand...
Click to collapse
At the moment NO temp root is not stable enough to reliably run long enough to enable and keep enabled wifi hotspot unless your carrier has opened that option. Lucky for me wifi teathering is included in my plan with at&t
Any way to run Xposed with this?
So is it available for download somewhere? Or will it be soon?
terryowen said:
Does this temporary root allow the 910A to act as a wifi hotspot?
I was just about to list my Note 4 on Swappa. I can get by without root most of the time but when I need a hotspot, I really need it so I'm back on my Z2 for the moment.
Click to expand...
Click to collapse
After delete all the bloatware it allow me to use Hotspot without need foxfi but I'm in Verizon so I couldn't tell you if it applies the same in at&t but I'm sure one of the program installed is the one that blocks or prevents Hotspot to work properly
I used Kingroot 4.8.1 (after you install 4.8.0 and open the app it tells you to update it) on my N910A and it got to 25% and failed? Happened a few times
*Update*
Make sure you go into Settings/App Manager and Disable all Verizons App except the Mobile login and My Verizon Mobile app.
Easy way to do is type in the search for vzw,disable all of vzw apps. Then search for Verizon and disable all of Verizons related app except the two mentioned.Verizons bloatware seem to be the problem that prevents us to get tempt root.
****
1.Download KingRoot app and install it
2.Run the app, it will show theres no root method availabe,still try to root it anyways.
3. As soon as the rooting starts(percentage page going up) hit the home key so the app will run in the background.eek:therwise rooting will not work.
4.Wait for 2 minutes then click on the KingApp again, it might take a few tries and voila! Temp root.:laugh:
*Note*
1.make sure you have usb debugging enabled in Developer Option:good:
2.Bootloader is still locked so you will lose your root after any reboot.Sunshine is not sucessful in unlocking it rightnow.Maybe if we have a boot.img thats already unlocked we can flash it with Flashify app.:crying:
3. All root app works great, just cant modify any system files cause of temp root.
Htc 526 root?!?
tonismo said:
1.Download KingRoot app and install it
2.Run the app, it will show theres no root method availabe,still try to root it anyways.
3. As soon as the rooting starts(percentage page going up) hit the home key so the app will run in the background.eek:therwise rooting will not work.
4.Wait for 2 minutes then click on the KingApp again, it might take a few tries and voila! Temp root.:laugh:
*Note*
1.make sure you have usb debugging enabled in Developer Option:good:
2.Bootloader is still locked so you will lose your root after any reboot.Sunshine is not sucessful in unlocking it rightnow.Maybe if we have a boot.img thats already unlocked we can flash it with Flashify app.:crying:
3. All root app works great, just cant modify any system files cause of temp root.
Click to expand...
Click to collapse
Okay so the temp root can do what? Will root worthy apps detect the root and work up until a reboot??? if that's the case then the painfully annoying time spent to "re-temp root" the phone will be enough for me until KingRoot finds a way to successfully root the phone. :good:
If you get me temp root I can get perm root.
This temp root method isn't working for me
You have to keep doing it a few time.Im doing this even with the StageFright update. Once you get it the first time, everytime after that will work.It seems like Kingroot remember its exploit. Temp root will let you do things like running GameGuardian to cheat android games. Basically thats all I use tempt root for.
*Note*
Remember to run Kingroot rooting process in the backgroun only. Otherwise it will not work. As soon as you hit the root method, hit the homekey. Go use your phone as normal and then come back to the app,voila tempt root. It will ask you to fix the root binaries ,which means it works.
I also have full root but resets on reboot...
I'm not 100% sure but if the root resets after reboot then it's a temp root right?
Yeah. It's annoying.. I'd love to mod a little but it's been years since I dabbled. Full root would be fantastic. I've been looking for a solid solution that preferably doesn't require any help from a PC..
Hey Can u do and update on it because it's one work now in 2018
tonismo said:
*Update*
Make sure you go into Settings/App Manager and Disable all Verizons App except the Mobile login and My Verizon Mobile app.
Easy way to do is type in the search for vzw,disable all of vzw apps. Then search for Verizon and disable all of Verizons related app except the two mentioned.Verizons bloatware seem to be the problem that prevents us to get tempt root.
****
1.Download KingRoot app and install it
2.Run the app, it will show theres no root method availabe,still try to root it anyways.
3. As soon as the rooting starts(percentage page going up) hit the home key so the app will run in the background.eek:therwise rooting will not work.
4.Wait for 2 minutes then click on the KingApp again, it might take a few tries and voila! Temp root.:laugh:
*Note*
1.make sure you have usb debugging enabled in Developer Option:good:
2.Bootloader is still locked so you will lose your root after any reboot.Sunshine is not sucessful in unlocking it rightnow.Maybe if we have a boot.img thats already unlocked we can flash it with Flashify app.:crying:
3. All root app works great, just cant modify any system files cause of temp root.
Click to expand...
Click to collapse
Hey! actually i found that kingroot 4.8.2 works but i only got it to work once, when you did this what version of kingroot did you use?
.
.
Hi,
can anyone help me to revert A520f 2017 Knox to 0x0.
Unfortunately I tried to Root my A5 2017, I am luckily successful to root my phone, but after that I realized that I will not receive OTA nor able to use sHealth app.
So I downloaded stock Rom and Totally re-flash everything(AP, BL, CSC...).... Although it remove the Custom recovery + super user etc. But when I tried to Open sHealth App, it saying that "Due to new Security Policy Samsung Health cannot be opened on a Rooted device. 0x110040581".
So, Is there any way available to reset everything means to bring it to zero position?
qazihamayun said:
Hi,
can anyone help me to revert A520f 2017 Knox to 0x0.
Unfortunately I tried to Root my A5 2017, I am luckily successful to root my phone, but after that I realized that I will not receive OTA nor able to use sHealth app.
So I downloaded stock Rom and Totally re-flash everything(AP, BL, CSC...).... Although it remove the Custom recovery + super user etc. But when I tried to Open sHealth App, it saying that "Due to new Security Policy Samsung Health cannot be opened on a Rooted device. 0x110040581".
So, Is there any way available to reset everything means to bring it to zero position?
Click to expand...
Click to collapse
Sorry cant help you with this but just one curious question. Is samsung pay also not working after rooting?
Sent from my SM-A720F using Tapatalk
cardozclive said:
Sorry cant help you with this but just one curious question. Is samsung pay also not working after rooting?
Click to expand...
Click to collapse
Samsung pay cannot work with knox tripped
ponkz said:
Samsung pay cannot work with knox tripped
Click to expand...
Click to collapse
Can you tell me is there any way available to use Samsung Health App. I am not worried about knox tripped nor warrenty clain... but worried about using default Application, OTA and Patch etc.
Would it possible use all these using root? Or any other way available..
Eg. I was using xposed in LG G3 which having small app like root clock. Which allow to fake those app which were not working on rooted device. But knox case seems different
qazihamayun said:
Can you tell me is there any way available to use Samsung Health App. I am not worried about knox tripped nor warrenty clain... but worried about using default Application, OTA and Patch etc.
Would it possible use all these using root? Or any other way available..
Eg. I was using xposed in LG G3 which having small app like root clock. Which allow to fake those app which were not working on rooted device. But knox case seems different
Click to expand...
Click to collapse
If you want to hide root, use Magisk su instead.
ashyx said:
If you want to hide root, use Magisk su instead.
Click to expand...
Click to collapse
No I dont want to hide root explicitly , I just want to use Samsung Health Application, if there is any way available to by pass the error message
"Due to new Security Policy Samsung Health cannot be opened on a Rooted device. 0x110040581".
Kindly tell me, either by hiding the Root Or Editing any file
qazihamayun said:
No I dont want to hide root explicitly , I just want to use Samsung Health Application, if there is any way available to by pass the error message
"Due to new Security Policy Samsung Health cannot be opened on a Rooted device. 0x110040581".
Kindly tell me, either by hiding the Root Or Editing any file
Click to expand...
Click to collapse
I just told you, to bypass apps that detect root you need Magisk su.
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4
There is no way to restore knox, so... rip Shealt
Yes eFuse Chip is to blame....
Gesendet von meinem SM-A520F mit Tapatalk
qazihamayun said:
Can you tell me is there any way available to use Samsung Health App. I am not worried about knox tripped nor warrenty clain... but worried about using default Application, OTA and Patch etc.
Would it possible use all these using root? Or any other way available..
Eg. I was using xposed in LG G3 which having small app like root clock. Which allow to fake those app which were not working on rooted device. But knox case seems different
Click to expand...
Click to collapse
You are able to use samsung health after rooting.
you have to be rooted again and i would recommend using TWRP + Magisk to root so it is systemless and you can still pass safetynet after rooting.
you will need to download TWRP, Magisk v12.0, dm-verity patch.
1. put magisk v12.0 and dm-verity patch onto the sdcard in the phone
2. flash TWRP
3. boot into recovery and swipe to allow modifications.
4. under wipe there should be a button to format data (its in the bottom right). you will need to do this to flash magisk and dm verity.
5. flash dm verity and THEN magisk
6a. boot into phone and complete setup to get to home page.
6b. download any systemless root app that you want (adaway works you just have to turn on systemless host files in magisk settings + viper4andriod has a module in magisk that you download for it to work)
(DO NOT TURN ON HIDE MAGISK UNTIL THE END)
7. download the app buildprop editor, open it and grant it root. search for the line ro.config.tima=1 and change the value from 1 to 0.
8. reboot the phone and you should now be able to use s health.
continue following if you wish to pass safetynet and be playstore certified (set up your root apps like viper and adaway before doing this)
9. go into magisk settings and enable the setting Magisk Hide. reboot phone. check that you pass safetynet in magisk manager after booting up again
10. go into app manager, find google play store, tap storage and then clear the data.
11. open app again and you should be certified. (this took me a few tries. not sure if it was play store needing to update the property or me needing to reboot the phone)
12. Yay! your device should now be able to pass safetynet and will be play store certified in the play store app. you should soon be able to see netflix in the play store again.
source: I done this on my a520 just on the weekend to be able to update netflix
I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!
If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?
jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.
alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?
The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?
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