Related
Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
At the moment you can't until Google updates that feature to allow that. The multiuser is in its infancy. We will just have to wait I guess.
Sent from my Nexus 10 using Tapatalk HD
Thanks for your answer
waiting for this ...
It's actually the su binary which is tied to the primary user only at the moment... not sure how, or if, it can be built otherwise!
Furthermore, it is not even possible to enable developer settings (via build no) for second users, right?
So, without USB-Debugging no adb to backup second user apps (w/ data) using the Toolkit..
Is there any chance to fully backup second user apps? Apart from nand of course, as I would like to backup/restore apps for a switch to CM10.
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
craigacgomez said:
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
Click to expand...
Click to collapse
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
djd338 said:
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
craigacgomez said:
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
Click to expand...
Click to collapse
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
jrod091 said:
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I don't know if RC settings are global or user specific... depends of the settings... if the setting is specific to the user context, it will work, otherwise it won't...
drykc said:
Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
Click to expand...
Click to collapse
If you are using SuperSu, the dialog asking for root permission shows up on the owner's user account. In SuperSu, only the owner can grant superuser privileges.
Sent from my Nexus 4
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Should probably ask in the n7 forum...
Sent from my Nexus 10 using xda app-developers app
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
The SoC in the Nexus 7 is Tegra 3, which has an ARM processor. You're fine.
Sent from my Nexus 10
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Lol of course n7 has an arm cpu!
For android phones and tablets, there's arm, mips, and x86. Any good android will 98% likely be arm. Motorola released an x86 (Intel) phone, and I'm sure there's a few other ones out there. And if you have mips, you probably got a cheapy Chinese tablet. xP
Swiped from my Nexus 10 using xda-developers app
Sorry for hijacking.
My main reason for root is to restore application data. Will I be able to restore the data on both the primary user and also the secondary user if I have root (either through the main or secondary user)
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
1234556789 said:
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
KlipperKyle said:
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
Click to expand...
Click to collapse
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
1234556789 said:
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like you have Superuser 3.3 installed and working, right? In order to use Superuser 3.3 with another user account, you need to go to its preferences and change Multi-user Mode to something other than "Owner Only."
"Owner only" means that only the owner can su.
"Owner controlled" means that the owner is the only one who can set and deny root permissions. Any filters are applied to all users.
"User controlled" means that each user can define allow/deny filters. Only use this option if you really trust other users.
Don't update to the version of Superuser on the Play Store. The version on the Play Store is 3.1.3. You already have 3.3 flashed on your system partition. Because you won't need the version on the Play Store, you can also stay away from ChainsDD's Superuser Update Fixer. (The update fixer is for an entirely different issue than the one you have.)
If you have installed these packages, you should uninstall them.
For future reference:
I should have been clearer about deleting files in custom recoveries. If you use TWRP, there is a built-in file manager under the Advanced menu. If you use ClockworkMod, you should use ADB commands: (ADB is a tool found in the Android SDK)
Code:
adb shell
cd /system
ls -al
[I](You should see a bunch of directories. If not, make sure /system is mounted.
This is an option in one of the recovery menus; I can't remember which
one offhand.)[/I]
rm app/Superuser.apk
rm bin/su
rm xbin/su
Then reflash the Superuser zip.
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.
Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app
RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app
Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!
solved...
Installing busy box should resolve the issue...
Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?
Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.
My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.
I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues
CM Dev Settings
In Dev options is Root access set to Apps and ADB?
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?
I will update the method as and when newer methods are available!
So confirmed Root is here presented by @cybojenix
I am making the thread only for making it Noob friendly, and making the instructions bit more detailed!
All credit goes to @cybojenix
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Procedure
Download mfastboot-v2 extract its content and use that for unlocking Bootloader
Unlock your bootloader From Here
TIPs:
Unlocking bootloader will wipe your device, Backup your photos, music, contacts using applications in play store or whichvere method you prefer
The motorola site tells us to download the android SDK, You can skip that big download and use the fastboot in step 1
Follow the further steps given on motorola's site, After clicking on Request an Unlock Key, You will get an email which will consist guideline to proceed further!
Clicking on Request an Unlock Key is the point where you lose your warranty
Download The TWRP recovery from here(thread) or here(Goo.im) rename it recovery-twrp.img and move it in the same folder as of step 1
Download The SuperSU from here(thread) or here(chainfire.eu)() and copy it into the root of your internal memory!
Connect your phone to PC and Reboot to bootloader by pressing VolumeDown+Power button for about 6-7 seconds.
Go to the directory in step 1, Do Shift+RightClick in empty space in the folder without selecting anything, Select Open a command window here.
Run following command
Code:
fastboot boot recovery-twrp.img
If facing errors refer to TIP No. 2 and 3
[*]Now touch doesn't work in recovery straight away, so wait 60 seconds without touching the phone, The phone screen will go blank.
[*]Press power button and do swipe to unlock to get your touch working again!
As Motorola released source code for the kernel, @cybojenix has fixed the touch issue, you can skip to step 10 directly!
Select Install, scroll down and find the SuperSU Zip downloaded in step 4.
Swipe to confirm, wait untill the flash is complete and then select reboot, to boot into your phone which is rooted now
Check your app drawer, There should be SuperSU installed. Congratulations you are rooted!
TIPS:
Downloading things from the thread link is a better option as the hotlinks may get outdated, Thread links will not!
If you want to install twrp rather then just booting into it for once, you can use following command to flash it permanently
Code:
fastboot flash recovery recovery-twrp.img
If stuck on Boot Logo of Motorola (blue M), @JerryGoyal has provided a Thread Here to solve the problem using CWM instead of TWRP.
According to the method you can download CWM and Rename it to recovery-cwm.img in place of TWRP in step 3. Execute other steps the same
And in step 7 Replace the given code with
Code:
fastboot flash recovery recovery-cwm.img
In CWM Touch doesn't Work to scroll Use Volume Buttons and Use Power Button to select the choice
in Step 10 you would select Install from sdcard
If you do something wrong and stuck somewhere, The stock firmwares are available for restoring.
[Condor][Stock Firmware] Restore your Moto E to Stock[Lock Bootloader][Noob Friendly]
Reply if any issues! I'll try my best to help!
Reserved!
Very good effort :thumbup:
Some newbies actually need it
Sent from my XT1022 using XDA Free mobile app
quick question.. is it possible to remove that annoying bootloader unlocked warning that shows up everytime you start up the device?
dpool94 said:
quick question.. is it possible to remove that annoying bootloader unlocked warning that shows up everytime you start up the device?
Click to expand...
Click to collapse
Right now it's not but in the coming days I will look into a method similar to this for our device to "remove" the warning.
shimp208 said:
Right now it's not but in the coming days I will look into a method similar to this for our device to "remove" the warning.
Click to expand...
Click to collapse
You don't need to do it bro.. Motorola updated their bootservice .. I mean the warning shows up but only for 2-3 secs and after that comes a new logo loading.. So I think It would be best not to waste time on such things
Just a suggestion.. Instead of flashing a custom recovery, you could also just boot into the recovery using "fastboot boot recovery.img".. This way the stock recovery won't get changed for people who would like to keep it.
I unlocked the bootloader,installed twrp and flashed the superuser.. and I can even see superuser in my app drawer but none of the apps that require root like titanium backup are working.. it says my device isn't rooted :/ help please
dpool94 said:
I unlocked the bootloader,installed twrp and flashed the superuser.. and I can even see superuser in my app drawer but none of the apps that require root like titanium backup are working.. it says my device isn't rooted :/ help please
Click to expand...
Click to collapse
Check your device by installing this device if you really rooted it or not. DOWNLOAD THIS APP
Mrtoxicgamer10 said:
Check your device by installing this device if you really rooted it or not. DOWNLOAD THIS APP
Click to expand...
Click to collapse
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 1.00 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 96144 2008-08-01 17:30 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your XT1022 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
Guys check this too
We can flash this through stock recoveryhttp://forum.xda-developers.com/galaxy-s2/orig-development/30-10-2012-k-la-lp-t1103399
Sent from my XT1022 using XDA Free mobile app
dpool94 said:
I unlocked the bootloader,installed twrp and flashed the superuser.. and I can even see superuser in my app drawer but none of the apps that require root like titanium backup are working.. it says my device isn't rooted :/ help please
Click to expand...
Click to collapse
I am sorry, I by mistake provied the superSU 1.00 link
I changed and updated it superSU 1.64
Please Try again! using the new link from the description for step 4
vin4yak said:
Just a suggestion.. Instead of flashing a custom recovery, you could also just boot into the recovery using "fastboot boot recovery.img".. This way the stock recovery won't get changed for people who would like to keep it.
Click to expand...
Click to collapse
Could you confirm it?
I cannot test it till tuesday?
startracker said:
Guys check this too
We can flash this through stock recoveryhttp://forum.xda-developers.com/galaxy-s2/orig-development/30-10-2012-k-la-lp-t1103399
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Friendly warning about this Do NOT I repeat DO NOT flash this in recovery this is meant for the Galaxy S2 and is not only outdated by not compatible with our Motorola E. Only flash things intended for your device!
dpool94 said:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 1.00 - is installed!
Results provided on your XT1022 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
Click to expand...
Click to collapse
See ? Your device is not rooted. You must have missed something. Try again. Good luck.
Mrtoxicgamer10 said:
See ? Your device is not rooted. You must have missed something. Try again. Good luck.
Click to expand...
Click to collapse
Nah i fixed it. OP posted link of superSU v1.00 which is why my phone wasnt getting rooted. He fixed it. T
but not able to flash recovery.
it gives error -
target reported max download size of 299892736 bytes
error: cannot load 'recovery.img': No error
Click to expand...
Click to collapse
vivekbumb said:
but not able to flash recovery.
it gives error -
Click to expand...
Click to collapse
Did you flash this recovery image, TWRP 2.7.0.0 V1.2, using fastboot?:
vivekbumb said:
but not able to flash recovery.
it gives error -
Click to expand...
Click to collapse
You have copied the recovery.img file in some other folder, bring it to the same folder as of fastboot.exe
and it will work!
deej_roamer said:
You have copied the recovery.img file in some other folder, bring it to the same folder as of fastboot.exe
and it will work!
Click to expand...
Click to collapse
got it thanks.
I have rooted successfully Desire 626 (At&t) that's on Android Version 5.1, Steps on how to root below:
First Enabled "Unknown sources," Settings->Security->Tick the Check Box and Click yes.
Return to App Drawer, open File Manger and install "KingRoot-4. 1 .0.249.apk" when finish installing open the app
"Ignore any error message" and start root (Internet Connection required) once successfully rooted verify with "Root Checker" app
Now to replace "Kinguser" with "Supersu" install a "Terminal Emulator" app, Extract the file "KS.zip" and place the extracted folder on the root (main) of your Phone Storage, now open terminal emulator app and type the code below:
su
"allow root permission when asked"
sh /sdcard/mrw/root.sh
" after typing the above code ignore any errors til the process is complete, Supersu will open if successful
When asked to update binary select "normal" and reboot if asked.
Done.
N.B. I have package the files needed to do the root here : https://goo.gl/A7BIsD
N.B. Your Bootloader must be Unlocked !
Link to packaged files needed to do the root is broken. Could you please re-post?
Michaela888 said:
Link to packaged files needed to do the root is broken. Could you please re-post?
Click to expand...
Click to collapse
Sorry bout that....link has been Updated.
Thank you for the quick reply. I don't know what I'm doing wrong. I downloaded the zip file, installed KingRoot and opened the app, but the root keeps failing. I've tried multiple times and KingRoot fails at around 60% every time. I updated KingRoot and that failed, too. Based on your screenshots, it seems like we have the exact same phone with AT&T. Would really love to root if you have any suggestions. ("Unknown sources" is enabled and Bootloader is unlocked ) Thank you!
Michaela888 said:
Thank you for the quick reply. I don't know what I'm doing wrong. I downloaded the zip file, installed KingRoot and opened the app, but the root keeps failing. I've tried multiple times and KingRoot fails at around 60% every time. I updated KingRoot and that failed, too. Based on your screenshots, it seems like we have the exact same phone with AT&T. Would really love to root if you have any suggestions. ("Unknown sources" is enabled and Bootloader is unlocked ) Thank you!
Click to expand...
Click to collapse
use the kingroot app provided...if your bootloader is unlocked then it should work.
uninstall kingroot and restart your phone.. connect to WiFi or Data, reinstall kingroot open and try root again..if it fails try again at least 3 more times.
Worked perfect for me
Adrian Dennis said:
I have rooted successfully Desire 626 (At&t) that's on Android Version 5.1, Steps on how to root below:
First Enabled "Unknown sources," Settings->Security->Tick the Check Box and Click yes.
Return to App Drawer, open File Manger and install "KingRoot-4. 1 .0.249.apk" when finish installing open the app
"Ignore any error message" and start root (Internet Connection required) once successfully rooted verify with "Root Checker" app
Now to replace "Kinguser" with "Supersu" install a "Terminal Emulator" app, Extract the file "KS.zip" and place the extracted folder on the root (main) of your Phone Storage, now open terminal emulator app and type the code below:
su
"allow root permission when asked"
sh /sdcard/mrw/root.sh
" after typing the above code ignore any errors til the process is complete, Supersu will open if successful
When asked to update binary select "normal" and reboot if asked.
Done.
N.B. I have package the files needed to do the root here : https://goo.gl/A7BIsD
N.B. Your Bootloader must be Unlocked !
Click to expand...
Click to collapse
hey, i was helping a friend out and see kingroot dose work, but we want to get SU on his phone can you upload that KS.zip as the link dont work
thanks
Hey everyone! I seem to have found put together 3 methods of installing/bypassing the V4A App on android. These methods include:
Regular Installation, and 2 Error bypasses/fixes.
If you get the error "superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!", then you've come to the right place.
Requirements: ROOT, (maybe) TWRP (or anything you can flash the zip onto your phone with. With this tutorial I'll be using TWRP.)
If you don't have TWRP, here's the link to that \\ https://twrp.me/Devices/
Type in/select your device, click download, and flash it to your phone.
====================================================================================
Regular installation:
1.) Download V4A from Google Play Store \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) Open, and grant root permission.
3.) Install drivers, and reboot phone. DONE!
==================================================================================================
V4A SuperSU Manager Error:
1.) Download V4A from Google Play Store (the newest one) \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
Open it, grant permissions, click "install drivers" <- just get through the driver menu. This is a troubleshoot test. If it fails, keep going on with the tutorial. If not, You're A-Okay.
2.) Download V4A Flashable ZIP from here \\ https://drive.google.com/file/d/0By-5wpCgi7OHMjFZRU1PYXljbDQ/view
Drag and drop from your computer onto your phone in your "Downloads" folder.
3.) Open TWRP and click "Install" and navigate to your "Downloads" folder where you Installed the V4A Flashable ZIP (Viper4AndroidMM_v2.4.0.1.zip)
Install the ZIP in TWRP, and reboot.
4.) Open your apps/app menu, navigate to the new (it's an older version, but it's newly installed) V4A. It should be a purple logo instead of a blue logo. At this point in the tutorial, you should have both the Google Play Store APK, and the TWRP Flashed APK. Open the PURPLE V4A, and Install drivers now.
5.) Reboot phone, go to the NEW (blue logo) V4A, and install drivers on that one too.
The rest is clean-up. You may now delete the older version of V4A (purple logo).
========================================================
Bypass/fix #2, The SELinuxModeChanger issue:
1.) Download V4A (newest version) from \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) (Grant root access) Attempt to install drivers. If this succeeds, then Idk why you're still here.
3.) Download SELinuxModeChanger APK from \\ http://forum.xda-developers.com/devdb/project/dl/?id=12506
4.) Open it, grant root access, and click "Permissive".
5.) Re-boot phone, and open V4A when done.
6.) Install drivers!
Sources/credit go to:
https://forum.xda-developers.com/showthread.php?t=2524485
^ SELinuxModeChanger
https://forum.xda-developers.com/lg-g3/themes-apps/app-viper4android-v2-4-0-1-lg-g3-t3311403
^ Driver install failure/ Disc I/O error/"superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!" error
https://twrp.me/about/
^ Team Win
https://forum.xda-developers.com/member.php?u=7249915
^ Me, I contributed very small amounts, that's why I'm last (I guess I contributed some common sense .. ?)
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
masri1987 said:
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
Click to expand...
Click to collapse
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
zahidm said:
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
Click to expand...
Click to collapse
my head unit doesn't have vendor/etc or the audio effects configuration file....
Thanks
I had the Viper.apk from their website and the Google play version loaded also and I was getting the I/O error when trying to load the driver and the Google Play version didn't work at all. I did try to load SuperSU and busybox before attempting to load the driver again and it still didn't work. I don't know about permissive kernel, I'm running Resurrection ROM on a Rooted Note 3. The way I got this to work was to uninstalled the V4A Viper APK version that I had retrieved and loaded from their website. Next I booted into TWRP recovery and installed the V4A Flashable ZIP from the link that I found here. Next I ran the flashed version and granted SU permissions when asked during the install driver process. The driver finally loaded and bingo it works now.
Viper4android
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Banty448 said:
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Click to expand...
Click to collapse
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
zahidm said:
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
Click to expand...
Click to collapse
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Banty448 said:
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Click to expand...
Click to collapse
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
0
zahidm said:
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I already told u that I did it before opening the v4a
Banty448 said:
0
I already told u that I did it before opening the v4a
Click to expand...
Click to collapse
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
zahidm said:
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies?
Banty448 said:
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies[emoji106]
Click to expand...
Click to collapse
You didn't followed this guide?
https://forum.xda-developers.com/mo...od-viper-4-android-oreo-tested-t3700287/page2
Sent from my Nokia 5.1 Plus using Tapatalk
When I install drivers for ViPER4Android FX I get "Driver installed, please reboot your device." and when I reboot, I'm asked to install drivers again. Did anyone figure out how to successfully install these drivers? I saw fixed around the forum, but they don't seem to work for me.
My phone huawei p10 lite rom Resurrection Remix OS Beta 3!