Root acces not working on cm9 help - TouchPad Q&A, Help & Troubleshooting

Hi everyone I just bought an HP touchpad from Craigslist and it was already dual boot for cm9 and webos. I thought that once you had cm9 you could have root access if you turn it on in the settings . I did that but still no root access not working . I've looked for an answer on how to re-root it but I didn't find it .. I would love your help.. so I can do the hulu fix

if you dont have superuser app in your applications then redownload it from the google play store app.

I do have super user but it denies all apps and when I run root checker it sais that its not rooted. I can see the log and everything. I turned root on and off from the settings but nothing.

kipster3001 said:
Hi everyone I just bought an HP touchpad from Craigslist and it was already dual boot for cm9 and webos. I thought that once you had cm9 you could have root access if you turn it on in the settings . I did that but still no root access not working . I've looked for an answer on how to re-root it but I didn't find it .. I would love your help.. so I can do the hulu fix
Click to expand...
Click to collapse
In webos, enable debugging, there's a code you type in, that gets you root.
Look around the webOS nation forum, there are good tutorials there that will help you out.

chicle_11 said:
In webos, enable debugging, there's a code you type in, that gets you root.
Look around the webOS nation forum, there are good tutorials there that will help you out.
Click to expand...
Click to collapse
Will it then let me have root access when I boot cm9 . I know the code is webos20090606.
Let me try it..

kipster3001 said:
Will it then let me have root access when I boot cm9 . I know the code is webos20090606.
Let me try it..
Click to expand...
Click to collapse
It should. It did for me. And that is the code.

chicle_11 said:
It should. It did for me. And that is the code.
Click to expand...
Click to collapse
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in android.
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip

Just flash the first zip in the post above to get root in Android
Enabling Developer Mode in webOS will have no effect on Android Root Access.
Make sure you go to CM Settings and make sure for Developer Options, Root Access is set to Apps and ADB
Also open the Super User app and look at the "Default Action" property and settings and make sure it isn't set to deny.

I'm about to go try this thank you
haxin said:
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in andro
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip
Click to expand...
Click to collapse

When I try to flash the zips it said it can't open install aborted
kipster3001 said:
I'm about to go try this thank you
Click to expand...
Click to collapse

haxin said:
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in android.
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip
Click to expand...
Click to collapse
kipster3001 said:
I'm about to go try this thank you
Click to expand...
Click to collapse
I just downloaded the zip files and there is something wrong with them. I can't open them. Either way, why don't you go into the Google Play Store on your Touchpad and then uninstall the SuperUser app. Then re-install it. After that double check to make sure that you have latest su binaries.

Related

SuperSu not granting automatic permissions anymore

hey guys i have one problem with supersu.
i installed clean master and do cleaning **** and startup cleaning things and after reboot all apps that have granted root permission( foldermount, gmd gestures, lightflow, etc), these apps shows no toast popup after boot and to make them grant permissions i have to open them. Same thing when i installed boot manager and did not do anything but boot and again no supersu toast popups about root permissions after boot.
is there a way to keep the root grants after the boot? ( i have checked default acces to grant in supersu app)
I'm having problems with clean master working with SuperSu too.
clean master is so powerfull that disables supersu permissions.
They probably change some file permissions that SuperSU frowns at.
Chainfire said:
They probably change some file permissions that SuperSU frowns at.
Click to expand...
Click to collapse
i want to maintain supersu permissions after every boot no matter what. is there some option in supersu to be activated for that?
i'm on note 3 rooted with stock tw.
''enable supersu during boot''
please explain to me for what is this option
thx :good:
bump
dancapitan said:
''enable supersu during boot''
please explain to me for what is this option
thx :good:
Click to expand...
Click to collapse
This option has a summary that's pretty unclear. I've emailed the dev, hope to receive an answer soon. Fact is apps running during the boot_completed seem to get root randomly if this option is not enabled! Let me insist on the random fact, as my apps get root on boot frequently but not all the time. Other users have reported the same random behavior. Once the option is enabled everything works as expected!
However the option seem to imply that any root request on boot will be granted!? Regardless of user choice????
To make it short, check the option "enable supersu during boot" and root apps will receive root on boot as they used to!
3c said:
This option has a summary that's pretty unclear. I've emailed the dev, hope to receive an answer soon. Fact is apps running during the boot_completed seem to get root randomly if this option is not enabled! Let me insist on the random fact, as my apps get root on boot frequently but not all the time. Other users have reported the same random behavior. Once the option is enabled everything works as expected!
However the option seem to imply that any root request on boot will be granted!? Regardless of user choice????
To make it short, check the option "enable supersu during boot" and root apps will receive root on boot as they used to!
Click to expand...
Click to collapse
You should turn this into a proper bug report in the proper thead (either the beta or its own new thread) with all the useful information you think may be relevant. There is no email support, all support is here.
The option itself is for apps that run before Android is fully up and running, or su from adb shell during a bootloop, etc. I thould not influence apps running su from bootcomplete receivers, and if it does, then that needs to be investigated.
Is there currently any way to enable this feature via ADB on a boot looped phone? I really wish I would have known about this! I wouldn't be stuck where I'm at if I had only checked this option. Device is stuck at LG logo, no download or recovery, but has access to ADB. SU was installed, but I don't have root via ADB since the phone isn't finished booting...thus I'm not able to copy over the proper system.img or change the recovery/laf. Dang!
I have the problem too, when I install Fake Wifi, the automatic SuperSU granted is not working. Please help some advance. Thank's.
Hey guys why root required apps request for root access after installing super su
I have the same problem, have to add a task in tasker, auto open supersu and root granted apps once after boot,

Adaway problems on Nexus 6 marshmallow

I've researched and tried every method to get AdAway to work. I uninstalled some system apps which allowed me to install it but I cannot get past that because of the S-off warning screen.
I am rooted and bootloader is unlocked. Ive attatched a screenshot of my kernel etc
Do you have a folder called init.d in system/etc?
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
miguelito18 said:
Do you have a folder called init.d in system/etc?
Click to expand...
Click to collapse
No i do not
Mike02z said:
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Click to expand...
Click to collapse
Do you have a suggestion on a kernel? And id like to stay stock on the ROM if possible
Mike02z said:
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
Click to expand...
Click to collapse
Ya sorry, i was tryng to post it quick on my phone and didnt look at all the options as to where the best place to post would be
Khizar said:
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
Click to expand...
Click to collapse
What is system less root if i may ask? and ill look for that zip you mentioned
*update* installed that zip. attempted to install and get the same error about s-off
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
gee2012 said:
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
Click to expand...
Click to collapse
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
trbomp5 said:
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
Click to expand...
Click to collapse
Symlink to /data/data/hosts in settings.
gee2012 said:
Symlink to /data/data/hosts in settings.
Click to expand...
Click to collapse
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
trbomp5 said:
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
Click to expand...
Click to collapse
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
gee2012 said:
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
Click to expand...
Click to collapse
cleared data and tried again same results.
stock rom, unlocked bootloader, kernel is 3.10.40-ElementalX-N6-3.00, twrp 2.8.7.1
Universal init.d install it from play store and follow instructions
miguelito18 said:
Universal init.d install it from play store and follow instructions
Click to expand...
Click to collapse
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
trbomp5 said:
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
Click to expand...
Click to collapse
I don't have an init.d folder as I run the stock kernel. There must be another problem.
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
gee2012 said:
I don't have an init.d folder as I run the stock kernel. There must be another problem.
Click to expand...
Click to collapse
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Yasharkhan said:
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
Click to expand...
Click to collapse
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
any way i can get you to step by step these with all i need to do?
trbomp5 said:
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Click to expand...
Click to collapse
Look in the stickies thread in general for how to root.
Usually what i do is:
Flash or boot into TWRP
Flash superuserSU
Install BusyBox
That's it as i use the stock rom, kernel and recovery. I just need root.
---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------
trbomp5 said:
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
Click to expand...
Click to collapse
No, when the device is turned on.

Cannot find Supersu tool in Settings menu

I cant find supersu in settings..im running on cm11s on OPO.
But im getting root access. When i search in settings, it shows a superuser tool. bt i cant access it through the settings.
plz give me your valuable points..screen shorts are attached below for ur clarification. please help me..
cjl bny said:
I cant find supersu in settings..im running on cm11s on OPO.
But im getting root access.....
Click to expand...
Click to collapse
Suggestion: uninstall su - reboot - reinstall su.
Go to the play store and select superSu. Hopefully you see the Uninstall button.
I tried to reinstall supersu many times. does not appear in the menu and does not have an open button in settings.
Yes I have verified I have root access. Using Android x86 7.1.2
How do I run this app?

Rooting LN14????

Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).
have you enabled Developer Options?
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".
Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse

how to open Magisk after it's hidden?

I outsourced rooting my device. Now I need access to Magisk to change the settings for the monitoring software I need to install. How do I open the Magisk app after it's been hidden? TIA!!!
It's in your app drawer, named "Manager".
gamoses said:
I outsourced rooting my device. Now I need access to Magisk to change the settings for the monitoring software I need to install. How do I open the Magisk app after it's been hidden? TIA!!!
Click to expand...
Click to collapse
Just run the app "Magisk Manager" or "Manager" (with the Magisk icon) that is on your app drawer.
Don't you have it? Well, then you don't have a proper installation of Magisk, at least the Manager is lacking. Download it (the apk) and install. Then open it and see if everything is fine or not. Check main Magisk release thread for links.
Thank you so much for replying! Magisk Manager is not in my app drawer, but it *is* listed in the device settings as an installed app. I just can't figure out how to open it. I assumed that app had also been hidden somehow. Advice?
Whoever you outsourced it to have done something that's not standard. Ask them...
Bummer. They'll probably charge me again. Thanks for your help, though!!!
gamoses said:
Bummer. They'll probably charge me again. Thanks for your help, though!!!
Click to expand...
Click to collapse
By the sound of it, they've messed up. So if I were you I would demand they fix things free of charge.
Didgeridoohan said:
By the sound of it, they've messed up. So if I were you I would demand they fix things free of charge.
Click to expand...
Click to collapse
Yeah, that didn't work. So I'm again trying to DIY...
Your wonderful guide says:
Unhiding the Magisk Manager
Go to the Manager settings and choose "Restore Magisk Manager".
Click to expand...
Click to collapse
But I can't do that because "Manager" is not in my app drawer.
You also have:
Starting MagiskHide manually
MagiskHide is enabled by default and should start automatically on boot. If it isn’t working, try toggling MagiskHide off and on in the Manager settings. If MagiskHide just won't start when toggling it in the Magisk Manager (check the Magisk log, it might have started but the Manager doesn't reflect it), try starting it manually. This can be done in a terminal emulator (as su) by executing the following command:
su
magiskhide --disable
magiskhide --enable
Click to expand...
Click to collapse
So I downloaded a terminal emulator and ran this command, but got this error message: su: unrecognized option '--disable'
Any more tips before I lose more money? Should I just try and reinstall Magisk completely? Having watched the tech guy do it the first time, I'm not sure I'm completely up for the task. Would it be easier after it's already been successful? Should this be straightforward, or am I better off handing over my wallet?
THANK YOU so much!!!
gamoses said:
Yeah, that didn't work. So I'm again trying to DIY...
Your wonderful guide says:
But I can't do that because "Manager" is not in my app drawer.
Click to expand...
Click to collapse
I'm curious... What happens when you want to grant superuser access to an app? Do you get the prompt to accept or deny?
I'm also curious what Magisk version you actually have installed. What's the result if you run this command in the terminal emulator:
Code:
magisk
You also have:
So I downloaded a terminal emulator and ran this command, but got this error message: su: unrecognized option '--disable'
Click to expand...
Click to collapse
You need to run the three commands separately, not all together.
Any more tips before I lose more money? Should I just try and reinstall Magisk completely? Having watched the tech guy do it the first time, I'm not sure I'm completely up for the task. Would it be easier after it's already been successful? Should this be straightforward, or am I better off handing over my wallet?
THANK YOU so much!!!
Click to expand...
Click to collapse
My first tip is to not trust your "tech" guy... From what you've described here it doesn't at all sound like he knows what he's doing.
Secondly, I would try to install the Manager and see what happens. Download the apk from here (that's the current version of Manager v7.2.0) and install that. If that works you're golden, if it doesn't report back...
I'm curious... What happens when you want to grant superuser access to an app? Do you get the prompt to accept or deny?
Click to expand...
Click to collapse
I don't know what this means or how to do that.
I'm also curious what Magisk version you actually have installed. What's the result if you run this command in the terminal emulator:
Click to expand...
Click to collapse
19.1
Secondly, I would try to install the Manager and see what happens. Download the apk from here (that's the current version of Manager v7.2.0) and install that. If that works you're golden, if it doesn't report back...
Click to expand...
Click to collapse
So I downloaded and installed this apk. I think. All that's necessary to do that is just click on it while on the phone, right? It said it was updating my previously installed Magisk Manager, so I assume it worked. But both immediately and after a reset, there is still nothing new in the app drawer. It still shows in my phone settings->apps, but that's it.
I've attached a log from my results in the terminal emulator regarding magisk and magiskhide. I'm sure I'm doing something wrong.
What launcher do you have? Sounds like the guy just his it from showing up the app drawer?
Sent from my MI 6 using Tapatalk
I was about to kick myself if it was that easy. Just installed Nova to check, and still no Manager app.
So should I just try to reinstall Magisk completely? Do I need to uninstall first? Is it as simple as opening the .apk on the device?
Hi, I have the same problem, did you find a solution?

Categories

Resources