I know these phones are a bit dated, but I have a pair of AT&T SGH-I747's that I've been trying to get rooted. Using Kingoroot, they both crashed and rebooted at different %'s and upon reboot one failed and one passed the root checker test.
The one that passed crashes upon attempting to do anything with root (seemingly as soon as an app requests the permission), this includes attempting to update the binary for SuperSU and any other root-based app.
The one without root continues to crash upon re-attempting the root process. Attempting a CF-Autoroot via Odin elicited a crash during the "Extracting" step on the phone (the actual Odin part went fine).
Is there any way to fix whatever may have been damaged/corrupted by the initial crashes and start over, or otherwise repair it? If there is a crashlog somewhere I can access I will post that if someone tells me where it may be.
Thanks in advance.
Related
So I have bitten the bullet after all of the issues that I was having with my phone today and I did an SBF flash of my Droid 4's firmware. I rooted successfully and installed Busy Box, but I am unable to install Safestrap v3.72
I get to the 60/100 point where it is "Running Installation Script" but it never gets beyond that. I have also tried to Uninstall in case one of the several tries worked behind the scenes, but that also gets stuck at 60/100. This allegedly has something to do with Busy Box not being installed, but I have done that for sure.
Update: Just repeated the root process with SafeRoot and that installs Busy Box as part of the process. Completed successfully, and I'm still hanging at 60/100...
What else am I forgetting to do?
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
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
I have the same problem?? Did you get any answer from any body? Do I have to re root again?
Just flash super su in recovery. Same thing happened to me and i don't know what is the cause of the problem
Roamin64 said:
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
Click to expand...
Click to collapse
Im having similar issues. 6.0.1 on my tmo note 5 rooted perfectly using Max Lee's method. However as soon as I rooted and transfered all my data back I did a nandroid backup. Happen to wipe my phone the other night and and restored the nandroid backup and as soon as it restored I lost root. Happens everytime I restore even a newer nandroid in twrp. Never had this happen on any root method on any note.
WTF..
It's happened again this morning.. Root dissapeared by itself. The only recent thing I can think I did , was buying a game (The cave) from play store last night.
Any way to identify what is removing SU ?
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
I also lost root
I have a Samsung Galaxy Note 5 on the Sprint Network. I just now noticed that my applications that require root access, including Titanium Backup are reporting that my device is no longer rooted. Weird. This has never happened in the past when I had rooted Samsung phones. I will re-flash the Super User file as instructed in this thread and see if that resolves the issue.
---------- Post added at 03:01 AM ---------- Previous post was at 02:32 AM ----------
Per your insstuctions, I reflashed SuperSU 2.74 using TWRP. Then once my Note 5 rebooted, I launched Titanium Backup and found "SecurityLogAgent" and uninstalled it. However, in order for me to access TWRP I have to reinstall it using ODIN and immediately after I get the green "PASS" light in ODIN I have to quickly do the 'three finger' button press to launch TWRP. Weird....
Anyway, so far so good.
Thank you.
Battlehero said:
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
Click to expand...
Click to collapse
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Bosbouer said:
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Click to expand...
Click to collapse
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Roamin64 said:
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Click to expand...
Click to collapse
Thanks that worked to a certain extent. Titanium requesting root privileges for backup would still pop up as failed. Checking root would show as unrooted. The Superuser app was updated on the 5th of July 2016. Since I applied that update, i have not lost root on any of my devices.
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.
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.