With some help on the cyanogenmod forums, I worked out a way to enable the integrated superuser manager to actually function!
REVISED EDITION:
WARNING! DO NOT ATTEMPT UNLESS YOU KNOW WHAT YOU ARE DOING.
This is an experimental step to bring a feature from regular Cyanogenmod to 11S. You have been warned.
This requires adb and fastboot to be installed.
Please read all the instructions before attempting
1)-- Optional-Flash a custom recovery of your choice. There are threads out there that explain this.
2)Next flash the debuggable kernel, found at the bottom of this post. You can easily flash it via fastboot.
fastboot flash boot ./path/to/boot-debuggable.img
2)Download su.zip I created.
3)Boot into custom recovery(a requirement). This can be done without actually flashing it. Look up how, plenty of threads already.
4)Flash su.zip
8) Reboot.
9)If you didn't before doing this, go to Settings => About Phone and enable developer mode. Under Settings => Developer Options select Root Access and change it to Apps and ADB. Now install any root application or root checker and test it out.
Debuggable Kernel is downloadable here at the bottom:
https://cyngn.com/products/oneplusone/
su.zip
http://www.androidfilehost.com/?fid=23578570567721138
https://mega.co.nz/#!sp8nmL5J!Pj2Z4UI-7vG2YsMwEpIbDLTWOwiyWwu398oLE9edFdk
RESERVED
RESERVED
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
joaocadide said:
I'm going to try this one.
I suspect that the normal root is doing something bad for my battery life.
Click to expand...
Click to collapse
What current superuser manager are you using? SuperSU?
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
How can I get rid of the menu when I use SuperSU instead?
Veiti said:
Download*Android Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm
Launch the app and type the following commands:
su (will request for superuser permissions)
setprop persist.sys.root_access 3
This is the other way to install Superuser in the Settings.
Click to expand...
Click to collapse
That only makes the menu visible. The menu will not actually function as a Superuser manager. For that, you would need the debuggable kernel and the proper compatible su binary which is why I wrote my instructions.
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
jbass350z said:
Will this solve the problem I am currently having?
I have the new OnePlus One phone. It is unlocked and rooted.
In the Secure Settings plugin for Tasker, I cannot get the System+ Module to install, but get the following message:
Code:
Root access i currently disabled for all applications by a system setting.......
Would you like to enable it now?
Clicking OK sends me to the developer menu where there are no options to enable root access.
How can I get this thing to install?
Click to expand...
Click to collapse
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
vladashram said:
Well you have two options, either enable the functional Superuser menu by following my instructions or enable the developer options menu and then from within the developer options menu disable it. That will enable the NON-functional Superuser menu.
Click to expand...
Click to collapse
I had this same exact issue with secure settings, and elected to follow the instructions on this page to activate the cyanogenmod root settings - it worked just fine. Interestingly, even after losing the "built in root" after updating to XPNH300, secure settings still seems happy.
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
chenkeikari said:
I have followed the intro on 30O except using franco's kernel replace the debugable one. No notification show up when the app asked ROOT authority and also the authorization didn't success. Is this method only support by stock kernel?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
vladashram said:
It isn't supported by the stock kernel.
It is supported by the stock debuggable kernel.
It is also supported by any kernel that has ro.debuggable set to 1. To check if a kernel has that set, boot into it and run from a terminal app or adb "getprop ro.debuggable".
Currently, there is no stock debuggable kernel available for 30O yet however the link below has a workaround zip that will enable integrated superuser access, with the exception of adb root.
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Click to expand...
Click to collapse
As of right now, the stock debuggable kernel for 30O is live and available.
Thanks for your work.
But could you please update to the latest version of the SuperSU binaries or could you tell me, what you modified comparing it to the normal SuperSU.zip?
Would you please share how and why would this be different than a straight forward install of SuperSU?
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Not working for me
Titokhan said:
@vladashram
I have tested it days ago but forget to post feedback
Its successfully tested on both OnePlus One & YU Yureka.
Click to expand...
Click to collapse
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
remortr said:
pls help me i unlocked bootloader aswell as rooting also done but built in super user i caunt...pls hep see attachment me on windows 7 64bit
Click to expand...
Click to collapse
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Pls help me step by step procedure..
sendhiloo7 said:
Confirm phone in fastboot mode .. can you type fastboot devices..if no device showing , then phone not in fastboot mode or not connected to pc
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Every thing done but fast boot wont work in my case pls help me sir .pls see my attachment...
Related
I have LG optimus one and Iam try new rom Omnirom beta 7 and beta 7.1. Iam saw ther isnt any superuser app and Iam try flash SuperSU (chainfire) and SuperUser (CloakWorkMod) with cwm recowery 6.4.0.6 and twrp 2.7.0.0.
Now I can run some apps like a total commander with superuser aces, Rom manager, but Iam style not can run titanium backup and lot of more. Sorry my English. Thanks for all reply.
Just FYI it is recommended to run twrp and su. Regarding you question: can you use the functionality that requires root in the apps you mentioned to be working? If not you simply have no su access at all. In case you can run them go into the su UI under settings and see if you can manually grant su permission to TiB and the like. It seems strange to me that super user should only work for some of your apps. I might be wrong though, I'm no expert.
Sent from my Find 5 using XDA Premium 4 mobile app
thanks
chuSmu said:
Just FYI it is recommended to run twrp and su. Regarding you question: can you use the functionality that requires root in the apps you mentioned to be working? If not you simply have no su access at all. In case you can run them go into the su UI under settings and see if you can manually grant su permission to TiB and the like. It seems strange to me that super user should only work for some of your apps. I might be wrong though, I'm no expert.
Sent from my Find 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks Iam try it.
I am found error
chuwork54049883 said:
Just FYI it is recommended to run twrp and su. Regarding you question: can you use the functionality that requires root in the apps you mentioned to be working? If not you simply have no su access at all. In case you can run them go into the su UI under settings and see if you can manually grant su permission to TiB and the like. It seems strange to me that super user should only work for some of your apps. I might be wrong though, I'm no expert.
Sent from my Find 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This dont work
Iam dont saw a easy think. My result app hawe root aces but adb no.
How to repair. Settings -> for developers ( If you dont see it, you must go to settings -> About phone and seven times touch build number)
In setings you mustvote apps & adb in defoult only apps.
Hi all. I've installed kodi and with the confluence ++ skin. There are a few observations and questions I would be grateful if someone could help point me to the right direction.
1. I cannot get the power suspend option on kodi like how it exists in spmc. Is there a settin somewhere to enable it.? I cannot seem to find it. maybe some config file?
2. When adding 7 tiles to the bottom, the first tile gets slightly cut.
3. With rbox's boot menu. Is there a way to disable the boot menu display on every boot? or at least decrease the time of 5 seconds?
Really appreciate your help.
I tried to add the power options from elmero's repo but that requires the su and when I try to run the su script, it fails. however I do have root. am confused to make kodi my main OS yet . any guidance?
have you went into the SU app under the FTV menu ( the OEM rom, not XBMC ) and launch SU. Update binaries and apply etc. Try that.
mroneeyedboh said:
have you went into the SU app under the FTV menu ( the OEM rom, not XBMC ) and launch SU. Update binaries and apply etc. Try that.
Click to expand...
Click to collapse
what is the su app you are referring to in the ftv menu? I have supersu and I have an option to force stop only
also when I try spmc, I get the power options
confused.
Open superuser from the FTV app list and let it update.
Montisaquadeis said:
Open superuser from the FTV app list and let it update.
Click to expand...
Click to collapse
I have the supersu application. That does not have an open option. I also downloaded the superuser from the playstore and I still get eh checksu.py script failure. on spmc I too get the script failure but I have the power options working just fine.
Sorry man, there should be an option to update binaries like in any SU app.. Which version are you using
When I installed rbox's CMW recovery and custom ROMs I lost the ability to open su. I believe this is a known issue.
jmerrilljr2 said:
When I installed rbox's CMW recovery and custom ROMs I lost the ability to open su. I believe this is a known issue.
Click to expand...
Click to collapse
For now I'm still sticking to spmc. I don't think helix has the support ready yet. SPMC 13.3.2 (not the latest one) works the best with .ts files as well.
Working Root Method For your Memo Pad 7
1. Extract the File from http://www.mediafire.com/download/lp7ngv5l6vm5lin/AsusIntelRootKit.zip
2. Have Debugging Mode Enable (Setting>About>Software Information>7 Clicks on the Build Number)
Back to Settings>Developer Options and select USB DEBUGGING
3. Open the extracted folder and click "Root" (Follow the instructions)
Your Rooted
Dont update the superuser app!!!!
Install Busybox from the play store
Install and Reboot
Check with root checker
ADB Driver for Asus http://www.mediafire.com/download/u46c7zwf2k2xjr8/AsusADBdrivers.zip
JarrelStudios said:
Working Root Method For your Memo Pad 7
1. Extract the File from http://www.mediafire.com/download/lp7ngv5l6vm5lin/AsusIntelRootKit.zip
2. Have Debugging Mode Enable (Setting>About>Software Information>7 Clicks on the Build Number)
Back to Settings>Developer Options and select USB DEBUGGING
3. Open the extracted folder and click "CheckBeforeActivation" (Follow the instructions)
4. When Device Restarts unlock screen and go back to the same folder and click Root....
Your Rooted
Dont update the superuser app!!!!
Install Busybox from the play store
Install and Reboot
Check with root checker
ADB Driver for Asus http://www.mediafire.com/download/u46c7zwf2k2xjr8/AsusADBdrivers.zip
Click to expand...
Click to collapse
Thanks for the completely bland and incorrect Guide! Nowhere in that ZIP archive is a file called "CheckBeforeActivation". With many hundreds of thousands of these devices in the marketplace, do your fellow XDA members and GET YOUR FACTS STRAIGHT BEFORE YOU POST!!!:silly:
The file was removed as it was it copy of another file
Sent from my K013 using XDA Free mobile app
This method works on my zenfone 4 where else fail using fastboot zip file method
Thanks for posting this!
how come you cant update supersu??
I tried this method to root my device, I have a BBY build. The application says it rooted okay. When I reboot the device and try to install BusyBox it says it doesn't get a response from the device. When I check root with Root Checker Basic it says that the device is not rooted. Any thoughts on what I might be missing?
Is the super user app installed?
Sent from my K013 using XDA Free mobile app
yay, i am now rooted, thankyou for an easy way to do this..
a few questions..
1..how come i cant update the supersu, and how can i prevent this from happening..
2..can i now uninstall the busybox app as its now downloaded the files to the device..
3, is it now safe to uninstall all the asus rubbish on the tablet(what have you uninstalled)
Memo Pad 7 ME572C:
after the latest update 11.8.3.31 (from 11.8.3.30), this root method and the rootzenfone method can no longer root the tablet.
slim_thumb said:
Memo Pad 7 ME572C:
after the latest update 11.8.3.31 (from 11.8.3.30), this root method and the rootzenfone method can no longer root the tablet.
Click to expand...
Click to collapse
Ahh, thanks for this. What I was looking for. I did the update, and now regretting it lol.
I would also like to know why we can't update SuperUser
onimorza said:
I would also like to know why we can't update SuperUser
Click to expand...
Click to collapse
its safe to update it now..before it would remove superuser and you would have to factory reset the re-root
To the OP, it looks like you just reposted the work of twenty-three pin from here:
https://translate.google.de/transla...sts/247110-merry-christmas&edit-text=&act=url
Too bad when you were stealing someone else's work you didn't work slowly enough to notice that he mentions that the Asus 572C should use V2 of his work:
http://www.mediafire.com/download/ui9ipe786dulj98/AsusIntelRootKitv2.zip
Hope this helps someone.
If you check the commands int the .bat file, you will see they are different... Its just basic fastboot commands. And as of recent updates the me572 can't be rooted using this method. So I'll head back to the drawing board as soon as I get time to
Sent from my K013 using XDA Free mobile app
I honestly haven't seen that post before
Sent from my K013 using XDA Free mobile app
JarrelStudios said:
its safe to update it now..before it would remove superuser and you would have to factory reset the re-root
Click to expand...
Click to collapse
Thanks, but meanwhile I've rooted with this method http://forum.xda-developers.com/memo-pad-7/help/rooting-memo-pad-7-rootzenfone-t3000389 and also updated without problem.
Also no need for ADB with that method.
question
abudabu said:
Ahh, thanks for this. What I was looking for. I did the update, and now regretting it lol.
Click to expand...
Click to collapse
Will this work for ASUS 16GB 8" IPS HD Android Tablet, 1.33GHz Intel Bay Trail-T Z3745 quad-core processor, with kit kat 4.4?
(ME180A-A1-WH)
zach
any method of rooting on stock LP?
will this work with latest WW_K013-12.10.1.33-20150917 ? Lolipop 5.0
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
goalkeepr said:
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
Click to expand...
Click to collapse
Nice find, I'll be adding this thread to my Guides / Info Thread....
Thank you dude
Cool Awsome!! Now my phone is working properly with ROOT.
Is this step still needed? Been following the links on DrakenFX's thread that lead me here.
Thanks guys. The dev is much appreciated as is the guide pulling everything together.
Barsky said:
Is this step still needed?
Click to expand...
Click to collapse
Whether it is done by a script (if so there should be clear indication that it does this so people know where they stand in the overall process) or by hand it still needs to be done, it is a completely separate issue from whether or not the boot-loader is unlocked or the phone rooted.
Already did it. :cyclops:
Is this only needed if your bootloader is locked but you still wanna root ?
Ugh, so this was the reason why I couldn't uninstall system apps even w/ a system app uninstaller....
So developer unfriendly :/
Haha needed to do this on the official root for EU as well.
Yay, thanks guys! got adaway running. Starting to feel like home again..now to backup it before I screw it up..
I'm not getting it to work on my Axon 7 rooted with terminal emulator
Sent from my ZTE A2017U using XDA-Developers mobile app
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
nickcaper said:
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
Click to expand...
Click to collapse
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
xtermmin said:
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
Click to expand...
Click to collapse
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all it does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
nickcaper said:
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all ti does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
Click to expand...
Click to collapse
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
xtermmin said:
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
Click to expand...
Click to collapse
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
nickcaper said:
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
Click to expand...
Click to collapse
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
xtermmin said:
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
Click to expand...
Click to collapse
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
nickcaper said:
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
Click to expand...
Click to collapse
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
xtermmin said:
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
Click to expand...
Click to collapse
Can you tell me if your phone is rooted? what update version si your phone? Mine is 27.
Did you do this permission fix before or after root? did you use an emulator to do the fix or adb?
Anyone tried rooting Pixel XL and how does it works after rooting ? Reviews
Everything works fine here
Rooting generally does not and can not effect the device. What you do after may either harm or help the device.
All that rooting does is give you SU access it is what you do with the access that makes a difference.
Mind you even though in itself rooting is pretty harmless, Google will always try and detect the root and stop APPs like Android Pay from working.
AstroDigital said:
Rooting generally does not and can not effect the device. What you do after may either harm or help the device.
All that rooting does is give you SU access it is what you do with the access that makes a difference.
Mind you even though in itself rooting is pretty harmless, Google will always try and detect the root and stop APPs like Android Pay from working.
Click to expand...
Click to collapse
I mean is there any bootloop or something and how is everything working any lagging or somethjng
Huzaifaamirka said:
I mean is there any bootloop or something and how is everything working any lagging or somethjng
Click to expand...
Click to collapse
No issues here, Enable OEM unlock and unlock the device via ADB then use adb to "fastboot boot boot-to-root.img" allow it to reboot and set up again then away you go ( you might have to ADB BOOT the boot-to-root for it to stick )
Using the ad away work around now ad blocking is a go
Working fine with ElementalX kernel and root.
hutzdani said:
No issues here, Enable OEM unlock and unlock the device via ADB then use adb to "fastboot boot boot-to-root.img" allow it to reboot and set up again then away you go ( you might have to ADB BOOT the boot-to-root for it to stick )
Using the ad away work around now ad blocking is a go
Click to expand...
Click to collapse
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
trapperjohn said:
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
Click to expand...
Click to collapse
With USB Debuiing enabled open your ADB terminal and type :
"adb shell"
"su"
"mkdir /su/etc; cp /system/etc/hosts /su/etc/hosts; echo "#!/su/bin/sush\nmount -o bind /su/etc/hosts /system/etc/hosts" > /su/su.d/50adaway; chmod 0700 /su/su.d/50adaway"
After this reboot your device and apply ad blocking hosts with the latest ad away build
Thank you for the info!
I wonder if there are plans to update adaway so this procedure will not be needed..
Thanks again great detail
Bryan
Sent from my SM-N900V using XDA-Developers mobile app
Wrong sub forum.
trapperjohn said:
Hi,
What is the adaway workaround?
Thank you for your help,
Bryan
Click to expand...
Click to collapse
All you have to do is download the 3.2 Dev preview build and enable systemless mode in preferences. Works like a charm.
https://www.androidfilehost.com/?fid=312978532265366394
That's great so with version 3.2 dev no adb procedure is needed?