Database Develop

What am I Doing Wrong Here?

Hello everyone! Last night I used Sunshine to unlock/s-off to root/unlock my phone. this morning i tried to install SuperSU, but got a message stating that the binary wasn't installed and SuperSU couldn't install it. I have done some searching on this, have tried to uninstall/reboot/reinstall SU, but each time I get the same error message. Iinstalled TWRP, but since I dont have super user access, it just closes, and because the binary isnt installed for SU, it just closes as well.
So, what I am trying to figure out is how to get superuser installed so twrp works, and i so i can on my merry flashing way. Any help you guys can give would be great!
Thanks

tammerlane said:
Hello everyone! Last night I used Sunshine to unlock/s-off to root/unlock my phone. this morning i tried to install SuperSU, but got a message stating that the binary wasn't installed and SuperSU couldn't install it. I have done some searching on this, have tried to uninstall/reboot/reinstall SU, but each time I get the same error message. Iinstalled TWRP, but since I dont have super user access, it just closes, and because the binary isnt installed for SU, it just closes as well.
So, what I am trying to figure out is how to get superuser installed so twrp works, and i so i can on my merry flashing way. Any help you guys can give would be great!
Thanks
Click to expand...
Click to collapse
Actually nevermind.....i'm going to continuing reading through the phone book of replies on the supersu 2.13 thread. This can be closed for now.

You don't need root for a custom recovery on this device .
You unlock bootlooader 1st,custom recovery 2nd, install SuperSU.zip using custom recovery,3rd is cause you need superuser to gain S-OFF with Sunshine.

jball said:
You don't need root for a custom recovery on this device .
You unlock bootlooader 1st,custom recovery 2nd, install SuperSU.zip using custom recovery,3rd is cause you need superuser to gain S-OFF with Sunshine.
Click to expand...
Click to collapse
Not true...Sunshine does not require any of those.

When you run the apk from the website it ask for root permission. I'm S-OFF from using Sunshine
Edit : your right thank you for correcting me

[Q] Xposed cant get root, other apps can...

Hey all,
I apologise as this is a second thread to the same question but my problem has not been resolved and no one really pays attention to long threads.
My HTC has returned from repair with the latest firmware installed, therefore it has the latest hboot meaning i cannot s-off. I believe i have root but im not sure if i have 'FULL root'.
I was able to install a cusom ROM, Google play edition Plus. I can use Titanium backup, SuperSU, BusyBOX (is installed) etc.. but i cannot use Xposed or cheating apps as they say i don't have root access.
When trying to install Xposed i have two options as you can see in the screenshots, 'Soft reboot' does nothing, reboot brings up the message "failed to get root access" also im struggling to access files on my device when connected to a PC, it is in MTP mode
Why is this? i have a sneaking suspicion its due to hboot and s-on

bump

stevey88 said:
Hey all,
I apologise as this is a second thread to the same question but my problem has not been resolved and no one really pays attention to long threads.
My HTC has returned from repair with the latest firmware installed, therefore it has the latest hboot meaning i cannot s-off. I believe i have root but im not sure if i have 'FULL root'.
I was able to install a cusom ROM, Google play edition Plus. I can use Titanium backup, SuperSU, BusyBOX (is installed) etc.. but i cannot use Xposed or cheating apps as they say i don't have root access.
When trying to install Xposed i have two options as you can see in the screenshots, 'Soft reboot' does nothing, reboot brings up the message "failed to get root access"
Why is this? i have a sneaking suspicion its due to hboot and s-on
Click to expand...
Click to collapse
flash latest supersu.zip (2.46) from recovery then flash xposed from recovery. reboot phone, launch xposed and wait for supersu's request to grant/deny xposed. Once granted su to xposed, you should see your app_procces active version in green.
also im struggling to access files on my device when connected to a PC, it is in MTP mode
Click to expand...
Click to collapse
Using a terminal emulator:
Code:
su
restorecon -Fr /data/media/0
exit
exit
then reboot if needed.

[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.

Difficulty Rooting Newest RUU

Hello everyone,
I'm having an issue - I wasn't able to flash the newest extracted firmware in the development section so I went ahead and just ran the full RUU. I've been running custom roms for years and I decided that maybe I just wanted to run stock rooted for a while so I unlocked my bootloader again, flashed the most recent TWRP and installed the most recent SuperSU zip.
Unfortunately it does not seem to have rooted my phone. SuperSU is indeed installed in the system folder and it prompts for root permission when I use root apps, but even when I grant permission the apps cannot obtain root access. What happens is it looks like they are going to get root access, the phone slows down a bit for a second, and then I get an error message from the app in question saying that either my phone isn't rooted or that root permission has been denied. If I open SuperSU, it lists all of my root apps with the green hashtag indicating that permission is granted.
Am I correct in assuming that installing SuperSU did not root my phone? If so, is there a way to root without installing a custom rom?
For clarification, this is all on the most recent RUU, software version 6.23.651..10, Lollipop 5.0.2
Thanks in advance.

Which version of SuperSU are you flashing?

Sloth said:
Which version of SuperSU are you flashing?
Click to expand...
Click to collapse
Well I'm a dolt, I was using v1.69 but now I see that is a very old version. Going to try 2.46 right now, thanks.
Edit: Same issue on 2.46 :/

For anyone still looking at this thread, I was able to achieve root by flashing the newest SuperSU, version 2.52 which is actually still in beta and therefore not offered if you go to the main portion of the SuperSU website.

SuperSU v2.65 is the current stable offering

Problem on install AdAway (S-ON)

My device is S-ON (UNLOCKED, TWRP, HBOOT 1.61, flashed SuperSU 2.78, Android 5.0.2, stock 7.18.709.151). The only way to s-off is paid money. So I flash AdAway_systemless_hosts_v2.zip in TWRP, but I have problem.
There's no error shows when install AdAway_systemless_hosts_v2.zip, but after install it and reboot to system then install AdAway v3.1.2 apk, enable AdAway and download host, restart system, I found AdAaway didn't enable every time I restart.
I also use this way, but I can't find any "su" folder in my phone, also read these way, B can't be update by APP, C looks not safe and old, A didn't work (/data/data/hosts). I already flashed Xposed, and it seems work fine, Root Checker also shows I have root access, so I think I got root right.
Is there anyone tell me how to make AdAway_systemless_hosts_v2.zip work in my S-ON M7? Thanks!

matif525 said:
My device is S-ON (UNLOCKED, TWRP, HBOOT 1.61, flashed SuperSU 2.78, Android 5.0.2, stock 7.18.709.151). The only way to s-off is paid money. So I flash AdAway_systemless_hosts_v2.zip in TWRP, but I have problem.
There's no error shows when install AdAway_systemless_hosts_v2.zip, but after install it and reboot to system then install AdAway v3.1.2 apk, enable AdAway and download host, restart system, I found AdAaway didn't enable every time I restart.
I also use this way, but I can't find any "su" folder in my phone, also read these way, B can't be update by APP, C looks not safe and old, A didn't work (/data/data/hosts).
I already flashed Xposed, and it seems work fine, Root Check also shows I have permission, so I think I got ROOT right.
Is there anyone tell me how to make AdAway_systemless_hosts_v2.zip work in my S-ON M7? Thanks!
Click to expand...
Click to collapse
I think systemless root and everything related to it is Android M feature, and it doesn't work on M7. Someone please correct me if I'm wrong here

donkeykong1 said:
I think systemless root and everything related to it is Android M feature, and it doesn't work on M7. Someone please correct me if I'm wrong here
Click to expand...
Click to collapse
Thank you! So, I can't use AdAway normal in S-ON Android 5.0.2?

matif525 said:
Thank you! So, I can't use AdAway normal in S-ON Android 5.0.2?
Click to expand...
Click to collapse
You can use the normal adaway, not the systemless one. Find it in xposed

donkeykong1 said:
You can use the normal adaway, not the systemless one. Find it in xposed
Click to expand...
Click to collapse
Thansk you very much!
I searched "AdAway" in http://repo.xposed.info/module-overview, nothing useful, but found hosts Enabler, are you talking about this?

matif525 said:
Thansk you very much!
I searched "AdAway" in http://repo.xposed.info/module-overview, nothing useful, but found hosts Enabler, are you talking about this?
Click to expand...
Click to collapse
I just remembered. You are on stock kernel, right? Because stock kernel has system write protection and you can't use AdAway. You can flash a custom kernel with system write protection disabled and you should be fine