After a long time thinking about it, I finally decided to try to root my Nexus 4 and install the Franco kernel. I wanted to do this mainly to get some control over the audio output of my device.
The amazing Wugfresh Toolkit got me up and running as root. I then used the Cyanogen auto-installer to install Cyanogenmod 11. I was very happy, and went ahead and downloaded the paid version of the Franco Kernel Updater from the Play store.
All good, but then when I went to lauch the Franco Kernel, I got an error saying 'You're root, but Superuser seems to be denying access. Open Superuser, choose 'forget' and come back to the Franco Kernel and you will likely be asked to allow it'.
So I went to Superuser (took me a while to find it because it used to be an icon on my desktop but it seems that it went away after I installed a custom theme, and I found it only at the bottom of the settings list). I couldn't find anything about 'forgetting', but I could see a log that showed 'deny' then 'allow'. So I went back to to the Franco app and voila! It was open and allowed me to look into all the different functions.
Using the video which is up at the Franco Kernel page at the Play store as my guide., I tried to go into 'Kernel Settings' to access those audio controls... and strangely, there were only 4 items there, the vibration control and 3 others. None of the audio control choices were there.
I thought I had to flash the Kernel so I went ahead and did that. After restart, I again got the 'Superuser' access error. I opened Superuser, but this time I could not get it to 'allow' the Franco Kernel. I could see the log with lots of 'Deny' events. I then did something I probably shouldn't have - I clicked the 'trash' icon. Now, it just says 'There are currently no Superuser app policies'.
So I'm at a standstill. I'm not a huge tech guy but I thought I would give this a try because how else will I learn, right?
Can anyone help me figure out
a) How to simply get the Franco Kernel app open again (by configuring Superuser to stop denying it), and
b) Why I can't see those audio controls in Franco Kernel?
Sorry for such a long post
Nick
Wow.
I saw that there was an option to 'Disable' Superuser permissions. So I tried that, but the Franco Kernel error message still popped up.
I went back to Settings to open Superuser and reset it to where it was... and now the Superuser icon has disappeared from the list at the bottom of the Settings page!
It doesn't show up in the list of Apps either (but it never did, even when I was searching for it earlier and found it on the Settings page).
CyanogenMod has their own implementation of superuser. And as such they can put it in settings instead of in an app.
Here is how you re-enable the superuser menu http://forum.xda-developers.com/showpost.php?p=39903306&postcount=5
As for your how to allow root action, see if there is an option in the superuser menu for something like a default action and make sure that it's set to ask for permission.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
SMillerNL said:
Here is how you re-enable the superuser menu http://forum.xda-developers.com/showpost.php?p=39903306&postcount=5
As for your how to allow root action, see if there is an option in the superuser menu for something like a default action and make sure that it's set to ask for permission.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Click to expand...
Click to collapse
Thanks a lot for the response. I was able to tap 7 times and get back to Develope Mode. I then clicked Developer Options and turned it 'on' as instructed. However, in the long list of items on that 'Developer Options' list, I could not find anything that says 'Root Access'.
Can you give me any indication where 'Root Access' can be found?
Thanks again, I will try to Google it in the meantime.
Unfortunately, I just cannot get Superuser to allow the Franco request. I can see the 'deny' event and I have played with everything available to me via Superuser-->Settings, but there's nothing there that says 'Forget', which the error message from Franco tells me to look for, and there's nothing that says 'Permissions' or anything else with which I can allow Franco!
tradernik said:
Unfortunately, I just cannot get Superuser to allow the Franco request. I can see the 'deny' event and I have played with everything available to me via Superuser-->Settings, but there's nothing there that says 'Forget', which the error message from Franco tells me to look for, and there's nothing that says 'Permissions' or anything else with which I can allow Franco!
Click to expand...
Click to collapse
When you open the superuser tab of the settings app, you should get a list of all allowed and denied apps. When you then long-press on one of the apps, you get another window where you should be able to deny access (to the apps that are allowed) or vice versa
Moreover, Franco kernel is not officially compatible with cm, so don't expect a bug-free experience even if you get it working.
Sent by carrier pigeon
Isn't Franco recommanded only for AOSP roms ?
laufersteppenwolf said:
When you open the superuser tab of the settings app, you should get a list of all allowed and denied apps. When you then long-press on one of the apps, you get another window where you should be able to deny access (to the apps that are allowed) or vice versa
Click to expand...
Click to collapse
Thanks for the response. Unfortunately, when I open SU, the main window is empty and there's a message saying
"There are currently no Superuser App policies".
Trying to open Franco and allowing SU to deny it doesn't populate this window - it just says the same thing. When I click on Settings or Logs in SU, I can see the logs with the denial events. Even long pressing on those doesn't pop up a box which allows me to give Franco access.
Any thoughts?
klvnhng said:
Moreover, Franco kernel is not officially compatible with cm, so don't expect a bug-free experience even if you get it working.
Click to expand...
Click to collapse
I see. Okay, I wasn't aware of that.
It looks more and more like I am going to let Wugfresh re-configure my phone. I am assuming that in its current state, I can ask Wigfresh to just re-do the root process. Everything was going great until i installed Cyanogen and then Franco.
As an aside, rooting the phone has solved a problem I was having with my Gmail app. One initial startup each day, I would have to do a restart to get the Gmail app to pull emails in. It was always exactly two starts that were necessary, and it always worked on the second start. The native Andorid app which was handling my Hotmail didn't have that problem.
So rooting has been a positive for me so far.
AndyTimE said:
Isn't Franco recommanded only for AOSP roms ?
Click to expand...
Click to collapse
Aha, okay. Well, maybe the thing for me to do is let Wugfresh re-do the root process and then try an AOSP ROM. Of course, the thing about CM is that there was that handy self-installer.
This is a slippery slope, I can see that. I have seen a few good guides here for doing this stuff manually. Maybe the time has come for me to really figure it out...
In fact the phone is definitely a bit unstable now. It's working fine but the screen is flashing at me a lot. The Swiftkey keyboard intermittently disappears when I am writing an email or a text.
I think I'll start over again. If possible, can someone confirm for me that I can just use the Wugfresh toolkit and ask it to do the root process again from the phone's current state, or do I have to do a restore back to factory and then do the root process again from there?
Related
Was working and after flashing the new image for Sprint from Flipz it stopped working..
what do i have to do to fix it? can someone guide me please
What is it doing / not doing? It works fine. What steps did you take when you flashed it? What rom did you come from?
Make sure USB Debugging is checked in Settings>Applications >Development
Hey flipz....
I'm on your latest ROM Fresh 2.0d and flashed the new image over it..
Superuser doesn't pop up the allow/deny option whenever i try to run an app that uses it..
PROBLEM SOLVED!
MOD's delete this thread please ..thanks!
Just flashed from the first RegawMOD to Fresh 2.0d on my wife's and had to check it i didn't have to on mine but I've flashed so many times I can't even remember what it was before flashing Fresh. Always wiping before flashing as well.
I was having problems with all my apps that require SU permissions since I installed Fresh 2.0d. I realized that usb debugging was not enabled, but after enabling i was still having problems when the SU window would pop up totally black and just hang there.
What worked for me was enabling usb debugging then going into settings>applications>manage applications, then selecting the Superuser app and clearing the data. Now the Superuser allow/deny window pops up like normal when opening those apps which require permissions.
I have a question that some of you might be able to answer. It got buried in the dc2.05 thread. It's regarding the Superuser Permissions app/utility.
I get allow/deny prompts for various tasks, so the actual function works fine. I'm wondering about the management when I open the Superuser Permissions app. It looks like I can clear a set permission by tapping on the rule. However, it always looks like I only have one rule, which is listed at the top. If I tap on it to clear it, another rule will be displayed. It's as if all my rules are overlapping on the top row.
If I want to clear a single rule, there's a chance I need to clear multiple rules to get to it. Is that how things are supposed to work? I'm guessing all the rules should be displayed in a list; but being new to all this, I could be wrong. Are fresh users seeing this behavior?
e30user said:
I have a question that some of you might be able to answer. It got buried in the dc2.05 thread. It's regarding the Superuser Permissions app/utility.
I get allow/deny prompts for various tasks, so the actual function works fine. I'm wondering about the management when I open the Superuser Permissions app. It looks like I can clear a set permission by tapping on the rule. However, it always looks like I only have one rule, which is listed at the top. If I tap on it to clear it, another rule will be displayed. It's as if all my rules are overlapping on the top row.
If I want to clear a single rule, there's a chance I need to clear multiple rules to get to it. Is that how things are supposed to work? I'm guessing all the rules should be displayed in a list; but being new to all this, I could be wrong. Are fresh users seeing this behavior?
Click to expand...
Click to collapse
Same function for me, just shows one rule at the top. Its been like this on fresh 1.0 and 2.0. Looks like you can only clear one at a time, or all at once in the "manage applications" setting as I described above.
First I love AOKP, and it has defined android for me for a while. I need some help getting multi-user support on the aokp nightly. Apologies, if this is against any rules.
I am running the latest 10/15 nightly, although a majority of my attempts were done on the 10/10 nightly.
My setup post freset:
twrp to install nightly, gapps 08/13, photosphere, lte zip.
boot rom, no google sign in
adb push titanium backup, restore android device id, reboot, restore all apps with data
restore nova settings and lte apn settings
Click to expand...
Click to collapse
So this is where I'm starting from.
ATTEMPT 1
I use terminal for the following
adb shell
su
pm get-max-users (should show 1)
setprop fw.max_users 8
pm create-user Guest
Click to expand...
Click to collapse
This brings up the users tab in settings where I can see the Guest user I just created. I go to set it up and it soft reboots to the welcome to android setup screen. Great. but every gapps start crashing. basically fail fail fail. no keyboard means I cant set up the profile. Even then there's no way to get to terminal to softboot back to my original. so from here I nandroid restore in twrp.
ATTEMPT 2
My next option was to start from a clean install and download/install the xposed framework. That allowed me to use the Modaco Toolkit module that list the following as a feature.
Google Nexus (all): Enable multi-user support if unsupported on stock (e.g. Nexus 4).
Click to expand...
Click to collapse
This actually worked well. I saw the users option in settings, I was able to create different users, and the phone soft rebooted to set up the new user. Great, but still every gapps stoppes working as soon as the welcome screen pops up. Although with this option I can long press the power button and go back to my original user.
So can anyone provide some insight as to how to install the gapps in the emulated /1 folder for a second user?
Since multiuser on phone is a Microsoft Nokia patent, Google can't enable it by default.
I don't know how to edit the buildprop to do it, but I use this app to enable it: https://play.google.com/store/apps/details?id=org.sferadev.multipleuser
The problem is your DPI have to be below a certain number for the multiuser switching to show up on your lockscreen, 192 or something. But then everything on the screen looks very small so its not worth it anymore unless you have a 6" device maybe.
I know that Paranoid Android have multiuser feature so it's the only solution I know of. I'm just not willing to let go of AOKP either.
Hey guys in this tutorial i will show you how to root the Samsung Galaxy Exhibit from Metro PCS, model SGH-T599N.
The phone comes Stock with Android Jelly Bean 4.1 Jelly Bean. This will also work on 4.1.2 Jelly Bean.
So lets get started.
There is a tutorial video at the bottom of the page
WARNING:
THIS WILL MOST LIKELY VOID YOUR WARRANTY.
YOU DO THIS AT YOUR OWN RISK, THERE IS A CHANCE YOU COULD BRICK YOUR PHONE.
What you will need:
1) A Samsung Galaxy Exhibit SGH-T599N
(To check your model number, go to Settings / About Device / Model Number)
2) A PC running Windows (XP, Vista, 7, 8 or 8.1)
3) A Usb Cable
4) Rooting program called VROOT
Step 1:
You need to download the VROOT rooting program.
https://www.dropbox.com/s/f85okpyc1u33zgt/Galaxy_Exhibit_Root.zip
Once the link is downloaded, extract the zip. You will get a .exe file called VRoot_1.7.3.4863_english_cid1005_7337ba1e_89.exe
Run the VRoot_1.7.3.4863_english_cid1005_7337ba1e_89.exe You will be greeted with the VROOT Setup Screen.
Click the Next button. You will be taken to the screen where you can chose where the installer, installs the program. You can chose a directory or use the default. Use the default.
Click the Next button. The next screen will ask you if you want the program to be put in your Start Menu, this is up to you.
Click the Next Button. The next the screen will ask if you want to place a Shortcut on your desktop, again this is up to you.
Click the Next Button. The program will now install it self. It should only take a couple of seconds. once the installer is done you will see the Setup Complete screen. Make sure the Launch VROOT box has a check in it and click the Finish Button.
The VROOT program will open. You will see a screen saying Device is connecting. After a moment the program will install daemon.
Step: 2
For the program to recognize you phone, you will need to turn on Usb Debugging on, on your phone. To do this on your phone go to Settings / Developers Options
Scroll down to the Debugging Section. Look for USB debugging and click on it.
A warning will pop up saying Allow USB debugging, select OK
After you turn on Usb Debugging a second warning should pop up on your phone asking if you wanna allow Usb debugging between your computer and phone. Check the always allow and then OK. Checking Always makes it so you do not have see that warning everything. Your computer and phone will allow debugging connect every time you connect in that mode.
Step 3
Now back on your PC you should see VROOT trying to connect to your phone. Once it connects you should see your phones model number on the screen. T599N
VROOT will now check to see if your phone already has root permission. VROOT will tell you, you do not have root.
The green root button in the bottom right corner should now be available. Press the Root button.
You will see the Rooting now screen. This should only take a moment to complete.
When VROOT is done, you will see a screen saying Success, your T599N is rooted. Rebooting.
You can now click complete, you are done with the VROOT program.
Step 4
You Exhibit will now reboot back into the Android OS
Once you are back at your home screen, open the app drawer in the bottom right hand corner to show all your phone apps. Scroll all the way to the right. You should now have two new apps installed on your phone. Superuser and one that is in Chinese. The one in Chinese was installed when VROOT told you it was installing daemon. You will no longer need that app.
The Superuser app is the one we want. This app regulates which app you grant root permission to. Just open the app. Make sure it does no tell you, you do not have root permission.
Now my suggestion here is to get a different app to do the same thing. The one you should use is SuperSU by Chainfire from the Play Store. Go to the Play Store and in the search look for SuperSU. There are 2 verions, a free one and a paid one. The free on works just fine.
Install this version. You will now have a app that looks like a Superman symbol with a # inside of it. Open the app. Make sure SuperSU does not tell you, you do not have root.
Now anytime a app requests root, a warning will pop up from SuperSU asking if you want to allow that app root access.
You have the option to Deny or Grant that app root. You can also check the Ask again box. If you check this box and Grant a app root, after some time SuperSU will pop up again asking the same thing. If you chose to Grant a app root without checking the box, that app will have full root access anytime you use it.
If you Deny it then the app will not have root access and not work the way it was ment to.
And that's it guys. You now have root access on your Metro PCS Samsung Galaxy Exhibit SGH-T599N
Video Tutorial
https://www.youtube.com/watch?v=SzUpbP55k30
Checkout my blogger page for these instructions with lots of pictures.
Checkout my Youtube page also
If this helped in any way please leave a comment of say thanks.
Can anybody here confirm that this method works? My mothers phone is in need of rooting and I want to make sure this won't brick her phone.
Same question
any verification this will work? Thanks in advance.
dadlovsyall said:
any verification this will work? Thanks in advance.
Click to expand...
Click to collapse
I can verify that this rooting method works. 100%. It's simple and easy to do. I'd recommend it.
Rooted my wifes t599n , metro pcs, stock rom. Worked perfect exept now i can't remove he chinese superuser app, i can disable, but new superuser will not install over it.
Never mind, got it.
sent from my lgms323 towelrooted waiting on cstom rom
brentwago said:
Rooted my wifes t599n , metro pcs, stock rom. Worked perfect exept now i can't remove he chinese superuser app, i can disable, but new superuser will not install over it.
Never mind, got it.
sent from my lgms323 towelrooted waiting on cstom rom
Click to expand...
Click to collapse
How did you get it?
jeankeeRD said:
How did you get it?
Click to expand...
Click to collapse
Found it in one of the cleaner apps on there, don't remember which one tho, sorry I went through like 6 of them that day.
sent from my lgms323 towelrooted waiting on custom rom
brentwago said:
Found it in one of the cleaner apps on there, don't remember which one tho, sorry I went through like 6 of them that day.
sent from my lgms323 towelrooted waiting on custom rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2843809
still working, EXE auto-updated, then i followed simple instructions, and the device rebooted with root.
vroot does install its own Super User Permission Management app, and a System Cleaner app (which are both actually useful), and some other junk (i uninstalled this). all their apps seem to have links to their other apps/appstore, but as long as you ignore them the apps themselves seem to be harmless enough.
Hi all. I've installed kodi and with the confluence ++ skin. There are a few observations and questions I would be grateful if someone could help point me to the right direction.
1. I cannot get the power suspend option on kodi like how it exists in spmc. Is there a settin somewhere to enable it.? I cannot seem to find it. maybe some config file?
2. When adding 7 tiles to the bottom, the first tile gets slightly cut.
3. With rbox's boot menu. Is there a way to disable the boot menu display on every boot? or at least decrease the time of 5 seconds?
Really appreciate your help.
I tried to add the power options from elmero's repo but that requires the su and when I try to run the su script, it fails. however I do have root. am confused to make kodi my main OS yet . any guidance?
have you went into the SU app under the FTV menu ( the OEM rom, not XBMC ) and launch SU. Update binaries and apply etc. Try that.
mroneeyedboh said:
have you went into the SU app under the FTV menu ( the OEM rom, not XBMC ) and launch SU. Update binaries and apply etc. Try that.
Click to expand...
Click to collapse
what is the su app you are referring to in the ftv menu? I have supersu and I have an option to force stop only
also when I try spmc, I get the power options
confused.
Open superuser from the FTV app list and let it update.
Montisaquadeis said:
Open superuser from the FTV app list and let it update.
Click to expand...
Click to collapse
I have the supersu application. That does not have an open option. I also downloaded the superuser from the playstore and I still get eh checksu.py script failure. on spmc I too get the script failure but I have the power options working just fine.
Sorry man, there should be an option to update binaries like in any SU app.. Which version are you using
When I installed rbox's CMW recovery and custom ROMs I lost the ability to open su. I believe this is a known issue.
jmerrilljr2 said:
When I installed rbox's CMW recovery and custom ROMs I lost the ability to open su. I believe this is a known issue.
Click to expand...
Click to collapse
For now I'm still sticking to spmc. I don't think helix has the support ready yet. SPMC 13.3.2 (not the latest one) works the best with .ts files as well.
Hello!
So I recently rooted my Samsung Galaxy S5 (SM-G900i)
I flashed the kltedd .tar.md5 file through odin (downloaded the .tar.md5 file through Chainfire's CF Auto Root Website)
Everything worked, after going through the whole process my phone rebooted and everything seems normal.
All my data has been preserved and it all works fine.
The only problem is to check that my phone actually has root access I need to download one of those root-checker apps from the play store, but I need to sign into my Gmail account to get to the play store in the first place.
I just wanted to know if it is safe to log into my gmail account on a rooted device - is it possible in any way shape or form that I might have a sneaky keylogger or some spy-ware that could potentially see my Gmail password?
Any help would be appreciated
Sincerely, a noob to XDA Forums.
If you have rooted then there should be a SuperSU app or similar, and when you enter it it should tell you somewhere if root is working fine.
There's an easy way to check for root, which doesn't involve any app, but you need to be able to connect the phone to a PC and you will need USB drivers, and to get your hands on adb.exe (or android-tools-adb package on Linux). Assuming you've done that:
* Enable developer options. (Settings > About Phone, tap Build number 10 times, you will get a popup telling you that Settings > Developer options has appeared.)
* Enable "USB debugging mode".
* Connect via USB to the PC.
* Run `adb devices`.
* You will be asked if you want to accept the debug connection, and possible if you want to enable MTP, say "yes" to both.
* Run `adb shell`.
* Once inside the shell you can type "su[ENTER]". The terminal should freeze and you should get a popup from your SuperSU app asking if you want to grant root access to ADB. If you don't get a popup and "su" fails in the terminal, you don't have root. If you don't get a popup but you get a "#" prompt in the terminal, you have root, but you don't have a root controller app, which is not good (anybody can get root).
Another even simpler method would be to use a terminal app... provided you already have one installed. Most custom ROMs do, stock ROMs don't. Then you just use the same "su[ENTER]" stuff in the terminal.
also, you can bypass the whole thing of logging into your gmail acct and go directly into your phones main screen, go into menu, settings, about phone and tap on the build number until you see the message stating that you are now a developer, back up one step, go into developer options, check the box to allow the installation of third party apps and just download the root checker apk from elsewhere. Sounds compllicated, but its easier than CLI stuff for the uninitiated
---------- Post added at 08:45 AM ---------- Previous post was at 08:45 AM ----------
also also, ive never heard of anyone getting a keylogger after merely rooting their phones
It's technically possible if you get your "root app" from random websites. It's a golden opportunity for a hacker, you're practically begging them "please exploit my phone, I'm gonna help by running your app and bypassing all safety measures".
security should be fine as long as you dont lose your device or download apps from unsafe sites.
as for whether it is rooted or not, already answered above.
Good to see another aussie here.
I'm still a bit of a noob too but happy to help with any endevours regarding phone, especially model specific ones (I have G900I too).
wirespot said:
It's technically possible if you get your "root app" from random websites. It's a golden opportunity for a hacker, you're practically begging them "please exploit my phone, I'm gonna help by running your app and bypassing all safety measures".
Click to expand...
Click to collapse
really mate!?
i have my rooted S5 with my 3 gmail accounts logged in
and i didnt have any secuirty issue at all in past and now