Related
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?
Digitizer is broken, but I can see the screen. I need to enable debugging but I have absolutely no touch response.
I know that debugging is enabled in a custom recovery but I need it to be enabled on the os level. Is there a ROM that has USB debugging enabled by default? A backup image of a stock image with usb debugging enable would work too. (I am not trying to enable MTP or pull data, I am trying to establish adb and lunch a program with os running"
I have tried enabling it via terminal in recovery but its not working; I can't seem to find the path to change the value.
Thanks in advance.
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
frankyredz said:
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
Click to expand...
Click to collapse
well your problem is easy...well easier.
unlock the bootloader flash a custom recovery (cwm) you can enable SD card via the recovery and move your files using MTP. search the forum for "how-tos"
Why not use a mouse or keyboard?
ace7196 said:
Why not use a mouse or keyboard?
Click to expand...
Click to collapse
No otg and you need your screen to setup a Bluetooth connection, right?
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
ziddey said:
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
Click to expand...
Click to collapse
No otg without external power*
Better?
ace7196 said:
Why not use a mouse or keyboard?
Click to expand...
Click to collapse
no native OTG, Enabled debugging ROM would solve my problem much easier
ziddey said:
otg http://forum.xda-developers.com/showthread.php?t=2181820
also, use the google. tons of people have busted their digitizers. http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
Click to expand...
Click to collapse
I actually stumbled upon this but only saw the first part. and had the same problem where the value would not stick. Didn't see the second part; will try. Still, a rom that has debugging enabled would be ideal and is originally what I asked for in the op. Nevertheless, thank you.
estallings15 said:
No otg without external power*
Better?
Click to expand...
Click to collapse
LOL. this.
Bump. None of the above has worked. Is there a ROM that adb is enabled by default? CM?
Sent from my Nexus 4 using xda app-developers app
Thread Necromancer requires assistance!
frankyredz said:
I actually have the same exact issue. The screen is smashed to hell, but it still turns on and off. I still get calls, texts, and all other notifications...but the touch screen is totally unresponsive and I can't get to my files through my computer because I can't unlock the phone. If there's anyway around this, I'd much appreciate the help too.
Thanks.
Click to expand...
Click to collapse
Sorry for dredging up a dead post from ages long forgotten, but I was hoping to find some semblance of help here.
I am fully aware of the fact that this is for the Nexus 4, but I'm optimistic in my approach to find answers regarding the absolutely decimated screen and digitizer of my (otherwise undamaged) AT&T Exhilarate (i577) android.
It'll be about a week before I can get in to get them replaced, so I was hoping to at least read the texts that I've since received or scavenge my contacts via [email protected] due to situational intensity ((family member health issues)My Google account does not hold this information), and I've followed all of the setup walk through found here: droid-at-screen.ribomation..com/installation/
My issue now is that I cannot load my device from the [email protected] application, presumably caused by a severe lack of USB debugging enabling.
My phone is not rooted or modded in the least.
Is there any hope for me?
Thanks in advance!~
I was in the same situation with a HTC Sensation.
I had to S-OFF to get superCID and get the screen calibration to work.
But juopunutbear required to be in normal mode and ADB enabled. I finally get it working by installing CWM recovery, which has ADB, and enable the adb debugging.
adb shell
mount -a
(if the following two commands show error "file doesn't exist", don't worry, it's ok!)
rm /data/property/persist.service.adb.enable
rm /data/property/persist.sys.usb.config
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value='1' where name='adb_enabled'";
/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value='1' where name='development_settings_enabled'";
sync
reboot
Click to expand...
Click to collapse
If the sqlite3 command shows error (command not found) then your phone doesn't have sqlite3 installed.
Still, you can do it!
First extract settings.db:
adb pull /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Copy that file to a usb drive or whatever.
Now you need linux. It's ok to use a live Ubuntu DVD, but you need to be connected to internet.
http://www.ubuntu.com/download/desktop
I recommend to use the 32bit version for compatibility.
Usually sqlite3 is not installed by default.
In ubuntu:
sudo apt-get install sqlite3
Click to expand...
Click to collapse
You will be asked for the root password!
Now we can edit the settings.db:
sudo sqlite3 /path_to_your_folder/settings.db
update global set value='1' where name='adb_enabled';
update global set value='1' where name='development_settings_enabled';
.exit
Click to expand...
Click to collapse
Now we have the settings.db changed and ready!
Copy that settings.db again to a pen drive or whatever, go back to windows or keep in linux if you already have a working ADB.
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell "chown system.system /data/data/com.android.providers.settings/databases/settings.db"
adb shell "chmod 644 /data/data/com.android.providers.settings/databases/settings.db"
sync
reboot
Click to expand...
Click to collapse
Done! ADB should work when in starts.
I had to use "mass_storage,adb" because "mtp,adb" or just "adb" didn't work. Thought, the phone was not working in mass storage, but who cares! ADB was!
thanks @dabyd64 , i was in a similar situation of dealing with an htc evita, basically a corrupted rom made the display useless, so had to enable debugging via recovery, I used twrp. And its enabled now.
Thanks @dabyd64!!!! I also was in a similar situation of my Samsung Xcover 2 S-7710. I succesfully enabled the debuging mode
Wow, I'm working with something old... My old Nexus 7 2013 is having touch screen problems so I tried the sqlite3 option. The commands executed fine but now I'm in a boot loop. It's been booting for twenty minutes. Any advice?
Wow this is OLD !
Make a factory reset,that should fix the bootloop .
And then try again?
Morning all,
So here is the deal. Buddy of mine broke his phone last night, I gave him one of my spares and he is keeping that. I took his broken S4.
The screen si dead and the digitizer does not work
Had CWM flashed on it but stock rom when I gave him the S4 initially
I tried every possible way to get usb debugging working without the screen. edited the build.prop and default.prop
change the settings.db no luck
using adb in recovery i was able to flash cyanogenmod 10 as i read it had usb debugging enabled by default
well after the flash and booting the device (using an MHL) i still cant access an adb shell. I'm guessing i have to go through the setup process of cy mod before it kicks on maybe.
so i'm stuck here. now what I was hoping, and I know its a long shot. Could someone maybe make a nandroid of a stock rom, any rom that is rooted. but with vnc or other remote software installed and setup so I can flash and access this device.
I was also going to try to find a TV with CEC support as I heard the MHL will pass them through
If I can convince someone to upload a nandroid for me (I'll provide hosting) anyone have any ideas on controlling this thing remotely. I just need to be able to install arliberator, pair it with my cars deck via Bluetooth and i'll be good to go.
-pete
More thoughts. Having usb debugging enabled is clutch. Just realized, it wont be on my wifi so vnc wont work to well. I know droid vnc and do usb using adb. so maybe thats my best bet
making some progress
Copied the wifi settings from wpa+supplicant.conf from my brothers phone
so the S4 witht he broken screen now connects to my wifi
I installed the droid vnc apk using recovery
also installed it on another phone, setup the way I want
copied the settings folder from the /data/data frolder and copied it to the S4
chmod the folder and files to 777 and set 776 on "androidvncserver" file not sure about that step
cant get vnc to connect. but making progress
made a bit more progress
downloaded fastdroid vnc
pushed it to /data/ in recovery using adb
set 777 as i didt feel like dealing with permissions
made a super simple script to load it and placed in /data/local called userinit.sh or something like that
so it started and I was able to make a vnc connection, but it was all black and didnt accept mouse or key inputs.
i assume this is because it is no longer maintained and is many years aold
tried to do the same with droid vnc server and starting the androidvncserver file.
unfortunatly it never accepted a connection and i'm not even sure if the file starts
need more work
anyone willing to save me all the trouble and get me a nandroid with usb debugging enabled? pretty please! :crying:
Final update. Working
so I ended up placing androidvncserver in /data/
chmod 777 /data/androidvncserver
placed my wpa_supplicant.conf in /data/misc/wifi
chown system.wifi wpa_supplicant.conf
made a userinit.sh and pushed to /data/local/userinit.sh
chmod 777 /data/local/userinit.sh
reboot
connected to wifi, accepted the vnc connection and mouse movement. still a black screen but with the MHL and the mouse. I was able to get ARliberator installed and connected to my appradio2 and configured everything there
done
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
Just checking it there is some way to recover files. I previously rooted it and can't remember if that means there's any way to get at it via ADB or otherwise to recover files before transfering to a new device
Well, if you have ADB working you can just transfer the files.
Or you could use my AdbSync.exe (along with ADB) to backup.
Code:
C:\>mkdir whatever
C:\>adb devices
C:\>adbsync /hcsu /s /v C:\whatever sdcard
ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction
mrbryan said:
ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction
Click to expand...
Click to collapse
You're the second person in a week or so that seems to have this issue and it got me curious. There's a message at the beginning of NookManager about starting WiFi if you want to directly connect with the device via SSH(?) or ADB. I've always ignored it but I just tried it to see what would happen. After you elect to start WiFi (your NST must have been known to your network beforehand, password entered, etc.), you are given the option to start either SSH or ADB (the IP address is displayed at the top of the screen).
When I chose ADB I was then able to start up ADB on my PC and connect to the IP address shown on the NST screen. Of course.....if your screen is broken........Maybe you know the IP address of your NST already or could find it by starting WiFi and then consulting your router?
Anyway, the advantage with NookManager is that everything is done with the side hardware buttons. If you can't read your screen at all I can see that even that would be a problem, though. If you have some partial display, you might be able to limp along until you have ADB connected and then handle everything from your PC. Or I could supply you with a button-push sequence to try.
To just get this working you can make a NookManager card--no need to make the updates I described elsewhere.
thanks so much for the suggestion. I'll have to think that through and whether I have my current wifi set up ( edit: in the nook already).
maybe I can hack around in the scripts for nook manager in case I can set it to go right to the ADB on boot and inject a wifi name & key too
Get an image for the old noogie and put it on an SD card.
Boot up, you should have ADB.
Or do the whole OmapLink procedure and boot from there.
Or connect to the 1.8V UART root console inside the case.