hi, I downloaded botbrew, supersu granted it super access. It says something like "extract archive: cannot create symlink from ./system/bin/botbrew to /data/botbrew/bin/borbrew read-only file system.."
To reinstall I tried choose uninstall in the play store, and on phone, then install but it just starts back up without reinstalling. So didn't really uninstall. And also I can't see any terminal with it. I went into android terminal but it can't see any command like apt-get I see about adding a repository and searching for packages.. what repository to add to use ssh and nmap and get apt-get? (i'd like to do apt-get install dropbear)
I don't recall if that was when trying botbrew root or botbrew basil.
I have gone to the android terminal and run 'botbrew' , I see the $PATH variable change to include botbrew/bin so I know i'm in. but I don't have apt-get (which I want)
I had installed botbrew root beforehand, then realised it didn't have apt-get, so I went for botbrew basil experimental.
Botbrew basil experimental is showing nothing in the 'installed' tab, At one point one tab said something like dpkg or something was pending, but something was locked and it couldn't continue with that. So I closed some other programs and turned my phone off and on, and went back into Botbrew but now I see nothing pending.
I just got this message
E: Couldn't create temporary file to work with /var/lib/apt/lists/repo.botbrew.com_basil_main_Release - mkstemp (13: Permission denied)
E: The package lists or status file could not be parsed or opened
E: No packages found
I suppose perhaps that message might be from apt-get.. operating within the botbrew gui..
It's not surprising that it can't write to /var , as there is no /var directory on my phone. I tried cd /var, also as root.. from a terminal but nope, that directory doesn't exist.
I considered posting to http://forum.xda-developers.com/showpost.php?p=26261600&postcount=119 as that looks like it might be a dedicated thread. I don't know if i'm too newby to post in that section, but anyhow I can't in that section as one needs 10 posts to.
TIA
Related
Hello all,
I recently put backtrack 5 on my atrix and was really enjoying having a pentesting suite on my mobile phone.
I used the method and image from this thread
http://forum.xda-developers.com/showthread.php?t=1074169&page=26
Everything worked perfectly for a while until...
I updated to 4.5.91 GB OTA and now it no longer works.
When attempting to start BT I get this
Code:
#startbt
losetup:applet not found
mount: applet not found
mount :no such file or directory
mount :no such file or directory
mount :no such file or directory
net.ipv4.ip_forward=1
Setting /etc/resolv.conf to Google open DNS 8.8.8.8 and 8.8.8.4
startbt cannot create /data/local/bt/etc/resolve.conf: directory non-existent
startbt cannot create /data/local/bt/etc/resolve.conf: directory non-existent
startby cannot create /data/local/bt/etc/hosts directory non-existent
It looks to me like the backtrack image is not getting mounted, thus the directories cannot be found.
Can someone please explain to me what in the world happened, and perhaps how I can go about fixing this?
I am rooted and do have busybox installed. Both are confirmed through the rootcheck app.
Also I apologize for not posting this in the thread in the thread I mentioned before, but post count prevents me from posting in dev forums.
If someone successfully solves my issue I would be glad to donate a a few bucks to the dev of their choice.
EDIT***
Nevermind It is fixed. Just in case others are having similar issues I will explain what was wrong...
After I updated to GB and re-rooted, I ran rootcheck to verify that I had root access. One thing I noticed is that my rootcheck claimed I didnt have busybox installed. So I reinstalled it. Like a dummy I installed it /system/xbin instead of /system/bin. Simply installing it to the correct place fixed things. I feel silly. Mods feel free to delete this.
So here's the deal. I'm getting in to some dirty work with Ninjamorph, but after finishing a project, I know it does not resign an .apk. When I try to put the .apk I've modded through Signapktic it spits out the error: "which: applet not found".
Typing which into the terminal emulator yields the same result. Apparently I'm a serious noob when it come to androids, because Busybox is installed and I thought which would have been added to the commands at that point. How do I get which to work? Because being able to do all this modding on the phone is ridiculously convenient.
So, I failed, and didn't realize there was a new busybox version available. which is now working on my phone.
Signapktic, however, does nothing. I click start, it says it's been given su permissions, and then says finished (the terminal log is empty).
So I'm taking a free computer science/programming class (edx.org offered by MIT and Harvard, check it out, even give you the textbook for free) and I'm trying to install the programming package they recommend by Enthough, I downloaded the .sh file and tried to install it (bash xxx.sh) using WebTop2SD with WebTopScripts with the packages fixed, then tried Ubuntop with no luck, I keep getting "Cannot create symlink to "xxxx" Operation not permitted" for everything when trying to install it on either.
I remember before using Webtop2sd I had the webtopmod and all that crap (tried it first, kept messing up and I figured they all did the same thing since they're all by Sogarth) even had a username instead of adas and installed some linux chemistry programs, I still have all that too but webtop2sd wouldn't install the ubuntu.sh (I made a backup cause I really want to get that webtop back up, had programs I can't get anymore).
Would something like Gentop work or is it just a limitation from android?
thanks
EDIt: moved it to /osh/home/adas and then did sudo bash on it, getting "cannot execute binary file" now, someone saud chmod u+x xxx.sh, but still getting same error
Try just sudo -i. If you end up in a root shell, that's good. If not, your sudo might have issues.
Hi,
I tried to upgrade the busybox with different manner (busybox, busybox installer, manual installation from xda), but no one works properly.
Each time i broke the original Archos busibox, so i lose the adb shell.
Can someone explain to me the good way to upgrade the busybox?
Thanks.
SirOch
Hi,
Nobody to explain a clean upgrade of the busybox?
cheers
SirOch said:
Hi,
Nobody to explain a clean upgrade of the busybox?
cheers
Click to expand...
Click to collapse
Google? also XDA has a great search feature have you tried that? :silly: Any particular reason why you want/need to upgrade busybox?
Hi,
As i said, i tried the different busybox installers and the installation was ok, but i each time, i lost the shell from adb.
That's just my problem.
So i just want to understand why the upgrade of the busybox broke the original archos busybox?
Moreover some application need to have other busybox installed.
Regards.
David
SirOch said:
Hi,
As i said, i tried the different busybox installers and the installation was ok, but i each time, i lost the shell from adb.
That's just my problem.
So i just want to understand why the upgrade of the busybox broke the original archos busybox?
Moreover some application need to have other busybox installed.
Regards.
David
Click to expand...
Click to collapse
Ahhh right, the quest for knowledge Your problem is as much to do with adb ( /sbin/adbd to be precise ) as it is to do with busybox, firstly you've probably wiped out the symlinks in /bin, especially /bin/sh which is the location that adbd on archos looks to run the when you do adb shell from your desktop. This is not the default location which just about every other android OEM adheares ,that is /system/bin/sh.
If you are going to upgrade the archos busybox be aware that a large number of symlinks back to /bin/busybox exist not only in /bin but also in /usr/bin /usr/sbin
Archos for reasons I still haven't fathomed, really went to town on restructuring and customized Android on the platform level.
A little tip if you've got more question, to save you bumping threads , which really does upset some folks round here... you'll probably get more more if you add more details, such as error messages etc. Saying " i lost the shell from adb." doesn't really help anyone who might be able to offer assistance. There about 10 different ways adb can fail to connect, Did the device disappear from the list or report as offline. or even come up with the message "- exec '/bin/sh' failed: No such file or directory (2) -".??
Hopefully that's helped.
Hi SirOrch,
i don't know why you loose your adb shell, but concerning busybox... the things on Archos tablets are like this:
Basically on a non rooted device we got a squashfs image mounted read only.
This image contains the stock busybox compiled by Archos (sharing system's uclibc) with limited functionality,
but containing enough tools to handle the daily job.
The path to this busybox is "hard-coded" as well. It's location is /bin which is the second entry in the path environment.
You might check that by typing printenv in your console.
The first entry should be /data/local/bin on your device.
So if you like to replace stock busybox with an advanced one, you should make sure that it will be installed to /data/local/bin.
Often there's no need to use all this apk Android Market stuff to get a proper busybox installation.
Sometimes it's little better to really understand what's happening under the hood.
Most busybox app's are statically linked, because with a static binary you don't have to take care of the device's libc or uclibc.
So you might easily extract on of the apk's or get one from xda-developers.
There are many floating around in the end.
If got one push it to /data/local/bin with adb.
You might need softlinks in this directory as well. This could be done by hand as well.
Anyway if you are a lazy person, who doesn't care about what's happening, go to the market install busybox.
Then check at /data/local/bin if it is there.
If it got installed elsewhere, some commands will still use stock busybox.
Extended commands might then use the installed one.
So check it out...
EDIT:
... aaaargh again simultaneous posting.
scholbert
Hi gentlemen,
Thanks for your help and sorry to forget to give you the error message i had:
the message was : - exec '/bin/sh' failed: No such file or directory (2) -
After investigation i found my mistake:
- In manual mode, i forget to change the ownership of busybox to root in /bin.
- when i tried to use any application from the market, the busybox was well updated in /system/xbin but the application also delete the busybox in /bin and don't change the symlinks in /bin. That's explain why adb shell won't work.
Regards.
SirOch
I thought I'd post this...even though I'm a noob...so that others can benefit if possible. If you're using the JRummy BusyBox installer, please be careful with the Advanced Install option. Here's why:
After rooting my phone I installed JRummy's BusyBox installer. First, after checking busybox.net for the latest stable install version, I did a full install without the symlink apps option selected. Then I did another full install with the symlink apps option checked. Finally, after reading through the entire list of available commands and what they did, I decided to do an advanced install. I selected "Remove Symlinks" for each of the busybox commands I wanted NOT to have available in Terminal Emulator.
Soon after the advanced installation, I noticed that Terminal Emulator wasn't working. Then I noticed that my WiFi connection wasn't working...specifically the part in which the phone attempts to lease an address using DHCP. After emailing the developer with my issue, I tried to re-install BusyBox manually based on a link he included in the reply. I could push the file to the phone using 'adb push' but when I tried to open a shell to run the install commands, I would get the following error: exec '/system/bin/sh' failed: No such file or directory (2) . Long story short, I had to re-flash the phone using Odin to fix it.
In the AFWall+ logs, around the time I ran the Advanced Install, there were a bunch of entries like this: ld_library_path=/vendor/lib:/system/lib busybox rm /system/xbin/strings exit. There may have been a -s after the 'rm' command and before the directory but I'm not completely sure. After I flashed the phone with Odin, I opened Root Explorer and took a look at the files under /system/bin/. I noticed that the commands that can be run without installing busybox...like ls, or ifconfig...were linked to 'toolbox'. /system/bin/sh was linked to mksh.
After more research and reading, I'm about 90% sure what happened. Here's an excerpt from the email I sent to the developer:
<snip>
Basically, the "Remove Symlinks" option in your app does either one of two things:
It removes the directories entirely
It removes the symlinks to busybox, but doesn't restore the original symlinks that were present before busybox was installed.
<snip>
So if you're using this particular installer, please be careful with the Advanced Option.
Please help
MonaLisaOverdrive said:
I thought I'd post this...even though I'm a noob...so that others can benefit if possible. If you're using the JRummy BusyBox installer, please be careful with the Advanced Install option. Here's why:
After rooting my phone I installed JRummy's BusyBox installer. First, after checking busybox.net for the latest stable install version, I did a full install without the symlink apps option selected. Then I did another full install with the symlink apps option checked. Finally, after reading through the entire list of available commands and what they did, I decided to do an advanced install. I selected "Remove Symlinks" for each of the busybox commands I wanted NOT to have available in Terminal Emulator.
Soon after the advanced installation, I noticed that Terminal Emulator wasn't working. Then I noticed that my WiFi connection wasn't working...specifically the part in which the phone attempts to lease an address using DHCP. After emailing the developer with my issue, I tried to re-install BusyBox manually based on a link he included in the reply. I could push the file to the phone using 'adb push' but when I tried to open a shell to run the install commands, I would get the following error: exec '/system/bin/sh' failed: No such file or directory (2) . Long story short, I had to re-flash the phone using Odin to fix it.
In the AFWall+ logs, around the time I ran the Advanced Install, there were a bunch of entries like this: ld_library_path=/vendor/lib:/system/lib busybox rm /system/xbin/strings exit. There may have been a -s after the 'rm' command and before the directory but I'm not completely sure. After I flashed the phone with Odin, I opened Root Explorer and took a look at the files under /system/bin/. I noticed that the commands that can be run without installing busybox...like ls, or ifconfig...were linked to 'toolbox'. /system/bin/sh was linked to mksh.
After more research and reading, I'm about 90% sure what happened. Here's an excerpt from the email I sent to the developer:
<snip>
Basically, the "Remove Symlinks" option in your app does either one of two things:
It removes the directories entirely
It removes the symlinks to busybox, but doesn't restore the original symlinks that were present before busybox was installed.
<snip>
So if you're using this particular installer, please be careful with the Advanced Option.
Click to expand...
Click to collapse
Hello I installed BusyBox and I had same issue with WIFI also others for example after reboot of my tablet wholle setting is set to orignaly(language and everithing).How can put back everithing?Does exist some apps etc???Thank you.
OMG... i installed busybox with this app into /system/xbin on my dopo d7015 with advanced install... and then the problems started... 0 total internal size, wifi not acquiring ip with dhcp ... no factory restore could fix it. then i eventually learned that /system/bin/sh didn't exist when trying to adb shell. i've downloaded an sh binary and copied it, now i have valid internal total size, and android terminal works... but wifi won't even turn on now! like an idiot i didn't backup before i started playing with the tablet... i have no clue as to how to fix it! please someone help me!
With one version of this app, it said Busy box 1.20.x is not compatible for my phone. But busy box installer by Stericson does the job perfectly.
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands