Related
This is for all who are not brave enough to root your phone, but want tethered internet from your Android phone to your laptop or desktop.
Android free USB tether.
The following procedure will allow you to access the Internet through one computer using your Android phone. Rooting is not required. Uses Android App "Internet Sharer" by JADS, but you can use any Android Proxy Server, with slight modification.
This is not a Wi-Fi hotspot, and it is not a Bluetooth PAN.
Always make sure you know what your doing, before you do it. I’m not responsible for your internet not working on your computer. I’m also not responsible for your phone bill.
You assume all risk.
I recommend you research “Internet Sharer JADS“, “proxy server”, “port forwarding”, and “Android ADB” before executing the procedure.
Procedure Tested on:
Android: Sprint HTC EVO 2.2 non-rooted
Computer: Windows 7 laptop, Wi-Fi
High level view:
1. Setup proxy server on Android phone
2. Use Android phone USB debuging port and Android SDK on computer, to forward computer’s localhost port 1080 (SOCKS5) and 8080 (HTTP) to Android phone.
3. Setup browser to point to proxy server on Android phone.
Detailed setup:
Install ADB drivers on computer:
1. You need to install the ADB driver for you phone.
- HTC this can be done by downloading the HTC Sync program. You can remove HTC Sync, just don’t remove the “HTC driver Installer”.
- Others follow instruction on Internet.
2. Connect your phone to the USB port on your computer.
Install SDK on computer
1. Download Android SDK from developer.android.com.
2. Unzip the SDK file to the following location: C:\Android\
Android Setup:
1. Set USB debug. Go to Settings -> Applications -> Development ->USB debuging (Make sure this option is checked). This will allow the SDK program ADB to talk to the phone.
2. Download from the Android Market the program “Internet Sharer” by JADS Limited. This is a free program. This program is a HTTP and SOCKS 5 proxy server.
3. Launch the “Internet Sharer” program.
Computer Setup:
My recommendation is to use Firefox as the program you use to access the Internet, as it allows you to setup the proxy and DNS proxy. If you require more than the plain Internet, such as Flash, and other programs that use the Windows connection settings you’ll need to change the proxy on the IE browser. IE does not support HTTPS, using this method.
Proxy server setup:
1. From a cmd window run the following commands:
c:\Android\android-sdk-windows\tools\adb forward tcp:1080 tcp:1080
c:\Android\android-sdk-windows\tools\adb forward tcp:8080 tcp:8080
Note: Use the path that is relevant to the ADB command.
Firefox setup:
1. Download and launch Firefox.
2. Under Tools -> Options -> Advanced -> Network -> Settings.
3. Select Manual proxy configuration.
4. All Proxys are blank, except SOCKS Host: is “localhost”, no quotes, Port 1080. Select SOCKS v5.
5. Ok out of the Options window.
6. In the URL text box, type in “about:config”, click the “I’ll be careful, I promise!” button.
7. In the Filter text box, type in “dns”
8. Locate the “network.proxy.socks_remote_dns” option, click it until it’s value is “true”.
9. The procedure is complete.
Internet Explorer 8 (IE):
1. Go to the LAN settings window. Select “Tools” -> “Internet Options” -> “Connections” -> “LAN settings”.
2. Un-check “Automatically detect settings,. You can possibly leave this checked if your unsure of the integrity of this procedure.
3. Check “Proxy Server box”, click on “Advanced” box.
4. Enter HTTP: “localhost”, Port 8080, and Socks: “localhost”, Port 1080.
5. Ok out of the “Internet Options” window.
6. Procedure is complete.
Note: IE does not support HTTPS,using this method, let me know differently.
Test configuration:
1. Make sure the Android “Internet Sharer” application is running.
2. The Proxy server setup is done with the adb forward commands ran.
3. Disable the Internet interfaces on your computer.
4. Access the Internet, via your proxy server enabled browser, or computer program.
5. On the “Internet Sharer” screen you will see text scrolling. If SOCKS server is being used, it’ll pre-pend SOCKS to the IP being pulled. If HTTP server is being used, it’ll pre-pend GET/PUT to the lines.
Hulu:
Requires IE setup, as the Flash proxy is set by the IE proxy settings. You can use Firefox to launch the URL.
HTTPS sites
Works fine on Firefox, using SOCKS 5 proxy. I haven’t had success on IE, but could be possible with PAC???
Common Issues:
Not connected to Internet…
-Make sure that IE has a HTTP proxy setup, port 8080 on the Proxy Server.
-For Firefox, make sure that the DNS Remote setting is TRUE.
Backout:
If for some reason it doesn’t work for you do the following:
1. Remove the proxy settings from Firefox, IE, and any other program you may have set proxy settings on.
2. Remove the proxy server from the Android Phone.
3. The SDK can be removed by deleting the SDK directory.
4. ADB driver can be removed using the standard windows Control Panel Software Uninstaller. Uninstall HTC driver Installer.
Good luck!
romah said:
Proxy server setup:
1. From a cmd window run the following commands:
c:\Android\android-sdk-windows\tools\adb forward tcp:1080 tcp:1080
c:\Android\android-sdk-windows\tools\adb forward tcp:8080 tcp:8080
Note: Use the path that is relevant to the ADB command.
Firefox setup:
1. Download and launch Firefox.
2. Under Tools -> Options -> Advanced -> Network -> Settings.
3. Select Manual proxy configuration.
4. All Proxys are blank, except SOCKS Host: is “localhost”, no quotes, Port 1080. Select SOCKS v5.
5. Ok out of the Options window.
6. In the URL text box, type in “about:config”, click the “I’ll be careful, I promise!” button.
7. In the Filter text box, type in “dns”
8. Locate the “network.proxy.socks_remote_dns” option, click it until it’s value is “true”.
9. The procedure is complete.
Click to expand...
Click to collapse
Worked like a charm
Want to add this : Even works to share an already established wifi connection.
During my vacation, my hotel only provides me one free wifi access that I configure on my phone. Using this method allows me to share the free wifi connection with my mac book pro, thanks
Just asking
romah said:
Proxy server setup:
1. From a cmd window run the following commands:
c:\Android\android-sdk-windows\tools\adb forward tcp:1080 tcp:1080
c:\Android\android-sdk-windows\tools\adb forward tcp:8080 tcp:8080
Note: Use the path that is relevant to the ADB command.
Click to expand...
Click to collapse
Is this used to forward ports? Can I forward minecraft ports using this? thanks!
Look up the adb forward command if you want specifics, but yes.
That procedure would be too complicated for me. I used to use the easytether app. I always held on to the version that came out just before the one in which they started making people pay for it. I always made sure I kept a backup copy of that app and program at all times. I don't use it anymore because I am another phone now.
I was to B&N today, read few books in store (on nook)
Came home, tried to connect:
adb unable to connect...
run dropbear - unable to ssh
rebooted nook via terminal
adb unable to connect...
Scratched head…
rebooted nook again via terminal
adb unable to connect...
Did basic adb troubleshooting:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb unable to connect...
stop adbd
adbd &
adb unable to connect...
netstat
showed listening (with adbd running)
127.0.0.1:5037
0.0.0.0:5555
rebooted nook via terminal
rebooted PC…
adb unable to connect...
put noogie SD, reboot, check uRamdisk – same size & timestamp
removed noogie, off/on - connected right away!
I’m puzzled…
I saw few times, after 2-3 days of reading adb is unable to connect, but reboot fixed it always.
What was different this time?
“Cold reboot”?
I spend like 30min and feel like an idiot right now…
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Adapt0r said:
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Click to expand...
Click to collapse
I did it as well before every adb connect, thought it not worth to mention.
Naturally, "rebooting PC" should reboot adb server too, right?
But it didn't help either...
If you see this issue again, just try toggling ADB Wireless On/Off and it should reset anything on the devices side. Also I've noticed that sometimes and completely random from what I can tell "USB Debugging" will get unchecked, which will mess with ADB access via USB.
Disabling/Enabling ADBwireless sometimes may help.
Maybe a stupid question: Do you have a firewall running on your pc?
digiflash said:
Disabling/Enabling ADBwireless sometimes may help.
Click to expand...
Click to collapse
won't it be the same as below or it does more?
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
digiflash said:
Maybe a stupid question: Do you have a firewall running on your pc?
Click to expand...
Click to collapse
Always
I did check it too. It was nothing worth to mention.
abd attempted to connect - got nothing back (timeout)
on NST adbd was listening, I was able to access gmail.
I can ssh neither, and dropbear was listening too.
Looks, in fact, like firewall on NST was blocking all incoming connection.
That's why I wrote "Scratched head…" - which means I checked pretty much everything.
Could somebody explain, what is the major difference for NST between:
reboot (hot reboot) & shutdown/start (cold reboot)
Or more precisely for the latter:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
ApokrifX said:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
Click to expand...
Click to collapse
Cannot connect today at all. Cold reboot doesn’t help anymore...
Did some more tests (including ADBwireless):
I cannot ping [nook IP] from my computer
I can ping [nook IP] from router.
From PC
>telnet [nook IP] 5555
Connecting To [nook IP]...Could not open connection to the host, on port 5555: Connect failed
From router:
telnet [nook IP] 5555
Connection didn’t timeout (i.e. it does connect!)
Again, looks like something on Nook blocking connections from all IP, except from default gateway (i.e. router)
Question: Does rooting process unblock connections from other IPs?
About Disabling/Enabling ADBwireless:
Before running ADBwireless
netstat
127.0.0.1:5037
0.0.0.0:5555
netstat -tapn doesn’t work
stop adbd
both above disappear from netstat
start adbd
both show up
run ADBwireless
get message: ADBwireless is off
pushed button, message changed to: adb connect [nook IP]:5555
(adb connct didn’t work)
Switch to terminal,
netstat
127.0.0.1:5037
I.e. no more: 0.0.0.0:5555
Subsequent "stop adbd"/"start adbd" changes nothing:
netstat
127.0.0.1:5037
I was wondering what ADBwireless supposed to do then?
Could somebody check from his nook what netstat shows, please?
Nook can connect to internet (gmail, market) + netstat shows all outgoing connections…
What else can I try?
I guess, I can switch to adb usb…
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Adapt0r said:
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Click to expand...
Click to collapse
One box is XP with Outpost firewall (abd set to full trust).
Another win7 (FW policy – allow outgoing connections + few exceptions).
I’m Win developer/admin and Linux(CentOs) admin.
I’m complete noob when it comes to Linux non-shell related programming.
Router runs DD-WRT.
As of now I switched to uRamdisk_1_1_rooted_usb.
When I run dropbear, I see it listening on 22, but cannot ssh still.
That’s all I guess…
Could you do one test for me please?
If your NST runs uRamdisk_1_1_rooted_wifi:
Could you ping you NST from you box
If not - could you do same from your router/AP?
1. I don't have uRamdisk_1_1_rooted_wifi on my NT and can't test it.
2. adbWireless works on my Win 7 and Mac the same way. Both comps have firewalls running and both are on the same network. I can connect and ping NT.
Just for clarification I will describe how it works on my setup:
- I start adbWireless on NT,
- it asks for root permission if it for the first time and I grant it
- then shows fat button on the screen and says adbWireless is off
- I push the button
- it says adbWireless is on, from your computer run
adb connect 192.168.15.112:5555
At this point I can ping IP address and run adb shell.
I've rooted NT for purposes of software testing and customization. I did it twice with older and newer Nooter and did not find any noticeable differences.
Let me know if you want some other tests or info.
Adapt0r said:
I can connect and ping NT.
…
At this point I can ping IP address and run adb shell.
Click to expand...
Click to collapse
To clarify (trying to get a setup as simple as possible):
We connected NST to our home wireless network and it gets IP.
We didn’t touch adbWireless yet!
Now do two tests, please:
1. From NST we ping gateway or "another device on same network", (providing it let us).
2. From "another device on same network", ping NST.
What do you get?
I thought, adbWireless just configure adbd for IP connection (as opposite for USB one) and starts it - nothing else.
If #1 works, but not #2,
and #2 starts working after you “hit adbWireless button”, than adbWireless does more then I wrote above…
Sorry, I didn't have time to do your test at home. I'll try today.
I think you are correct, adbWireless does configuration of connection by executing something like this:
Turning On:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Turning Off wifi and start listening on usb
setprop service.adb.tcp.port -1
stop adbd
start adbd
Cheers!
Edit:
Ping NST_ip_address from PC works fine.
Since I don't have terminal installed I could not test reverse pinging.
Ouch…
Just figured out:
1: I press “big red button” in adbWireless.
2: I push back button
And it pushed adbWireless into background.
If it’s the same as turning it (adbWireless) off,
it’s possible, that adbWireless reset adbd service to use USB.
Thus there is nothing listening on 5555 when I run netstat in terminal on NST.
Who’s with me?
Should be east to test:
press “big red button” in adbWireless.
I push back button
try to connect
ApokrifX said:
Ouch…
Click to expand...
Click to collapse
Updated router firmware - I can ping nook and ADB over wireless works too.
Not sure thought, if it was wireless channel problem.
I've read somewhere, some NST firmwares doesn't work on high channels or certain combined modes - like works on A+B, but not A+G
Apparently, NST firmware 1.1.2 was targeted to solve some of these issues.
PROBLEM SOLVED.
I didn't have the proper folder for the adb.exe.
-----
I have a similar problem: I recently rooted my nook simple touch with touchnooter 2.1.31, and all seems well but I can't connect to the adb wireless. IP is 192.168.0.6:5555 according to adb; I can ping from my Win XP computer if I use 192.168.0.6, but not if I add the 5555, but I just can't connect to the ereader. Wireless connections seem fine otherwise. I've tried shutting off and one the wireless adb.
I'm a complete beginner in this. On the reader, the screen has this:
"from your computer run: adb connect 192.168.0.6:5555"
This suggests that I can't simply use a firefox browser to connect? I tried using the windows cmd box, but windows indicates it doesn't know what 'adb' is. Then I found a website about adbwireless: http://theunlockr.com/2011/04/12/how-to-connect-to-your-android-device-through-adb-wirelessly/
and installed Adroid SDK Tools as indicated. When I use the cmd window, go to the proper sdk tools subfolder, and type 'adb connect 192.168.0.6:5555', windows still insists it doesn't recognize 'adb'
Please help!
try adb.exe
Meter 13,
Thanks for the reply. I added a pre-script to my op. I had created a bat file to move to the proper folder but had realized that the adb.exe had been moved to the platform-tools subfolder from its old location in the tools folder. Once I realized this, all worked well - connected to my nook, and used adb to install an apk file.
Bob
Just a note:
Ping isn't the usual TCP/UDP stuff, so there are no (port) numbers on the end.
ping 192.168.1.27
ADB uses TCP and a port number but it usually defaults to 5555
adb connect 192.168.1.27
adb connect 192.168.1.27:5555
You can also telnet to check if you can connect to the nook via TCP and port 5555
telnet 192.168.1.27 5555
(Note: If this works it will tell you that you are connected, but you can't do anything because ADB is a binary protocol.)
I had the same problem, turns out the correct drivers weren't installed. Ive downloaded HTC sync from HTC.com. I installed it and removed HTC sync afterwards. The drivers should stay there. Now reconnect your phone and try "adb devices" Before ADB wouldn't recognize my device but now it does. Tried to "adb backup -all" again, and it worked instantly.
Maybe this solves the problem?
You could try going back to a stock /boot partition.
I run my nstg rooted with the addition of about 8 files (su, xbin, busybox in system, adb wireless in /data plus a launcher) when I first root.
with the nstg, at least, I don't actually need the modified kernels - adb connects from my computers to the nstg, I simply don't have a root shell when I first connect.
This is fixed by doing an
su
once I'm in
Might be worth trying a restore of just partion 1 from your backup?
I have rooted my Nexus 7. Currently, the only way to change my MAC address is the following:
Code:
$ echo -n <MAC> > /persist/wifi/.macaddr
Using busybox ifconfig seems to work because new HWaddr is shown but in fact it doesn't - Settings->About tablet->Status shows old Wi-Fi Mac address. Additionally I cannot connect to AP any more. OpenWRT says:
deauthenticated due to local deauth request
Click to expand...
Click to collapse
I can write a script to automatically write new MAC to /persist/wifi/.macaddr and reboot, no problem, but I would prefer to avoid rebooting.
Kernel version 3.4.0-g03485a6, Android 4.4.4, Nexus 7 2013 Wi-Fi only.
Is this possible?
Has anyone ever got this to work? I'm searching on a way to have my MAC address changed upon booting the device and keeping it that way. Using ifconfig/busybox just allows you to change the MAC on that "boot session" and reverts back when you disconnect from an AP. I want to change my "stock MAC" from the get-go so that if I disconnect from an AP, it wont go back to the actual one. There is no /persist/wifi dir on my Nexus 7. Anyone who has done this before who can tell me how to do it?
Hi,
I just had the problem of being behind a Http/Https proxy and there is currently no option available to set this on the fire TV Stick.
Android offers this option at least since version 4 by default but they must have deactivatetd this feature intenionaly (region rights and such things).
But it is still possible.
1. Setup your AFTVS on a normal Wifi with internet connection ( if not already done)
2. Activate Apps from unkown sources and ADB
Settings --> System --> Developersoptions
3. Make sure your are connected to the same network as your pc.
4. Sideload following app:
Code:
AndroidProxySetter:
github.com/jpkrause/AndroidProxySetter/releases
How To sideload:
aftvnews.com/sideload/#more-7959
5. Start the App over adb on your pc:
Code:
//connect to device
adb connect 192.168.1.184:5555
//check the connection
adb -s 192.168.1.184:5555 get-state
//start app
adb -s 192.168.1.184:5555 shell am start -n tk.elevenk.proxysetter/.MainActivity -e host 192.168.56.1 -e port 8080 -e ssid PrivateWifi -e key Passw0rd
Where u would replace the device ip, host, port, ssid and key with the settings of your network.
Please mind that ur on a linux based system and everything is case sensitiv.
For more options look here:
Code:
github.com/jpkrause/AndroidProxySetter
5. Now, if everything is fine some little popups will be displayed and at last it should say connected.
6. Going back to the home screen and Done.
Known issues: After some major updates you will need to set the proxy again, so just repeat step 4
It should also run on the normal AFTV but i got none so i can't test it.
All Credit goes to JPKrause who wrote that little app, I just happend to find it
Update 21.06.2016:
With Fire Os 5.2.1.0 it seems like you cant start adb on the device itself so you have to start the proxysetter over adb on your pc.
This "new" way doesnt require to install the terminal emulator anymore and its actually more comfortable.
best regards N4b0
how to setting up proxy using pac file?
N4b0 said:
Update 21.06.2016:
With Fire Os 5.2.1.0 it seems like you cant start adb on the device itself so you have to start the proxysetter over adb on your pc.
This "new" way doesnt require to install the terminal emulator anymore and its actually more comfortable.
best regards N4b0
Click to expand...
Click to collapse
how to setting up proxy using pac file?
zcrself said:
how to setting up proxy using pac file?
Click to expand...
Click to collapse
Hi,
well I guess the AndroidProxySetter doesn't cover any way to use PAC files.
But you can actually open your pac file with an editor of your choise and extract your proxy settings from the containing functions.
bg N4b0
Hello, I have this working on a Fire Stick, I ran the commands on a Fire TV and is not working. Anyone has this working on a AFT (no stick)?
Any help is appreciated.
Thanks.
edit: it not working anymore on my fire tv stick, I see the connection going to the proxy but in the screen it says invalid_geo_ip, somehow they manage to get my original ip. My gf is american, and we are abroad, this was the only way to watch amazon content. Sad. I'll try to get a vpn instead, but this proxy setting was easy configuration.
Hi mastodonian,
in my case it still works like a charm on the AFTVS. I just tried it over a vpn that my home server provides, but the tv stick then says something about geo restriction even though its a german vpn. I suppose they are doing some kind of deep packet inspection or they got an ip blacklist.
Can't say but eventually the proxy you are tring to connect uses internally a vpn or is on a blacklist.
Cheers n4b0
can someone help me with this one im a bit slow on following instructions especially codes like these
gjhech said:
can someone help me with this one im a bit slow on following instructions especially codes like these
Click to expand...
Click to collapse
its pretty simple just do the following
Download adblock plus and install it on your firestick - use the power of google or an app store on your fire stick to get it
Download this app to your pc - https://github.com/jpkrause/Android...d/v0.1.3-alpha/proxy-setter-release-0.1.3.apk
Adb this app to your firestick by (assuming you have adb installed if not google howto)
enable adb on the fire stick in dev options if not already done so
adb connect 192.168.1.1 (change the ip address to your firesticks)
adb devices (you should see a list of devices connected if adb is working with your firestick ip address and port number)
adb install (then drag and drop the apk file into the command window - This will auto complete the path of the apk to save you entering it manually)
once the apk is installed
Code:
adb -s 192.168.1.1:5555 shell am start -n tk.elevenk.proxysetter/.MainActivity -e host localhost -e port 2020 -e ssid MyWifiName -e key MyWifiKey
Starting: Intent { cmp=tk.elevenk.proxysetter/.MainActivity (has extras) }
Change the ip address in the above code to your firestick ip address - the numbers after the : is the port address - it should match what you saw when you typed adb devices
Change the ssid to your wifi name and key to your wifi password
you will get some pop up windows on the firestick telling you if it has succeeded or you have errors
next open adblock plus and enable adblocking
restart the firestick
open adblock plus again and you shouldnt see the warning about it cannot manually set the proxy at the top of the screen
load up an adblock test website to test its working
Thank you for making this method clear and easy. However, even though I get the successful messages and the proxy chnages to localhost and the Port to 2020, Ad Block Plus still shows the "please configure manually" message after reboot.
Testing on some apps, the ads are most definitely not blocked!
Any suggestions?
Thanks for malking this app , I just have a problem , netflix connects directly and not through the proxy , any idea how to force connecting through proxy ,
It works perfect
I bought FireStick today and it wouldn't let me connect to Amazon as my ISP has made mandatory to use HTTP proxy.
I followed your step wise instructions and it worked. Thanks a ton
Hello,
Thank you for this! One issue: I'm unable to disable to proxy via adb... is there a specific way to do this? I've attempted to uninstall the apk file and clear data, but it still remains connected to the host.
Any assistance would be greatly appreciated!
pdesai91 said:
Hello,
Thank you for this! One issue: I'm unable to disable to proxy via adb... is there a specific way to do this? I've attempted to uninstall the apk file and clear data, but it still remains connected to the host.
Any assistance would be greatly appreciated!
Click to expand...
Click to collapse
Hi,
I actually had to do this myslef recently so what i did was just remove the network via the GUI and add the network again.
If you have to do this over ADB you should try to remove the network and add it without proxy flag
Cheers N4b0
xbarsasy said:
Thanks for malking this app , I just have a problem , netflix connects directly and not through the proxy , any idea how to force connecting through proxy ,
Click to expand...
Click to collapse
Well I have to clarify i did not make this app i just found it and put it to good use
On the issue i cant really say how to force him using the proxy. This method just configures the android intigrated Wifi network stack that supports proxys since 2.X is suppose. If an app like Netflix detects this, then u need an other method.
For windows i got an app called Proxifier, but until now i didnt find anything similar for android.
Only alternativ solution for your problem I can think of would be to configure your Accesspoint with a VPN on a second virtual network (well that's how i would do it).
Cheers N4b0
Hi All,
-I posted as a guest but didnt see my message, so posting again. sorry if it will be duplicate-
After Fire OS 6.2.1.3 upgrade, this wonderful proxysetter app doesn't seem to work anymore. I tried both 0.1.3 and 0.2 versions and it can not set the proxy.
Poareq said:
Hi All,
-I posted as a guest but didnt see my message, so posting again. sorry if it will be duplicate-
After Fire OS 6.2.1.3 upgrade, this wonderful proxysetter app doesn't seem to work anymore. I tried both 0.1.3 and 0.2 versions and it can not set the proxy.
Click to expand...
Click to collapse
Facing the same issue, unable to connect to Amazon after October update.
Any workaround available?
Not working for me too
uj812 said:
Facing the same issue, unable to connect to Amazon after October update.
Any workaround available?
Click to expand...
Click to collapse
I recently bought a fire tv stick. But unfortunately unable to make http proxy work. Kindly advice.
Solved... I think
phildani7 said:
I recently bought a fire tv stick. But unfortunately unable to make http proxy work. Kindly advice.
Click to expand...
Click to collapse
Not sure if anybody is still interested in this, but I recently uninstalled the apk and was unable to install it again getting the following error: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]
The solution is simple! The latest version of the FIreTV OS includes a proxy setting!
Just follow Step 1. in the instructions here: Blocked
The original instructions are posted on the Amazon appstore -> Appstore Blogs -> Viewing Secure (SSL/HTTPS) Traffic From Your App on Fire TVs Running Fire OS 6 on November 02, 2018
Since I've been blocked from posting a URL, here are the slightly modified instructions:
Setting a proxy on Fire TV
Bring up the Developer Tools Menu by one of the following two ways:
Remote: 1) Press and hold the Select and Down buttons for five seconds release and then 2) Press the menu button
ADB: adb shell am start -n com.amazon.ssm/.ControlPanel
Select Network Proxy
Select Manual
Enter your proxy IP address
Enter your proxy port
Click Save
Enjoy!
Hi All,
These proxy setting were working for me until the last update on OS 6.x and OS 7.x. The Developer setting app crashes on selecting save on the Network settings and the IP/port info is not saved.
Is someone else facing same issue.. Any work arounds?
Try this. It worked for me.
Use this .apk AndroidProxySetter. Install and follow the commands. It will route Network traffic to Charles proxy.
https://github.com/manadream/AndroidProxySetter
HI DOES Anyone know how to enable RNDIS + DM + Modem mode?
i could access it on Stock rom but cannot on Custom rom is there a way to do it through Terminal mode? if so how please
anime12345 said:
HI DOES Anyone know how to enable RNDIS + DM + Modem mode?
i could access it on Stock rom but cannot on Custom rom is there a way to do it through Terminal mode? if so how please
Click to expand...
Click to collapse
Hi, I've used RNDIS (sharing PC's internet to phone) on my own phone (huawei honor 4c, Android 6, ROOTED!) but I believe the basics are the same. Generally to have RNDIS working (you can share your pc's internet to your phone) you must do the following steps:
1. connect phone to PC via USB cable & Install USB drivers
2. select RNDIS mode : (in my case) Settings > Developer options > Select USB configuration > RNDIS (USB Ethernet)
3. on the PC: share your internet connection to RNDIS connection (Note that windows 7 & higher uses 192.168.137.0 IP range for sharing connection, so you must use this range on your phone)
4. set an IP address on RNDIS dev & bringing it up (type in terminal emulator: ifconfig 192.168.137.2 rndis0 up)
5. set the default gateway for your phone (type in terminal emulator: route add default gw 192.168.137.1)
6. set DNS for your phone (refer to this thread for a complete guide, because setting DNS methods usually depends on phone rom & android version), I used this command & it answered me thanks to GokulNC:
Code:
ndc resolver setnetdns rndis0 <dns ip from my internet> 8.8.8.8
Good Luck!
hosseinb said:
Hi, I've used RNDIS (sharing PC's internet to phone) on my own phone (huawei honor 4c, Android 6, ROOTED!) but I believe the basics are the same. Generally to have RNDIS working (you can share your pc's internet to your phone) you must do the following steps:
1. connect phone to PC via USB cable & Install USB drivers
2. select RNDIS mode : (in my case) Settings > Developer options > Select USB configuration > RNDIS (USB Ethernet)
3. on the PC: share your internet connection to RNDIS connection (Note that windows 7 & higher uses 192.168.137.0 IP range for sharing connection, so you must use this range on your phone)
4. set an IP address on RNDIS dev & bringing it up (type in terminal emulator: ifconfig 192.168.137.2 rndis0 up)
5. set the default gateway for your phone (type in terminal emulator: route add default gw 192.168.137.1)
6. set DNS for your phone (refer to this thread for a complete guide, because setting DNS methods usually depends on phone rom & android version), I used this command & it answered me thanks to GokulNC:
Code:
ndc resolver setnetdns rndis0 <dns ip from my internet> 8.8.8.8
Good Luck!
Click to expand...
Click to collapse
I know this is 4 years ago but I've been pulling my hair out trying to do this in reverse. I have Lenovo Yoga 2 Pro running Android 9 x86 (Bliss 11.13 x64). It's rooted and the phone is Android 8.1 that is not rooted. I want use the phone as my wifi because the Yoga has a broken wifi card. The phone doesn't support USB tethering using wifi, only cell data. I use PDANet in Windows fine but it doesn't support USB tethering from Android to Android (to my knowledge). You can turn on RNDIS mode in Developer Options on the phone. Is this possible without rooting the phone?
i_guana said:
I know this is 4 years ago but I've been pulling my hair out trying to do this in reverse. I have Lenovo Yoga 2 Pro running Android 9 x86 (Bliss 11.13 x64). It's rooted and the phone is Android 8.1 that is not rooted. I want use the phone as my wifi because the Yoga has a broken wifi card. The phone doesn't support USB tethering using wifi, only cell data. I use PDANet in Windows fine but it doesn't support USB tethering from Android to Android (to my knowledge). You can turn on RNDIS mode in Developer Options on the phone. Is this possible without rooting the phone?
Click to expand...
Click to collapse
'dun' option in APN settings. Pretty much make a new APN and copy everything exact and then add dun to APN type.
anime12345 said:
HI DOES Anyone know how to enable RNDIS + DM + Modem mode?
i could access it on Stock rom but cannot on Custom rom is there a way to do it through Terminal mode? if so how please
Click to expand...
Click to collapse
On my Samsung A51, I can enable RNDIS + ADB mode by dialing *#0808# and choosing from the menu.
Dr Doppio said:
On my Samsung A51, I can enable RNDIS + ADB mode by dialing *#0808# and choosing from the menu.
Click to expand...
Click to collapse
*#0808# are working with Samsung devices.