Installed su, busybody and SuperSU.... What next? - MTCD Android Head Units Q&A

Hi all. I've got a PX3 7.1.2 MTCD headunit and I've managed to copy su, busybody and SuperSU.apk into /system. SuperSU is in /app however what is su and busybox meant to be in? I've copied them into both /bin but also /xbin as I don't know which ? Also SuperSU says it can't update the binary - what have I missed?
Help please!
Seeing as I'm quite new to all this I'm rather pleased I've got this far!
Thanks.

Related

[Q] Unroot / Return to Stock Recovery for Nexus S 4G (Sprint)

Gang, I've searched and couldn't find. I rooted the Sprint Nexus S 4G and installed CW recovery.
Would some one please be kind enough to point me on how to unroot and return to stock recovery for a return.
Thank you!
Why do you want to return it?
dmora01 said:
Why do you want to return it?
Click to expand...
Click to collapse
Exchanging for another, I appear to have a defective screen which flickers when phone is shaken.
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
r80ies said:
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
Click to expand...
Click to collapse
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
What about the custom CWM recovery?
oldblue910 said:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
a2k said:
What about the custom CWM recovery?
Click to expand...
Click to collapse
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
oldblue910 said:
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Many thanks!!!!
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
a2k said:
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
Click to expand...
Click to collapse
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
oldblue910 said:
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
Click to expand...
Click to collapse
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
a2k said:
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
Click to expand...
Click to collapse
OK check /system/bin then. Is BusyBox in there?
oldblue910 said:
OK check /system/bin then. Is BusyBox in there?
Click to expand...
Click to collapse
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
a2k said:
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
Click to expand...
Click to collapse
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
oldblue910 said:
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
Click to expand...
Click to collapse
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
a2k said:
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
Click to expand...
Click to collapse
Oh no wonder! You're all set then. BusyBox is located within Titanium Backup's data folder. You don't need to worry. BusyBox will go away when you uninstall Titanium. So just follow my updated instructions and you're good. Let me know if you have any problems. Make sure you have a nandroid backup of your ROM before you delete root, just in case! You can never be too careful!
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
spdwiz18 said:
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
Click to expand...
Click to collapse
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
oldblue910 said:
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
Click to expand...
Click to collapse
Nope .... no such file. I even did a search for it with root explorer and it does not come up. If worse come to worse ill pull it from someone's Tom just so I have it on my phone. But I know I did not delete it.
Sent from my Nexus S 4G using XDA Premium App
That is very strange indeed. I wonder if Google didn't install it on the Nexus S 4G. Can any other NS4G owners verify if /etc/install-recovery.sh exists on your phone?

[Q] can i delete /system/xbin folder?

hi,
anyone who has galaxy nexus and haven't modified anything, can you please check and see if you have /system/xbin folder?
i installed some program called busybox by accident and i think it created /system/xbin folder.
so i uninstalled the app but the folder is still there..
so i'm wondering if it was there in the first place..
can i delete the whole folder?
right now i have 3 files in that folder : busybox, dexdump, su.
anyone?
dlxowhd said:
hi,
can i delete the whole folder?
right now i have 3 files in that folder : busybox, dexdump, su.
Click to expand...
Click to collapse
I would not delete the xbin directory, it is a system directory included with the operating system.
"dexdump" is Dalvik disassembler (usefule for developers).
"su" is superuser, so if you delete that you will no longer have root.
"busybox" is a set of useful Linux utilities that are essential when you have root privileges.
So, like I said I would leave it, busybox was not the one who installed that directory.

Busybox for HTC 820

Here everyone working Busybox for HTC 820
Download it and Flash it through Custom Recovery. (TWRP or CWM)
Credit Goes to [email protected]
will it run on rooted htc d820u lillipop device?
Now in marshmallow after rooting you can use Busybox from Play Store. SuperSU in version 2.65 is enabling file system overlay and you can modify /system/xbin dir.
Wysłano z Tapatalk / Sent with Tapatalk
QkiZMR said:
Now in marshmallow after rooting you can use Busybox from Play Store. SuperSU in version 2.65 is enabling file system overlay and you can modify /system/xbin dir.
Wysłano z Tapatalk / Sent with Tapatalk
Click to expand...
Click to collapse
Latest SuperSU uses system-less root and I don't think you can write to /system/xbin from MM (in 820).
Install busybox from recovery...
Read what I wrote earlier. SuperSU creates layer on /system/xbin path. You can write files in this path but changes really is saved in /su/xbin_bind. System path /system/xbin is not really modified. Read >> http://forum.xda-developers.com/showpost.php?p=64161125
chainfire said:
A poor man's overlay is used on /system/xbin. We are creating a copy of /system/xbin in /su/xbin_bind, adding a symlink to /su/bin/su there, then mounting the entire thing on top of the original /system/xbin. This is likely to fix some compatibility issues with some apps, without actually modifying /system
Click to expand...
Click to collapse
QkiZMR said:
... SuperSU creates layer on /system/xbin path. You can write files in this path but changes really is saved in /su/xbin_bind ....
Click to expand...
Click to collapse
My friend, I suppose there is a misinterpretation of chainfire's concept. The idea is, transparently placing files in /system BUT without modifying the actual partition. Pls take a look once again...
"We are creating a copy of /system/xbin in /su/xbin_bind, adding a symlink to /su/bin/su there, then mounting the entire thing on top of the original /system/xbin"
That I was said I think that you misinterpretation my words. Word 'layer' makes big diffrence
newer/alternate versions (flashable) can be found here and here. they both work well for me.
I have rooted my htc 820pi kitkat. Now I want to install custom recovery. But, not finding any way. Can you please help me.
Xposed for HTC 820pi
I Dragon said:
Here everyone working Busybox for HTC 820
Download it and Flash it through Custom Recovery. (TWRP or CWM)
Credit Goes to [email protected]
Click to expand...
Click to collapse
Hello dear, I am a HTC 820pi user running in Android 4.4.2. I have rooted my phone but couldn't install any custom recovery. Is it possible to install xposed framework in my rooted phone? Mind it, no custom recovery is installed in my phone!!!!

su binary question (no troubleshooting)

Hello, i read a lot on google about root but didn't find the answears that i'm looking for, hope some of you can explain.
I want to access the /system of my phone to change hosts file for example.
I know i need root access for that of course but that is my question.
What is neccessary for that, is placing the su binary in
/system/xbin/su
enough to access /system?
do i have then root access? or i need busybox, superuser.apk and some commands also?
thank you guys
if you have su already pushed into system partition means you got root access but if you dont have supersu installed you can't manage permissions that an application would request
so it is just the *su binary* necessery without chmod or something else? (theoretic)

Can I flash supersu over kingo root?

Trying remove kingo root I tryed removeing root and kingo app stay's behind and then im stuck with the app. Then I looked up how to remove apk and files all i found was go to xbin delete the su file and apk file found the su file no kingo apk file so had other idea could I install supersu I installed it off Google play and allow root tryed installing and it said fail because my su binary is occupied or something like that now could I flash it useing twrp safety ?
Androidnomad26 said:
Trying remove kingo root I tryed removeing root and kingo app stay's behind and then im stuck with the app. Then I looked up how to remove apk and files all i found was go to xbin delete the su file and apk file found the su file no kingo apk file so had other idea could I install supersu I installed it off Google play and allow root tryed installing and it said fail because my su binary is occupied or something like that now could I flash it useing twrp safety ?
Click to expand...
Click to collapse
1) https://www.xda-developers.com/xda-external-link/guide-to-replace-kingoroot-with-supersu/
2) https://forum.xda-developers.com/general/general/solved-replace-kinguser-supersu-binary-t3324525
Follow either instructions on your own accord. I will not be responsible for any damaged caused.
Cheers

Categories

Resources