echo murata > /data/.cid.info
chown system /data/.cid.info
chgrp wifi /data/.cid.info
chmod 0660 /data/.cid.info
I saw this on another thread as my s3 wifi is not connecting to my pocket wifi even though other devoces can. Just wondering where can I inpit this command? I have rooted my device and looking for some help? Do I need to install an app to use this command? Any steps or screenshots is greatly appreciated as Im about to give up.
Looks like you need to connect to localhost through a JuiceSSH or a similar terminal.
Better use Solid Explorer.
Be very careful though. You may end up with completely broken WiFi.
Related
i searched and cant seem to find anything on my problem....i connect via mass storage mode , it detects the phone, but for some reason it doesnt let me access the files on the card....in other words ,i cant open them...any help ????
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
I am using it just fine on Ubuntu 10.4
I connect my phone and it is mounted automagically, and I can move the files from/to the phone.
Do you have se_linux installed?
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
thanks, I'll give this a try, let you guys know tomorrow...
Gotta say it works on Ubuntu better then does on Windows XP. You may have some permissions fudged somewhere. Do as the guys above said and let us know.
the3dman said:
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
Click to expand...
Click to collapse
this is not working for me
aksoutherland said:
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
Click to expand...
Click to collapse
nothign when i enter command
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
lqaddict said:
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
Click to expand...
Click to collapse
nothing again.....i have it set to ask on connection, then i swithced to mass storage mode....... what else should i do?
error message : "could not display" "the file location is not a folder "
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.
lqaddict said:
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.[/QUOTE]
thanks, I appreciate the help, I will give this a try in the morning
Click to expand...
Click to collapse
The rooted with Superuser...
after that, I have to be in debugging mode to connect to computer and everytime I connect to different computer, it keep asking me to install the driver.
Before root, it did not ask any driver, it was working with mass storage like USB thumb drive.
I try to unroot but it is not working I don't know why..
And I try to use Restore Backups through ROM Manager v2.5.0.4 but not working....
I am so frustrated with this root..... I just want to unroot and I really want to use 2.2froyo ....
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
And I also try that, but it says, rm failed for /system/app/Superuser.apk, Read-only file system
all three same error message.
Could anyone please help me to unroot my phone or.... anyway to use my mass storage without installing the driver?
It is using the adb interface
The second issue is that /system is mounted read only have to remount read write
Sent from my bionix powered Vibrant
Okay well its not as urgent as the title but I am having some problems rooting my thunderbolt. I am using the root method here http://forum.xda-developers.com/showthread.php?t=996616 however, I getting stuck. The first three commands provide a return in terminal but the last two
adb shell chmod 777 /data/local/psneuter
adb shell chmod 777 /data/local/busybox
just return to C:\sdk\platform-tools. I proceeded to the next command adb shell and I get a # instead of $. Any ideas? I have tried it in both charge only and disk drive with usb debugging enabled and fast boot off. In the instructions I am following it didnt specify what to do with the exploits contents so I dropped them all in the platform-tools folder.
http://chat.andirc.net:9090/?channels=#
type in your name and #thunderbolt
I got a ton of help rooting my phone yesterday
After once I was conected and than disconected from wifi network I can't connect again. I had that problem beforee on nAa 10 minicm7 2.1.8. And I have the same problem now om nAa 11 minicm7 2.1.9
EDIT
I must say that i am talking about ad-hoc wifi
Once i create ad-hoc over laptop i can conect with my phone, and wifi works. But once i disconected (on phone) turn off wifi or go out of range, when i try to cenected again it doesnt works. It says getting Ip adress but than that just repeat.
When that happens I make new one ad-hoc wifi point and i can conect. But the problem remain if again gou out of range or turn off wifi and try reconect.
anyone else??
any solution??
70 views 0 coment
Anyone try that and check if problem is for everyone who want to conect ad hoc wifi point?????
Sent from my U20i using XDA App
Try this
Try this, it worked for me.
USING ADB:
adb shell rm -rf /data/misc/wifi && reboot
From the Terminal app.
# su
# rm -rf /data/misc/wifi && reboot
It removes all wifi settings.
Mine was overwritten by TB so I started again with clean settings.
Hidden Tethering Usage, PDAnet Instability and recreating "Hide Tether Usage"
Two Questions.
1) What is going on inside PDAnet to cause it to be so unstable?
2) Can whatever magic pixie dust running inside PDAnet /FoxFix hiding the tethering usage, be recreated in a linux environment, without full-root?
Ive found a HackerNews post here about using adb to set the DUN configuration:
https://news.ycombinator.com/item?id=20461879
Code:
adb shell settings put global tether_dun_required 0
This coupled with the Tether package (https://github.com/bemehiser/Tether/) and cyanogenmod tether results in blazing fast, yet impressively sporadic bandwidth ( 50 or 1mbps ... nothing in between @ 90% time being spent in crawling )
Additionally I've run this line:
Code:
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,,,,310,120,,default,mms,dun"
Yet it seems to have done nothing to change the misbehaving speed fluctuations.
Ive found a few other packages:
https://github.com/RiFi2k/unlimited-tethering
https://github.com/double-m/easy-usb-tethering
https://github.com/evdenis/tether_unblock
But havn't used them yet.
Endgame I want my phone to not snitch on my USB-based tethering.
Can this be done with just ADB or do I need to full root the phone?
Heres another possible workaround using SQLITE to define what seems to be able to be set using ADB
http://www.madore.org/~david/linux/android.html
I BELIEVE this substantiates that changing a routing table, once full-rooted, would fix any DUN-based carrier reporting:
https://danielpocock.com/android-betrays-tethering-data/
Found more information on how PDAnet might work its magic:
https://www.howardforums.com/showth...-tethering-look-like-on-device-data-use/page4
PDANet hides tethering by changing the user agent of every HTTP request passed through, and also blocking OS-specific ports and features (Windows Update, Mac App Store, etc).
This in turn has the smartphone route each request, and then replicate the data back to the device. Anything only a PC could truly do (like Mac App Store), is in turn blocked.
Since then you're getting the mobile-formatted versions of sites, and not doing anything that you couldn't also do on the smartphone... if Android Auto isn't counted tethering, PDANet's stealth mode certainly is doing the same thing - basically... especially under Block C rules.
Click to expand...
Click to collapse
crazycarl said:
Can this be done with just ADB or do I need to full root the phone?
Click to expand...
Click to collapse
To enter Android's Shell
Code:
adb shell
requires a rooted Android.
Wait running the command requires a rooted phone?
Ive been able to run the command and my phones not rooted.
Maybe its just not giving me an error explicitly saying I dont have auth to run the command?
jwoegerbauer said:
To enter Android's Shell
requires a rooted Android.
Click to expand...
Click to collapse
I dont think this true. Im fairly certain that i've not rooted my phone yet Im able to connect the USB and bring up the adb shell promp:
Code:
[email protected]:~$ adb shell
a50:/ $
@crazycarl
What you think means nothing to me.
jwoegerbauer said:
@crazycarl
What you think means nothing to me.
Click to expand...
Click to collapse
That's good to know.
So youre saying that the $ adb shell will run on a terminal, accept commands, and issue no notification of failures.
IDK just seems unlikely.
Typical linux envs will notify you if you're got insufficient permissions. So what youre suggesting is an anti-pattern to whats most common.
Now you see my skepticism.
For example:
$ adb shell dumpsys activity
gives appropriate output.
Code:
ACTIVITY MANAGER Freecess (dumpsys activity freecess)
mFreecessManagedPackages --- size 132
-Uid 10192(-)-Idle(-)-Pkg com.amazon.mShop.android.shopping
-Uid 10033(-)-Idle(-)-Pkg com.sec.android.widgetapp.samsungapps
-Uid 10168(-)-Idle(-)-Pkg com.google.android.youtube
-Uid 10032(-)-Idle(-)-Pkg com.samsung.android.app.galaxyfinder
-Uid 10101(-)-Idle(-)-Pkg com.samsung.android.themestore
-Uid 10177(-)-Idle(-)-Pkg com.sec.android.app.chromecustomizations
-Uid 10197(-)-Idle(-)-Pkg com.sprint.care
-Uid 10194(-)-Idle(-)-Pkg com.sprint.ecid
-Uid 10271(-)-Idle(-)-Pkg com.sprint.w.v8
-Uid 10112(-)-Idle(-)-Pkg com.sprint.zone
So what is it @ jwoegerbauer ?
Either I've got a rooted phone and I don't know about it. Or running commands with $ adb shell doesn't require a rooted phone.
@crazycarl
In order to bring it to an end: Yes, i was mistaken, I apologize.
crazycarl said:
I dont think this true. Im fairly certain that i've not rooted my phone yet Im able to connect the USB and bring up the adb shell promp:
Code:
[email protected]:~$ adb shell
a50:/ $
Click to expand...
Click to collapse
You will get limited shell action. I don't think you have SuperUser permission so you can't change anything significant.