Develop Bugs

Use TP2 as Modem without administration rights

Hi, i work on an Notebook without administration rights and i want use my TP2 to connect to the the internet. But i can't install ActiveSync or the necessary drivers, because i do not own any administration rights.
I tried the WMWifiWouter Software and it works, but Wifi need to much energy.
Has anybody another idea?

Sketch85 said:
Hi, i work on an Notebook without administration rights and i want use my TP2 to connect to the the internet. But i can't install ActiveSync or the necessary drivers, because i do not own any administration rights.
I tried the WMWifiWouter Software and it works, but Wifi need to much energy.
Has anybody another idea?
Click to expand...
Click to collapse
i use htc wifi router and plug my device into computer usb port for power. my computer will ask to install drivers and i just hit cancel and it will charge my device and my device will provide wireless internet access

yes, i tried, but i get the info that the charging power is not enough ... so in the course of time my battery emptied out

root without USB

Is the anyway to root the evo WITHOUT THE USE OF USB..I ask bcuz my usb port is broken on the phone..my bootloader is 2.18 locked...help plz

If the problem is that you need to use ADB (Android Debug Bridge) without connecting through USB, there's a thread about connecting over wifi:
http://forum.xda-developers.com/showthread.php?t=623828
I haven't tried it myself, but you should be able to use "adb push" and "adb pull" to move file on and off the device.

weefbellington said:
If the problem is that you need to use ADB (Android Debug Bridge) without connecting through USB, there's a thread about connecting over wifi:
http://forum.xda-developers.com/showthread.php?t=623828
I haven't tried it myself, but you should be able to use "adb push" and "adb pull" to move file on and off the device.
Click to expand...
Click to collapse
But will this help unlock bootloader (s-off)?

As long as your root method uses fastboot, you should be able to use the wifi technique to run all the commands you need. There are a lot of guides for rooting your phone on the forums, just look around.
How do you even charge your phone if the USB port is broken, anyway? Do you take the battery out

weefbellington said:
As long as your root method uses fastboot, you should be able to use the wifi technique to run all the commands you need. There are a lot of guides for rooting your phone on the forums, just look around.
How do you even charge your phone if the USB port is broken, anyway? Do you take the battery out
Click to expand...
Click to collapse
I have multiple batteries & those wall mount battery chargers......& that method in the link u provided is not gona work cuz.It says it must be hooked up by the USB at least one time before it can be done ....I appreciate the help

Can no longer connect via ADB

I had it all set up correctly and it worked fine both by USB and TCPIP. At some point in the last day or two this stopped working. I've done a complete reinstall of the SDK on my desktop and followed the instructions here https://devs.ouya.tv/developers/docs/setup
When I do adb devices I just get nothing. adb connect xx.xx.xx.xx gives nothing as well.
When I try to run adb from a terminal emulator on the unit I can start or stop the server but any other adb command results in a 'device not found' message. This message is preceded by some two or three digit word but since my TV crops the image I cannot tell what it says. so it is something like '##r: device not found'
Does anyone have any idea on what I need to do to get ADB working again?

Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2

TadeoNYC said:
Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
There aren't any drivers involved here yet. Nothing happens at all when I plug the system in. No devices are detected, correctly or otherwise.
I'm starting to think the micro usb port is just physically broken. I've tried multiple cables, restarting. Connecting other android devices to my desktop which work fine.

could be the port. I have a heck of a time plugging mine in sometimes. it's like the hole in the casing is just a bit bigger than the actual plug, and I have to fumble around for it. I mostly leave the microusb connected all the time now.

Oh!lol.
That happened to me as well. The micro usb port is deeper than normal. My Samsung plugs did not work,I was able to use one from my Kodak pocket video cam.
Sent from my SCH-I535 using Tapatalk 2

Ok, so I'm trying to just adb tcpip working now to bypass the usb issue. I installed an SSH server and I'm getting this
[email protected]:/ $ adb kill-server
[email protected]:/ $ adb tcpip 5555
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $

Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.

beowolfschaefer said:
Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.
Click to expand...
Click to collapse
If you have wireless adb enabled the way to control it so it does not shut down the micro usb port debugging , find the wireless adb .Apk here on xda in the nook color general section and install it then you will beable to open the app and toggle it back and forth to get micro usb debugging back.

My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?

Broomfundel said:
My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?
Click to expand...
Click to collapse
Did you set up adb over wireless?

tcollum said:
Did you set up adb over wireless?
Click to expand...
Click to collapse
I had done but. But it stopped working some time after, and I have not managed to get it going since. Would it stop wired at the same time? Even so would it not have been reset by the factory reset?
Either way, Ill set it with an ethernet cable and see if the flaky wifi was why adb over wifi did not work.
I'm sure a workable solution will turn up. Just disappointed.
Ill report back.
Thanks
Update: Thanks for your help. I tried over wifi and no joy. But ethernet is working. So just got to sort out the flakey wifi now.
Thanks again.

Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta

For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!

HaYNigloo said:
For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!
Click to expand...
Click to collapse
It's also available through the f-droid app.
Sent from my GT-P3113 using Tapatalk 4 Beta

TadeoNYC said:
Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
My wifi works great. unless i try to login to google.

Look here: https://devs.ouya.tv/developers/docs/setup
They changed the device ID, you need to do step 5-6.
More info here: http://www.ouya.tv/devnews.html

no micro-usb connection after tcpip setup

I have a KS ouya. i have rooted it before, but the stupid auto updates got the best of me a couple times.
i've done it the same thing every time-
connect to micro-usb, turn it on, install the drivers, get adb working, set up the tcpip, install superuser, lucky patcher, etc.
this time though, after I set up the tcpip, it will NOT connect via usb again. windows xp no longer recognizes it.
no luck even after tcpip disconnect, adb usb.
any insight?

ArdDarvis said:
I have a KS ouya. i have rooted it before, but the stupid auto updates got the best of me a couple times.
i've done it the same thing every time-
connect to micro-usb, turn it on, install the drivers, get adb working, set up the tcpip, install superuser, lucky patcher, etc.
this time though, after I set up the tcpip, it will NOT connect via usb again. windows xp no longer recognizes it.
no luck even after tcpip disconnect, adb usb.
any insight?
Click to expand...
Click to collapse
You could try flashing a new rom or maybe a factory reset (amusing you are backed up).

i tried a couple things. I pulled the build.prop again and removed the tcpip entry, then pushed it back on. even after that I can still connect tcpip.
i also tried a factory reset. everything LOOKS factory, but i can still connect through tcpip and NOT through usb at all.
I have no idea wtf i'm going to do, but i'm going to figure it out and do it.

Install the app Wireless adb. It has resolved this issue for most people.
Sent from my GT-P3113 using Tapatalk 4 Beta

TadeoNYC said:
Wireless adb.
Click to expand...
Click to collapse
thank you very very much. my problem was that I enabled wireless adb, then rooted. when it didn't connect via wire, I factory reset it. this unrooted it, but left me with only wireless adb. I can't do shell things through wireless adb.
SO, I found adbwireless by Sherdle, which is no-root. I haven't dedicated to using it, but it looks promising. I'll post updates. thank you again for your help. I kinda feel like Stevie Wonder in an obstacle course.

ArdDarvis said:
thank you very very much. my problem was that I enabled wireless adb, then rooted. when it didn't connect via wire, I factory reset it. this unrooted it, but left me with only wireless adb. I can't do shell things through wireless adb.
SO, I found adbwireless by Sherdle, which is no-root. I haven't dedicated to using it, but it looks promising. I'll post updates. thank you again for your help. I kinda feel like Stevie Wonder in an obstacle course.
Click to expand...
Click to collapse
I hope it works out. After seeing all of the headaches people have had with wireless adb the tuts should have a warning added.
Sent from my GT-P3113 using Tapatalk 4 Beta

well, no bueno.
its totally my fault, but i think the factory reset didn't touch the build.prop, but it DID unroot me. so now i'm stuck without root and only wireless adb.
when I wireless adb shell, su. it says I don't have permission. is this because I'm using wireless? I've used the su command to root the device, why no permission now?

Download the wireless adb apk onto your ouya , it can be found here on xda . Then open the wireless adb app on your Ouya and use the trackpad on the controller to toggle wireless adb on and off.

27scoob said:
Download the wireless adb apk onto your ouya , it can be found here on xda . Then open the wireless adb app on your Ouya and use the trackpad on the controller to toggle wireless adb on and off.
Click to expand...
Click to collapse
thank you for the help. i downloaded the apk, (its called adbWireless?) and installed it, but it says "kernel does not have all the necessary features for running this app. you need rooted phone". bummer.
I'm sure i sound like a complete newb; this is the first time i've ever joined a tech forum and had to write down what is happening. talking about it is easy, typing it is a little different.
i can pull the build.prop and at the bottom is the wireless code i put in. BUT, i can't push it back on because I need to change the permissions first. BUT to change permissions, i need su to work. to push su to /system/xbin, i need to change permissions.

I think I have the same problem :s
My computer don't recognize via USB, and I think is after enable tcpip ...( for wireless connection adb )
I update my ouya, lost my root and can't connect it ...
Do you find the solution ?
Thx
Edit : If I look the build.prop, I don't see the line for adb by tcp, so not sure it's my problem

Ok, i got it. and i feel great about it.
when setting up the drivers, we edited the android_winusb.inf to say
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
(that underlined part is the Hardware ID for the ouya in normal operation)
then we point the new hardware to the driver, then in terminal
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
and thats all well and good, but **** hits the fan sometimes.
and when it does, recovery mode is your friend.
if you lost wired adb due to enabling wireless adb then lost su, RECOVERY ENABLES WIRED ADB! so plug it in! it'll connect in recovery
2 ways-
1) "adb reboot recovery" (over wired or wireless connection), then use a USB keyboard and press the home key, and boom, theres recovery
2) plug in a USB keyboard, restart the ouya, when its booting up, push "Alt + PrntScrn + i" a lot, that'll eventually put you in recovery.
from recovery, we can sideload the most current OTA again via adb, BUT! the ouya changes hardware ID's when it is in recovery mode!
so, you have to go into the device manager, right click the device without the driver, go to details, then to hardware ID. you'll see that it is changed. so in the android_usb.inf, change it to say %CompositeAdbInterface% = USB_Install, USB\WHATEVER_HARDWARE_ID_IS (not REV)
once its changed, go into the device manager, right click the device, point it to the driver, then
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
and, there it is, wired adb capabilities in recovery so you can sideload in a OTA.
CWM recovery also changes the Hardware ID, so, after you do THAT, you gotta get the new hardware id again.
idk if its right, but it works- i just put the Hardware IDs for the different modes in the android_winusb.inf separated by commas. adb connects in ALL modes, which is WAY better than having to copy the IDs everytime and reload them.
hope it helps. i kinda feel like i know what i'm talking about a little, so, i'll try to help as much as i can.

billouetaudrey said:
I think I have the same problem :s
My computer don't recognize via USB, and I think is after enable tcpip ...( for wireless connection adb )
I update my ouya, lost my root and can't connect it ...
Do you find the solution ?
Thx
Edit : If I look the build.prop, I don't see the line for adb by tcp, so not sure it's my problem
Click to expand...
Click to collapse
yeah, it seems enabling tcpip disables wired connection.
idk about your build.prop, but i would suggest sideloading the most current OTA over in recovery. really thats all i can suggest. it overwrites the build.prop.
wireless adb seems to destroy all my dreams at once.

Help! Bricked Firestick2 by Disabling WiFi

I sideloaded settings.apk to my Fire Stick 2.
I opened it up, & accidently disabled wifi.
Now the stick barely boots past the logo, and displays a no network WiFi error message. It wants to connect to a network, but won't since Wifi is off. Rebooting has no effect.
Worst of all: the remote will no longer communicate with the stick. I guess that connects over wifi too.
I need to enable wifi again to unbrick my device. Or factory reset. But I can't use the remote. I have no way to input commands, that I know of. So the remote reset is a no go.
I will try to reset using adb commands over windows, connected via micro usb.
And/Or find a way to reflash the stock rom, or a custom one. I don't care about root. My stick is not rooted, runs some version of Fire OS, and its got Kodi and a few other apps sideloaded. Install Unknown Sources and Adb debug should both still be enabled.
Please help me guys! I need my tv back. What's my best course of action? Anyone got any steps, instructions or helpful links? I'm no expert, and I'd love experienced input.

If you can connect via ADB, then see this guide on how to control it: http://www.aftvnews.com/how-to-remotely-control-an-amazon-fire-tv-or-fire-tv-stick-via-adb/
Your other option is to use an OTG cable with a USB keyboard. See here: http://www.aftvnews.com/amazon-fire...d-ethernet-adapters-via-usb-otg-without-root/