Have a very weird and frustrating issue with my UK i9305 on EE.
As soon as it's rooted, no matter what SU app I use, it starts to heat up and leak RAM once booted until it runs out of RAM and restarts. And repeat. Until I unroot it and the problem stops. Initially, I thought it was a problem with SuperSU but I've also tried ChainsDD and Koush's Superuser apps with the same result. It looks like something requesting root access is causing a problem but I don't know what. It has said that it's granting root access to "shell" if that's anything to go by?
I resorted to wiping, flashing a newer 4.1.2 stock ROM (BLL5) but I still have the same problem. Can't for the life of me work out what's going on and really don't want to have to wipe again, especially since it seems not to fix the problem anyway.
Any ideas?
What method of root are you using??
Sent from my GT-I9305 using xda premium
Which version of SuperSU are you using? This was an issue in V1.0 for all Galaxy phones, and Chainfire has already released a workaround for this in the latest versions.
I've rooted using both CF Autoroot and mskip's toolkit. Same issue with both.
I'm aware of the issue with SuperSU and I've used subsequent versions of it (and indeed different SU apps) without success.
Interestingly, whatever version of SuperSU I try, the binaries can't be updated. I'm wondering if a previous unroot has left me with some relic of SuperSU that is causing me problems.
dave_uk said:
I've rooted using both CF Autoroot and mskip's toolkit. Same issue with both.
I'm aware of the issue with SuperSU and I've used subsequent versions of it (and indeed different SU apps) without success.
Interestingly, whatever version of SuperSU I try, the binaries can't be updated. I'm wondering if a previous unroot has left me with some relic of SuperSU that is causing me problems.
Click to expand...
Click to collapse
What about an Odin flash with stock firmware than try and root or flash a pre-rooted stock firmware?
Thanks
I did Odin flash the firmware I currently have but once I rooted, had the same problem.
dave_uk said:
I did Odin flash the firmware I currently have but once I rooted, had the same problem.
Click to expand...
Click to collapse
Use Odin v3.0x and flash Stock pre-rooted ROM from here http://forum.xda-developers.com/showthread.php?p=32929446
Sent from my GT-I9305 using xda app-developers app
Have you tried rooting without restoring the apps?
Snowstormzzz said:
Have you tried rooting without restoring the apps?
Click to expand...
Click to collapse
Thats what I thought reading his problem, never heard of "Shell" asking for SU-Rights
Related
Hi
I have installed SuperSU to my phone
Will this stop me getting any updates OTA
Thanks
Lee
No,
But you may lose root after ota.
Sent from my GT-N7000 using xda premium
Well, I installed SuperSU by flashing CWM-SuperSU-v.0.87.zip in CWM (which was first temporarily flashed using CWM.zip as an upgrade in the stock recovery)...
Here is the link for both zip files that I used to root:
http://downloadandroidrom.com/file/GalaxyNote/rooting/ICS
That rooted the phone fine while keeping everything stock and everything appears to work great, but now the OTA is failing...
So I'm running, thus rooted, stock 4.0.3 ICS and tried updating to 4.0.4 via OTA. Any ideas how to fix the failing OTA update without flashing a clean stock ROM via ODIN?
voxano said:
Well, I installed SuperSU by flashing CWM-SuperSU-v.0.87.zip in CWM (which was first temporarily flashed using CWM.zip as an upgrade in the stock recovery)...
That rooted the phone fine while keeping everything stock and everything appears to work great, but now the OTA is failing...
So I'm running, thus rooted, stock 4.0.3 ICS and tried updating to 4.0.4 via OTA. Any ideas how to fix the failing OTA update without flashing a clean stock ROM via ODIN?
Click to expand...
Click to collapse
Unroot your phone using Busybox Uninstaller (If you have installed busybox from Dr.Ketan thread only) from Dr.Ketan Thread. And Try Again.
Thanks for the suggestion, but the rooting zip that I mentioned didn't come from the Dr's thread, so his unrooting zip won't help here...
I updated my post above with the link to the zip file that I used for the rooting.
Looks like installing SuperSU this way did something to the /system that causes the OTA to fail... Any ideas on how to work around this?
open super SU - setting - Full unroot
Thanks, but I already tried that: SuperSU uninstalls, but OTA still fails at apparently the same place. I installed it back from the market and tried the full unroot again, with the same result... Any other ideas?
Before rooting, all the previous OTA updates worked flawlessly.
Did you flash a custom kernel, e.g. franco (as also in the webpage)? It may be the issue.
I also tried to unroot using the Voodoo OTA RootKeeper, but that didn't help me either.
If you can download 550MB data, then just flash using PC odin.
kopitalk said:
Did you flash a custom kernel, e.g. franco (as also in the webpage)? It may be the issue.
Click to expand...
Click to collapse
No. Only stock kernels, regularly updated OTA
dr.ketan said:
If you can download 550MB data, then just flash using PC odin.
Click to expand...
Click to collapse
Yeah, looks like I will have to...
I just thought that installing only the SuperSU was such a minimalistic way to root and would be easy to unroot since the app itself provides that feature.
The only other thing that was done to this phone was to make Titanium backups of several apps, but I don't see how that could affect anything either.
Anybody else ran into this exact problem?
Easy Unrooting?
dr.ketan, is there a "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread:
http://forum.xda-developers.com/showthread.php?t=1424997
?
I see a set of attached files at the bottom of this post:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
, but the insides of the SU-Busybox-Installer.zip are not the same as SUPERSU-Busybox-Installer.zip,
so I assume the SU-Uninstaller-signed.zip will not work. Or will it?
Thanks.
You can try the uninstaller. If you look at the script basically it will remove superuser.apk and su binary. Since superuser (by chainsDD) and superSU are using the same apk name (superuser.apk), the effect will be the same. However I'm not sure how to remove busybox other than by flashing stock kernel.
voxano said:
dr.ketan, is there a "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread:
http://forum.xda-developers.com/showthread.php?t=1424997
?
I see a set of attached files at the bottom of this post:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
, but the insides of the SU-Busybox-Installer.zip are not the same as SUPERSU-Busybox-Installer.zip,
so I assume the SU-Uninstaller-signed.zip will not work. Or will it?
Thanks.
Click to expand...
Click to collapse
This is for SU Busybox installer, not for SuperSU busybox installer.
If you have rooted with same file, you can see attached with that uninstaller, then only it works
May it be work, but chances of leftover there.
Not so easy UNrooting...
kopitalk said:
You can try the uninstaller. If you look at the script basically it will remove superuser.apk and su binary. Since superuser (by chainsDD) and superSU are using the same apk name (superuser.apk), the effect will be the same. However I'm not sure how to remove busybox other than by flashing stock kernel.
Click to expand...
Click to collapse
Thanks for the input, kopitalk. Sounds like flashing stock kernel would be the only certain way to unroot in this case...
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
dr.ketan said:
This is for SU Busybox installer, not for SuperSU busybox installer.
If you have rooted with same file, you can see attached with that uninstaller, then only it works
May it be work, but chances of leftover there.
Click to expand...
Click to collapse
So there is NO "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread, right?
Moot
http://forum.xda-developers.com/showthread.php?t=1810954
http://forum.xda-developers.com/showthread.php?t=1329360
I rooted my XT890 which is on 4.0.4. I don't know what it's called that I used to root it with and I don't have the same exact download link but it's the only one on the internet that doesn't require you to flash anything.
So I ran that and I thought I had my phone rooted. The major problem is that most apps that require root privileges don't work. The only root app that works is busybox. On other ones, the superuser permission prompt will pop up and will I press "allow". Then, it will say "[whatever program] has been granted superuser permissions". After that, whatever superuser requiring app I'm using will go to an error the same way it would on a completely stock un-rooted phone.
Will buying superuser elite fix it?
Will un-rooting and re-rooting by flashing a homemade fastboot fix it? If so, how do I un-root?
Can anybody help?
Did you solve your problem?
Veraster said:
I rooted my XT890 which is on 4.0.4. I don't know what it's called that I used to root it with and I don't have the same exact download link but it's the only one on the internet that doesn't require you to flash anything.
So I ran that and I thought I had my phone rooted. The major problem is that most apps that require root privileges don't work. The only root app that works is busybox. On other ones, the superuser permission prompt will pop up and will I press "allow". Then, it will say "[whatever program] has been granted superuser permissions". After that, whatever superuser requiring app I'm using will go to an error the same way it would on a completely stock un-rooted phone.
Will buying superuser elite fix it?
Will un-rooting and re-rooting by flashing a homemade fastboot fix it? If so, how do I un-root?
Can anybody help?
Click to expand...
Click to collapse
Hi, obviously we had a similar problem (
forum.xda-developers.com/showthread.php?p=42529975#post42529975) and I am not sure about how to tackle the problem. Did you find a solution for your rooting problem? If yes I am curious how you solved it.
Cheers
BlackundDecker said:
Hi, obviously we had a similar problem (
forum.xda-developers.com/showthread.php?p=42529975#post42529975) and I am not sure about how to tackle the problem. Did you find a solution for your rooting problem? If yes I am curious how you solved it.
Cheers
Click to expand...
Click to collapse
Nope I never figured it out.
It seems that most superuser apps aren't compatible with x86 Android unless the developers have specifically taken steps to solve it. Since RAZR i users make up an incredibly small amount of android users, almost no one bothers to make their root apps work.
Veraster said:
I rooted my XT890 which is on 4.0.4. I don't know what it's called that I used to root it with and I don't have the same exact download link but it's the only one on the internet that doesn't require you to flash anything.
So I ran that and I thought I had my phone rooted. The major problem is that most apps that require root privileges don't work. The only root app that works is busybox. On other ones, the superuser permission prompt will pop up and will I press "allow". Then, it will say "[whatever program] has been granted superuser permissions". After that, whatever superuser requiring app I'm using will go to an error the same way it would on a completely stock un-rooted phone.
Will buying superuser elite fix it?
Will un-rooting and re-rooting by flashing a homemade fastboot fix it? If so, how do I un-root?
Can anybody help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2281224
That link above will install you cwm if you don't already have it then with that you can flash either the RAZR I Root or RAZR I Root 2 .zip... It just depends which one is for your ROM and I didn't link because I couldn't find it or have it bookmarked anymore but if you find it and flash it through cwm it will definitely work
Sent from my RAZR I XT890 using XDA premium
Cause you are on ICS (4.0.4) you have to follow the instructions from this thread
http://forum.xda-developers.com/showthread.php?t=1928509
There is a way with unlocked bootloader and one without
So I was having issue with my note 3 ( bluetooth issues ) I upgraded to 4.4.2
AT&T sent me a new / refurb phone and it has 4.3 on it.
So Im curious on what you guys would do?
Upgrade to 4.4.2 and stick with all this stupid bloatware
or
Root, and rom it?
If that latter, does anyone have any links to do that ( I used to do it with my S2, S3 and S4 )
thank s
Root it. It's not worth the grief to upgrade it to 4.4.2.
You can root it and use safestrap to install custom ROMs, or just enjoy the stock setup with root.
Sent from my locked down Note 3 via the tapatalk app
ROOT AND ROM it!
I was ROOTED and ROM'd, but I got bit by the OTA Upgrade bug... I went through all the hassle of downgrading, unrooting, resetting, then upgrading.
Now I've got the fresh new bloated OTA official 4.4.2 and NO ROOT.
Should I use Kingo? is that still safe for the Note 3 on 4.3?
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Root it!
I rooted with Kingo, no problems, the first day I got the Note 3 and took the Nb4 update. I was so lucky to catch the KK update and froze it mid-download with ttb. I am so glad!! I wouldn't be able to use this thing without root. I have installed safestrap and roms without issue. (staying on 4.3 roms mind you)
scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
try uninstalling ss then install it again, make sure it is 3.71 not 3.72. 3.71 doesnt need busybox if im not mistaken.
scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
I am going to use Kingo tomorrow as well I think. How does get root? Will it have superuser on it after it roots or do you have to put it on the phone yourself?
Thanks.
Krunk83 said:
I am going to use Kingo tomorrow as well I think. How does get root? Will it have superuser on it after it roots or do you have to put it on the phone yourself?
Thanks.
Click to expand...
Click to collapse
kingo installs supersu. when supersu installs, click on it and choose disable knox, presto!
i upgraded to nc2 and want to downgrade to mj5 now.. any method ?
anuragsodhi1 said:
i upgraded to nc2 and want to downgrade to mj5 now.. any method ?
Click to expand...
Click to collapse
no downgrades from official ota nc2 sir, no root method and no unlocked bootloader.
scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
Did you try rebooting into recovery via a power menu? That is what the tutorial says it should do. Hold power to bring up the menu and it should then have an option to reboot into recovery. I am going to try safestrap too I think.
So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.
I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...
Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?
I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it
Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk
Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?
Did you flash over 2.71. And do you have a su app icon on your scrren.
noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.
Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot
MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!
Welcome bud.
Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother
Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk
Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha
My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk
I think it's normal...maybe...ha Im pretty sure it's the warranty bit
are there root for N910A 5.1.1
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.
Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...
I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Thanks! I'll give that a try when I get home today.
S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...
Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.
https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app