As the title says, I have no write access in device root. I am running stock 5.1.1. SuperSu installed and working.
Would sure appreciate some help. Being half-rooted is not acceptable.
Thanks in advance
Problem is fixed. Bad BusyBox install it seems.
Hi, i have the same problem.
For example, im not able to make the tablet adfree with the rom-toolbox.
The romtoolbox errormessage is "can not remount read/write"
Use NextApp SDfix
The romtoolbox still reports "faild mount read/write"
The Micro-SD-Card is writeable.
(sorry for my english)
SeLinux is set as enforced. You need to set it to permissive. Google up tools and means for doing that. I often use paragon ntfs.
Tanks a lot!
I didnt found a tool, but i can Set it temporarly with a terminal emulator:
Su
Setenforce 0
Related
I am using superSU, and I need temporary unroot to try and fix my issue with google Wallet.
However, I can't find the option called "Temporary Unroot"! I have searched XDA and also done a general google search. the feature is mentioned all over the place, but nowhere does anybody explain where it is or how to access it.
In SuperSU, under settings, I found the option to enable or disable "superuser", but that's all. Is that it? Confused.
You can use an app called ota root keeper I believe to do what you want.
leebo said:
I am using superSU, and I need temporary unroot to try and fix my issue with google Wallet.
However, I can't find the option called "Temporary Unroot"! I have searched XDA and also done a general google search. the feature is mentioned all over the place, but nowhere does anybody explain where it is or how to access it.
In SuperSU, under settings, I found the option to enable or disable "superuser", but that's all. Is that it? Confused.
Click to expand...
Click to collapse
Yes, that's it.
Thanks Captain.
Since my post I've seemed to have screwed up my Build.prop file and now it won't boot. I hope that $10 from Google Wallet will be worth it! Ha.
Yes, Disable SuperUser is the correct option within the app. If you have already opened Walletbthen you will need to disable then reboot. Now in terms of the OTA Updating and trying to OTA you can use SuperSU Pro and enable before OTA but disable BEFORE BackUp within Recovery
Brought To You By TapTalk 2 Via LTevo
EPayne123 said:
Yes[...] Now in terms of the OTA Updating and trying to OTA you can use SuperSU Pro and enable before OTA but disable BEFORE BackUp within Recovery
Click to expand...
Click to collapse
Thank you, I was looking for this exact thing !
But I don't understand the last part, about backupenavke what? why pro ? and how strong is recommended a backup for a simple Ota From 2.2 to 2.3
??
leebo said:
I am using superSU, and I need temporary unroot to try and fix my issue with google Wallet.
However, I can't find the option called "Temporary Unroot"! I have searched XDA and also done a general google search. the feature is mentioned all over the place, but nowhere does anybody explain where it is or how to access it.
In SuperSU, under settings, I found the option to enable or disable "superuser", but that's all. Is that it? Confused.
Click to expand...
Click to collapse
if you or anybody else coming across this thread is interested in the technical details around how this works, the process is very simple with some background knowledge.
there are two elements in play when an application, such as Google Wallet, or any other application attempts to verify whether or not the device has root access. It can directly attempt to issue the "su" command see if it gets returned elevated privileges, or it can look for the su binary to be specifically located in /system/bin or /system/xbin.
based on the methods used to determine root access, you can "temporarily" unroot by moving/renaming root access away from the standard location.
example:
adb shell
su
mount -o remount,rw /system /system
mv /system/bin/su /system/bin/backupsu
mount -o remount,ro /system /system
exit
now root access has been moved and android apps requiring root or searching for root access won't be able to locate it. when you want to restore root access, follow these steps based on the example above:
adb shell
backupsu
mount -o remount,rw /system /system
mv /system/bin/backup /system/bin/su
mount -o remount,ro /system /system
exit
these steps will moved the su binary back to the standard location. hope that helps provide some insight and detail to the process!
EPayne123 said:
Yes, Disable SuperUser is the correct option within the app. If you have already opened Walletbthen you will need to disable then reboot. Now in terms of the OTA Updating and trying to OTA you can use SuperSU Pro and enable before OTA but disable BEFORE BackUp within Recovery
Brought To You By TapTalk 2 Via LTevo
Click to expand...
Click to collapse
^^^
Doesn't work on N7100 with or without rebooting after unchecking the box.
Hi there,
I have a Rockchip RK3188 Tablet with Android 4.2.2, which I need to root ON DEVICE. Actually, the device was already rooted (using a Laptop via the adb bridge), so I already have busybox installed and I have one of my own apps in /system/app. However I managed to delete the su program (yeah great!) and therefore don't have root access any more. I know I can easily root the device again if I connect it to my laptop again, but that is not possible, because the device is at my parent's place and I can't go over there any time soon.
Therefore I want to root the device just with an app. Actually I would only need to copy su to /system/xbin.
These are the things I already tried (without success):
Framaroot (doesn't work, because framaroot does not support Rockchip tablets)
Writing my own app, which contains su in the assets and using this su for temporary root
Using adb (on the device) for a local connection (adb connect localhost), because if I connect from my PC I automatically have root (doesn't work because Android 4.2.2 has increased security on adb)
Start telnetd via busybox and then execute my commands via nc (doesn't work, because I can't start telnetd in a way that it ends up with a root shell)
Any other ideas?
My last idea is, that I could maybe gain temporary root access with the app I already have in /system/app. Basically this would be similar to the Master Key Exploit, except that I do not have to fiddle around with the apk and instead install it normally. However I don't know how to continue from that point. I know, I have special permissions if I have an app in /system/app, but which permissions are that? And how can I use those permissions to make /system writeable (and copy my su file there)?
Thank you for your help,
Tobias
ToBe_HH said:
Hi there,
I have a Rockchip RK3188 Tablet with Android 4.2.2, which I need to root ON DEVICE. Actually, the device was already rooted (using a Laptop via the adb bridge), so I already have busybox installed and I have one of my own apps in /system/app. However I managed to delete the su program (yeah great!) and therefore don't have root access any more. I know I can easily root the device again if I connect it to my laptop again, but that is not possible, because the device is at my parent's place and I can't go over there any time soon.
Therefore I want to root the device just with an app. Actually I would only need to copy su to /system/xbin.
These are the things I already tried (without success):
Framaroot (doesn't work, because framaroot does not support Rockchip tablets)
Writing my own app, which contains su in the assets and using this su for temporary root
Using adb (on the device) for a local connection (adb connect localhost), because if I connect from my PC I automatically have root (doesn't work because Android 4.2.2 has increased security on adb)
Start telnetd via busybox and then execute my commands via nc (doesn't work, because I can't start telnetd in a way that it ends up with a root shell)
Any other ideas?
My last idea is, that I could maybe gain temporary root access with the app I already have in /system/app. Basically this would be similar to the Master Key Exploit, except that I do not have to fiddle around with the apk and instead install it normally. However I don't know how to continue from that point. I know, I have special permissions if I have an app in /system/app, but which permissions are that? And how can I use those permissions to make /system writeable (and copy my su file there)?
Thank you for your help,
Tobias
Click to expand...
Click to collapse
are you rooted check with root checker if yes(as you alredy said)
install super su or super user to gain root acces controls
but iam not sure from your question you are rooted or not or are you trying to root
P.S deleting super su will not unroot you
sangalaxy said:
are you rooted check with root checker if yes(as you alredy said)
install super su or super user to gain root acces controls
but iam not sure from your question you are rooted or not or are you trying to root
P.S deleting super su will not unroot you
Click to expand...
Click to collapse
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
ToBe_HH said:
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
Click to expand...
Click to collapse
I don't think you can root without any pc
If your phone has recovery just flash the root files :thumbup:
Sent from my Xperia Live with Walkman using xda app-developers app
ToBe_HH said:
Root checker says: "Sorry! This device does not have proper root access."
Right now, I am NOT rooted. So the device WAS rooted and then /system/xbin/su was deleted. Meaning: everything else is in place (SuperUser, Busybox, etc.) but I cannot execute anything as root, because I cannot switch the user to root (what su does). Although I am not really unrooted, I cannot do anything any more. So basically I would like to re-root my device.
The goal is to get fully rooted again.
Click to expand...
Click to collapse
Have you tried looking in /system/bin/su instead of /system/xbin/su
Hi,
I've been trying to root my Argos Bush MyTablet 10.1" running Android 4.4.4 for a while now, but all the rooting methods I have tried didn't work.
Framaroot (The exploit didn't work)
Key Root Master (I don't understand, since it's Indonesian, but some kind of error popped up.)
Root Master (Failed to root.)
iRoot (Failed to root.)
TowelRoot (device not supported. I tried using different modstrings, but they all turned my screen gray and rebooted my device.)
I have no access to a computer.
Argos ac101bu
Hi,
Really struggling to root this tablet. I have spent around 4 days trying.
I first altered the boot.img and set it up for adb.
ro secure = 0
allowmock location = 1
constant usb device = adb
ro debuggable = 1
This stops the "cant use adb root on production builds".
However, when I do adb root, it just says restarting adb as root.
It disconnects and then adb cant see the device, I have checked the drivers and its still there.
The device changes to "class for rk device", I tried lots of different drivers, but nothing seems to work after using "adb root".
I then also altered the system.img and made these changes.
ro factory location = 2 <-- which should use external SD (also added media,rw to permissions).
ro rkadb root = 1
ro secure = 0
I also manually installed SuperSU and set all the correct permssions. chown 0.0 and 06755 (in both xbin and bin).
SU works but SuperSU apk cant see the SU binary for some reason and doesnt show grant permission option. So its bassically useless.
Very frustrating, can anyone help?
EDIT:-
Got it rooted now, adb root still wont work. However I managed to manually root by following SuperSU v1.93 update script. Had to mount system.img in linux and edit that way.
Hi .. I also have got one of these... how did you manage to get it rooted???
Cheers
tron1275 said:
Hi .. I also have got one of these... how did you manage to get it rooted???
Cheers
Click to expand...
Click to collapse
Sorry for not answering sooner. I have the custom system image, if you still need it.
Its around 1.6gb, you have to flash it via rockchip flash tools. I also tweaked it some more and added init.d support.
I have a weird problem that I can't figure out....
I installed the rooted 5.1.1 from this thread, http://forum.xda-developers.com/xpe...3-23-4-0-546-completeguide-t3171219?nocache=1, to a rooted Z2.
Root checker shows as rooted...SuperSU and Busybox up to date, can get to # in terminal emulator. I have tried ES File Explorer, Root Explorer and Terminal emulator, and all fail. The only error message I get is from Terminal emulator which is mount: Operation not permitted.
Any ideas what might be wrong?
Thanks!
Sony ric protection is probably still running on your phone... easiest way to defeat it is to install nut's dual recovery, it disables ric on boot and works on locked bootloader:
http://forum.xda-developers.com/showthread.php?t=2261606
There is also a zip you can flash that only disables ric if you have your bootloader unlocked and a recovery in the kernel...can't remember the thread search if you need it.
Edit: SElinux might also make your system read only, if you face this problem either set nut's dual recovery .prop file to keep byeselinux always running, or install selinux mode changer app and disable it when you need.
You Sir, are a GOD to me!!!!
I already had dual recovery installed, but I updated it and problem solved!
Thank you so much for your very able assistance!
@nhpilot43 no problem, just remember something important too, don't install / update busybox from the playstore as it will break nut's dual recovery and everything that comes with it. xzdr has integrated busybox too, you don't need anything else
Will do and good to know!
Hello community,
I'm new in the forum, It's 2 days I'm fighting with this problem: I want to root my BlackPhone 2 using TWRP and SuperSU (I think that this is the only method that works with BP2, since KingoRoot and others are patched for security)
I flashed the recovery TWRP, then I tried the following SuperSU versions:
SR3-SuperSU-v2.79-2017...zip
BETA-SuperSU-v2.74-2.zip
SuperSU-v2.79-2016...zip
UPDATE-SuperSU-v2.79-2016...zip
None of them works, in TWRP all goes OK, no errors and no warnings, but then when I open SuperSU apk it says "There is no SU binary installed... ...If you just upgraded to Android 5.0".
This is really crazy because I'm running on Android 6.0.1 (Silent OS 3.0.7) and using Total Commander I can see /su directory.
Using a root checker app it says that my device is not rooted, but the SU binary is present and also the busybox one.
The Silent Circle's Security Center in their "Privacy Meter" app warns me "Security alert, active root access detected! ...."
For install TWRP I had to switch these things on in Developer Options: "OEM unlocking", "USB debugging", then I enabled installs from unknown sources by ADB and SD card.
Any help will be great, Thanks guys
EDIT: sorry for the Thread title, I can't modify it, it should be SuperSU not sudo su (too much linux)
But did you try sudo su? Install a terminal emulator and cd to the xbin directory. FYI, the SU directory is there by default afaik.
RAZERZDAHACKER said:
But did you try sudo su? Install a terminal emulator and cd to the xbin directory. FYI, the SU directory is there by default afaik.
Click to expand...
Click to collapse
Oh I didn't knew that the /su dir was there by default sorry. I downloaded the terminal emulator and "sudo" is not a valid command, when I type "su" it says nothing, and "which su" tells "/su/bin/su", but it does nothing apparently.
If it's not rooted at all how can Silent OS say "root access active detected"?
I just installed SuperSU zip via TWRP, there are other things to do in order to maintain root privileges?
PS: another RootChecker app detects that busybox is installed in /system/xbin/busybox with version 1.13.3, I don't know how that happened, busybox is installed by SuperSU?
Unfortunately they are in the same situation. But I admit that I did not install the TWRP permanently due to a possible bootloop phone. Has anyone found a solution to the root?
i have same problem i want unlock bootloader .............need help plz!!!
Koskha said:
Oh I didn't knew that the /su dir was there by default sorry. I downloaded the terminal emulator and "sudo" is not a valid command, when I type "su" it says nothing, and "which su" tells "/su/bin/su", but it does nothing apparently.
If it's not rooted at all how can Silent OS say "root access active detected"?
I just installed SuperSU zip via TWRP, there are other things to do in order to maintain root privileges?
PS: another RootChecker app detects that busybox is installed in /system/xbin/busybox with version 1.13.3, I don't know how that happened, busybox is installed by SuperSU?
Click to expand...
Click to collapse
After you flashed the su zip, did you get the superuser app?
Blackphone 2 bootloader
RAZERZDAHACKER said:
After you flashed the su zip, did you get the superuser app
phone not flash with any file.....devices lock ....need to bootloader unlock.
Click to expand...
Click to collapse
A litle guide to increase bp2 performance
https://forum.xda-developers.com/an...e-make-bp2-t3735815/post75218344#post75218344