Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
JackBackstack said:
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
Click to expand...
Click to collapse
If you can get into recovery, just copy over the latest OTA file onto a usb stick, wipe Data/cache then flash the OTA.
Also for windows, not doing " echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini" " can sometimes make it not be found on its own, was originally required to do it for ADB
In recovery mode, the only way is to flash the OTA via ADB. There is no option like from usb-stick or internal/external sd-card.
and my adb_usb.ini seems to be correct.
But thanks for your suggestions (=
I had the same issues. I'm waiting on a replacement. http://forums.ouya.tv/discussion/comment/13562
JackBackstack said:
Hey Guys,
as the title says, I can't connect to my OUYA anymore.
What have I done?
Set up adb and sdk descripted here
https://devs.ouya.tv/developers/docs/setup
Set up wireless adb, busybox, superuser, and su binaries descripted here
http://forum.xda-developers.com/showthread.php?t=2272266
Everything worked fine so far.
Then I rebooted the OUYA. From now on the device manager didn't found the OUYA anymore. If I switch USB-debugging off, its found as 'portable device'. If I switch USB-debugging on, it disappears and there is no other new item.
OUYA factory reset
This didn't helped anything. But with this step I lost SU.
So, as i read, USB-ADB is shut down on OUYA as soon as you enable wireless-ADB. A terrible 'feature', whatever. Now I can't modify the build.prop to take out the "service.adb.tcp.port=5555" line.
I managed to get into the recovery mode (by connecting a keyboard and pressing alt+print+i multiple times, then home) , but that's pretty helpless if adb can't find the ouya.
Has anybody an idea how I can get adb working properly again? Any ways are good, flashing a new rom, getting su, factory reset, anything =D
Click to expand...
Click to collapse
I haven't messed with root/cwm, since there really isn't much brick protection... you might try 'adb reboot recovery' during bootup... if you can force it to fastboot, you can boot the recovery image, and it should have adb with su access, you should be able to repair you mistakes from there, or just do a data/cache reset to wipe the device.
EDIT: assuming you can get to fastboot somehow, you would just have to 'fastboot boot recovery.img' where recovery.img is the build of cwm.
EDIT 2: try booting with a usb keyboard, during boot, you might be able to spam the kernel with the key combination alt-SysRq-i. This may force it to boot into recovery... Then you should be able to either use regular ADB, maybe push a OTA.zip via ADB, and ultimately install a OTA... Hope some of this is helping, I have no real hands on practice with much of ADB on this specific device... But I'm a LONG time android tinkerer.
EDIT 3: If you're able to get it to crash and boot into recovery via Alt-SysRq-i . It's a recovery based on 4.x as it should be... and you should be able to 'adb sideload OTA.zip'... Sorry for all these edits, I just keep realizing I have more to say.
Here's the link for the apk(down page a bit) to enable disable wireless adb allowing USB adb:
http://forum.xda-developers.com/showthread.php?t=961466
Sent from my Galaxy Nexus using xda app-developers app
HaYNigloo said:
Here's the link for the apk(down page a bit) to enable disable wireless adb allowing USB adb:
http://forum.xda-developers.com/showthread.php?t=961466
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Will that require root?
Yes, since it's right inline with installing su, busybox, and supersuer using ADB. With the option to go ADB wireless, this is a necessity if you'll be installing CWM.
HaYNigloo said:
Yes, since it's right inline with installing su, busybox, and supersuer using ADB. With the option to go ADB wireless, this is a necessity if you'll be installing CWM.
Click to expand...
Click to collapse
Yeah that's what sucks. I followed a post on here and thought I had the unit rooted but either I messed it up or the OTA updates wiped it out. Since I no longer have adb access I cannot get root to enable wireless adb access. Snake eating its own tale
Oh! I believe there are wireless adb apps that don't require root. Try looking into the play store to find out which ones.
Edit 1: The Play Store has a wireless ADB app by Sherdle [ADB Wireless (no-root)]which doesn't require root!
Sent from my Galaxy Nexus using xda app-developers app
Hi everyone,
Actually I'm stuck the exact same way and I'm wondering if beowolfschaefer and JackBackstack have found a solution to get ADB work over TCPIP.
Thanks guys.
KrelianGS said:
Hi everyone,
Actually I'm stuck the exact same way and I'm wondering if beowolfschaefer and JackBackstack have found a solution to get ADB work over TCPIP.
Thanks guys.
Click to expand...
Click to collapse
I'm missing something. I have read this a couple times but cant figure out what is happening.
Is your Ouya not booting up at all?
If it boots can you do an
adb connect xxx.xxx.xxx.xxx and then adb shell to get a shell?
HT123 said:
I'm missing something. I have read this a couple times but cant figure out what is happening.
Is your Ouya not booting up at all?
If it boots can you do an
adb connect xxx.xxx.xxx.xxx and then adb shell to get a shell?
Click to expand...
Click to collapse
The Ouya is booting perfectly and wifi-ADB is enable. Problem is I can't connect to it anymore.
I already tried adb connect 192.168.xxx.xxx but i get a "device not found" error. It's the good IP (check on the Ouya and on my router with the MAC Adress)
It might be a port probleme. I tried both 5037(default) and 5555.
By the way, in the settings, should I switch USB-Debugging on or off ? Or it doesn't matter ?
KrelianGS said:
The Ouya is booting perfectly and wifi-ADB is enable. Problem is I can't connect to it anymore.
I already tried adb connect 192.168.xxx.xxx but i get a "device not found" error. It's the good IP (check on the Ouya and on my router with the MAC Adress)
It might be a port probleme. I tried both 5037(default) and 5555.
By the way, in the settings, should I switch USB-Debugging on or off ? Or it doesn't matter ?
Click to expand...
Click to collapse
I am pretty sure USB debugging needs to be on for ADB to accept connections. make sure it is on
Hello, ive managed to shatter my phones screen and digitizer and am trying to get into the device using android screencast though when typing in "adb devices" it shows up as unauthorized. Is there ANY way to get past this? I'm able to access adb in recovery, maybe I can add the exception manually or disable thar check perhaps?
Im not afraid to play around with the source code of specific files if necessary. Thanks in advance
How are you able to access adb in recovery? I'm trying to do the same but my computer just won't recognize the device while it's in recovery.
davelee1054 said:
How are you able to access adb in recovery? I'm trying to do the same but my computer just won't recognize the device while it's in recovery.
Click to expand...
Click to collapse
To be completely honest it didnt work for me for a while then it just worked after a bit, though I had to manually flash cwm through fastboot befire I could attempt that
Sad day today.. dropped my S6 Edge and the result was a shattered front screen. I can't use any of the touch function, but the phone does appear to work partially ( I still get email alerts on my connect android wear).
I wanted to perform an adb backup , I'm able to connect the phone to my computer, however, when I give the :
adb backup -all -f C:\backup.ab command, it wants me to unlock the device and confirm the backup operation.
I tried unlocking with my fingerprint but it's not working. I can't see anything on screen, other than a flashing light.
Any other suggestions how to backup/ transfer data from phone? sadly kies no longer works which would have worked...
Thanks for all help in advance.
That sucks big time. Turn the phone off, put the phone in download mode and issue the commands that way. This will by pass the phone asking you to unlock it.. See if that works for you.
grneyez said:
That sucks big time. Turn the phone off, put the phone in download mode and issue the commands that way. This will by pass the phone asking you to unlock it.. See if that works for you.
Click to expand...
Click to collapse
I just tried that. When I give the adb backup command screen reads: "waiting for adb Mode" and does not seem to progress. when I loaded odin it does seem to recognize phone ready to go so the connection is live.
any other suggestions?
Are you rooted? If so, do you have developer options checked?
S6 edges is not rooted. Developers options was enabled previously since I had used Helium for date transfer from my older S5 to edge.
Not sure why you can't ADB in download mode. Wish I could of been more helpful.. Maybe someone else will be able to help.
grneyez said:
Not sure why you can't ADB in download mode. Wish I could of been more helpful.. Maybe someone else will be able to help.
Click to expand...
Click to collapse
So I rooted my phone even though the screen is cracked. I tried everything I could think of, not much to lose anymore.
I can still access the adb , shell, but still having same issue.
I tried the pull command but I get an error after screen starts creating a list " No such file or directory"
Any more suggestions?
at first - sorry for my bad english
My friend have Xiaomi note 10t lite 5g(M2007J17G) with broken screen, locked bootloader and USB debugging off ... i just need to copy his files(pictures, videos etc.) to computer... i know it is possible on Samsung devices via fastboot mod trough flashing custom recovery, then using ADB commands like "pull", otherwise Xiaomi devices have much more complicated security, and I don't know if I will brick the device, when I try to flash TWRP via fastboot
thanks for answers
With unlock bootloader there is a small chance to do anything on Xiaomi
Did you enable developer options and USB debugging? Then you could theoretically use adb shell to access the phone from PC through USB cable and then you must push an exploit to your phone that enables temporary root. For example this one
Then you should be able to pull all your personal data from the phone.
Please let us know if you succeed, thanks. Good luck in your endeavor!
And remember: whenever you buy a new device the first things to do are activate developer options, enable USB debugging and UNLOCK BOOTLOADER or you will regret it !!!
lebigmac said:
Did you enable developer options and USB debugging? Then you could theoretically use adb shell to access the phone from PC through USB cable and then you must push an exploit to your phone that enables temporary root. For example this one
Then you should be able to pull all your personal data from the phone.
Please let us know if you succeed, thanks. Good luck in your endeavor!
And remember: whenever you buy a new device the first things to do are activate developer options, enable USB debugging and UNLOCK BOOTLOADER or you will regret it !!!
Click to expand...
Click to collapse
it is not my phone(all my phones are with unlocked bootloader of course) ... and unfortunately it have not enabled developer options, nor USB debugging, so all partitions on the phone are permanetly unaccessible, until there will be display...
maybe It will be possible to acces the data from PC, if I will turn the phone normaly and unlock it with biometrics(fingerprint, or iris) ... there are much larger chances...
tommorow I will have time for it, so I will let you know ;-) thanks for trying to help me
Just buy cheap display replacement online for 15$ and replace the display and try to get your files that way. Good luck!
scrcpy on GitHub is an amazing tool.
Control phone from PC, no funny app needed to be installed on phone.
And `scrcpy --turn-screen-off` even lets you control the phone with the screen off so that the crazy touch screen doesn't interfere with its touches