Database Develop

One click root but not rooted >.<

I have used the one click root program to root my captivate.. the problem is I'm still cannot use those program that require root permission.
I got the superuser permission icon already but I'm still cannot use root required apps... someone pls help.
Sent from my SAMSUNG-SGH-I897 using XDA App

One rooted when you try and run a program that requires root access a notification should open asking if you why to allow root access.
Click on the super user app. What happens?

nope nothing pop up to ask if i allow the access...
I have tried a two types of one click root program which is Superoneclick and another one by TGA_Gunnman..
But both act in the same way that nothing will pop up and ask whether to allow access...

What happens when you click on the super user app?
Have you tried rebooting the phone?
Have you tried replacing apk with market, search superuser in market, see if it shows installed, try to update or replace
You are on stock, correct

yeap i have tried to reboot after the rooting process...
I can open the superuser app too.
Yes im on stock.
Im thinking should i use z4root now?

Might as well. Did you check for the app in the market?
What are you looking to accomplish with root? What is your goal?

yup i checked the market too... it shows i ald installed the superuser..
Just want to root and use the rom manager to back up...
And i dunno y suddenly the root works! now im okay! Thanks for the help!
I guess we need to install again from market and reboot in order to use this...

No problem, who knows what the issue was. Enjoy, I am sure you will be flashing roms in no time

Trouble Rooting my Note 4

Hey everyone. I am not new at rooting phones but this appears to be the one phone that is giving me issues.
My note 4 is telus, was n910w
installed this rom:
http://forum.xda-developers.com/note-4-tmobile/development/rom-vision-x-n4-intl-t2943448
working beautifully thus far but I cant seem to root....
I have tripped KNOX 5 times so far trying to do it, each time it appears my phone is not rooted as titanium cannot verify SU, and aswell I have a root checker which tells me it is not rooted.
I have tried several versions of ODIN, and cf auto root n910t, AND V.
Do I maybe have to reinstall my rom? Or is there something I am missing because this is frustrating me....
Is there something I am doing wrong? Superuser IS on my phone, but its not doing anything but being there.... Please any kind of help would be appreciated as I am stumped.

I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access

Framaroot
Sent from my Trident-A1 using XDA Free mobile app

neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
This worked, I am a dummy lol
Thanks alot!

Glad I could help

Glad you got it worked out but note that you can only ever trip Knox once. Once it's tripped it's tripped, so don't worry about it.

neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
I had lost root after flashing the PopRocks ROM. Couldn't figure it out and stumbled across this post. Now it works perfectly. Thanks! :good:

[Q] Super su binary update making sdcard & system read only XPERIA M2 DUAL 4.4.4

I downgraded my Xperia M2 dual d2302 to 4.3 and rooted with towelroot and then flash 4.4.4 followed by flashtool force towelroot using super su. This would uninstall super su on my phone and install its own super su binaries and busybox content. The super su pro would however, remain installed. So, I would have to redownload the super su and as soon as i would open it, it would ask for binary update and then ask for reboot. I would just follow the prompt without question. As soon as it reboots,though the root would be there but sd card and system rewriteable will be gone and there is no way to make my system rewriteable without flashtool reflashing back to 4.3 and following the long procedure. I till now, would blame kitkat and sony for that. This continued for over 8 days till I realised that the real culprit was not sony or kitkat but super su binary update followed by reboot. This is highly anoying. What is the point of root if system or sd card writing is not allowed? For now, I am living with super su by canceling the binary update everytime I open it. I have OCD and I find it highly annoying. I tried searching for an option to cancel auto search for updates bur in vain. My phone works just fine without update. I need no updates and need a way to stop super su asking for update everytime. Please suggest me something.
I have now discovered that even if I cancel binary updates, supersu auto updates causing the same problem. So, now I have decided to live without Supersu as supersu is not needed for root. I have an unlimited root access for all my apps which have root permission now and to add icing to the cake, my bootloader is locked. If anyone else is searching for a way to make Sony Xperia M2 dual 4.4.4 system writebale without unlocking bootloader, just follow:
LOCKED BOOTLOADER
1. Downgrade to JB, Root your Phone using Towel Root in Jelly Bean
2. Update via OTA to KK 4.4.2 or KK 4.4.4 whatever you need (4.4.4 is recommended)
3. In this process, don't try to install or uninstall anything
4. Wait for booting finish
5. Install latest SuperSU from Play Store
6. Open Flashtool in PC
7. Connect your phone to PC
8. Now flashtool will describe your phone information, then click Root Tab in top, after that choose force root by TowelRoot
And after this, do not install supersu or any other root control app. Just let your phone be as such without updating binaries or anything and you will have root. You will have unrestricted root on Xperia M2 dual, Enjoy and remember not to install supersu, kingsu, cm superuser or any similar app.

I was thinking to help you, but then i was worried if something else goes wrong, then you will blame me, just like you blame super su.

Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt

gauthamraob said:
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
Click to expand...
Click to collapse
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
---------- Post added at 02:42 PM ---------- Previous post was at 02:31 PM ----------
BTW, tell us what do you need on your device that will make you feel better. (About the superuser @ root thing of course)

NeoLogY said:
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
Click to expand...
Click to collapse
No, I am already having root . I have integrated most of the updates to my system app to my sys/app folder through lucky patcher and have installed the modded play store . I can even edit and delete system files in "ES explorer" file manager and stop items from startup using "all-in-one-toolbox" boot manager. I have an older version of su binaries which was installed automatically into my phone by "flashtool by androxide" using the force root mode using towel root :good: . But the supersu app was not installed and if the app existed before rooting, flashtool would uninstall it and also replace the new su binaries with an older version ! So, I already have full root access without the supersu app.
As far as i know, supersu is not needed for root. It is only a gatekeeper app which restricts the unlimited access of root to any app by making the apps that need root to ask for permission first. Without supersu installed, root apps get root access without asking permission provided binaries (any version) are already present. Also, for normal people who don't know or can't install binaries directly, they rely on apps like supersu, CM etc for installing the binaries. But once the binaries are installed, the supersu app is no longer needed for root (except in cases of OTA updates or updation of binary to a newer version) but instead works as a security guard for root.
Edit:
What I want is a way to make supersu submissive and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like.

What I want is a way to make supersu submissive to my command and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like and must not be done

Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?

NeoLogY said:
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
Click to expand...
Click to collapse
At present I am using my phone without supersu as I will have to spend a lot of time downgrading to 4.3 and then rooting followed by painfully slow 4 OTAs in succession (there is no single direct OTA from 4.3 to 4.4.4 on Xperia M2 dual, unfortunately :crying: ) followed by installation of all my apps. I too wish there was a fix for supersu but the time I'll have to spend on that will be enormous and also considering that in this september my phone will mostly get lollipop 5.1, the 4.4.4 woes will soon be history.
Also, I want to mention that I haven't unlocked my bootloader yet. If I unlock my bootloader, all these problems with supersu will vanish. The actual difficulty I am facing is because there is no single post on the internet that says how to get system to be rewriteable without unlocking bootloader in Xperia M2 devices. Every post I have read of only has people with unlocked bootloader saying what to do and people with locked bootloader complaining that they aren't able to make their system rewriteable. I am probably one of those rare people who managed to get complete root with locked bootloader and hence facing the issue of lack of peer help.
Anyways, I really appreciate your interest shown in helping me. If I ever have to update my binaries in the future I will definitely take a log of it and pm it to you in case similar situation arises.
Cheers.

Same thanks to you. Actually, i think it is better to put the log here, as more hands and mind will be able to reach it, meaning higher percentage on discovering any hidden in the log. You are right about the lock bootloader, even until now i still unable to manage to truely understand about bootloader, as i didn't have any device with it to get inhand with the system. As always, i do appreciate any kinda knowledge exchange. Thanks in any way.

That's exactly why your system is read only and you can't move apps/data to sd ect without supersu installed and the binaries updated and Sony ric killed you don't have full root r/w access to system. The way you have rooted your device is the same way I did mine it's the easiest way there is if you can't get it right doing that way then maybe you should put your Phone back to stock. Flash jb, root with towelroot apk(at this point do not update anything), now update over the air to 4.4.2 then again to 4.4.4(again update nothing but phone)root will stick after each update. Download supersu connect your phone to flashtool and click on the force root tab(kills Sony ric installs supersu binaries and busybox) making system r/w
Search on here for the m2 forum if you still have problems
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.

I have a rooted Sony xperia z1. By mistake, I had deleted the king root app. And now

Sent from my A0001 using XDA Free mobile app

Have you checked via root checker that you still have root?
I'm pretty sure kingroot is a manager like app similar to supersu so I'm not sure if you'll still be able to grant superuser access to apps that will request it.
You could try reinstalling the apk and it might detect root and work again but if it wants you to root your phone again then just leave it.
There is a method to replace replace kingroot with supersu but if can't grant superuser access then it won't work.
Search Google for how to replace kingroot with supersu.
There is a webpage and video by w0lfdroid
This is the method I used to root my xperia Z1 running 5.1.1
You are in risk of bricking your phone if you are not careful.
If terminal emulator doesn't ask for superuser access then you might need to wait till someone has an answer because the only one I could suggest for that situation is to try and unroot your phone and start again.
Also what do you mean by "and now"

Build.prop won't save changes on reboot + Trouble with temp root (using Kingroot)

Hi all.. I am having some issues with both rooting and modding my build.prop.
My ultimate goal right now is to have a stable root, on essentially stock rom, with a modded/bypassed native tether app (I have unlimited data and verizon blocks it). I am having issues with both processes, and if anybody can help it would be greatly appreciated!
First, I am having a ton of trouble with the temp root process; I am using Kingroot, and although I have been able to gain root successfully, it seems completely random when the process works and when it doesn't. About a quarter of the time, the root seemingly works.. the rest of the time, I either get force crashes on all running apps until system reboot, I am told I have root but cant access system files still, or the root fails altogether. Perhaps there is a flaw in my process? I also have been unable to update the SU binaries.. I have tried using both the latest stable and beta APKs from Chainfire. Is there a specific process that someone has used more successfully, order of installations, etc?
Secondly, when I have gained root successfully, I have been trying to add a line into my build prop to bypass the tether subscription check, which I believe will work.. but whenever I reboot my phone, it overwrites my saved changes to Build.prop. I will successfully get r/w (Using root explorer btw), mod the build.prop just adding in a single line, save, and then reopen confirming that the changes stuck. However, when I reboot, the stock Build.prop comes right back. I have also attempted to copy a modded brand new build.prop into /System instead, which also appeared to work, but ends with the same problem on reboot.
Please note that if possible I want to keep running stock, I do not want to have to flash a modded rom.
TL;DR - Root is finnicky, SU binaries won't update and build.prop resets to stock on reboot even after confirmed edits.

I just read the tldr.
You need to use kingroot to root. This will be a very crappy root and all changes will be lost on every boot at first.
To obtain a proper root and permanent write access do the following.
Download twrp for quark
Download supersu flashable zip
Download and install flashify
Download and install sunshine
Download and install kingroot
Run kingroot and root the device
Run sunshine pay $25 for unlocked bootloader
Reboot
Run kingroot and root the device
Run flashify and flash the twrp for quark recovery.
Reboot into recovery run twrp
In twrp it will ask you a question that has to do with write access SWIPE YES.
Reboot
Run kingroot and root the device.
Kingroot is now stable.
Uninstall kingroot from the 3 dots in the app
Reboot into recovery and start twrp
Flash the flashable chainfire supersu zip
Reboot.
You now have root and the ability to make permanent changes to system.
P.S.
There is currently no way to do this without sunshine.
Sent from my XT1254 using XDA Free mobile app

mrkhigh said:
I just read the tldr.
You need to use kingroot to root. This will be a very crappy root and all changes will be lost on every boot at first.
To obtain a proper root and permanent write access do the following.
Download twrp for quark
Download supersu flashable zip
Download and install flashify
Download and install sunshine
Download and install kingroot
Run kingroot and root the device
Run sunshine pay $25 for unlocked bootloader
Reboot
Run kingroot and root the device
Run flashify and flash the twrp for quark recovery.
Reboot into recovery run twrp
In twrp it will ask you a question that has to do with write access SWIPE YES.
Reboot
Run kingroot and root the device.
Kingroot is now stable.
Uninstall kingroot from the 3 dots in the app
Reboot into recovery and start twrp
Flash the flashable chainfire supersu zip
Reboot.
You now have root and the ability to make permanent changes to system.
P.S.
There is currently no way to do this without sunshine.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the input..
I was hoping to avoid unlocking the bootloader, but I suppose I might as well. Kingroot does give me root, even if unstable, and Root Explorer tells me I have right access to /system.. plus, I can see that the changes have been implemented to build.prop, so it doesn't really make sense to me how/why it would revert to the stock build.prop on a reboot. Oh well.

The ROM checks the system on reboot. If it sees a change it reverts to what it was.
To fix that you need write protection disabled. Which twrp can do on an unlocked boot loader
Sent from my XT1254 using XDA Free mobile app

I may be wrong but I don't think you need to install TWRP to get rid of kingroot. I didn't feel like installing twrp partially because I'm lazy and partially because I dont plan on installing any other rom any time soon. Anyway, what I did was install kingroot, pay my $25 to sunshine and unlock the bootloader, then ran a script to remove kingroot an install supersu. The result was a perm rooted phone with super-su.
Maybe root checker is lying when it says i have root but adblocker can write to the hosts file so i don't think it is.

Kingroot cannot gain u permission for edit system partition. It only gain permission for run some script, program, it not true root, form what i read then even flash root by mofo, we still can't edit system partition
So u need unlock your bootloader

Okie Dokie smokie. I'm not here to convince anyone, I'm just letting you know what worked for me. I have su persistent in /system/xbin and have never installed TWRP. Root lives through reboots and superSU is installed and processing root requests. Kingroot is gone off the device. Feel free to PM me. I would be interested to see if it works without an unlocked bootlaoder. As i said, I unlocked with sunshine but never installed TWRP.
Are you sure recovery doesn't just check the recovery partition and restore it if it finds it has been modified. I have seen that behavior in the past very often. It seems a little wonky that every time the system boots it would check the whole /system partition.

Yes, it reverts all changes.
This is the first device I've owned that did this as well.
Sent from my XT1254 using XDA Free mobile app

mrkhigh said:
Yes, it reverts all changes.
This is the first device I've owned that did this as well.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
As I said, I think you may be mistaken. i am looking through the script i used to replace kingroot. What does TWRP modify to allow persistent recovery. I wonder if booting into recovery will wipe out the persistent root. A normal reboot does not effect it. Maybe build.prop gets restored while other files do not. As i said, my hosts with adblockign persists through reboots.
As far as the first post, there is an app out there which will add the line needed on the fly. com.ncsoftwaresolutions.entitlementbypass It worked perfectly on my Moto X running 5.1
I did not write the script i used and take no credit for it. Lets get that out of the way.

I am not completely sure as to how they accomplish this. Since there are things that can get "stuck" there such as kingroot app.
Perhaps someone else would like to chime in.
But I do assure you that write protection exists on this device.
And that the changes you're attempting to make requires it to be off.
Sent from my XT1254 using XDA Free mobile app

mrkhigh said:
I am not completely sure as to how they accomplish this. Since there are things that can get "stuck" there such as kingroot app.
Perhaps someone else would like to chime in.
But I do assure you that write protection exists on this device.
And that the changes you're attempting to make requires it to be off.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I don't doubt that is your experience. I was sharing mine. I rebooted into recovery and root stayed. What i am saying, with confidence because i have done it, is that you do not need to install TWRP to keep root persistent through reboot.
Here is the script i ran.
http://pastebin.com/w7MqXBZZ
After looking more my best guess is that the Sunshine process disabled nand lock which is why i am able to write to the system partition.

Thanks for the help guys.. interesting notes.
It turns out I can pay 30$ a month now even with unlimited data to unlock hotspot, which is good enough for an interim solution. I also don't plan on flashing any roms.. I prefer to do my own tweaks. I will probably proceed with unlocking the bootloader for persistent root and /system write permissions, once I get some time.

Cryptrix said:
Thanks for the help guys.. interesting notes.
It turns out I can pay 30$ a month now even with unlimited data to unlock hotspot, which is good enough for an interim solution. I also don't plan on flashing any roms.. I prefer to do my own tweaks. I will probably proceed with unlocking the bootloader for persistent root and /system write permissions, once I get some time.
Click to expand...
Click to collapse
That option has been around for a long time.
Sent from my DROID Turbo using XDA Free mobile app

Not Quite
cstone1991 said:
That option has been around for a long time.
Sent from my DROID Turbo using XDA Free mobile app
Click to expand...
Click to collapse
Actually, the rest of the users on my line were on a very outdated plan, so Verizon blocked both the free hotspot on the current plans for limited data users, and my option to pay for it on my own line. So instead I spend two hours on the phone convincing them to put the other lines on a "sub-plan", and upgrade them collectively to an Everything More, while mine is singular on the cycle but technically still on the same plan. And NOW I have the option to pay.
Now I just need to figure out how to utilize my upgrade without losing Unlimited data..

I said this a few posts up, it may be of no concern now.
As far as the first post, there is an app out there which will add the line needed on the fly. com.ncsoftwaresolutions.entitlementbypass It worked perfectly on my Moto X running 5.1.
You need root and you need to run it every time your phone is rebooted but ti works to bypass the entitlement check.