I don't know how this happen but it was previously on JB (slimbean) and I flashed Slimkat. It said it couldn't installation had failed a couple of times, so I did a factory reset and stuff and wiped the phone completely and tried again. The phone flashed correctly this time and I was able to boot into Kitkat, everything was working fine.
But when I tried to install Greenify etc. I found out that I had lost root. I'm not sure how this happened because obviously I was previously rooted otherwise none of this could have worked. I tried flashing another kernel (Mackay) nothing changed. I tried installing SuperSU etc. nothing.
Any ideas why? I just want to be rooted so that I can use the Galaxy S Unlock app to unlock the phone which is my main concern (need it for new sim). If there is any other method to unlock the phone without having to root it would be fine as well as long as I can unlock the phone.
Any ideas?
Thanks
utsmaster18 said:
I don't know how this happen but it was previously on JB (slimbean) and I flashed Slimkat. It said it couldn't installation had failed a couple of times, so I did a factory reset and stuff and wiped the phone completely and tried again. The phone flashed correctly this time and I was able to boot into Kitkat, everything was working fine.
But when I tried to install Greenify etc. I found out that I had lost root. I'm not sure how this happened because obviously I was previously rooted otherwise none of this could have worked. I tried flashing another kernel (Mackay) nothing changed. I tried installing SuperSU etc. nothing.
Any ideas why? I just want to be rooted so that I can use the Galaxy S Unlock app to unlock the phone which is my main concern (need it for new sim). If there is any other method to unlock the phone without having to root it would be fine as well as long as I can unlock the phone.
Any ideas?
Thanks
Click to expand...
Click to collapse
When you flash most of these KitKat ROMs it seems you lose the superuser facility in so doing. Go to Settings>About Phone>Build number .... and press it like 7 times until it says you have developer options. Then go to Developer options and allow root access to apps or apps and ADB depending on your preference.
Then try Galaxy S unlock.
If the unlock doesnt work (and I know some people who say it hasnt) go back to GB 2.3.6 stock, root it with cf-root as usual, and then try unlock there. Then move back up to your kitkat after its unlocked.
Incidentally when moving up to Kitkat be sure to flash fist Cyanogenmod ROM, CM10.2 (or above) to get the new CWM recovery and the correct partition so that the rom works well.
Let us know
Thanks for the response. What I did was flashed semaphore for KitKat using Odin. That did the trick for giving root. Used galaxsim unlock and everything succeeded except for one thing (network lock) but I think that may have been due to there being no Sim in the phone currently.
Sent from my Nexus 4 using Tapatalk
Root permission
joedom1 said:
Go to Settings>About Phone>Build number .... and press it like 7 times until it says you have developer options. Then go to Developer options and allow root access to apps or apps and ADB depending on your preference.
Click to expand...
Click to collapse
Thanks man!! I was also worried abt this. Installed SlimKat on my GT-N7000, everything worked ok (still testing) until I wanted root access, I installed SuperSU but it didnt get any response, I even reinstalled the CWM, which screwed my firmware (had to reinstall that too! :silly: )
After pressing "build number" as u said repeatedly, I got the developer options enabled, where I activated root permission. Then SuperSU installed n updated with proper root permission! :good:
Stallione said:
Thanks man!! I was also worried abt this. Installed SlimKat on my GT-N7000, everything worked ok (still testing) until I wanted root access, I installed SuperSU but it didnt get any response, I even reinstalled the CWM, which screwed my firmware (had to reinstall that too! :silly: )
After pressing "build number" as u said repeatedly, I got the developer options enabled, where I activated root permission. Then SuperSU installed n updated with proper root permission! :good:
Click to expand...
Click to collapse
Pleasure mate, not the first time its happened,
_________________
Hit the Thanks button if you think it helped
Related
Two days ago i rooted my phone with VRoot, but now after i tried to install a new app i found, it said i couldn't and then i went to settings, checked Unknown sources, but after i back it is no longer checked, also some apps are crashing randomly.
One thing i did was using the Market enabler/DroidVPN method to unlock the us play store only to find out it does not work, i would say after i did this my phone started acting all weird
edit: phone is also randomly freezing
ppgab said:
Two days ago i rooted my phone with VRoot, but now after i tried to install a new app i found, it said i couldn't and then i went to settings, checked Unknown sources, but after i back it is no longer checked, also some apps are crashing randomly.
One thing i did was using the Market enabler/DroidVPN method to unlock the us play store only to find out it does not work, i would say after i did this my phone started acting all weird
edit: phone is also randomly freezing
Click to expand...
Click to collapse
My best advice to you is backup your personal data, and reflash with odin, you can also flash custom rom, recovery + kernel with the odin packages supplied by the maclaw team or flash stock .
sheephog said:
My best advice to you is backup your personal data, and reflash with odin, you can also flash custom rom, recovery + kernel with the odin packages supplied by the maclaw team or flash stock .
Click to expand...
Click to collapse
thanks for the reply, what i did was install cyanogenmod 4.4.2, everything is fine so far, i don't understand much about flashing and roms and stuff.
Hello there everyone, total noob here.
I have tried to "root" my S3 LTE using this method: http://forum.xda-developers.com/gal...-cf-root-cwm-recovery-ported-supersu-t1914394 (or more likely this: http://forum.xda-developers.com/showpost.php?p=45291825&postcount=306 ). Everything went great, Odin has shown a pass and it was successful while installing CWM, then I installed Supersu through CWM (only thing I did differently was putting a supersu zip file on internal storage) and that was a success too. I did everything like it said, even without plugging out my phone. After rebooting everything went down...
1. Knox is blocking SuperSU, someone reccmmended that I should have tried to disable it by installing supersu.apk manually, but then it has shown a popup that supersu doesnt have access to binary files. I have checked with root checker and it said that device isnt rooted...
It wouldnt bother me much, because having root isnt necessity for me, but...
2. I cannot access internet via wifi. It connects to router, signal is pretty decent, but still, when I try to use a build-in browser/chrome it just doesnt connect. Nevertheless, I can connect via 3/4g with no problems at all.
Now, I dont have root AND internet access.
Other info that might me useful:
Android 4.3
Null IMEI: no
Baseband: i9305XXUEMK1
I have performed factory reset, still no use.
Any help regarding repairing wifi, getting root access or bringing back state before "rooting" would be appreciated.
Regards,
Maziu92.
Maziu92 said:
Hello there everyone, total noob here.
1. Knox is blocking SuperSU, someone reccmmended that I should have tried to disable it by installing supersu.apk manually, but then it has shown a popup that supersu doesnt have access to binary files. I have checked with root checker and it said that device isnt rooted...
It wouldnt bother me much, because having root isnt necessity for me, but...
Click to expand...
Click to collapse
Just download the "SuperSU version 2.02" apk and install it. Its provided in this thread. (its newer than whats currently on Google play)
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
It will ask to disable KNOX. select YES.
Maziu92 said:
2. I cannot access internet via wifi. It connects to router, signal is pretty decent, but still, when I try to use a build-in browser/chrome it just doesnt connect. Nevertheless, I can connect via 3/4g with no problems at all.
Click to expand...
Click to collapse
The best thing i can suggest you is moving to the new 4.4.4 Stock Rom
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Use Odin v3.07
and then (if u want) root it using "CF-Auto-Root-m3-m3zh-gti9305.tar.md5."
and install "SuperSU version 2.02"
tharinduwijewardane said:
Just download the "SuperSU version 2.02" apk and install it. Its provided in this thread. (its newer than whats currently on Google play)
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
It will ask to disable KNOX. select YES.
Click to expand...
Click to collapse
Oh, I did it, that's why it said the binary was missing. But I did it other way around:
1. I have flashed CWM like it said in second link provided in first post
2. Installed SuperSU 2.02 from zip file on internal card though CWM instead of file provided in thread (I could have installed remove-boot-recovery too, but I didnt notice that I needed that. Anyway, I did that later)
3. Rebooted and tried to turn on - supersu was still blocked by knox :/ BUT!
4. I have installed manually supersu.apk, then opened it via installator (important! Dont tap 'done' but 'run'!) and next I didnt get the "missing binary" popup but if I want to disable KNOX. Well, yeah, I do, so I tapped OK and it looped and looped... http://www.reddit.com/r/galaxys5/comments/2a92qq/supersu_stuck_disabling_knox/cisq087 found this soulution and it worked (reboot phone and start supersu again). Sorry about my short memory, but I think I needed to install supersu.apk manually again and tap disable once more time, but disabling KNOX took a few seconds.
5. And then I went to the settings in Supersu and tapped option 'install supersu into /system', rebooted and it worked fine!
5.a To make sure it really works I downloaded (via 3g ) Root checker and it said it is rooted.
So now I have root, yaay, but still no Wifi access :/
tharinduwijewardane said:
The best thing i can suggest you is moving to the new 4.4.4 Stock Rom
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Use Odin v3.07
and then (if u want) root it using "CF-Auto-Root-m3-m3zh-gti9305.tar.md5."
and install "SuperSU version 2.02"
Click to expand...
Click to collapse
I have been using odin 3.07.
Really, It is the only way to get back wifi? Are there any other options apart this?
Nooby questions:
-will it work with my phone? It says that its "MODEM: I9305XXUFNI3" and mine is XXUEMK1.
-in the meantime I have read about efs files/folder, what are they for and should I somehow backup them?
-while flashing 4.4.4 it is possible that my IMEI will go null?
-will it be possible to go back to 4.3?
I dont want to brick it or anything, thats why I am asking.
And of course, thanks for your help, Tharinduwijewardane ^^
Edit:
Actually, I have managed to repair my WIFI connection without flashing new rom etc.... So what was wrong, you will ask? Me.
I have downloaded adblock (before factory reset) and it asked to connect via proxy, so I did. And then I have disabled it because it was blocking SuperSU along with KNOX. And my phone tried to connect with internet via proxy, but it couldnt, because of this configuration.
Found this by complete coincidence (my GF told me to check if I get connection though Chrome and it said that it cant connect because of proxy settings). It is strange that this configuration was still there, even after factory reset.
Oh well, case solved, thanks again for helping and even everyone else for checking this out^^
glad to hear u got it fixed.
:good: :good:
Hello everyone... I just bought at&t note 3 unlocked version. Problem is that its on kitkat 4.4.2 and doesnt show any ota update so can anyone please provide me a link of stock rooted at&t lollipop rom which i can flash and root method with a proper guide please? I would be very thankful.
What you do is root what you have, install Towelroot https://www.androidfilehost.com/?fid=23991606952593961 (open the app and click "make it rain" and it's rooted). Install Supersu and Busybox, then Safestrap https://www.androidfilehost.com/?fid=23991606952593962, open it and install it and this is rooted lollipop http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2. Just one thing, (not saying you will) but flash the OC1 Kernel in Safestrap before you leave Safestrap. " 5. Flash the file called "SM-N900A_OC1_Kernel_Safestrap_Installer.zip" which is located under /sdcard/OC1_Kernel/ "
Hey Rooted, i have a 1.39gb file on my ext sd card called SM-N900A_0C1_Lollipop_Rooted_rom.zip, is it safe to delete this if i already have rooted oc1? or do i need it to flash safestrap? Also, for the past few weeks my oc1 rooted note 3 has been randomly rebooting itself in the middle of me using it, then entering a bootloop until it successfully boots up. Then sometimes when it successfully boots up, it reboots itself right when i put my password into the lockscreen. Sometimes clearing the cache doesnt help, i clear it multiple times for it to work. The other day i clicked the end button on a phone call, and right when i ended the call it rebooted itself. im lucky it didnt reboot during the call, i was on the phone with a towing company lol! Any idea whats going on?
If it's rooted, yea you can delete the file then. Do you have Xposed install, flash anything else with Safestrap, did you do a clean install of the Rom? When did the rebooting start, after you installed an app?
I do not have xposed framework installed, i heard its not compatible with the oc1 root. I never flashed any custom rom, im running just a stock rooted rom. Im not sure exactly when the rebooting started, its been going on for 2-3 weeks, i cant remember what i did before that. Last night i swapped sd cards to make sure it wasnt that, but i already had 1 random restart today. Do you think swapping sim cards is a good idea?
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 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