Related
Hello guys ,
Yesterday i followed the tutorial in the xda channel for s-off and Root for the HTC One.
I installed twrp and after that superuser. To Check my Root i downloaded Root checker from the play Store.
The app says i have no root acccess.
I have the stock HTC One Rom with Sense 5.5 and Android 4.3 installed.
Why i have no root Access ?
Thank u very much and sorry for my Bad english skills.
Did you install SuperUser from TWRP?
Have you launched it to make sure it's running?
Make sure you have superuser Access in the Superuser settings set to apps and adb
Also have you got logging on?
I installed superuser over twrp an I can lunch it.
But i have no access. I dont know how to fix that.
Any one ideas ?
Make sure it's superuser 1.65.
Sent from my HTC One using XDA Premium 4 mobile app
Lighthex said:
I installed superuser over twrp an I can lunch it.
But i have no access. I dont know how to fix that.
Any one ideas ?
Click to expand...
Click to collapse
Have you flashed this supersu?
i installed it over twrp.
I have no idea how i can fix that
Lighthex said:
i installed it over twrp.
I have no idea how i can fix that
Click to expand...
Click to collapse
Which rom do you have and which version of twrp?
The latest Version of both of them.
Twrp 2.6.3.0 i believe and for my Rom its the latest stock HTC Rom Witz Android 4.3 and Sense 5.5
I read on another forum that Titanium Backup does not work if you're using systemless root. Can anyone verify if this is true ?
If TB does work, how would I go about upgrading stock Android 6.01 rooted with TWRP to 6.0.1 with systemless root ?
aparanoidandroid said:
If TB does work, how would I go about upgrading stock Android 6.01 rooted with TWRP to 6.0.1 with systemless root ?
Click to expand...
Click to collapse
Make backup's with TWRP.
NLBeev said:
Make backup's with TWRP.
Click to expand...
Click to collapse
I know how to make backups with TB. That wasn't my question. My question is, how do I go from 6.0 rooted with SuperSU to 6.0.1 with systemless root (assuming TB works in 6.0.1)
aparanoidandroid said:
... how do I go from 6.0 rooted with SuperSU to 6.0.1 with systemless root (assuming TB works in 6.0.1)
Click to expand...
Click to collapse
Read post 2153 of @Tylog in this thread
http://forum.xda-developers.com/showthread.php?t=3059493
NLBeev said:
Read post 2153 of @Tylog in this thread
http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
So is SuperSU 2.61 the ZIP for Chainfire's systemless root ?
aparanoidandroid said:
So is SuperSU 2.61 the ZIP for Chainfire's systemless root ?
Click to expand...
Click to collapse
Yes since version 2.6x.
NLBeev said:
Yes since version 2.6x.
Click to expand...
Click to collapse
What about Titanium Backup ? Can anyone verify if it works or not with systemless root ? I read a post on Reddit where someone said that they were not able to use it with this root method. Do root apps need to be specifically modified for this type of rooting so it can recognize it ?
Also just to be clear, I am on stock Android 6.0 ROM, rooted and with TWRP recovery.
so the order that I would need following according to the post that you gave me is:
Flash 6.0.1 ROM
flash Update-unSU
flash SuperUser 2.61 or 2.52
Is that correct ? Can I dirty flash 6.0.1 over 6.0 ?
aparanoidandroid said:
What about Titanium Backup ? Can anyone verify if it works or not with systemless root ? I read a post on Reddit where someone said that they were not able to use it with this root method.
Click to expand...
Click to collapse
Root apps with hard coded su-stuff needs to be updated for use with systemless root.
What I read....There is a new version 2.62 that solves compatibility issues. But Android Pay will not work.
NLBeev said:
Root apps with hard coded su-stuff needs to be updated for use with systemless root.
What I read....There is a new version 2.62 that solves compatibility issues. But Android Pay will not work.
Click to expand...
Click to collapse
Oh really ? From what I read, Android Pay and OTA both do work using systemless root although many people think that Google will find a way to block Android Pay again. Its one of the reasons I wanted to use systemless root in the first place.
aparanoidandroid said:
Oh really ? From what I read, Android Pay and OTA both do work using systemless root..
Click to expand...
Click to collapse
Not with version 2.62. Info in the SuperSU thread.
http://forum.xda-developers.com/showpost.php?p=64161125
NLBeev said:
Not with version 2.62. Info in the SuperSU thread.
http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
OK. Thanks for the info.
Yes, TB works with systemless root.
I was running stock 6.0 w/ root (a few xposed mods) and here's what I did:
Wiped system, flashed Cataclysm, flashed SU 2.61, rebooted, profit.
I also manually updated the radio by using fastboot, for what it's worth. AdAway made me create a simlink with the systemless root, but TB seemed to work just fine.
EDIT: I wiped system before anything as I knew it would get rid of any root files and anything related to Xposed. Phone has been running great, but I haven't re-done Xposed as the only modules I really used were GravityBox and YouTubeAdAway. Catacylsm has almost all the features I used in GB so no need to do both. I might put Xposed on tonight for kicks, but I don't really need it for anything right now.
hayzooos said:
Yes, TB works with systemless root.
I was running stock 6.0 w/ root (a few xposed mods) and here's what I did:
Wiped system, flashed Cataclysm, flashed SU 2.61, rebooted, profit.
I also manually updated the radio by using fastboot, for what it's worth. AdAway made me create a simlink with the systemless root, but TB seemed to work just fine.
EDIT: I wiped system before anything as I knew it would get rid of any root files and anything related to Xposed. Phone has been running great, but I haven't re-done Xposed as the only modules I really used were GravityBox and YouTubeAdAway. Catacylsm has almost all the features I used in GB so no need to do both. I might put Xposed on tonight for kicks, but I don't really need it for anything right now.
Click to expand...
Click to collapse
thanks but what happens when you wipe system ? What will I lose other than root ?
aparanoidandroid said:
thanks but what happens when you wipe system ? What will I lose other than root ?
Click to expand...
Click to collapse
Anything Xposed related will be gone, but other than that...nothing. All apps, settings, etc of mine were all retained. Wifi networks, bluetooth connections, all those stayed. Wallpaper, Nova Launcher setup/settings, stayed.
Most ROMs have built in their script to wipe the system partition before flashing anyway, so you're likely already doing it if you're flashing ROMs. I just wanted to start with a pretty clean slate and check to see if anything in data was causing issues, and nothing so far.
Titanium Backup 7.4.0.2 and System Root was working about 2 weeks ago FLAWLESSLY
My last Titanium Backup was on July 7, 2016 with Systemless root, with XPosed, Gavitybox for MM and Stock 6.0 ROM Build MPHS24.49-18-3. I have been using Titanium Backup since I got my MOTO X Pure (2015) in May of 2016, and everything is working great, except I just noticed that Titanium Backup v 7.4.0.2 states
"Error
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."
CLETjB said:
My last Titanium Backup was on July 7, 2016 with Systemless root, with XPosed, Gavitybox for MM and Stock 6.0 ROM Build MPHS24.49-18-3. I have been using Titanium Backup since I got my MOTO X Pure (2015) in May of 2016, and everything is working great, except I just noticed that Titanium Backup v 7.4.0.2 states
"Error
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."
Click to expand...
Click to collapse
Do you have Busybox installed? If not, that may be why. Had the same issue, installed Busybox to /su/xbin, and all is good now.
Gravity Box works with XPosed Framework, which ONLY works with "BusyBox on Rails", which I do have installed. Not sure if I can tell it where to install BusyBox, but it seems to be working now.
Does anyone have a clue to get magisk and titanium backup to work with each other... TB does not seem to ask for Root, seems to simply bypass it...
-----Nevermind, just make sure you have unticked Magisk Hide- in Settings. WORKS!
I rooted my Nexus 6P running stock 6.0.1 and installed Xposed framework (ver 79), but then I found that I cannot login to Snapchat with the Xposed framework installed.
I went to uninstall it, but the uninstall button in the installer app is greyed out. Is there an alternative way to uninstall Xposed?
Use the Uninstaller zip. The in app options like that and reboot don't work
zelendel said:
Use the Uninstaller zip. The in app options like that and reboot don't work
Click to expand...
Click to collapse
Thanks, man. I should have seen that on my own. Been playing around with my new Nexus 6P all night must be making me lose my focus.
Where can I find the uninstaller zip?
It is usually there where you downloaded the installation zip.
Sent from my SM-N910C using XDA Free mobile app
"could not extract meta-inf/com/google/android/update-binary"
this is what I get in TWRP when I try to flash that file. Any thoughts?
Even I would love to know if the uninstaller works properly.
I'm trying to uninstall Xposed Framework from my OPO for the same reasons (Snapchat's geofilters don't work when Xposed is installed) and would know if this method works properly. Thanks in advance.
rmsalihdeen said:
Even I would love to know if the uninstaller works properly.
I'm trying to uninstall Xposed Framework from my OPO for the same reasons (Snapchat's geofilters don't work when Xposed is installed) and would know if this method works properly. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=67365622&postcount=3317
Djiribundi said:
http://forum.xda-developers.com/showpost.php?p=67365622&postcount=3317
Click to expand...
Click to collapse
I dirty flashed my ROM and every time I update, I'll flash the framework zip again. But on the last update it didn't get deleted. Will that be because I didn't delete the dalvik/cache?
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
A few days ago I posted a question about not being able to install any Xposed modules here, so far no one answered: https://forum.xda-developers.com/xposed/xposed-framework-installed-running-t3567230
I thought this problem had something to do with the modules specifically, but it turns out that on my phone, for whatever reason, installing the framework subsequently prevents ALL apps from installing, even those from Google Play itself, displaying a "-504" error.
I see people have asked this question before, but are also not getting answers: https://forum.xda-developers.com/xposed/install-apps-installing-framework-t3430922
Please, if anyone has any idea of why this can be and how to fix it, let me know. Any help will be infinitely appreciated!
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
Hey, thank you for your answer!
I am using a Sony Xperia M4 Aqua E2306, rom is 26.1.A.1.112 Latin America Generic. It is rooted and with TWRP installed accroding to this thread: https://forum.xda-developers.com/m4-aqua/general/root-e2306-m4-aqua-guide-t3270521
I also have a locked bootloader, and it cannot be unlocked, so unfortunately that shuts the door on most rooting options.
I never heard of Magisk before, but from what I'm seeing, it looks it TWRP is required to get root with Magisk, but some kind of root is already required on my phone in order to get TWRP. So I'm not sure how to go about this.
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Anova's Origin said:
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Click to expand...
Click to collapse
Oh well, thanks anyway. I might try it anyways, maybe it will work, you never know. Don't have much to lose at this point
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
FIY Magisk cannot hide Xposed...
I also facing these problem on my rooted Asus zenfone 2 (ze550ml 2gb ram version, Stock ROM, bootloader unlocked) and Asus Zenpad C 7 (p01y, stock rom, bootloader unlocked). The xposed firmware (version 86) is successfully install but can't install any apps from play store and using apk...
I really hope that dev team can solve it.....
Sorry for any grammatical mistakes....
The only way is to flash the firmware
I'm getting the same problem on my LG G4 with v88.2 of Xposed :/
I don't Know if this is too late,but I also have this problem. But there is a work around, go into the xposed installer and turn the switch off so its disabled on the next boot. rebot the device and exposed and its modules are disabled, allowing you to install apps from play store and downloaded .apk files... it would still be nice to install applications while its still on.
Sent from my LG-K550 using XDA Labs
I had this issue on my LGG3. This happens when you have Lucky Patcher enabled in your xposed modules. Disabling it (Lucky Patcher) should solve the problem.