Develop Bugs

[Q] Factory Reset Narfed su

I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.

vbrtrmn said:
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
Click to expand...
Click to collapse
I don't know too much about adb, but I'll try to help
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
I just turned on my console and have come to the conclusion that the automatic update broke su. How, i'm not sure, but it would seem that possibly you'll have to restart the process from scratch, redo adb and reload su.
lets just hope this isn't a sign that all future automatic updates will break su.
*EDIT* So it would seem that there is problems with the drivers. I have gotten ADB to work once again by deleting all the OUYA drivers from my computer and following the steps found at https://devs.ouya.tv/developers/docs/setup HOWEVER this presents a problem in that the system is only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know). Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
After getting ADB back, I got SU back by running through the steps found here: http://forum.xda-developers.com/showthread.php?t=2272266 under how to install busybox, superuser, and su binaries. You should only have to go from step 1 to 4 on that one (only 4 if you still have the files on your computer).
I will note that the steps to get ADB on that second link did NOT work this second time. I'm not sure what this is due to. I'll be starting a new thread with this info, too.

JLCollier2005 said:
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Click to expand...
Click to collapse
Nope.
JLCollier2005 said:
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
[/QUOTE[
No drivers, running OSX & Linux.
Click to expand...
Click to collapse

Hard boot the OUYA and laptop, adb via USB seems to work again.

So far every OTA has removed su.
Sent from my GT-P3113 using Tapatalk 4 Beta

[Q] no usb-adb, no wireless adb, no su

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

[Q] Why doesn't adbFire connect my Fire TV stick anymore?

Hello, I just recently bought the Amazon Fire TV stick. When I first got it, I was able to connect it to my computer using the adbFire tool with no problem. I was able to sideload Kodi and push apps to it with no problem. Now, a couple days later, when I try to connect the same device using the same program, it keeps popping up with the message "device not connected".
I tried to connect through command prompt but it still didn't work. I also tried pinging w/ command prompt but it keeps giving me "Destination host unreachable". I turned ADB debugging off and back on, turned wi-fi off and back on, and rebooted the stick multiple times yet it still doesn't work.
Anyone have any ideas on what might be the problem? I don't understand how it was connecting just 2-3 days ago but it doesn't work when i try it now. Only other thing I can think of is a factory reset but I'm hesitant to do that in fear of me not being able to sideload everything again.
Any help is appreciated, thanks.

AlphaBee said:
Hello, I just recently bought the Amazon Fire TV stick. When I first got it, I was able to connect it to my computer using the adbFire tool with no problem. I was able to sideload Kodi and push apps to it with no problem. Now, a couple days later, when I try to connect the same device using the same program, it keeps popping up with the message "device not connected".
I tried to connect through command prompt but it still didn't work. I also tried pinging w/ command prompt but it keeps giving me "Destination host unreachable". I turned ADB debugging off and back on, turned wi-fi off and back on, and rebooted the stick multiple times yet it still doesn't work.
Anyone have any ideas on what might be the problem? I don't understand how it was connecting just 2-3 days ago but it doesn't work when i try it now. Only other thing I can think of is a factory reset but I'm hesitant to do that in fear of me not being able to sideload everything again.
Any help is appreciated, thanks.
Click to expand...
Click to collapse
Make sure fire tv stick has not been assigned the primary IP address for your modem typically 192.168.1.100 if this is the case than simply get a new IP address. I wasn't able to connect adb when for some reason my fire tv grabs ip address 192.168.1.100.
Thanks

ashsha7877 said:
Make sure fire tv stick has not been assigned the primary IP address for your modem typically 192.168.1.100 if this is the case than simply get a new IP address. I wasn't able to connect adb when for some reason my fire tv grabs ip address 192.168.1.100.
Thanks
Click to expand...
Click to collapse
I tried changed the IP address on the FireTV and I am still getting the error when I try to connect it . However I am getting results when trying to ping so at least there's some progress. I'm going to play around with it more in a bit and see if I can get it to work. Thanks for the tip!

it's working again
just to update i reset my connection as well as rebooted my FireTV stick (once again) and now it's finally working. Thanks again for the help!

AlphaBee said:
just to update i reset my connection as well as rebooted my FireTV stick (once again) and now it's finally working. Thanks again for the help!
Click to expand...
Click to collapse
Same experience - couldn't connect to or ping the Fire Stick at first, then restarted it, the router and my computer, and it worked.

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/

unbricked Fire TV gen 1 boots to Amazon setup but no Ethernet, no WIFI network

my previously rooted Gen 1 AFTV started to have issues so I tried to update the rather old OS build - and bricked the device. no LED light, nothing.
using an A-A cable I successfully followed rbox' instructions in https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 writing the contents of update-kindle-bueller-51.6.3.2_user_632552020.bin to the respective partitions and wohoo, the box booted again, although without rbox' bootloader which I didn't care for too much then.
worse problem was there was also no network connection - neither Ethernet (no link) nor WIFI (just kept scanning forever) worked. not really knowledgeable about the boot process of Android devices I resorted to a factory reset, which seemed to work but now I'm stuck at the Amazon setup (just after language selection) still without network and no other way to go. tried the alt-prtscr-i route but that only got me to a screen with red text saying the device would enter recovery which never happened no matter how long the wait.
thinking the bin file may have been corrupted next I attempted to dd-write the partitions again with contents from another bin file but couldn't even "see" the partitions anymore. hooked up to a knoppix box nothing shows those sdcX partitions anymore: df -h, mount, fdisk -l, cat /proc/partitions. only command - briefly - showing a Qualcomm device was lsusb.
same on a W10 machine where the booting AFTV would briefly show up as a USB mass storage class device (of course without access to it) but would then disappear again with the corresponding sound. the box still boots to the amazon setup however.
now I'm stuck and don't know what to try next. previously ADB debugging was active and I sometimes used the interface to push packages to it but now I don't even have an IP connection anymore to dig into the config files :crying:
thanks for any ideas ! would love to get the box back to life again

bikernzrh said:
my previously rooted Gen 1 AFTV started to have issues so I tried to update the rather old OS build - and bricked the device. no LED light, nothing.
using an A-A cable I successfully followed rbox' instructions in https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 writing the contents of update-kindle-bueller-51.6.3.2_user_632552020.bin to the respective partitions and wohoo, the box booted again, although without rbox' bootloader which I didn't care for too much then.
worse problem was there was also no network connection - neither Ethernet (no link) nor WIFI (just kept scanning forever) worked. not really knowledgeable about the boot process of Android devices I resorted to a factory reset, which seemed to work but now I'm stuck at the Amazon setup (just after language selection) still without network and no other way to go. tried the alt-prtscr-i route but that only got me to a screen with red text saying the device would enter recovery which never happened no matter how long the wait.
thinking the bin file may have been corrupted next I attempted to dd-write the partitions again with contents from another bin file but couldn't even "see" the partitions anymore. hooked up to a knoppix box nothing shows those sdcX partitions anymore: df -h, mount, fdisk -l, cat /proc/partitions. only command - briefly - showing a Qualcomm device was lsusb.
same on a W10 machine where the booting AFTV would briefly show up as a USB mass storage class device (of course without access to it) but would then disappear again with the corresponding sound. the box still boots to the amazon setup however.
now I'm stuck and don't know what to try next. previously ADB debugging was active and I sometimes used the interface to push packages to it but now I don't even have an IP connection anymore to dig into the config files :crying:
thanks for any ideas ! would love to get the box back to life again
Click to expand...
Click to collapse
Only the unlocked bootloader is able to read/write to the emmc via the a-a usb cable. Adb debugging is gone due the factory reset.
What is installed on system? A prerooted rom? Then the solution is probably to boot into TWRP and wipe cache, dalvik, data, internalsd.
In case the TWRP bootmenu is gone too, there isn't much (maybe nothing) you can do...

Sus_i said:
Only the unlocked bootloader is able to read/write to the emmc via the a-a usb cable. Adb debugging is gone due the factory reset.
What is installed on system? A prerooted rom? Then the solution is probably to boot into TWRP and wipe cache, dalvik, data, internalsd.
In case the TWRP bootmenu is gone too, there isn't much (maybe nothing) you can do...
Click to expand...
Click to collapse
being a newbie to Android I'm not exactly sure. I believe it was a prerooted rom. it showed RBOX's BOOT MENU at startup and I did have root access.
according to "how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery" on aftvnews the reset to factory defaults should not have removed root or TWRP, however there is no menu when booting the device and pressing right-arrow won't bring one up either. it just boots to the amazon setup
does that mean that I'll have to toss it?

bikernzrh said:
being a newbie to Android I'm not exactly sure. I believe it was a prerooted rom. it showed RBOX's BOOT MENU at startup and I did have root access.
according to "how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery" on aftvnews the reset to factory defaults should not have removed root or TWRP, however there is no menu when booting the device and pressing right-arrow won't bring one up either. it just boots to the amazon setup
does that mean that I'll have to toss it?
Click to expand...
Click to collapse
Idk. If the bootmenu doesn't show, its probably gone.
About the network problem, maybe a router reset is worth a shot?

Sus_i said:
Idk. If the bootmenu doesn't show, its probably gone.
About the network problem, maybe a router reset is worth a shot?
Click to expand...
Click to collapse
thanks for your thoughts!
what has me curious still is the fact, that I no longer can access the box from Linux as I did before. wonder if the new OS is hiding TWRP info normally visible and if there is any secret way to invoke it?
the router is fine. always in use with various WIFI clients and also just successfully tested a cable connection to it with a laptop.

bikernzrh said:
thanks for your thoughts!
what has me curious still is the fact, that I no longer can access the box from Linux as I did before. wonder if the new OS is hiding TWRP info normally visible and if there is any secret way to invoke it?
the router is fine. always in use with various WIFI clients and also just successfully tested a cable connection to it with a laptop.
Click to expand...
Click to collapse
In case you are good with a solder iron, there is always the hardware option, in order to read/write to the EMMC partitions. Take a look here and here. But aside from the soldering skills, it cost some bucks to buy hardware...

Sus_i said:
In case you are good with a solder iron, there is always the hardware option, in order to read/write to the EMMC partitions. Take a look here and here. But aside from the soldering skills, it cost some bucks to buy hardware...
Click to expand...
Click to collapse
I fear my soldering expertise is not sufficient to attempt that guess I'll have to shop around for another used device instead as I need TOSLink and would also like to retain an Ethernet connection.
thank you so much for your help!