Related
When I purchased my Droid Maxx it was running 4.2.2 and I used the PIE exploit to root it. At the time, I didn't realize that allowing the 4.4.4 OTA update would completely frag the root so I took it. Now, on 4.4.4 I of course have very buggy and inconsistent root access. So, I decided to just unroot and forget about it for this phone. To that end, I ran a full unroot from SuperSU and the app disappeared. Great...until I rebooted and it came back. I went back into the app, disabled it via the app settings, full unroot again, and again the app reappears on reboot. I can't delete the apk from the System folder because even with SuperSU enabled it won't grant me write access (see above: root fragged). So what the hell am I supposed to do? The phone is essentially unrooted, but on every reboot, regardless of unroot attempts, SuperSU reinstalls itself.
Any ideas on how to get rid of it?
Either root it properly and use that to remove it, or reflash your full stock firmware.
Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Disable OTA
Dmriskus said:
Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Click to expand...
Click to collapse
1. Disable updates, link one post up
2. Root in TWRP
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Hi all.. I am having some issues with both rooting and modding my build.prop.
My ultimate goal right now is to have a stable root, on essentially stock rom, with a modded/bypassed native tether app (I have unlimited data and verizon blocks it). I am having issues with both processes, and if anybody can help it would be greatly appreciated!
First, I am having a ton of trouble with the temp root process; I am using Kingroot, and although I have been able to gain root successfully, it seems completely random when the process works and when it doesn't. About a quarter of the time, the root seemingly works.. the rest of the time, I either get force crashes on all running apps until system reboot, I am told I have root but cant access system files still, or the root fails altogether. Perhaps there is a flaw in my process? I also have been unable to update the SU binaries.. I have tried using both the latest stable and beta APKs from Chainfire. Is there a specific process that someone has used more successfully, order of installations, etc?
Secondly, when I have gained root successfully, I have been trying to add a line into my build prop to bypass the tether subscription check, which I believe will work.. but whenever I reboot my phone, it overwrites my saved changes to Build.prop. I will successfully get r/w (Using root explorer btw), mod the build.prop just adding in a single line, save, and then reopen confirming that the changes stuck. However, when I reboot, the stock Build.prop comes right back. I have also attempted to copy a modded brand new build.prop into /System instead, which also appeared to work, but ends with the same problem on reboot.
Please note that if possible I want to keep running stock, I do not want to have to flash a modded rom.
TL;DR - Root is finnicky, SU binaries won't update and build.prop resets to stock on reboot even after confirmed edits.
I just read the tldr.
You need to use kingroot to root. This will be a very crappy root and all changes will be lost on every boot at first.
To obtain a proper root and permanent write access do the following.
Download twrp for quark
Download supersu flashable zip
Download and install flashify
Download and install sunshine
Download and install kingroot
Run kingroot and root the device
Run sunshine pay $25 for unlocked bootloader
Reboot
Run kingroot and root the device
Run flashify and flash the twrp for quark recovery.
Reboot into recovery run twrp
In twrp it will ask you a question that has to do with write access SWIPE YES.
Reboot
Run kingroot and root the device.
Kingroot is now stable.
Uninstall kingroot from the 3 dots in the app
Reboot into recovery and start twrp
Flash the flashable chainfire supersu zip
Reboot.
You now have root and the ability to make permanent changes to system.
P.S.
There is currently no way to do this without sunshine.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
I just read the tldr.
You need to use kingroot to root. This will be a very crappy root and all changes will be lost on every boot at first.
To obtain a proper root and permanent write access do the following.
Download twrp for quark
Download supersu flashable zip
Download and install flashify
Download and install sunshine
Download and install kingroot
Run kingroot and root the device
Run sunshine pay $25 for unlocked bootloader
Reboot
Run kingroot and root the device
Run flashify and flash the twrp for quark recovery.
Reboot into recovery run twrp
In twrp it will ask you a question that has to do with write access SWIPE YES.
Reboot
Run kingroot and root the device.
Kingroot is now stable.
Uninstall kingroot from the 3 dots in the app
Reboot into recovery and start twrp
Flash the flashable chainfire supersu zip
Reboot.
You now have root and the ability to make permanent changes to system.
P.S.
There is currently no way to do this without sunshine.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the input..
I was hoping to avoid unlocking the bootloader, but I suppose I might as well. Kingroot does give me root, even if unstable, and Root Explorer tells me I have right access to /system.. plus, I can see that the changes have been implemented to build.prop, so it doesn't really make sense to me how/why it would revert to the stock build.prop on a reboot. Oh well.
The ROM checks the system on reboot. If it sees a change it reverts to what it was.
To fix that you need write protection disabled. Which twrp can do on an unlocked boot loader
Sent from my XT1254 using XDA Free mobile app
I may be wrong but I don't think you need to install TWRP to get rid of kingroot. I didn't feel like installing twrp partially because I'm lazy and partially because I dont plan on installing any other rom any time soon. Anyway, what I did was install kingroot, pay my $25 to sunshine and unlock the bootloader, then ran a script to remove kingroot an install supersu. The result was a perm rooted phone with super-su.
Maybe root checker is lying when it says i have root but adblocker can write to the hosts file so i don't think it is.
Kingroot cannot gain u permission for edit system partition. It only gain permission for run some script, program, it not true root, form what i read then even flash root by mofo, we still can't edit system partition
So u need unlock your bootloader
Okie Dokie smokie. I'm not here to convince anyone, I'm just letting you know what worked for me. I have su persistent in /system/xbin and have never installed TWRP. Root lives through reboots and superSU is installed and processing root requests. Kingroot is gone off the device. Feel free to PM me. I would be interested to see if it works without an unlocked bootlaoder. As i said, I unlocked with sunshine but never installed TWRP.
Are you sure recovery doesn't just check the recovery partition and restore it if it finds it has been modified. I have seen that behavior in the past very often. It seems a little wonky that every time the system boots it would check the whole /system partition.
Yes, it reverts all changes.
This is the first device I've owned that did this as well.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
Yes, it reverts all changes.
This is the first device I've owned that did this as well.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
As I said, I think you may be mistaken. i am looking through the script i used to replace kingroot. What does TWRP modify to allow persistent recovery. I wonder if booting into recovery will wipe out the persistent root. A normal reboot does not effect it. Maybe build.prop gets restored while other files do not. As i said, my hosts with adblockign persists through reboots.
As far as the first post, there is an app out there which will add the line needed on the fly. com.ncsoftwaresolutions.entitlementbypass It worked perfectly on my Moto X running 5.1
I did not write the script i used and take no credit for it. Lets get that out of the way.
I am not completely sure as to how they accomplish this. Since there are things that can get "stuck" there such as kingroot app.
Perhaps someone else would like to chime in.
But I do assure you that write protection exists on this device.
And that the changes you're attempting to make requires it to be off.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
I am not completely sure as to how they accomplish this. Since there are things that can get "stuck" there such as kingroot app.
Perhaps someone else would like to chime in.
But I do assure you that write protection exists on this device.
And that the changes you're attempting to make requires it to be off.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I don't doubt that is your experience. I was sharing mine. I rebooted into recovery and root stayed. What i am saying, with confidence because i have done it, is that you do not need to install TWRP to keep root persistent through reboot.
Here is the script i ran.
http://pastebin.com/w7MqXBZZ
After looking more my best guess is that the Sunshine process disabled nand lock which is why i am able to write to the system partition.
Thanks for the help guys.. interesting notes.
It turns out I can pay 30$ a month now even with unlimited data to unlock hotspot, which is good enough for an interim solution. I also don't plan on flashing any roms.. I prefer to do my own tweaks. I will probably proceed with unlocking the bootloader for persistent root and /system write permissions, once I get some time.
Cryptrix said:
Thanks for the help guys.. interesting notes.
It turns out I can pay 30$ a month now even with unlimited data to unlock hotspot, which is good enough for an interim solution. I also don't plan on flashing any roms.. I prefer to do my own tweaks. I will probably proceed with unlocking the bootloader for persistent root and /system write permissions, once I get some time.
Click to expand...
Click to collapse
That option has been around for a long time.
Sent from my DROID Turbo using XDA Free mobile app
Not Quite
cstone1991 said:
That option has been around for a long time.
Sent from my DROID Turbo using XDA Free mobile app
Click to expand...
Click to collapse
Actually, the rest of the users on my line were on a very outdated plan, so Verizon blocked both the free hotspot on the current plans for limited data users, and my option to pay for it on my own line. So instead I spend two hours on the phone convincing them to put the other lines on a "sub-plan", and upgrade them collectively to an Everything More, while mine is singular on the cycle but technically still on the same plan. And NOW I have the option to pay.
Now I just need to figure out how to utilize my upgrade without losing Unlimited data..
I said this a few posts up, it may be of no concern now.
As far as the first post, there is an app out there which will add the line needed on the fly. com.ncsoftwaresolutions.entitlementbypass It worked perfectly on my Moto X running 5.1.
You need root and you need to run it every time your phone is rebooted but ti works to bypass the entitlement check.
I recently used the "New Root Method For 5.1.1 w/o custom kernel" to root my otherwise stock Note4 SM-N910T.
Everything was fine, but after a few weeks I lost root. I was able to get it back by re-flashing SuperSU 2.65 from recovery.
After further research, I found the blog post by Chainfire on SuperSU 2.74, and understand that 2.74 addresses the Samsung security update.
I've been using "SuperSU 2.65 Stable" because of root access compatibility issues with some programs.
How do I know if the Security Policy update was the cause of losing root? My phone's About Device has "Android Security Patch level" as 2015-11-01. So it doesn't look like something that was updated in the last week.
If it was not the security policy, then what caused the loss of root?
I have automatic updates off, and did not update anything at the time I lost root. Is there any other way that an update or change can be pushed? My /data/security/spota folder is empty. Should I delete the empty folder just to be sure?
I guess because you upgraded the system root cause failure，you need to flash supersu.zip again ，can retrieve root
Supersuer said:
I guess because you upgraded the system root cause failure，you need to flash supersu.zip again ，can retrieve root
Click to expand...
Click to collapse
Here's a summary of the problem:
1) FlashSuperSU from recovery.
2) Enjoy Root
3) 1 to 3 weeks later - something disables SuperSU, and root is lost
4) Go to 1)
I want to understand what is happening in 3) so I can exit this annoying loop.
timg11 said:
Here's a summary of the problem:
1) FlashSuperSU from recovery.
2) Enjoy Root
3) 1 to 3 weeks later - something disables SuperSU, and root is lost
4) Go to 1)
I want to understand what is happening in 3) so I can exit this annoying loop.
Click to expand...
Click to collapse
This has only happened once? Interestingly, I had the same exact issue happen to me on my S5 with MM, I rooted using chainfire and just out of the blue, all root privelages were dismissed. So I flashed SuperSU v2.65. It happened multiple occasions until I was able to switch to an AOSP ROM. After going completely custom it seemed to have stop doing this. Maybe because of a contrast of coding that differ in security.
Sent from my SM-G900P using XDA-Developers mobile app
It has happened twice. I'm working on a Tasker recipe that will check for root regularly and report when it is lost.
Now it has happened three times. Still trying to figure out what causes it. I have not found a tasker function that checks for root.
Unless I can find a solution, I guess I'll have to go back to the traditional root with beastmode kernel.
timg11 said:
Now it has happened three times. Still trying to figure out what causes it. I have not found a tasker function that checks for root.
Unless I can find a solution, I guess I'll have to go back to the traditional root with beastmode kernel.
Click to expand...
Click to collapse
Nobody seems to have any idea what's going on. I'm guessing the loss of root was specific to SuperSU 2.65.
Here what I've tried today:
1) Recovery / Flash with SuperSU 2.65 to get root back.
2) Update SuperSU Pro to 2.76 from Google Store. Download and copy ZIP to phone storage just in case.
3) reboot and verify root still available from Titanium Backup
4) Uninstall ES File Explorer Pro. Install Solid Explorer
5) Test root access of Solid Explorer. It works. Buy Solid Explorer.
6) reboot again just to be sure root remains
7) Backup with TB.
So far, everything is working. Hopefully it will remain rooted.
Almost 3 weeks, and no loss of root. Super SU 2.76 seems to fix the problem.
J500G lost root minutes after connected to internet. I have to root every single day.
Hi!
I previously had rooted my S7 Edge with Super SU v2.79 years ago but now I want to switch to Magisk because I need to hide root from certain apps. Magisk fails to install saying:
! Boot image patched by unsupported programs
! Please restore to stock boot image.
Click to expand...
Click to collapse
From here I read I can try unSU. But in my case it did not work. How exactly can I fix this now? As I understand I need to reflash some stock images? But what exactly is the minimum requirement? Just boot.img? Or system? Also if I don't want to loose my apps, data, config, can I flash them without loosing them? Or if not is it possible to hide root while still using SuperSU since I really don't want to lose my data/apps/config.
You get the info to restore the stock boot image, which is just the kernel image. As you are rooted right now, use a backup tool like Swift Backup (full version is paid) or Neo backup (FOSS) to backup all app data and apps and personal data in case something goes wrong. Backup that stuff to your PC of course, saving all data that was created by the backup app and your other stuff. Then flash stock kernel, test if all is good and stick to Magisk stable plus needed modules.
Next time please provide all system data like used (custom?) ROM and Android version. If you use a custom ROM you need to revert to the unrooted custom ROM kernel of course.
Thank you for your response!
I am not rooted currently as I uninstalled Super SU but I think I can install it back if needed. Will flashing stock kernel always cause app data to be lost? Or is there chance that it does not get touched? As for ROM I use stock android 7 rom. I am not sure where and if can I still find it.
I don't really trust backup because because previous attempts have ended up with boot loops and broken apps. If there is chance that that app data stays intact without backup then I might try it but if the process factory resets everything and then relies on restoring backup as one part of the process then for now I would try to come up with some other solution.
Also will it cause all the stock bloatware to come back or is the kernel separate from apps?
sysctl said:
Thank you for your response!
I am not rooted currently as I uninstalled Super SU but I think I can install it back if needed. Will flashing stock kernel always cause app data to be lost? Or is there chance that it does not get touched? As for ROM I use stock android 7 rom. I am not sure where and if can I still find it.
I don't really trust backup because because previous attempts have ended up with boot loops and broken apps. If there is chance that that app data stays intact without backup then I might try it but if the process factory resets everything and then relies on restoring backup as one part of the process then for now I would try to come up with some other solution.
Also will it cause all the stock bloatware to come back or is the kernel separate from apps?
Click to expand...
Click to collapse
to back up use smart switch in pc, to install magisk is recommended to flash stock firmware first and instal magisk to avoid issues like bootloops