Hi, I have serious problem with root access. It does not matter which version of SuperSU (latest or older) if it is built-in Superuser or if I flash it via cwm or philz with fixing supersu or without that or TWRP. Still the same result (for example Titanium Backup), shortened error message is:
"I could not acquire root privilegies. This attempt was made using the "/system/xbin/su" command".
When I open the SuperSU app, everything is just fine, no error message explaining failure in installing SuperSU script.
What should I do to gain (how to call it) full root access? Thanks for any help.
Related
i have an htc desire running fryo
i have rooted it using unrevoked3
i can see and have used superuser icon on phone
but still titanium backup pro cant recognize whether my phone is rooted or not.busybox not able to install even when clicking on problems in titanium(thru net as well as manually)
i need to delete stock apps from phone,so i tried using adb shell on win7 as well as android terminal emulator on phone.either ways i get directory not found or read-only file system error
cant get to remove these apps through root explorer as well
i tried installing clockworkrecovery for nandroid backup but there are two wayts according to:
wiki link
first method(thru rom manager) is not working as not able to download
second method requires alpharev which inturn requires a safety nandroid backup(which requires clockwork recovery mod)
is there any other method for installing clockwork recovery method??
There is only 1 way to permanently flash a recovery and you need to be s-off to do it. You have to use the fastboot method or use the android flash utility. To remove system apps you have to be s-off anyway so there's no avoiding it.
As I was saying, rom manager temporarily fake flashes the recovery but for the desire its the old recovery 2.5.0.7.
Sent from CM7
Hi folks,
I've follow ParotZ's Recovery Installer process to root and am having SuperSu issues.
I install recovery (option 5), then reboot to recovery (option 0), system > reboot > swipe to install > and then once it loads I'm greeted with
"no su binary installed and supersu cannot install it"
I've put UPDATE-SuperSU-v2.16 on internal storage and tried earlier versions and flashed, with the same result.
The SuperSu app is installed. I attempted a manual update on the Play store, but the 'no su binary' message is still there.
I can't uninstall supersu, either with an uninstaller app or through Play (it does not show 'uninstall', just shows 'open')
It persisted after I factory reset and wiped (not through recovery).
Any help? Keen to get on Cyanogen.
My phone specs.
Model
Oppo x9076
ColorOS
v2.0.0i
Android version
4.4.2
Build number
FIND7WX_12_141017
Kernel
3.4.0-S3753
Baseband
Q_V1_P14
I've seen others with the question, but none with answers for the Find 7 :/
Cheers!!
solved
Hi folks,
I've solved the issue. I could not root using that method because I had updated the OS and there was some form of conflict that stuffed the SuperSu binary.
So I downgraded back to stock (the earlier ColorOS) and reapplied the root process.
For those with the same issue follow these steps http://theunlockr.com/2014/08/22/how-to-unroot-the-oppo-find-7-video/
Then reattempt the root.
Note that step 6. "Using the volume buttons to navigate and the power button to select the option you want, select Wipe Data and Cache." will erase the OS you just copied over, so do this prior to copying the OS or you'll just need to do it again.
When the OS loads and you come to the update SuperSu step, my Play store wouldn't load due to I think a delay in the accept terms of use popup. So I used the TWRP method and it worked fine.
Good luck.
Darren.
Hello,
I am new in this forum, but I have a question.
My device is HTC Desire 816 with unlocked bootloader and CWM recovery (I followed the manual in this forum)
After I booted into CWM I installed SuperSU binaries (at theory) without errors. I clicked reboot now. It asked me if I want to root yes or no. I chose yes. But however, when I booted into the device and started SuperSU (after an update from the Google Play Store) it said that I don't have binaries.
Please help.
(Also, my Android version is 5.0.1)
VelkovJR said:
Hello,
I am new in this forum, but I have a question.
My device is HTC Desire 816 with unlocked bootloader and CWM recovery (I followed the manual in this forum)
After I booted into CWM I installed SuperSU binaries (at theory) without errors. I clicked reboot now. It asked me if I want to root yes or no. I chose yes. But however, when I booted into the device and started SuperSU (after an update from the Google Play Store) it said that I don't have binaries.
Please help.
(Also, my Android version is 5.0.1)
Click to expand...
Click to collapse
Try flashing this version of SuperSu.
It worked!
It worked, thanks a lot! But now I have another problem. I am trying to open wp-mod.ko to get access to the system folder. But, however when I do the command
su
insmod /storage/(something)/wp-mod.ko
It says insmod: Can't open wp-mod.ko
I have tried many types of file path but no result. I have copied the file both on my internal memory and in my SD card. Please help.
P.S. I am using Terminal Emulator by Jack Palevich
i just rooted my s6, and i DO have root access, but when i try to open superuser (that was installed along with the root) it says "superuser binary out of date" and asks how i want to update it. The only options it gives me is Cancel and Recovery. If i choose recovery it boots into recovery then does nothing. I found the updated version of superuser online and transeferred it to my phone and flashed it thorug TWRP. Still says it. I tried installing supersu and when i open it it says "su binary is occupied" so i used an uninstaller to uninstall superuser, and supersu still says binary is occupied. So i reinstalled superuser but now i dont know what else to do to get my superuser app to work? Any ideas? TIA
I don't know how comfortable you would feel about this, but a lot of us have moved on to using Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
There are two parts, Magisk itself and the Magisk Manager.
Recommended path is to return to Stock, install TWRP via Odin but don't reboot. Instead shut down, reboot directly to Recovery and flash Magisk. Usually on first boot you will get a prompt to install Magisk Manager, do that and you are set.
Before you do that, take some time to read about Magisk. It is similiar to SusperSu, but allows you to conceal that you are rooted. (A feature that you enable within the manager.) I find it a great improvement.
ohhhh. i get it now. the method i used to root was with magisk. it prompted me to install it when it booted up so i did but didnt really go look at the magisk manager. i didnt realize that was what handles the su. thats why it says its occupied
tried to replace SuperSU with Magisk via TWRP.
Magisk won't take by itself.
Removed SuperSU. Tried again. Still NG.
"adb reboot recovery" back to TWRP and flashed SuperSU. I have root back, though I don't see SuperSU in the app drawer.
The info to install Magisk leave a bit to be desired.
"install manually" what does that mean?
Remove root (SuperSU) seems to prevent one from installing Magisk, though I did "adb reboot recovery" to get the re-install of SuperSU done.
In the long run, I want to update our other H811 to 20x from 20q. Thats' what started me down this track.
Any input?
Did Magusk Zip Got Trough without any issues in TWRP?
Did you have the magisk App in drawer after flashing Magisk?
Magisk manager is sometimes an older version, so you have to go to magisk manager (app) open ist and click on upgrade or install upgrade.
sometimes my device needed 2installations. one in twrp an another in MAgisk app. but both were v16.0 zip.
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
metropical said:
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
Click to expand...
Click to collapse
You should Always search the TWRP errors you have, that gives you more info.
Error 1 means on your system partition is not enough space anymore, so delete or Freeze some bloatware/apps and it should go trough.
boot.IMG files are containt in KDZ (firmware files).
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
uweork said:
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
Click to expand...
Click to collapse
went and posted in digeridoohan original thread.
https://forum.xda-developers.com/showpost.php?p=76980632&postcount=25580
all is well.. thanks very for the help. and I installed the Xposed module that works with TextAid and MM.
also your link won't doesn't seem to work. I've found that a I've had to use shortened links of late or they don't fire on XDA.
Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?