Hi,
I have a ArmA53 based SetTopBox, which has a native root adb shell and build in Google Play. I installed supersu from Google Play and ran it, it told me the binary files need to be updated. I tried to update by using the first normal way, but I failed. And I cannot use the second way by using TWRP/CMW, cause the box does not have those recovery for it.
Is there any other way to update those binary files, or I have to manually update binary files by adb? If I have to, what are the steps to do it?
Thanks a lot.
I delete the old su form /system/xbin, and replace with the new one from armv7 of UPDATE-SuperSU-v2.76-20160630161323.zip.
[email protected]:/system/xbin # ll su
-rwsrwxr-x root root 75348 2008-02-29 03:33 su
This one above is the new su. But supersu said that the device was not rooted after replace with this new one.
[email protected]:/system/xbin # ll su
-rwsrwxr-x root root 75340 2008-08-01 20:00 su
This one above is the old su. After restore to the old one, root is back, but supersu said that the the binariy file was needed to update.
Related
Can i unroot if necessarry
Is there a way yet
Sent from my DROID3 using XDA App
If you don't install the su binary to /system/xbin all you have to do is reboot and the root access from adb is gone until you do the exploit again.
Wait so if i do the one click root can i unroot that
Sent from my DROID3 using XDA App
You would have to delete the su binary from /system/xbin and uninstall superuser.apk for it to be considered unrooted.
wat if you factory reset it doesnt unroot
esp if you install superuser from the market, its in /data vs. /system right?
but that would leave /xbin intact right? so youd kinda be stuck rooted rofl idk
whoopsiedaisy said:
wat if you factory reset it doesnt unroot
esp if you install superuser from the market, its in /data vs. /system right?
but that would leave /xbin intact right? so youd kinda be stuck rooted rofl idk
Click to expand...
Click to collapse
I'm not sure if a factory reset leave xbin intact or not but even if it did you could just adb in, use the exploit and remove su manually.
Just keep in mind...SuperUser.apk is not root. You can install that on a non-rooted phone, it just doesn't do anything.
Root is su, having (s)uper(u)ser access to the system. SuperUser.apk is just your (you the user) control over what is granted su rights. Without the SuperUser.apk, anything and everything that wanted superusers permissions would have it, definitely something you don't want.
I'm not sure a factory reset would remove su from /system/xbin but it would remove SuperUser.apk from /data/app. This would mean you'd have no control over what apps would want to take superuser permissions and access your filesystem.
While you have superuser permissions...just delete the /system/xbin/su and reboot.
Root also doesn't prevent OTA updates.....though you will probably lose root after an OTA update and have to redo the exploit.
This game require unroot and was said to checks for:
-- Superuser.apk file (do a "find . -n Superuser.apk" from adb shell) in /system/app
-- the su file
Most of the method recommended temp unroot with Super User app.
but my default superuser doesn't have the function mentioned above so i downloaded another Super User app.
I tried temp unroot and rename the Superuser.apk but it doesn't work either.
Anyone out there can help with this problem?
http://forum.xda-developers.com/showthread.php?t=2265618
you need to read the Unlocking Bootloader section
Besides the SU Binary In /system/xbin, what else do I need for SuperSU to function?
It keeps saying the SU binary is not installed
SpikeyPsyche said:
Besides the SU Binary In /system/xbin, what else do I need for SuperSU to function?
It keeps saying the SU binary is not installed
Click to expand...
Click to collapse
did you download the su app from the playstore
jerrycoffman45 said:
did you download the su app from the playstore
Click to expand...
Click to collapse
I was rooted on MI9 using the DLV method. I updated to NC2, and the SU binary installed by SuperSU persisted in the /system/xbin/ directory, but the SuperSU app says it is not installed. I wanted to know what, if anything, I can do with the SU binary in place to get the SuperSU app up and running again.
SpikeyPsyche said:
I was rooted on MI9 using the DLV method. I updated to NC2, and the SU binary installed by SuperSU persisted in the /system/xbin/ directory, but the SuperSU app says it is not installed. I wanted to know what, if anything, I can do with the SU binary in place to get the SuperSU app up and running again.
Click to expand...
Click to collapse
i am not sure there is anything you can do till we get a root exploit for nc2
yeah, i too have still have su in system/xbin on NC2, but root isn't working. it's weird, but as stated above, we probably need a new exploit or something
Are the permissions correct on the su binary? Might as well check that before we start despairing.
DrAzzy said:
Are the permissions correct on the su binary? Might as well check that before we start despairing.
Click to expand...
Click to collapse
Yeah, I'm not allowed to set the permissions in Root Explorer without root, but it does show a preview and the permissions do match all the other files in xbin
YrrchSebor said:
Yeah, I'm not allowed to set the permissions in Root Explorer without root, but it does show a preview and the permissions do match all the other files in xbin
Click to expand...
Click to collapse
Same here, permissions match all the other binaries in xbin.
SpikeyPsyche said:
Same here, permissions match all the other binaries in xbin.
Click to expand...
Click to collapse
I wonder what this means. I figure we dont need a new kind of su binary, but there must be something in the new software that blocks it from working?
I hope it isn't in the kernel. I had a Sony device last, and we needed an ever so slightly modified kernel in order to get full root on 4.3. But I doubt if we will ever be able to flash kernels.
YrrchSebor said:
I wonder what this means. I figure we dont need a new kind of su binary, but there must be something in the new software that blocks it from working?
I hope it isn't in the kernel. I had a Sony device last, and we needed an ever so slightly modified kernel in order to get full root on 4.3. But I doubt if we will ever be able to flash kernels.
Click to expand...
Click to collapse
I'm guessing there is some setting or permission that needs to be changed.
In my 5th gen fire hd7 I tried to root using rootjunky supertool.
I don't know what went wrong during the process but the SuperSU app always says su binary needs to be updated and when I select normal it fails. I'm very much disappointed and annoyed and decided to unroot.I tried the universal unroot app but it fails .nRoot checker says root access is not proper and root explorer can't edit root files.
Is there any way to unroot without updating su binary?
Hi, I need your help
I have a MK903V Android TV HDMI Stick (Android 4.4.2, API Level 19). I need it to run apps requiring root without prompting for root access - which SuperSU allows.
The stick has a root shell via adb and comes with a su binary ("su --help" says "SuperSU v1.99 - Copyright (C) 2012-2014 - Chainfire"). I cannot boot a recovery like TWRP (I guess).
I've tried:
- install and run superuser.apk v1.99, says it must update su binary, fails updating su binary (normal mode)
- install and run superuser.apk v2.79, says it must update su binary, fails updating su binary (normal mode)
- install and run towelroot, says it got root, install superuser.apk (v2.79), says it must update su binary, fails updating su binary (normal mode)
- rooting via Kingo Root (PC), works including its su prompt on root apps (like the bloatware it installs), running superuser.apk, says it must update su binary, fails updating su binary (normal mode) (never prompted for root)
I found articles saying you could run the installer script from the update.zip, which is used to install SuperSU from recovery, in an adb root shell if you adapt it... I'm not so much into unix stuff / shell, so I'm pretty sure I won't do that on my own. Moving two or three files to the devices and setting chmod/chown is not a problem, but the script looks way more complicated...
Is there actually a version of the script that can run from a adb root shell?
Is there any other way I can get SuperSU on a device I already have root access to?!? Didn't think that could be so complicated...
Thx
P.S. I'd also take a su binary that just grants all access and doesn't even come with a gui
upgrade mk903v to android 5 or higher
How do i upgrade my mk903v stick to a higher version of Android. It comes with 4.4.2 kit kat. Any help would be appreciated...
Thanks
EDIT: SKIP THIS - READ NEXT
Okay, I finally rooted the device...
- Installed KingRoot APK (v5.0.4) from https://kingroot.net/
- Ran KingRoot which did its suspicious magic on the device for more than 15min
- Installed SuperSU and granted it root
- Ran the root.sh script attached which basically kills and removes KingRoot and lets SuperSu replace su binary
- Ran SuperSU again and successfully updated su binary
It is the only solution I found so far...
Sometimes the web just confuses me...
Found this:
http://freaktab.com/forum/tv-player-support/rk3288-devices/17987-new-3288-ez-root-tool
Simple and clean "update.zip" [MD5:7a2755fd5ebe8a2928fc01a4ab0cbabb]
Copy to internal or external sdcard and just reboot or wait for the system popup that says that a new firmware update was found. Update will be applied and device got proper (but old) SuperSU installed.
After that, you may just install the latest SuperSU. (is there a reason why the latest APK is not available on http://www.supersu.com/download#apk ??)
[email protected] said:
How do i upgrade my mk903v stick to a higher version of Android. It comes with 4.4.2 kit kat. Any help would be appreciated...
Thanks
Click to expand...
Click to collapse
Hello,
Did you solution for this?