[Q] No Root with Neak Kernel - Galaxy S II Q&A, Help & Troubleshooting

Hi,
I have installed XXKL1 firmware (stock from samfirmwares) and afterwards Neak Kernel 1.3.3.
Everything seems to be fine, the kernel shows up under system info, I have a NEAK CWM Recovery, I can do adb shell for a root shell, adb remount reports success.
But when actually using the phone itself, all root fails. The superuser app from the NEAK flash does not pop when using a root app, all apps instantly tell "no root" (Busybox installer, Titanium backup, ...). Even Superuser itself does not seem to have superuser access, it cant update the su binary.
What am I missing?

Check the Neak thread first .
And or reflash the kernel .
jje

Why dont you root with a CF-Root kernel to get root and superuser and then flash the Neak kernel to see if the root access stays.

I was a bit worried because there was no exact cf-root kernel for XXKL1. But I used the XWKL1 one and flashed back to the other kernel and yes it worked.
Thanks!
(Although I don't quite understand why...)

CF-Root kernels are basically stock root kernels by Chainfire so being stock rooted they are,I imagine,more likely to get and hold root access.They are the only kernels is use as Im not into overclocking or anything like that.Anyway once root was acheived flashing the other over top was no problem.XXKL1 is the same as XWKL1 as long as the Firmware is the same.The important part is the last 3 digits.

Hossie2k said:
Hi,
I have installed XXKL1 firmware (stock from samfirmwares) and afterwards Neak Kernel 1.3.3.
Everything seems to be fine, the kernel shows up under system info, I have a NEAK CWM Recovery, I can do adb shell for a root shell, adb remount reports success.
But when actually using the phone itself, all root fails. The superuser app from the NEAK flash does not pop when using a root app, all apps instantly tell "no root" (Busybox installer, Titanium backup, ...). Even Superuser itself does not seem to have superuser access, it cant update the su binary.
What am I missing?
Click to expand...
Click to collapse
This happens only when the space left into /system partition is very low, so the kernel cannot root the phone
Check first if you have the Superuser app, if not, try to install it from market and see if you can gain root access...
Probably my kernel has installed only the su binary, because there was no space left to install also the superuser apk

simone201 said:
This happens only when the space left into /system partition is very low, so the kernel cannot root the phone
Check first if you have the Superuser app, if not, try to install it from market and see if you can gain root access...
Probably my kernel has installed only the su binary, because there was no space left to install also the superuser apk
Click to expand...
Click to collapse
The same happens to me. Even installing the Superuser from Play Store it says I don't have root access. I'm on a n7100 with 4.1.2 stock (rom) and latest neak kernel.
Thanks.

Siyah anyone?
Sent from the little guy

Related

Root shuts down phone without warning

Using various root apps on the stock Ace S5830D DTLKI4 results in the phone shutting down without warning, or even any obvious clue in logcat/ddms.
I've separately installed root through ChainsDD Superuser-3.1.3-arm-signed.zip, Chainfire's CWM-SuperSU-v0.95.zip and also with the older files included in SuperOneClick 2.3.3...
Trying to run Adfree, Stericson's Busybox installer and Titanium Backup restore operations, for instance, all result in a sudden shutdown.
The idea here is to run the stock ROM, so I'm running out of ideas.
Help?
Thanks in advance,
Darkshado
Happens in XWKTM but does not happen in DDKQ8.
It is surely due to improper root privileges.
Sent from my GT-S5830 using Tapatalk 2
Darkshado said:
Using various root apps on the stock Ace S5830D DTLKI4 results in the phone shutting down without warning, or even any obvious clue in logcat/ddms.
I've separately installed root through ChainsDD Superuser-3.1.3-arm-signed.zip, Chainfire's CWM-SuperSU-v0.95.zip and also with the older files included in SuperOneClick 2.3.3...
Trying to run Adfree, Stericson's Busybox installer and Titanium Backup restore operations, for instance, all result in a sudden shutdown.
The idea here is to run the stock ROM, so I'm running out of ideas.
Help?
Thanks in advance,
Darkshado
Click to expand...
Click to collapse
Why don't you use the normal universal gingerroot? I've never had problems with it. And I actually used it while I was on KTM.
I had the issue that my phone wasn't letting me root. I just installed a custom rom that is already rooted and it worked fine after that.

Hide root DME (Excitor)

Hello,
I wish to install (and use) the application DME Excitor (corporate emails) but it is detecting the root in some way.
I have a i9100 device with cm9.1 (latest stable one) & siyah kernel 5.0.1.
I've also made sure (using ExTweaks) that the kernel is not re-rooting the device every boot.
I've tried to remove the root using "Hide my root" / "ExTweaks" / "SuperSU" - and others that say they will hide the root - so far with no success!!!
Can you please suggest how to prevent DME from detecting my root?
I really don't mind unrooting the device - but please do not suggest me to return to stock!
Any help will be highly appreciated! :good::good::good:
bump
bump
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
florox said:
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
Click to expand...
Click to collapse
sorry - no success yet
In case you find any way, please let me know
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
bkraptor said:
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
Click to expand...
Click to collapse
Did you tried it with DME ?
By default, installing the SuperSU from the play store is in '/data' (you can later change that option in settings to be set on '/system')
Anyway, tried that, didn't worked.
Any help would be highly appreciated. :good:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
bkraptor said:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
Click to expand...
Click to collapse
Hi,
First of all thanks for trying to help.
There's no any Superuser.apk in /system/app/ (that's the first thing I've checked).
And I did made sure to uncheck the "Enable Superuser" option within SuperSU.
Still doesn't work.
If you don't mind me asking, could you please provide me with more details on your firmware?
Which rom are you using (is it Cyanogenmod)?
Special kernel?
CWM ?
Any details would help.
And once again, thanks!
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
bkraptor said:
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
Click to expand...
Click to collapse
Thanks for the info.
I was afraid that you would note you're using a rooted stock firmware.
The thing is that by going back to stock rom, there's no need to root it and then unroot it to use the DME (simply use the stock firmware unrooted).
The first post on this thread was a question on how to use the DME on different rom than the stock one (such as CM).
After that being said, I would like to thank you for trying, but this didn't help me, since I wish to use the Cyanogenmod rom and DME together.
If you still have any suggestions on how to use the DME with a non-stock rom, I would be more than happy to hear.
I don't see how running CM is any different than running official. You should check that after disabling Superuser from within SuperSU that there is no "su" binary anywhere within the directories in the PATH variable (i.e. /system/bin or /system/xbin).
Is dual booting a stock/cm setup possible, and would that serve as a "workaround"?
Edit...just thought....even if possible, the dual boot kernel would probably give the game away....
Sent from my CM10 powered S2 via XDA Developers App
is there any solution at this point? I have cm installed and i want to use dme on my rooted phone...
finally!!! fully functional nexus 7 ))
meaning stock browser AND DME running
rooted with this method (from stock 4.2.2):
http://forum.xda-developers.com/showthread.php?t=2233852
installed stock browser from here:
https://play.google.com/store/apps/details?id=de.mkrtchyan.aospinstaller
SuperSU settings (many thanks to bkraptor):
http://forum.xda-developers.com/showpost.php?p=42009031&postcount=6
Can someone please let me know how to install superSU in /data. As If I instal UPDATE-SuperSU-v1.51.zip by using PhilZ-cwm6. It is installed by default in /system.
If I install it using Playstore it does the same got installed in /system. and further conflicts with SU installed by PhilZ-cwm6.
Will appreciate any suitable advice

I need clockWorkMod SuperUser apk please

Hi, when cwm SuperUser done a update to app and binaries the root not work in my device, can someone give me SuperUser cwm.apk v0.9 or some work please, i searched but I didnt found
fernan2001 said:
Hi, when cwm supersu done a update to app and binaries the root not work in my device, can someone give me supersu cwm.apk v0.9 or some work please, i searched but I didnt found
Click to expand...
Click to collapse
http://download.chainfire.eu/204
r
Very thanks for answer, but the link is a .zip and I want an apk or can I put it (.zip) with default recovery and not have problems?
Extract that zip, apk is in there
Tapped from my RazR
DumbleCore said:
Extract that zip, apk is in there
Tapped from my RazR
Click to expand...
Click to collapse
thanks now I understand I dont knew that...but the apk is not that, I tested that app and not worked because I dont have root chainfire installed , the super user that I have is SuperUser of ClockworkMod, I need a previous version.
fernan2001 said:
thanks now I understand I dont knew that...but the apk is not that, I tested that app and not worked because I dont have root chainfire installed , the super user that I have is SuperUser of ClockworkMod, I need a previous version.
Click to expand...
Click to collapse
Look man, superuser is ROOT. Either your phone is rooted or it is not. A rooted phone can run apps that require it like ClockworkMod ROM Manager, Titanium Backup, Greenify, Wireless Tether for Root Users, File managers like Root Explorer or ES File Manager if you want to be able to access the system areas of the phone. So far as I know, there is no "SuperUser of ClockworkMod". If your phone is rooted (You will see superuser or "Super SU" in your app drawer. Here is a free app from the playstore that will tell you if your phone is rooted or not.
Root Checker
Install it and use it to see if your phone is still rooted or if you lost root somehow. If you still have root, then when CWM starts, it will ask for root privileges and the first time it asks, you will be prompted to grant it, once, for a certain time period, or forever. For stuff like CWM, root file managers, and Titanium Backup, you always grant root forever and you will not be asked again until the app updates and requires you to okay granting root privileged or not, then you grand forever and leave it alone.
If you find out you do not have root or lost your root, then you have to root the phone and the procedure is different for different devices, versions, and ROMS. For that kind of help, you have to search for rooting <your particular device and android version number>
Ohmster said:
Look man, superuser is ROOT. Either your phone is rooted or it is not. A rooted phone can run apps that require it like ClockworkMod ROM Manager, Titanium Backup, Greenify, Wireless Tether for Root Users, File managers like Root Explorer or ES File Manager if you want to be able to access the system areas of the phone. So far as I know, there is no "SuperUser of ClockworkMod". If your phone is rooted (You will see superuser or "Super SU" in your app drawer. Here is a free app from the playstore that will tell you if your phone is rooted or not.
Install it and use it to see if your phone is still rooted or if you lost root somehow. If you still have root, then when CWM starts, it will ask for root privileges and the first time it asks, you will be prompted to grant it, once, for a certain time period, or forever. For stuff like CWM, root file managers, and Titanium Backup, you always grant root forever and you will not be asked again until the app updates and requires you to okay granting root privileged or not, then you grand forever and leave it alone.
If you find out you do not have root or lost your root, then you have to root the phone and the procedure is different for different devices, versions, and ROMS. For that kind of help, you have to search for rooting <your particular device and android version number>
Click to expand...
Click to collapse
Thanks for answer, well I thinked that too, because my phone cant use root privileges if the aplication superuser isnt installed, however with te superuser aplication my phone have root privileges but with the previous version, with actual version my phond dont have root, even the people in google play say the same "with the new version my phone losed root" and similars comments...
maybe the root version (clockWorkMod) work in this way and need the app for work.
maybe this one??? http://d-h.st/l91
DumbleCore said:
maybe this one???
Click to expand...
Click to collapse
Thanks DumbleCore! I have root again
fernan2001 said:
Thanks DumbleCore! I have root again
Click to expand...
Click to collapse
Solved it? No problem

[Q] Problems with superuser su

I just flashed CM11 onto my Amaze (T-Mobile S-ON) and everything runs fine except when I tried to use titanium to restore my apps, it gave me this message: "Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I opened Superuser and scrolled to info. It says "superuser v3.1.3 (46)" and "su binary v3.1.1 (17). When I press on the su, it goes to a binary updater which says "downloading manifest," then, after a minute or so, it says "fail" in red at the end of the "downloading manifest" line. I downloaded superuser by CWM after this problem and when I opened the app, it said: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." It gives me the option to press cancel or Recovery Install. When I press recover install, it says: "There was an error installing Superuser. Please send a log of the error to the developer." I went onto the superuser website, downloaded the latest arm su and superuser, put them on my sd card, went into 4ext and installed both from sd card and still have the same problem.
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Root?
luisandroid said:
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Click to expand...
Click to collapse
I think you are not rooted.
Try app "Simple Root Checker" from Play Store:
https://play.google.com/store/apps/details?id=com.simonedev.simplerootchecker
If not rooted, try this to gain root:
http://forum.xda-developers.com/showthread.php?t=2437057
pbergonzi said:
I think you are not rooted.
Try app "Simple Root Checker" from Play Store:
https://play.google.com/store/apps/details?id=com.simonedev.simplerootchecker
If not rooted, try this to gain root:
http://forum.xda-developers.com/showthread.php?t=2437057
Click to expand...
Click to collapse
I used that app and it said: "Android 4.4.2 HTC Amaze 4G Application Superuser found Terminal Rooted Busybox installed BusyBox v1.21.1" So I am guessing I am rooted. Should I try using that tool to flash SuperSU anyway? Thanks for helping me out with this.
SuperUserSU problems.
luisandroid said:
I used that app and it said: "Android 4.4.2 HTC Amaze 4G Application Superuser found Terminal Rooted Busybox installed BusyBox v1.21.1" So I am guessing I am rooted. Should I try using that tool to flash SuperSU anyway? Thanks for helping me out with this.
Click to expand...
Click to collapse
Nice--my mistake. In your Superuser info, where you found your su binary listed "su binary v3.1.1 (17)", did it give the file specs right underneath--it does in mine.
Also, if you go into Superuser app, then Preferences->Security->Automatic Response, is that accidentally set to "Deny?" Betcha' that won't work.
Is Titanium Backup listed in your Superuser apps list, and if you open the info there, is it "Allowed?"
Probably what you said about re-flash Superuser is reasonable, and worth a shot if the Automatic Response is already set to Allow or Prompt.
I'll also wager that someone else with good insight and experience will stop in the thread with a working answer for you.
luisandroid said:
I just flashed CM11 onto my Amaze (T-Mobile S-ON) and everything runs fine except when I tried to use titanium to restore my apps, it gave me this message: "Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I opened Superuser and scrolled to info. It says "superuser v3.1.3 (46)" and "su binary v3.1.1 (17). When I press on the su, it goes to a binary updater which says "downloading manifest," then, after a minute or so, it says "fail" in red at the end of the "downloading manifest" line. I downloaded superuser by CWM after this problem and when I opened the app, it said: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." It gives me the option to press cancel or Recovery Install. When I press recover install, it says: "There was an error installing Superuser. Please send a log of the error to the developer." I went onto the superuser website, downloaded the latest arm su and superuser, put them on my sd card, went into 4ext and installed both from sd card and still have the same problem.
Problem: I can't grant superuser permissions to any apps because something is wrong with my su binary. I tried installing su-bin-3.1.1-arm-signed.zip from 4ext and it said the installation was successful, so I do not know what is wrong.
Click to expand...
Click to collapse
The problem you describe is common with more recent versions of CM (at least I've experienced it). It's due to the way CM is now implementing their included Superuser app, which is different from how it used to behave and how many other apps expect it to behave. The solution is to flash SuperSU in recovery from this thread http://forum.xda-developers.com/showthread.php?t=1538053 (if it resolves your issues please remember to thank its creator and consider purchasing the full version).
When you set it up, enable "pro" mode, survival mode, allow it to install the scripts, and respect CM root settings. If installed correctly you should be good to go.
I hope this helps
Odysseus1962 said:
The problem you describe is common with more recent versions of CM (at least I've experienced it). It's due to the way CM is now implementing their included Superuser app, which is different from how it used to behave and how many other apps expect it to behave. The solution is to flash SuperSU in recovery from this thread http://forum.xda-developers.com/showthread.php?t=1538053 (if it resolves your issues please remember to thank its creator and consider purchasing the full version).
When you set it up, enable "pro" mode, survival mode, allow it to install the scripts, and respect CM root settings. If installed correctly you should be good to go.
I hope this helps
Click to expand...
Click to collapse
That solved the problem! Got CM 11 running on my Amaze! I made sure to thank the dev! Thank you for your help as well!

[Q] conflicting root messages

I've downloaded several root checker apps, and the all say I do not have root access, but I have root only apps installed, like greenify ad titanium backup. Whats happening here?
STEEPO said:
I've downloaded several root checker apps, and the all say I do not have root access, but I have root only apps installed, like greenify ad titanium backup. Whats happening here?
Click to expand...
Click to collapse
Your device may not be fully rooted. Which means that you have the app installed but the binary is not. Download Terminal Emulator from the Play Store. Then open it and type "su" (without quotes). If you get a new line saying "[email protected]:/ #" then you are rooted. If it says something like "su: not found" then you don't have the binary and you have to install it either via the superuser/supersu/other app (if you have a custom kernel with system write protection off, such as KofilaKernel or other) or by flashing a zip with the binary in recovery (you can find it here).

Categories

Resources