Galaxy S III adb shell error - Galaxy S III Q&A, Help & Troubleshooting

I was looking up the partition layout of the Galaxy S III while I stumbled upon this problem.
The first time you run a command in 'adb shell' everything is fine, but when you try to run a second command, it just hangs. It doesn't crash, it just hangs.
So, I tried to find out what could be wrong, by doing the following: Instead of going into the shell itself, I just entered a semi-random command 'adb shell mount', which returned the normal result.
Then, I typed 'adb shell' and guess what? It returns a commonly known error: 'error: protocol fault (status 72 6f 6f 74?!)'
The status code is HEX, which translates to: 'error: protocol fault (status root?!)'
So I suppose this has something to do with the fact that my SGS3 is rooted.
I don't feel like unrooting it, but if someone would be so kind to test this on an unrooted SGS3 and report back the results here so we can investigate this further that would be greatly appreciated.

it works without any error.
do you know what to backup which contains kernel and ramdisk ?

Mine is rooted, with Omega Rom V3 and everything works perfect with adb.

Cranck said:
Mine is rooted, with Omega Rom V3 and everything works perfect with adb.
Click to expand...
Click to collapse
Have you tried multiple shell commands? I know adb functions, but it's about using adb shell.
I'm on the stock rom, rooted manually with CF's insecure kernel by the way.

I'm not sure this is related, but there is some very suspicious new functionality in the FactoryTest.apk, called "SysScope". Its some kind of service checking and verifying the authenticity of "something". But I have no idea of what, only that a related java file (ResultCode.class [sysscope.service] contain the following code segment:
Code:
[SIZE=2] arrayOfResultCode[0] = OK;
arrayOfResultCode[1] = ADB_RUNNING_AS_ROOT;
arrayOfResultCode[2] = PARTITION_TAMPERED;
arrayOfResultCode[3] = ROOT_PROCESS_FOUND;
arrayOfResultCode[4] = DANGEROUS_FILE_DETECTED;
arrayOfResultCode[5] = NOT_OFFICIAL_BINARY;
[/SIZE]
Then it looks for SysScope files in the SysScopeVerifyer.class like this:
Code:
[SIZE=2]/data/app/com.sec.android.app.sysscope-1.apk
/data/app/com.sec.android.app.sysscope-2.apk[/SIZE]
I suggest you to back these up, and then replace them, with empty files of the same name, and see what happens.

I have the exact same problem on the GS2, OneX, and OneS. I have no problem shelling into the devices using another system, but on one of my computers I have the same issue. Windows 7 64bit with jdk7 installed.
Also, I enabled adb trace to see what was being returned: set ADB_TRACE=all
-Entering ls three times on the OneX, the first time works correctly
Code:
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=5
ls
system/core/adb/commandline.c::read_and_dump():read_and_dump(): pre adb_read(fd=
101)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=32
acct
cache
config
cwkeys
d
system/core/adb/commandline.c::read_and_dump():read_and_dump(): pre adb_read(fd=
101)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=318
data
default.prop
dev
devlog
etc
firmware_dsps
firmware_q6
firmware_radio
firmware_wcnss
init
init.elite.rc
init.goldfish.rc
init.qcom.rc
init.qcom.sh
init.rc
init.target.rc
init.usb.rc
mnt
proc
root
sbin
sdcard
sys
system
tombstones
ueventd.goldfish.rc
ueventd.rc
vendor
[email protected]:/ $ system/core/adb/commandline.c::read_and_dump():read_and_dump()
: pre adb_read(fd=101)
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)

Related

[HOWTO] Remove bash Color Codes

Anyone who uses the latest roms, mods, etc. is probably using bash. Bash is awesome, bash is great bash is...annoying if you use Windows with adb.
Familiar sight?
bash-4.1# ls
ls
←[1;36mbin←[0m ←[1;32minit.rc←[0m ←[1;34msbin←[0m
←[1;34mcache←[0m ←[1;32minit.smdkc110.rc←[0m ←[1;34msdcard←[0m
←[1;34mconfig←[0m ←[1;32minit.smdkc110.sh←[0m ←[1;34msqlite_stmt_journals←[0m
←[1;34mdata←[0m ←[1;36minit_samsung←[0m ←[1;34msys←[0m
←[1;34mdbdata←[0m ←[1;34mlib←[0m ←[1;34msystem←[0m
←[1;32mdefault.prop←[0m ←[1;32mlpm.rc←[0m ←[1;32msystem.prop←[0m
←[1;34mdev←[0m ←[1;34mmnt←[0m ←[1;34mtmp←[0m
←[1;34mefs←[0m ←[1;34mpreinstall←[0m ←[1;34muserdata←[0m
←[1;36metc←[0m ←[1;34mproc←[0m ←[1;36musr←[0m
←[1;32mfota.rc←[0m ←[1;32mrecovery.rc←[0m ←[1;34mvoodoo←[0m
←[1;36minit←[0m ←[1;34mres←[0m
Now my way:
bash-4.1# ls
ls
bin init.rc sbin
cache init.smdkc110.rc sdcard
config init.smdkc110.sh sqlite_stmt_journals
data init_samsung sys
dbdata lib system
default.prop lpm.rc system.prop
dev mnt tmp
efs preinstall userdata
etc proc usr
fota.rc recovery.rc voodoo
init res
Requirements:
Root.
Clockworkmod Recovery.
My busybox.
My color code removal patch.
Patch
http://dl.dropbox.com/u/2056318/bash_nocolor_1.1.zip
Install both via cwm. Make a nandroid backup first, JUST IN CASE.
If my patch hosed ls on your phone, this should fix it. Sorry about that.
http://dl.dropbox.com/u/2056318/bash_nocolor_fix.zip
Great Work!
What is this?
Did you remove all color from bash, or is it just not doing ls in color by default?
I would recommend people use something like mintty or console2 as their terminal on Windows instead of a regular cmd anyway, for anyone who actually uses the terminal frequently. Well, so console2 gets the same stupid behavior as the standard cmd with escape codes in adb for some reason, but it works with bash color escape codes in general (I have them in my $PS1). Mintty does support escape codes in adb shell, and is generally pretty nice, but doesn't have tabs unfortunately. Just a tip for people.
Nice job for those who don't want to change their terminal, of course. I just feel that for power users mintty is a better solution.
It removes them from ls, which is which is the only place the problem will lie for most windows users. I require my busybox, as there are many versions out there, but mine is the latest, and I know it supports ls. My patch removes the ls binary from Android and replaces it with my own symlink.
As for those options, I will stick with my powershell, but thanks. A poweruser should be using Linux anyway (I do normally).
Ah, yeah, that's probably true. But why is the default ls with colors in Android anyway? I normally need to create an alias to set ls to ls --color=auto or something along those lines usually. Is it just not getting the terminal info properly? I'm just curious about this I guess.
I'm a weird person who uses Unix shells on Windows, I guess because I like games too much.
Its not. ls in itself is a binary, not a symlink. It is running through the bash shell. Bash, is what supports colors. By default Android does not run bash, but sh.
Oh huh, didn't realize Android used sh by default. Guess I never paid attention.
Do you drop busybox in /system/bin to install it? That is, if you aren't flashing it from cwm.
Hate to be the bringer of bad news, but something in this breaks WiFi. After installing it, I can no longer connect to my router, it just stalls at "Obtaining address". When I check the router, it's already assigned an address.
I reflashed DL09 cleanly, and it connects right away. I re-apply this fix, and WiFi stops working again.
I did say make a nandroid backup....right?
Anyway, you are correct. Patch has been removed until I can figure something else out.
I did say make a nandroid backup....right?
Anyway, you are correct. Patch has been removed until I can figure something else out. Please revert to an earlier nandroid.
First post updated with a better fix that disables color for bash, system wide. Thanks to enderst from irc for the help.

Snowball Mod

I ran the Snowball Mod without a hitch. I then tried to run the update but it won't run for some reason. The window flashes some text quickly but then closes so I'm not even really sure why it's not working. Anyone run into this or have any ideas. Thanks in advance!
I haven't had the time to try out the snowball mod, yet -- so I can't offer any advice. But, I would post the issue in the development thread, that's where the most help will be.
Swyped from my B&N Nook Tablet.
Try running it from a command line to keep it up and be able to read any text.
Also, there is a log.txt, if you post that, it can be more helpful.
Yeah I was goin to but I don't have enough posts. I was hoping someone would see it here.
Well... if you post your log.txt and start it from a command-line window rather than double clicking the update.bat, then we can take a look at what's up.
Log file says:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
Command line:
Snowball is reporting: v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an "outdate"?
Thanks a lot!
There is no v2.0.2 update package in the zip folder. I renamed v2.0.1 to v2.0.2 and ran. Not sure if this was a good thing to do or not. Any help or direction would be appreciated. Thanks.
No write permissions
Tried to install snowball mod from a macbook pro by just running the snowball.sh. Started up and the B&N stuff was all there, although it looked like it ran without a hitch.
Looked at the log file in the snowball-mod folder and saw a lot of "Read-only file system" business. The first few lines being:
unzip: can't open nook-update-package.zip, nook-update-package.zip.zip, nook-update-package.zip.ZIP^M
rm failed for nook-update-package.zip, Read-only file system^M
Installing nook-update-package...
cd: can't cd to /mnt/media/nook-update-package^M
sh: Can't open install^M
rm failed for /mnt/media/nook-update-package, No such file or directory^M
Click to expand...
Click to collapse
How do you suggest I get around that?
conundrum768 said:
I haven't had the time to try out the snowball mod, yet -- so I can't offer any advice. But, I would post the issue in the development thread, that's where the most help will be.
Swyped from my B&N Nook Tablet.
Click to expand...
Click to collapse
We need 10 legit posts before we are allowed to post in the dev forum
Robotronik said:
Tried to install snowball mod from a macbook pro by just running the snowball.sh. Started up and the B&N stuff was all there, although it looked like it ran without a hitch.
Looked at the log file in the snowball-mod folder and saw a lot of "Read-only file system" business. The first few lines being:
How do you suggest I get around that?
Click to expand...
Click to collapse
Huh... this is weird... /mnt/media should not be read-only... although, I suppose, perhaps if you had it USB mounted, it might end up read-only.
Ensure that you have Automatic USB mounting turned off before you run the script.
You can actually push this update via wifi if you mod the update.bat (or update.sh for linux users) file.
Just turn on ADB Wifi (I prefer adbWireless app) and add the following to your bat file:
Code:
echo Waiting for device...
[B]adb connect XXX.XXX.XXX.XXX:XXXX[/B]
adb wait-for-device
...
adb shell "chmod 755 /data/local/tmp/update-package.sh ; su -c /data/local/tmp/update-package.sh" >> log.txt
if exist reboot adb reboot
[B]adb connect XXX.XXX.XXX.XXX:XXXX[/B]
echo INSTALLATION SUCCESSFUL
Use your IPort given to you by your ADB Wifi app in place of XXXs. Then just run the .bat!
Run from cmd if you don't want the output to vanish right away.
cfoesch said:
Ensure that you have Automatic USB mounting turned off before you run the script.
Click to expand...
Click to collapse
Okay, that got me a little further. Now:
Extracting nook-update-package...
Archive: nook-update-package.zip
creating: nook-update-package/data/
unzip: can't set permissions of directory 'nook-update-package': Operation not permitted
unzip: exiting
Installing nook-update-package...
sh: Can't open install
Click to expand...
Click to collapse
More permissions issues...
Still posting here because I don't have the 10 total posts to go in the Dev forum...
Anyway, I did the factory reinstall, and reran the snowballmod update. It said the root was still there, so I commented out that check from the snowball.sh, reran the package and everything went swimmingly.
Now, for the update:
The terminal spits out this:
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7 KB/s (46 bytes in 0.006s)
Snowball is reporting: v2.0.2
.zipte-package-v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an 'outdate'?
Click to expand...
Click to collapse
Where the log file gives me:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
Click to expand...
Click to collapse
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
same
Robotronik said:
Still posting here because I don't have the 10 total posts to go in the Dev forum...
Anyway, I did the factory reinstall, and reran the snowballmod update. It said the root was still there, so I commented out that check from the snowball.sh, reran the package and everything went swimmingly.
Now, for the update:
The terminal spits out this:
Where the log file gives me:
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
Click to expand...
Click to collapse
I AM HAVING THE SAME PROBLEM.MYBE..I need help some plz make a better howtos for dummies m
The first thing you need to do, if you have no clue what you're doing, is post the contents of the log file in the snowballmod folder.
The ".zipte-package-v2.0.2" seems to be related to adb shell "snowball-ver" returning DOS formatted text, even though you're in a *nix. I really did not expect this to happen with the linux and osx versions of adb, but apparently, they perform the same as cygwin... (cygwin I expected, after all, the adb.exe is a windows program). I will fix the update scripts to take that into account.
Code:
unzip: can't set permissions of directory 'nook-update-package': Operation not permitted
This message is reported by unzip when it is run by a non-root user on the /mnt/media partition.
You do _NOT_ have to run snowball-update though if you've installed snowball-mod fresh with the most recent version.
robtlebel said:
I AM HAVING THE SAME PROBLEM.MYBE..I need help some plz make a better howtos for dummies m
Click to expand...
Click to collapse
The changes made to the script were posted here:
Robotronik said:
Now, for the update:
The terminal spits out this:
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7 KB/s (46 bytes in 0.006s)
Snowball is reporting: v2.0.2
.zipte-package-v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an 'outdate'?
Where the log file gives me:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
Click to expand...
Click to collapse
I had the same issue with the name of the update file being called incorrectly: ".zipte-package-v2.0.2". With that output the script is looking for a file of that name and it's not finding it. I just changed the value of the variable ${VERSION} to v2.0.2 (since that was what was being reported by Snowball as my current version) and all worked after that.
Easy to fix temporarily:
-open "update.sh" in a text editor
-go to line 66 and change
VERSION=`awk '//{ print $2 }' snowball.version`
Click to expand...
Click to collapse
to
VERSION=v2.0.2
Click to expand...
Click to collapse
or whatever version yours shows to be running (v2.0.1, etc). Something tells me it might be important to input the correct current version number in
-save and close the file and rerun it.
EDIT: or wait until cfoesch fixes the scripts
Scripts should be updated. I changed the awk program from just "//{ print $2 }" to "//{ sub('\r', '', $2); print $2 }" ... this means that it works both ways... *insert your favorite "both ways" joke here*
It should also detect if you haven't turned off automount, and warn you about it. If the nook ends up rebooting, then it would tear the USB mount and could cause file corruption. I got around it by putting things in /data rather than /mnt/media, but then realized, if it has to reboot, then it could cause trouble. So better, to just warn them that automount was on, and quit out.
It also detects better if something went wrong in the installation process, and should report that installation has failed, rather than successful under all cases.
Things may have gotten broken in the process, so keep up the bug reports.
I just can't stop Nookin' Around.........god i need to sleep
I decided to check out the update.sh script (can only go so far currently since I have the latest update).
At least for me, (Ubuntu Linux 11.10) I figured something out about the $OSTYPE call to set the $adb variable. I could echo $OSTYPE in the terminal and got a response, but could not echo it in any scripts. Ended up finding the "uname -o" call and that seems to have gotten it to work, although the printout is different.
snowball-update# echo $OSTYPE
linux-gnu
snowball-update# uname -o
GNU/Linux
Changed lines 7 & 8 and seems to have worked:
case `uname -o` in
GNU*|linux*|Linux*)
Now this last part is probably something on my end but: update.sh: 62: ./adblinux: Permission denied
Thanks again for the work (and everyone else involved in rooting/hacking these things )
Indeed. $OSTYPE seems to be specific to bash, and not all sh implementations.
If you don't mind could you do this command and give me the output? "ls -l /bin/sh" and "sh --version" Those two commands should explain exactly which implementation of sh you have. (For instance, on the NT with snowball-mod, the sh is a minimal implementation, and does not support $OSTYPE. But on most OSes I've seen sh is actually a statically linked bash, as it is the most widely used shell scripting language.)
The case on that you provided though could be a poor choice, as GNU*) would match GNU/freebsd, or GNU/openbsd, or GNU/anykernel. Sure it is unlikely, but it is possible.
The permissions issue is not entirely your end, but it is an expected artifact of extracting from a zip file. Although, is suppose performing a chmod 755 on it prior to use would be a good idea in general.

Auto Keystore Unlocker

Hey Guys,
I know there is an app in the market already Keystore Unlocker, but it doesnt seem to work with the latest su binary. Does anyone know if there is a way to disable the password requirement for stored certificates. It would be a useful feature to bake into some roms or even a new app that works with latest su.
I decomplied the apk for Keystore Unlocker but it was no help. I emailed the developer and asked if he would either update the app and make it paid (99 cents wouldnt be too much) or release the source for us to use for future projects.
Let me know if you guys have any ideas.
Same issue on HTC Incredible, Stock + Root ROM 2.3.4. Really annoying, anyone know a fix? My initial thinking is it's at kernel layer, as Hot Reboot doesn't cause issue but a "full" reboot does. Anybody have a suggestion on fix or workaround?
+1
Would love to bypass the credential storage. It literally decimates the battery trying to log into a credentialed WiFi (try/fail/try/fail) if you don't happen to notice that you haven't done the credential yet.
+1
I have mailed to the app's author, perhaps he has a solution.
Does anybody knows what exactly the app does? Is there a way by command line to activate the credential storage? (so it could be done in autostart)?
There are two possibilities to unlock the keystore. Both need to be run under UID=1000!
1) You have an AOSP based ROM, like Cyanogen:
There is a tool called "keystore_cli", which provides basic access to the keystore by commandline.
Simply run
Code:
su -c 'keystore_cli u <password>' 1000
to unlock it.
Other options are can be found in keystore.c:
Code:
static struct action {
int8_t (*run)();
int8_t code;
int8_t state;
uint32_t perm;
int lengths[MAX_PARAM];
} actions[] = {
{test, 't', 0, TEST, {0}},
{get, 'g', NO_ERROR, GET, {KEY_SIZE}},
{insert, 'i', NO_ERROR, INSERT, {KEY_SIZE, VALUE_SIZE}},
{delete, 'd', 0, DELETE, {KEY_SIZE}},
{exist, 'e', 0, EXIST, {KEY_SIZE}},
{saw, 's', 0, SAW, {KEY_SIZE}},
{reset, 'r', 0, RESET, {0}},
{password, 'p', 0, PASSWORD, {PASSWORD_SIZE, PASSWORD_SIZE}},
{lock, 'l', NO_ERROR, LOCK, {0}},
{unlock, 'u', LOCKED, UNLOCK, {PASSWORD_SIZE}},
{NULL, 0 , 0, 0, {0}},
};
I guess you can figure them out, if you want to.
2) You don't have the keystore_cli tool:
a) You might be able to use a keystore_cli binary from another rom
b) Use unix domain sockets to communicate with the keystore.
The socket is under /dev/socket/keystore.
To access this, you'd have to write a small c programm and use the socket(), write() syscalls.
Luckily. this is exactly what that "keystore unlocker" from the market does.
It comes with a small native executable located at
Code:
/data/data/ru.chunky.AutoKeystore/lib/libkeystorecmd-executable.so
which reads input to send to the socket from stdin.
The format is:
Code:
<code><length1><message1>...
Where <code> would be 'u' to unlock
<length> would be the length of the password as 16bit unsigned int
<message> would be the string representation of the password
In this example the password is "password", which is 8 characters long.
So the length would have to be \0000\0008 and the message to send to the socket
Code:
u\0000\0008password
Running
Code:
su -c "echo -e 'u\0000\0008password' | /data/data/ru.chunky.AutoKeystore/lib/libkeystorecmd-executable.so" 1000
should show a result of
Code:
1
in the commandline, if successful and the keystore should be unlocked.
it sounds brilliant!
Do you have any idea what is the problem with the app and actual su versions?
Awesome find man, shame is ICS fixed this bug. It just requires a pattern lock or pin lock. I wish we could find a workaround for this....
Sent from my HTC Rezound
stm999999999 said:
it sounds brilliant!
Do you have any idea what is the problem with the app and actual su versions?
Click to expand...
Click to collapse
Nope, no idea.
I worked around it like this (cyanogenmod):
In /data/local/userinit.sh I put
Code:
#!/system/bin/sh
nohup /data/local/keystoreunlock_delayed.sh > /dev/null 2> /dev/null &
and the file /data/local/keystoreunlock_delayed.sh contains:
Code:
#!/system/bin/sh
sleep 60
su -c 'keystore_cli u <password>' 1000
The 60 second delay makes sure the phone has already initialized the keystore.
It's a bit of a diry way to do it, but this way it works without any android app.
To test this on my device, I made a file /data/keystoreunlock_delayed.sh
#!/system/bin/sh
su -c 'keystore_cli u <password>' 1000
and execute it within root explorer. But nothing happens!?
I tried su -c 'keystore_cli u <password>' 1000 in terminal Emulator, I got permission denied. I have to do a "su" before, without any parameters, then superuser asks for permission, and then the long command worked.
stm999999999 said:
To test this on my device, I made a file /data/keystoreunlock_delayed.sh
#!/system/bin/sh
su -c 'keystore_cli u <password>' 1000
and execute it within root explorer. But nothing happens!?
Click to expand...
Click to collapse
I forgot the permission 0755. It was 0555.
Can I download keystore_cli somewhere so I can use this script?
I have /system/bin/keystore but not keystore_cli on the rooted 2.3.4 OTA. Using HTC Incredible and would like to use this workaround script.
EDIT: I now realize this is in the Rezound forum. I found this thread by Google search but couldn't find much else on keystore_cli other than zip extract logs.
hm, I do not use a Rezound, too. I have a Desire.
Are you sure, this file is not an integral part of android?
I found one version on dropbox: https://www2.dropbox.com/s/cuu6hm8dvi3jxh5/BI/system/bin/keystore_cli
but I cannot say anything about this file. If it is genuine and ok.
What about asking in an Incredible subforum?
AutoKeystore fixed
I've just resolved "newer su" issue with ru.chunky.AutoKeystore and added password-less VPN Wizard there.

Solved: WiFi TXpower app error issue with missing iwconfig file

Want to save power when WiFi Tethering... try WiFi TXpower. You can find it here:
https://play.google.com/store/apps/details?id=rubberbibpepper.WiFiTxPower
Solution for missing IWCONFIG file:
1. Download the first attachment "iwconfig.txt" (default save location is '/mnt/sdcard/download')
3. Open 'File Manager'
a. Select: 'Menu' -> 'More' -> 'Settings' -> scroll down paste 'donate' (which you should do!)
b. Select: Mark Yes for both checkbox options of "Root Explorer" & "Mount System Folders"
3. Navigate your path over to '/mnt/sdcard/download' and find & rename the file "iwconfig.txt" to 'iwconfig'
4. COPY the file, and navigate your path over to '/system/xbin' and PASTE the file. It may say it wasn't pasted, but scroll down and the file will be there.
5. Launch busybox 'terminal emulator' and type these two commands:
# su
# chmod 755 /system/xbin/iwconfig
6. Boot up WiFi TXpower and verify that the iwconfig error message is gone, and that you do not get a 'iwconfig' permissions error. You should see "iwconfig" and "eth0" titles and all the signal and power stats listed in the app. Lower numbers, less range, and greater batter life.
7. Enjoy! If this has helped you, please hit the "Thanks" button below.
Backstory:
Problem is, this app needs a file 'iwconfig' to be installed in '/system/xbin' and this directory is R/O (read-only, write protected). There are a few ways to do this;
adb push to install the file
Find an APP that will install iwconfig for you
Symlink the file if its somewhere else
Copy & Paste File yourself
I'm old school, so I like to have a hard copy of the file anywhere its needed, and at 30.4 KB, who cares. So following the 80% help link below, I downloaded the 'iwconfig.tar' file, extracted the internal file, and started trying to copy it into '/system/xbin'. From this same site, I used fragments of commands in the busybox 'terminal emulator' to finish the install after the file was copied into the directory. I used '# chmod 755' to set the permissions on the new file, so WiFi TXpower could use it.
"Quoted from:
# su
# cd /mnt/sdcard/download — (this assumes the download location of the file)
# tar –xf iwconfig.tar — (this was to extract the single file from inside the tar file)
# mount –o rw,remount /system — (I couldn't get this command to work, but you can try next line below instead)
# mount -o remount,rw -t yaffs2 /system /system — ccdreadcc line of code, that looks like it would work, I received no terminal emulator errors when attempting.
# cp iwconfig /system/xbin — (Above didn't work, so I copy & paste this file in 'File Manager' as I couldn't get 'Root Explorer' to do it, it wouldn't R/W '/system')
# chmod 755 /system/xbin/iwconfig — (You will need this later to correctly set permissions on 'iwconfig', if you don't you will get a "permission denied" error in the WiFi TXpower App)
"
Helpful Links:
80% Help to figure this out, and will be quoting useful parts to solution:
http://jhanford.wordpress.com/2011/10/03/lowering-wi-fi-transmit-power-in-android/
20% Starting and finishing information for solution:
http://forum.xda-developers.com/showthread.php?t=1209251
Attached Files
Does anyone have this working on ICS or on an HTC Glacier MT4G?
My rom has the file needed, but I could not get it to show any type of config, then I tried this method and still nothing.
RUN IT
Working on VZW GS3! Thanks buddy for the help! BEEN LOOKING EVERYWHERE!
---------- Post added at 01:34 PM ---------- Previous post was at 01:11 PM ----------
What does iwmulticall do exactly? Would it benefit Galaxy S3 Wi-Fi or battery?
deep thoughts
zwieringa said:
Working on VZW GS3! Thanks buddy for the help! BEEN LOOKING EVERYWHERE!
---------- Post added at 01:34 PM ---------- Previous post was at 01:11 PM ----------
What does iwmulticall do exactly? Would it benefit Galaxy S3 Wi-Fi or battery?
Click to expand...
Click to collapse
I am running on a rooted sprint samsung S3, the app continues to show::
iwconfig:
Unknown id: wlan0.
when I select 4dBm, there is no indication it worked. In terminal I run iwconfig, and it shows that the setting took effect! My stock power is 1496, which seems to be my max. Selecting 11dbm works, but 18, 25 and 32 do not. I am guessing my wifi adapter will not allow anything over 1496.
If I had iw and ifconfig on my device I could try this to force a higher speed:
ifconfig wlan0 down
iw reg set BO<--------------is an o not a 0
ifconfig wlan0 up
iwconfig wlan0 channel 13
iwconfig wlan0 txpower 30
any suggestions how to pull this off.. I can install this on a debian destro, but there's no point to that... if I can get the iw and ifconfig on my andriod OS, maybe I can force it higher than 1496...
Tried this.. Surprisingly, it's also working on my Nexus 7 (2012) too..
Not that is requires wireless extensions.
Code:
[email protected]:/data/data/bcmon/misc $ ./iwconfig
lo no wireless extensions.
svnet0 no wireless extensions.
ifb0 no wireless extensions.
ifb1 no wireless extensions.
sit0 no wireless extensions.
ip6tnl0 no wireless extensions.
wlan0 no wireless extensions.
In last Samsung Aries kernel, it's one of these:
Code:
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211_WEXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
iwconfig has no effect on tx-power
This is great, thank you.
Unfortunately, when I followed all the instructions, got the iwconfig file from this thread, renamed it, successfully put it into system/xbin/, and then ran "iwconfig wlan0 txpower 2dBm" and then "iwconfig wlan0" the tx-power level is unchanged. It is still listed as 19 dBm. There's no error message.
Any ideas?
Does the "iwconfig [interface] txpower" command need to be run in a certain manner for it to have effect?
(I'm running a nightly build of Cyanogenmod 11 on a Moto G 4G.)
Yes, it's works on SGS4 i9506 4.4.2 after install iwconfig/iwmulticall. The signal is really changing, I see it when checking with other devices.
"iwconfig" shows txpower=31dbm for wlan0 (on other devices - S3, S5 and Tab - it shows 1496dbm)
I send command "iwconfig wlan0 txpower %%" with different values, but only 4, 11, 18, 25 and 31 works (yes, the last is not 32).
How can i increase it for better signal?
sorry for my english!
Thanks
Also I tried this:
iwconfig wlan0 sens -90
but
SET failed on device wlan0 ; Operation not supported on transport endpoint.
Is it needs orher diriver for wifi?
it doesn't work on lollipop
any ideas how to make it work on lollipop
Same here. Any solutions for Lollipop iwconfig?
error: only position independent executables (PIE) are supported.
how to fix this problem?
---------- Post added at 11:06 AM ---------- Previous post was at 10:46 AM ----------
kotaries said:
error: only position independent executables (PIE) are supported.
how to fix this problem?
Click to expand...
Click to collapse
Answering my own question:
You see this error because android doesnt want you to run old binaries on new version of system (as google explains, if I got the idea correctly)
To rebuild the binaries for new system is pretty complicated, so you can just fool the system by changing 17th byte in current (not working) binary file
Open some hex editor (online version for example: hexed.it), find the 17th byte (counting from 1, as humans do) and change it from 02 to 03
This byte (as I now see) is the first byte on 2nd string in the hex editor
Good luck
Try to edit, but the result "Segmentation Fault" :3

[Q] Rooting the Fusion 2

Can anyone advise if the Huawei-U8665 (At&T Fusion 2) can be rooted? It has Android version 2.3.6. I tried with the easy OneSuperClick approach but didn't work-wouldn't recognize device. Thanks.
ptbear said:
Can anyone advise if the Huawei-U8665 (At&T Fusion 2) can be rooted? It has Android version 2.3.6. I tried with the easy OneSuperClick approach but didn't work-wouldn't recognize device. Thanks.
Click to expand...
Click to collapse
Did you ever figure out how to root?
Why don't you Google search other huawei devices and look for root kit running Gingerbread
Sent from my LGL35G using xda premium
903tex said:
Why don't you Google search other huawei devices and look for root kit running Gingerbread
Sent from my LGL35G using xda premium
Click to expand...
Click to collapse
I have, and I haven't been able to find anything. Superoneclick, z4root and unlock root only work for 2.3 and the Fusion 2 is running 2.3.6 and while trying to use those tools to root, it always hangs when trying to gain shell root.
Have to wait til somebody with skills makes a exploit for the fusion.
Sent from my LGL35G using xda premium
Patience is a virtue I supposed. I should've just bought a galaxy player I guess.
I seem to have acquired root, but I had to use fastboot to restore the rom. Sry i cant be more specific because tthis touchscreen took a hard fall..... post later thx -RFE
RFE said:
I seem to have acquired root, but I had to use fastboot to restore the rom. Sry i cant be more specific because tthis touchscreen took a hard fall..... post later thx -RFE
Click to expand...
Click to collapse
i keep posting to the wrong threas. sry
hint hint....... u need the diag drivers which are not posted but i should have a recovery img ready soon (one that re-installs SU on each boot
RFE said:
i keep posting to the wrong threas. sry
hint hint....... u need the diag drivers which are not posted but i should have a recovery img ready soon (one that re-installs SU on each boot
Click to expand...
Click to collapse
these are the right drivers for adb
RFE said:
these are the right drivers for adb
Click to expand...
Click to collapse
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
RFE said:
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
Click to expand...
Click to collapse
Here is a clip of adb working. I am trying to get clockworkmod working, but it is difficult because of all this new 2.3.6 securiy (my last phone was a 2.3.4)
D:\android-sdk-windows\platform-tools>adb tcpip 8888
restarting in TCP mode port: 8888
D:\android-sdk-windows\platform-tools>adb root
error: device not found
D:\android-sdk-windows\platform-tools>adb usb
error: device not found
D:\android-sdk-windows\platform-tools>adb get-state
unknown
D:\android-sdk-windows\platform-tools>adb shell
$ exit
exit
D:\android-sdk-windows\platform-tools>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\android-sdk-windows\platform-tools>adb root
adbd cannot run as root in production builds
(you must copy certain files to the device via adb push/pull & you can have root too)
---------- Post added at 04:14 PM ---------- Previous post was at 03:46 PM ----------
I dumped the entire phone in user mode and this is what you get:
(let me know if you need anything)
Device connected.
Default pull path saved.
Detailed phone info: RECOVERY ACTIVE
Pulling file or directory from data/app/... successful.
Pulling file or directory from data/app_private/... failed.
Pulling file or directory from data/data/... successful.
Pulling file or directory from data/local/... successful.
Pulling file or directory from data/nv/... failed.
Pulling file or directory from data/system/... successful.
Pulling file or directory from system/app/... failed.
Pulling file or directory from system/bin/... successful.
Pulling file or directory from system/etc/init.d/... failed.
Pulling file or directory from system/fonts/... successful.
Pulling file or directory from system/framework/... successful.
Pulling file or directory from system/media/... successful.
Pulling file or directory from system/usr/keylayout/... successful.
\android-sdk-windows\f2pull1
05 <DIR> .
05 <DIR> ..
56 1,697 7k_handset.kl
56 3,894 7x27a_kp.kl
43,652 abtfilt
51 0 accounts.db-journal
55,168 akmd8962
55,168 akmd8975
191 am
313 am.jar
27,864 am.odex
5,520 amploader
313 android.policy.jar
248,448 android.policy.odex
313 android.test.runner.jar
193,944 android.test.runner.odex
58,132 applypatch
5,720 app_process
71,736 ast-mm-vdec-omx-test7k
17,076 ATFWD-daemon
24,064 athtestcmd
631,588 ath_supplicant
<DIR> audio
56 245 AVRCP.kl
5,504 battery_charging
5,292 bluetoothd
199 bmgr
313 bmgr.jar
13,784 bmgr.odex
23,208 bootanimation
23,192 bootanimationex
313 bouncycastle.jar
778,624 bouncycastle.odex
10,196 brcm_patchram_plus
33,428 bridgemgrd
380,435 btld
5,556 bugreport
5,360 callife
145,156 charge
14,404 CKPD-daemon
6,880 Clockopia.ttf
22,788 cnd
313 com.android.location.provider.jar
7,352 com.android.location.provider.odex
1,671 com.cequint.platform.jar
1,984 com.cequint.platform.odex
313 com.google.android.maps.jar
388,168 com.google.android.maps.odex
313 com.qualcomm.location.vzw_library.jar
46,000 com.qualcomm.location.vzw_library.odex
120,332 compassd
313 core-junit.jar
23,952 core-junit.odex
22,926 core.jar
4,801,784 core.odex
5,520 dalvikvm
109,504 dbus-daemon
18,112 debuggerd
9,796 dexopt
44,612 dhcpcd
102,056 dhd
5,648 diag_klog
5,568 diag_mdlog
108,820 dnsmasq
194,488 DroidSans-Bold.ttf
190,776 DroidSans.ttf
35,880 DroidSansArabic.ttf
3,725,920 DroidSansFallback.ttf
23,076 DroidSansHebrew.ttf
119,380 DroidSansMono.ttf
36,028 DroidSansThai.ttf
185,228 DroidSerif-Bold.ttf
190,304 DroidSerif-BoldItalic.ttf
177,560 DroidSerif-Italic.ttf
172,916 DroidSerif-Regular.ttf
56,468 ds_fmc_appd
34,544 dumpstate
9,812 dumpsys
5,548 dvz
204,900 e2fsck
313 ext.jar
1,393,000 ext.odex
06 60,920,794 fastboot-tools-full-copy-HUAWEI-U8665-EN-NONIG
rar
9,968 filebackup
14,084 fmconfig
360,282 framework-res-hwext.apk
10,368,022 framework-res.apk
12,413 framework.jar
9,007,376 framework.odex
22,640 fsck_msdos
35,028 ftmdaemon
5,604 gzip
27,652 hciattach
5,684 hci_dev_state
277,652 hostapd
22,420 hostapd_cli
5,440 hostapd_wps
9,920 hwvefs
194 ime
313 ime.jar
6,720 ime.odex
201 input
313 input.jar
4,408 input.odex
18,324 installd
133,556 ip
36,052 iperf
216,188 ipth_dua
313 javax.obex.jar
60,848 javax.obex.odex
10,112 keystore
9,692 kmsgcat
39,416 linker
13,952 load_oemlogo
44,484 loc_api_app
14,052 logcat
9,760 logwrapper
5,504 mediaserver
17,408 mm-abl-daemon
13,184 mm-abl-test
18,092 mm-adec-omxaac-test
22,156 mm-adec-omxadpcm-test
22,172 mm-adec-omxamr-test
22,288 mm-adec-omxamrwb-test
22,236 mm-adec-omxevrc-hw-test
26,172 mm-adec-omxmp3-test
22,236 mm-adec-omxQcelpHw-test
22,268 mm-adec-omxvam-test
22,204 mm-adec-omxwma-test
5,532 mm-adspsvc-test
18,108 mm-aenc-omxaac-test
13,852 mm-aenc-omxamr-test
18,252 mm-aenc-omxevrc-test
18,252 mm-aenc-omxqcelp13-test
5,408 mm-audio-alsa-test
15,996 mm-audio-ctrl-test
5,552 mm-audio-mvs-test
88,820 mm-audio-native-test
22,188 mm-jpeg-dec-test
18,096 mm-jpeg-enc-test
5,456 mm-qcamera-daemon
62,308 mm-qcamera-test
10,652 mm-qcamera-testsuite-client
26,464 mm-vdec-omx-test
63,620 mm-venc-omx-test
9,800 modempre
205 monkey
313 monkey.jar
89,864 monkey.odex
18,308 mtpd
5,552 ndc
5,660 netcfg
47,764 netd
76,324 netmgrd
5,520 nl_listener
5,376 oeminfo_test
5,584 oem_rpc_svc
32,616 omx_tests
51 6,374 packages.list
51 111,973 packages.xml
18,692 pand
18,112 pcm-bridge
67,860 pcscd
524,288 Phonesky.apk
2,870,672 Phonesky.odex
11,032 PicoTts.apk
12,640 PicoTts.odex
26,720 ping
5,540 PktRspTest
6,916,572 PlusOne.apk
5,932,352 PlusOne.odex
191 pm
313 pm.jar
28,392 pm.odex
3,757,662 pops_atnt.apk
1,511,304 pops_atnt.odex
18,096 port-bridge
700,557 PotterUnlock.apk
77,128 PotterUnlock.odex
139,540 pppd
56,764 ProjectMenuAct.apk
94,408 ProjectMenuAct.odex
313 qcnvitems.jar
125,648 qcnvitems.odex
313 qcrilhook.jar
12,544 qcrilhook.odex
86,836 qmiproxy
33,652 qmuxd
9,760 qrngd
5,564 qrngtest
56 1,950 qwerty.kl
56 2,601 qwerty_m660.kl
142,516 racoon
26,252 radish
57,140 recEvent
9,856 rild
5,588 rmt_oeminfo
10,220 rmt_storage
59,832 run-as
5,392 schedtest
9,748 sdcard
42,404 sdptool
9,860 service
9,956 servicemanager
313 services.jar
1,732,544 services.odex
6,792,432 Settings.apk
883,048 Settings.odex
33,309 SettingsProvider.apk
65,176 SettingsProvider.odex
974,859 SetupWizard.apk
92,928 SetupWizard.odex
82,840 sh
15,014 ShopMusic.apk
3,264 ShopMusic.odex
23,176 shutdownanima
9,828 sleeplogcat
3,858 SmartcardService.apk
28,064 SmartcardService.odex
1,704,489 SoundRecorder.apk
54,480 SoundRecorder.odex
313 sqlite-jdbc.jar
147,632 sqlite-jdbc.odex
81,284 Stk.apk
67,312 Stk.odex
153,434 Street.apk
323,656 Street.odex
5,456 surfaceflinger
56 1,999 surf_keypad.kl
192 svc
313 svc.jar
8,400 svc.odex
10,239,938 Swype.apk
647,512 Swype.odex
609,667 SystemUI.apk
191,344 SystemUI.odex
5,472 system_server
811,688 Talk.apk
514,136 Talk.odex
35,024 TaskManager.apk
20,472 TaskManager.odex
19,817 TelephonyProvider.apk
165,968 TelephonyProvider.odex
30,452 testpcsc
35,268 test_diag
3,444,531 tn70-android-att-7121044.apk
2,756,552 tn70-android-att-7121044.odex
81,544 toolbox
559,282 ToolBox.apk
24,400 ToolBox.odex
15,030 TtsService.apk
37,544 TtsService.odex
51 58 uiderrors.txt
1,580,748 UNO_DEMO_HUAWEI_U8665_EN_NONIGP_ATT_TS_102.apk
552,136 UNO_DEMO_HUAWEI_U8665_EN_NONIGP_ATT_TS_102.ode
5,440 usbhub
5,520 usbhub_init
13,689 UserDictionaryProvider.apk
16,504 UserDictionaryProvider.odex
27,284 v4l2-qcamera-app
5,552 vdc
1,125,753 Videos.apk
1,392,992 Videos.odex
3,171,658 vlingo.apk
2,772,800 vlingo.odex
91,893 VoiceDialer.apk
87,256 VoiceDialer.odex
1,485,636 VoiceSearch.apk
2,391,016 VoiceSearch.odex
64,100 vold
19,377 VpnServices.apk
32,648 VpnServices.odex
9,792 wiperiface_v01
109,465 WISPr_57_Android22_prepaid.apk
66,824 WISPr_57_Android22_prepaid.odex
9,732 wlan_detect
10,416 wlan_tool
408,520 wl_4330
92,564 wmiconfig
31,284 wpa_cli
372,356 wpa_supplicant
1,937,546 YouTube.apk
1,660,664 YouTube.odex
1,973,436 YPMAndroid-release_preload3_6_2990.apk
1,531,032 YPMAndroid-release_preload3_6_2990.odex
282 File(s) 178,328,187 bytes
Click to expand...
Click to collapse
GOT ROOT? Fusion 2 finally rooted!
RFE said:
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
Click to expand...
Click to collapse
Here is the superuser binary along with a working adb packaged together. Just push the apk to the phone once you have the drivers installed.
I shouldn't have to spell it out for you how to apply this root kit.
Enjoy and don't abuse!
>adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
>adb shell mount -o rw,remount rootfs /
>adb shell busybox --install -s /vendor/bin
>adb install ./Lib/Superuser.apk
2458 KB/s (196640 bytes in 0.078s)
pkg: /data/local/tmp/Superuser.apk
Success
Looking for the rar password
Thanks for posting, however its asking for a password.
RFE said:
Here is the superuser binary along with a working adb packaged together. Just push the apk to the phone once you have the drivers installed.
I shouldn't have to spell it out for you how to apply this root kit.
Enjoy and don't abuse!
>adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
>adb shell mount -o rw,remount rootfs /
>adb shell busybox --install -s /vendor/bin
>adb install ./Lib/Superuser.apk
2458 KB/s (196640 bytes in 0.078s)
pkg: /data/local/tmp/Superuser.apk
Success
Click to expand...
Click to collapse
Rar Password?
Will you either release the rar password or post and non encrypted link please?
I thought I mentioned the password is xda-developers.com ... something easy to overlook if you are skimming the forums.
EDIT: attached recovery image
RFE said:
I thought I mentioned the password is xda-developers.com ... something easy to overlook if you are skimming the forums.
EDIT: attached recovery image
Click to expand...
Click to collapse
I got this phone for my daughter and wanted to root to make it seem like an ordinary phone to AT&T. That way they won't charge me for having a smart phone. Anyway, it doesn't seem a lot of folks are rooting the Fusion 2. How has yours behaved since you've rooted? Any problems?
Spurs_Redskins said:
I got this phone for my daughter and wanted to root to make it seem like an ordinary phone to AT&T. That way they won't charge me for having a smart phone. Anyway, it doesn't seem a lot of folks are rooting the Fusion 2. How has yours behaved since you've rooted? Any problems?
Click to expand...
Click to collapse
Even if out root it that won't stop att from seeing it as a smart phone
Batcom2
Whenever I try to push the Superuser.apk into the Fusion 2, it keeps saying that
Code:
"failed to copy 'superuser.apk' : read-only file system
Okay, so I've obtained root, but I bricked my phone using Rom Toolbox Pro. Can someone please backup their /system folder, so I may try to unbrick my device?
Sent from my NookColor using xda app-developers app
yup im a friggin moron flashed that recovery.img to my system out of habit ended up bricking mine too. can someone please upload a stock system.img as well as the original recovery so i can attempt to unbrick this beast I was trying to root for a friend. all I get to is first white at&t screen and it freezes almost like stuck in fastboot mode
can someone help and rip/upload or do I have ne other options?

Categories

Resources