I have an HTC Evo 3D with HBoot 1.5 and have already unlocked it through HTC. I have also flashed recovery cwm-4.0.1.4-shooter.img. I have put the su-2.3.6.3-efgh-signed.zip on my sd card.
Now when I load up the bootloader and go into recovery aka blue screen with many options (revolutionary) and lock the sd card to phone and try to load zip from sd and it starts installing....however it stops and has an error message that is...
-- Installing: /sdcard/su-2.3.6.3-efgh-signed.zip
Finding update package...
Opening update package...
Installing update...
**********************************************
Superuser 2.3.6.3 for Android 2.0-3.1
**********************************************
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Deleting SYSTEM:xbin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 6755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/su-2.3.6.3-efgh-signed.zip
(Status 0)
Installation aborted.
----any help in this matter will be greatly appreciated
Thanks.
in addition....
would it be easier/a better way to flash it from the command prompt like the recovery mod?
http://forum.xda-developers.com/showthread.php?t=1239821 this has a instuctions on how to adb push su file & install
have SU and running barnacle....
i am now having a slight problem with the barnacle wifi tether app. when i boot it up and start tethering it says:
Starting...
Data network is ready
.ini file prepared
WIFI: driver loaded
Could not connect to NAT, will retry later
Running...
my laptop connects to the barnacle tether but no internet access...
i am also trying to connect my PS Vita to it but it wont find my phone at all
I already have Skip wpa_supplicant checked ON to configure wifi directly
under the barnacle settings.
custom wifi ad-hoc...
do i need to select a setting under the
Custom Wifi Ad-hoc?
only options are:
none
Hero/Eris
Samsung
Aria/Liberty (see blog)
SU binary updater
Also when running the Barnacle for the first time it said my SU was out of date and the SU app binary updater automatically updated my SU to version 3.0.3.2
dont think this would cause a problem but noting just in case...
Thanks again...
Try usinng this one its free an works for me http://code.google.com/p/android-wifi-tether/also in stall busybox installer from the market place
Sent from my PG86100 using XDA Premium App
Related
Hi,
Anybody using samba filesharing app?
http://nl.appbrain.com/app/samba-filesharing/com.funkyfresh.samba
I use it on my desire and works like a charm, however it doesn't work on my archos 101 with uruk 1.5
I install the app, allow superuser access and then I get a "Unable to find a way to execute shell commands" error.
I have superuser 2.3.6.3 with su binary v2.3.1-ef
There is a new binary available but I can't install it (I need to flash the zip), could this be the issue?
If so, how do I flash this zip?
Restart in Boot menu => recovery system and then what? update firmware or developer edition menu and flash kernel and initramfs?
thx!
Cheers
B
As Uruk has an embedded Samba, what do you need that for?
tried that but it doesn't work, it says "error during command" when I try to start it up... when I check "enable at startup" and restart my device flips out and keeps restarting
cheers
b
I used it on Defy with Stock Eclair and stock Froyo, but with CM7 RC1.5 it doesnt work, same errore message as the one from the threadstarter
I've had an automatic reboot enabled on my phone for well over a year now that has worked perfectly using the process described here:
http://tasker.wikidot.com/devicereboot
This morning I had a notification that my SU binary was outdated asking if I wanted to update to. I updated, and now I can't get a prompt for the Tasker/Locale Execute Plug In action to give it root privleages. I get a SuperUser prompt for other apps, Titanium, Voltage Control, Root Explorer, etc, but for some reason the Locale Execute Plug In get's automatically denied without any prompt whenever it requests root privileages. This is confirmed by viewing the log.
Any ideas?
Ok, more info..
Manually rebooting the phone seems to partially downgrade the SU binary.
I get the notice that a new version of su binary is found.
Code:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0
Checking installed version = 2.3.1-ef
Fixing database... okay!
Downloading custom busybox... okay!
Checking md5sum... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... okay!
Gaining root access... okay!
Remounting /system as rw... okay!
Copying su to /system... okay!
Checking md5sum... okay!
Moving su to it's final location... okay!
Checking md5sum... okay!
Changing su file mode to 06755... okay!
Remounting /system as ro... okay!
Checking installed version = 3.0
Cleaning up... okay!
It seems to be stuck in this endless loop now.
Every time I reboot the phone it reverts back to the older (working) SU binary and tells me a newer version is available. If I upgrade the SU binary, then my Tasker reboot is broken AND any reboot reverts the SU binary version back to the old one.
I'd be fine leaving the older SU binary on there and just ignoring the notification to update, but when it notifies of an update/newer SU binary it disables the ability to remember your SuperUser choices (Allow/Deny) for apps so either I have to manually allow any root apps every time they need access or change my Super User settings to always allow instead of prompt which isn't exactly ideal or safe.
Any thoughts or ideas?
Cross-posting for visibility...
Looks like others (Epic users) are having the problem as well with the SU binary update.
http://forum.xda-developers.com/showthread.php?t=1279238
In that other thread, the person get a message, that his su binary is installed in /sbin. That means it is in the ramdisk of his boot image.
su should be in /system/xbin, then it can be replaced. if placed in the ramdisk, you need to replace/modify the boot image, to change it.
Per
I don't have the problem with updating the binary, but I do have the same problem with the updated binary.
I've emailed the developer to ask him if there is a fix. I think what he's done is limit it to run only with the exact command you first grant.
So if you're using the Locale execute plugin to try running more than one command only the original command you allow is allowed and all others are denied.
Even setting the default to Allow doesn't help.
Hopefully he'll have a fix.
I'm noticing the same behavior with new Superuser. It no longer prompts to allow Locale Execute Plugin, just waits until the request times out and flashes that the permissions were denied.
I can't figure out how to execute Locale Execute Plugin in a manner that the new Superuser will prompt the request, nor haw to manually add it as allowed.
And this is a single line Tasker Execute, so it's not related to hastarin's comment.
Yes, it does seem to be a bug caused with the new su.
For anyone still stuggling, I managed to get my commands to run with this instead of the Locale Execute Plugin:
http://forum.xda-developers.com/showthread.php?t=1217767
Not sure if this is still relevant however I registered to post anyway.
Ran into this problem and couldn't find any answers so I fiddled around on my own.
By checking the "Advanced Prompt" option in Superuser's preferences I managed to get a prompt to appear and allow the locale execute plugin su permissions.
[FIXED]
Thank you all for the support! I was facing the same issue which Tasker had no root access.
The solution for me was checking the "Enable Permission Warning" option in SuperSU as in the attachment...
I have come to what seems to be the end of a very unique set of misfortunes. I was keeping my phone stock for as long as possible, to avoid running into these issues (I don't have any "backup" phones), but being sent on travel for work and staying in a hotel with no Internet forced my hand. I needed to be able to tether my phone.
I went about unlocking the bootloader and after booting into TWRP, I immediately made a backup. I then flashed the necessary zip file to acquire root access. After successfully rooting it, I was able to achieve wireless tethering via Wireless Tether for Root. However, I did not want to deal with the power drain and possible latency/bandwidth degradation of a wireless connection, so I began the process of flashing a custom ROM (MeanROM).
After laboriously acquiring the ROM zip via Panera Bread wifi and placing it in my external SD card, I booted into TWRP to attempt to flash it. While trying to flash a ROM, I ran into some problems and was able to successfully restore from the backup I had made. I attempted to flash MeanROM, however, and received a failure message. The zip program was unable to open the file.
After reading up a bit more, I decided to wipe cache, dalvik cache, and perform a factory reset and system wipe. These operations did not enable me to successfully flash my ROM. They did, however, result in corrupting my internal SD card partition, resulting in the loss of my backup. What I mean by this is that there are several messages about "failed to mount /sdcard (Invalid argument)" in the log. The next step was to try to reformat the internal SD card.
I discovered that the busybox install provided did not have the ability to do what I needed, so I went about pushing a newer version onto my phone using adb push. The exact command I ran (copied and pasted from my terminal) was this:
Code:
sudo ./adb-linux push busybox /sbin
This had the unfortunate result of assuming /sbin was the new name of the busybox file on my phone, thus overwriting my /sbin folder with a file. Now, when I try to run adb shell, I get the nasty message
Code:
- exec '/sbin/sh' failed: Permission denied (13) -
So! Does anyone want to undertake the task of trying to help me?
After another Factory Reset and reboot, I was able to get past that last error message and can now adb shell in again. Hopefully I'll just be able to re-download the (or another) ROM and get that flashed.
Aaaaaaaaaaand I just learned about this: Enable WiFi Hotspot and USB / Bluetooth Tethering on the EVO 4G LTE
Note to self, do more reading.
elead1 said:
After another Factory Reset and reboot, I was able to get past that last error message and can now adb shell in again. Hopefully I'll just be able to re-download the (or another) ROM and get that flashed.
Click to expand...
Click to collapse
That would be my suggestion. Make sure to check the md5 on the rom download, especially on questionable wifi networks.
Sent from my EVO LTE
Definitely a bad download. Also, you must be on twrp 2.2.1 to install the latest MeanRom. With the addition of GoogleNow to the rom it has grown to over 600mb and the older versions of twrp seem to fail more often than succeed during install. If you want to use usb tether, you probably should bite the bullet and buy PDAnet. It is by far the best and most reliable method of USB tether. You won't be able to get it in the market though, you will have to get it directly from their website: http://junefabrics.com/android/
I've been using PDAnet for 3 years now and you don't have to be rooted to use it. PDAnet's latest version offers wifi and bluetooth tether now, but unfortunately it doesn't work on HTC phones because it uses FoxFi for its wireless tether which doesn't work on HTC phones.
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
I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Algo2 said:
I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Click to expand...
Click to collapse
until you have updated your binaries, rooted apps will do this....
if you have safe strap installed and working, you can download the updated SU 1.99 zip and flash it thru safestrap....other methods are talked about I believe in the towel root threads but I haven't done that myself
Algo2 said:
I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Click to expand...
Click to collapse
The version of SuperSU on the playstore is outdated, you have to do the folowing:
5. Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip
6. Use ES File Explorer https://play.google.com/store/apps/details?id=com.estrongs.android.pop or other unzipers and unzip the file
7. Open the /common folder in the unzipped file, and copy the SuperUser.apk to the /system/app/ folder in the root of the phone, confirm any SuperUser Access requests at this point.
You can also use the safestrap method:
Note: SafeStrap doesn't work with encryption turned on (disabled by default). If you don't know if you don't have encryption on/your phone isn't a business phone (in which case you shouldn't be doing this!!!) then you most likely don't have encryption on!!
5. Use this app to change your SELinux mode to "Permissive" https://play.google.com/store/apps/details?id=com.mrbimc.selinux, this is required to use SafeStrap
6. Install SafeStrap 3.72 APK from this thread http://forum.xda-developers.com/showthread.php?t=2448925, NOT 3.71 FROM THE VERIZON THREAD!!! Then click install in the SafeStrap App
7. Flash http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip, this step is NOT OPTIONAL, without this file, your SU Binaries will not update!!! (This is important!)
Credits to @npjohnson
SuperSU in the Playstore has been updated top 2.0 and is the latest, greatest version now.