Ok, so here's what happened.
When I got my ouya, the first thing I did was root it and set up Wireless adb. I noticed that when I had adb running over wifi though, it would disable my micro usb port for some reason, and I couldnt copy anything to the device while I had debugging enabled.
Long story short, I disabled adb to copy some files, and I accidentally replaced the launcher while trying to get GAPPS working. Unfortunately whatever launcher overwrote the ouya one doesnt work, and just force closes on boot.
Does anyone know of a recovery mode for the ouya? Most phones require holding down the power button as well as one of the volume buttons, but the ouya doesnt have any volume buttons.
I opened the case, and didnt see any switches or jumpers either.
I even tried using a usb keyboard and holding down the volume buttons on it out of desperation haha.
Is it possible to get Clockwork Mod booting from USB or something?
with wireless adb, if you disconnect from it by closing the cmd window, you need to type adb usb to re-enable the usb mode
its okay if the launcher fails as long as it still boots and you get into android, you can turn on adb again and just re-install stock launcher. I'll attach it in an sec
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Paulenski said:
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Click to expand...
Click to collapse
Thanks for attaching the launcher. I hopefully will be able to use that soon. Unfortunately, I disabled USB debugging in the Developer options on the Ouya itself.
I tried running your command (adb usb) and it tells me that no devices were found. I tried doing 'adb connect x.x.x.x' as well, but since USB debugging is disabled, it won't connect that way either.
Thanks for the suggestion though. Do you have any other ideas?
I have this samba app installed, and I was hoping i could access root through that, but I can only figure out how to access the sd card.
I also have airdroid and es file manager installed if there are any exploits to get those running.
Thanks for any help offered
Check this command
adb devices
does it even show up on the list?
Paulenski said:
Check this command
adb devices
does it even show up on the list?
Click to expand...
Click to collapse
i tried it, but it doesn't show up. I also checked device manager to see if it came up it there but all I get is an mtp device. I also copied the hardware id from that device and added it to the adb driver and reinstalled it that way, but it still does not show up in adb devices.
just to clarify, the mtp has a different hardware id than the adb mode one. When I did adb TCP originally, it disabled my micro USB port from mtp access, so I could not transfer files. That's why I had to disable USB debugging on the ouya. I'm afraid adb is doomed to not work until we can figure out how to get a USB bootable recovery image.
thanks for the suggestions I really appreciate it
any other ideas? I have been toying around with samba a little. I noticed that there is a share named admin$ but it doesn't work with the password I set up for the other share. Does anyone know what the default root password is for samba? If this will let me access the system folder, I can dump the launcher back in through samba.... Probably a long shot though.
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Paulenski said:
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Click to expand...
Click to collapse
I have PM'd you.
I double checked, and made sure to do the echo command. Still no dice.
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
This is the process:
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse
check out the thread here: http://forums.ouya.tv/discussion/1380/recovery-mode
Thanks for all the help here guys! I am glad to be running again
darthcircuit said:
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
Click to expand...
Click to collapse
Glad it helped.
- mbm
Related
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Nobody?
hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
hxdrummerxc said:
Nobody?
Click to expand...
Click to collapse
only thing i can think of right now, before suggesting omap flash or odin, would be try a different usb port, another computer, another OS!
try installing the latest CWM recovery and see if it helps.
hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
Try going to settings and look for something related to Root Access and it would have three options:
1. Apps only
2. ADB only
3. Apps & ADB
Choose the 3rd.
You might have to hunt the exact location under Settings where this option will be available as I don't remember them exactly.
Hit Thanks, if this helps...
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
hxdrummerxc said:
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
Click to expand...
Click to collapse
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
freezer2000 said:
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
Click to expand...
Click to collapse
hi. i try all this ways. i know that my usb debuging have problem, in development option i'll checked this, and it says enable. but infact it's not enable and still i got device offline error.
also i use z4root app and when i touch on root, it says that rooting need usb debuging enable (please enable it)!!
then move me to development setting to enable that, but this was checked and enable.
is any way that we make device online from my phone? for example using terminal emulator to turn on usb debuging or turn it off. this way is only my way! any one know some trying this?
i also use usb debugger app, but it move me in settings too! LOL
i need enable my device to root that.
thanks every one
I know this is an old topic, but if somebody else googles it, I had that offline issue, the solution was to upgrade adb : http://stackoverflow.com/questions/10680417/error-device-offline
You simply need to upgrade to the latest version of adb. Went thru this a few weeks ago.
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
I'm having issues with unlocking/rooting my nexus 7 2013.
I downloaded and installed the nexus root toolkit at wugfresh.com
I've followed all the instructions precisely. However, I always failt the ADB Driver test.
Here are the things I've found while trying to troubleshoot my problem:
1. When I enable usb debugging mode and plug in the nexus 7, I NEVER received the RSA Fingerprint authorization screen.
2. I've installed all the drivers and when it's plugged into the PC, it is recognized as a "google nexus ADB Interface": i.imgur.WHAT/f5Rk5qg.png
3. Inside of USBDeview it is recognized as mass storage device (color purple instead of green): i.imgur.WHAT/r4SwmVM.png
4. Under My Computer I am unable to reach the harddrive anymore.
I believe this is what is preventing me from moving forward. I know this because I've plugged this into my co-workers PC (he already had NRT installed to root his 2012 Nexus 7 awhile ago) and unlocking it on his PC works fine.
5. After uninstalling the drivers installed with NRT and uninstalling the NRT, I still can't access the drive as I could before.
Any help would be appreciated.
This is my first post so I cannot post links to the image... On #2 and #3 replace the i.imgur.WHAT with i.imgur.com
I had the same issue with Wug's toolkit. I finally went the google route using the SDK and usb drivers and it worked like a charm. I would try that method if you feel comfortable enough. Here's a guide to help with that: http://forum.xda-developers.com/showthread.php?t=2382051
railed said:
I had the same issue with Wug's toolkit. I finally went the google route using the SDK and usb drivers and it worked like a charm. I would try that method if you feel comfortable enough. Here's a guide to help with that: http://forum.xda-developers.com/showthread.php?t=2382051
Click to expand...
Click to collapse
I think my issue isn't with the toolkit but with the drivers on my computer right now. I'm not sure how to fix the driver issue i'm having. The link you provided only links to drivers I've already tried.
Laxxium said:
1. When I enable usb debugging mode and plug in the nexus 7, I NEVER received the RSA Fingerprint authorization screen.
Click to expand...
Click to collapse
This is usually because you are not running the latest adb version 1.0.31, but might be for other reasons like the adb that is running in the background is the older version and you need to adb kill-server then adb devices to restart it
Don't underestimate the power of reboot. Sometimes things get in a weird state and even though you have it set up properly, the changes won't really kick in until a reboot.
Laxxium said:
3. Inside of USBDeview it is recognized as mass storage device (color purple instead of green): i.imgur.WHAT/r4SwmVM.png
Click to expand...
Click to collapse
I didn't see mass storage device where you highlighted in red.
You shouldn't see USB mass storage device with this device. It doesn't support it. Only MTP mode. If you are seeing mass storage device, then probably some drivers are out of whack and you should use usbdeview to remove them.
Laxxium said:
4. Under My Computer I am unable to reach the harddrive anymore.
Click to expand...
Click to collapse
There could be many explanations for this. The simplest one is you have USB debugging enabled. Try disabling USB debugging. If that doesn't work, try PTP mode settings->storage->3baroptions If you see PTP mode, but not MTP, then it is a USB ID problem. If you don't see PTP mode either, you probably need to remove some drivers, reboot, and reinstall the drivers.
msellsio completely
Well... my work day ended and I figured I would simply try to do it at home.
I got the drivers to work at home. The nexus was already unlocked so I click on the root button.
After clicking on root, it looks like my tablet got stuck in Bootloader mode, IE in the videos I saw people doing it, it would restart and go into bootload and do something then restart again, mine restarted and just stayed on the bootload screen until I pushed the on/off button (for yes to start).
Now it loads into the tablet and I get about 17 error messages of
"Unfortunately, Google Play Services has stopped" and
"Unfortunately, the process com.google.process.gapps has stopped".
So now I have no idea what to do, I can't even use the damn thing anymore.
Laxxium said:
So now I have no idea what to do, I can't even use the damn thing anymore.
Click to expand...
Click to collapse
Do a factory reset
settings->backup&reset->factory data reset
If you can't get into that, power down
then press Power+VolUp until you see Google, then let go.
You'll see fallen android.
Press and Hold Power, then press/release VolUp, then release Power
Use VolDown to highlight wipe data factory reset, then Power to select.
sfhub said:
Do a factory reset
settings->backup&reset->factory data reset
If you can't get into that, power down
then press Power+VolUp until you see Google, then let go.
You'll see fallen android.
Press and Hold Power, then press/release VolUp, then release Power
Use VolDown to highlight wipe data factory reset, then Power to select.
Click to expand...
Click to collapse
Thanks for this.
I FINALLY got everything to work.
1. I did a factory reset (the 1 thing i was trying to avoid). This fixed the issues with the error messages.
2. I figured out what went wrong with the root toolkit. I decided to try and do the rooting manually, while trying to flash the recovery file, it was getting an unknown error. So the toolkit was basically getting stuck there. It took me 2 hours to figure out that this was happening simply because I was using my front USB3.0 ports. I switch to the back USB2.0 ports and the flashing worked fine.
3. Since I had already managed to flash teh recovery file, I deleted the universal adb drivers and let windows handle it, it installed the regular drivers and I finally managed to access the drive. I was able to upload the supersu file thus completing the root.
I still don't know why the ADB drivers won't let me access the drive though. Guess this mystery will have to be solved anytime.
Laxxium said:
I still don't know why the ADB drivers won't let me access the drive though. Guess this mystery will have to be solved anytime.
Click to expand...
Click to collapse
If you can access the Nexus 7 over MTP (ie as a drive) while USB debugging is disabled but not when it is enabled, that is a known issue and here is a fix.
http://forum.xda-developers.com/showthread.php?t=2391236
If you can't access MTP at all, I would also look at that link to d/l Nirsoft USBDeview and remove all the drivers for the nexus 7 (sort by date and select all the nexus 7 entries) Let the drivers reinstall from scratch.
Stuck at boot animation.
I was trying to get the settings.apk working again.
Rebooted a few times. No problems.
I think restoring the wrong app and data with Titanium may have done it.
Anything new on debricking? - I'm passed the point of normal returns at Amzn.
Thanks
[email protected] said:
Stuck at boot animation.
I was trying to get the settings.apk working again.
Rebooted a few times. No problems.
I think restoring the wrong app and data with Titanium may have done it.
Anything new on debricking? - I'm passed the point of normal returns at Amzn.
Thanks
Click to expand...
Click to collapse
can you still connect via adb?
If it does still connect with ADB,then we need a new topic for when de-bricking hopefully becomes a possibility.
No ADB. No ping.
My USB flash drive does blink a few times tho.
When installing xposed module for xbmc launcher, I did not load xbmc.apk Therefore system was stuck.(tried launching an app that did not exist) I thought bricked. after unplugging and plugging in a few times I was able to connect via adb which I achieved bye
adb kill-server
adb start-server
adb connect IP
on every unplug/plug in reboot.
I eventually got in and uninstalled the launcher. sometimes it would hang on the amazon screen and reboot. sometimes it showed the launcher and how it could not find and png file. was behaving differently which I thought strange. hope this helps.
rp201 said:
When installing xposed module for xbmc launcher, I did not load xbmc.apk Therefore system was stuck.(tried launching an app that did not exist) I thought bricked. after unplugging and plugging in a few times I was able to connect via adb which I achieved bye
adb kill-server
adb start-server
adb connect IP
on every unplug/plug in reboot.
I eventually got in and uninstalled the launcher. sometimes it would hang on the amazon screen and reboot. sometimes it showed the launcher and how it could not find and png file. was behaving differently which I thought strange. hope this helps.
Click to expand...
Click to collapse
I'm trying this now.
I wonder if a soft boot will work the same.
I plugged in a USB keyboard and found that Ctrl-Alt-Del does a soft boot.
Thanks
If only there was a button or key-combo to reset or go into recovery.
rp201 said:
When installing xposed module for xbmc launcher, I did not load xbmc.apk Therefore system was stuck.(tried launching an app that did not exist) I thought bricked. after unplugging and plugging in a few times I was able to connect via adb which I achieved bye
adb kill-server
adb start-server
adb connect IP
on every unplug/plug in reboot.
I eventually got in and uninstalled the launcher. sometimes it would hang on the amazon screen and reboot. sometimes it showed the launcher and how it could not find and png file. was behaving differently which I thought strange. hope this helps.
Click to expand...
Click to collapse
i am having this very issue, tried to uninstall the xbmclauncher.apk but i keep getting 'Failed' . i have also tried installing the xbmc.apk again but thats not working either. i fear i may have a brick . all i am getting onscreen is the 'Activity org.xbmc.xbmc/blah,blah.splash not found. i am able to connect with adb and get adb shell and su, im baffled and worried, any help would be greatly received, thanks
millsy1973 said:
i am having this very issue, tried to uninstall the xbmclauncher.apk but i keep getting 'Failed' . i have also tried installing the xbmc.apk again but thats not working either. i fear i may have a brick . all i am getting onscreen is the 'Activity org.xbmc.xbmc/blah,blah.splash not found. i am able to connect with adb and get adb shell and su, im baffled and worried, any help would be greatly received, thanks
Click to expand...
Click to collapse
Since you can get in and have root once you're in, you have lots of options.
Try an adb install of xbmc and the launcher you'd tried to install, for starters.
You can also push the update into /cache and then force an update - take a look at fire general for the how to force an install thread. That will cure Xposed issues by refreshing the framework files that Xposed changes.
---------- Post added at 03:08 PM ---------- Previous post was at 03:02 PM ----------
[email protected] said:
No ADB. No ping.
My USB flash drive does blink a few times tho.
Click to expand...
Click to collapse
A quick note on the suggestion I made a while back: Once the firmware update became available, I tried putting it (as update.zip and as bueller-ota-51.1.1.0_user_511069920-signed.bin) both at the root of the scard directory and as the only file on a fat32 foratted thumb drive, and doing
adb reboot recovery (yes, each of the four possible permutations.)
All to no avail. Conclusion: It's pretty easy to brick this device. And not easy to fix it yet.
I'm rooting for my dvd player to get Prime, at which point I'm much less dependent on the fire, as it supports smb and netflix already, not to mention a service I'm really enjoying the digital concert hall from the Berlin Philharmonic.
..sorry I missread you.
[email protected] said:
Stuck at boot animation.
I was trying to get the settings.apk working again.
Rebooted a few times. No problems.
I think restoring the wrong app and data with Titanium may have done it.
Anything new on debricking? - I'm passed the point of normal returns at Amzn.
Thanks
Click to expand...
Click to collapse
I did the exact same thing, i did a titanium backup of setting from my madcatz mojo that i was going to apply on the FTV. Mojo now supports Ouya Everywhere and i was going on restore that on the FTV and see if i can play ouya games on my fire tv. Now i have to wait for my new unit to arrive on tuesday
---------- Post added at 05:50 PM ---------- Previous post was at 05:21 PM ----------
Okay so i connected a Male to Male Usb 2.0 cable to the FTV with it was unplugged. Plugged the power cord and now i get fastboot to work. anything i can do to fix my FTV?
millsy1973 said:
i am having this very issue, tried to uninstall the xbmclauncher.apk but i keep getting 'Failed' . i have also tried installing the xbmc.apk again but thats not working either. i fear i may have a brick . all i am getting onscreen is the 'Activity org.xbmc.xbmc/blah,blah.splash not found. i am able to connect with adb and get adb shell and su, im baffled and worried, any help would be greatly received, thanks
Click to expand...
Click to collapse
Recovery MODE might help
http://forum.xda-developers.com/showthread.php?t=2799779
Debricked with recovery mode
Recovery MODE might help
http://forum.xda-developers.com/showthread.php?t=2799779
Dropped phone, broken screen/digitizer, doesn't respond to touch
Was able to see the screen a bit yesterday but now its almost all black. I mainly just need my photos off it. Tried an RMA to replace the screen but they said they had to wipe everything first
Is there any way I can pull the photos off it? I haven't tried an otg yet, but I also can't see the screen, so im not sure it would help
Is there a screen sharing program I could get w/o first installing it on my phone?
I think my phone may be rooted, i forget if i ever did, but i dont have TWRP installed on it? (i dont super know what that is but i see other people talking about it)
Any thoughts on how to pull photos off it? I tried the adb devices but the cmd prompt doesn't seem to recognize the phone
Im quite sure I have debugging enabled, just coudln't get the file transfer button hit
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Ok cool, how would i go about sorting the drivers? o.0
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
side note.... wth is this image verification lol, ive tried like 30 of them, why is it so hard to post lol ><
Click to expand...
Click to collapse
Sorry, can't give definite answer, I know that I had an issue with drivers (device wasn't properly recognized) and tried pretty much everything that Google suggested ... Until it finally started working. I have no idea exactly what solved the issue, it was over a year and a half ago. The next time I clean installed Windows (10 in both cases) it was smart enough to automatically find right drivers.
So ... I'm guessing Googling something like "OnePlus 3 Windows # drivers" should find something useful?
About image verification: are you talking about anti-bot system that checks if you're human? Wouldn't know much about that, never personally had issues with it, but also very rarely see it on XDA as I'm nearly always checking this forum in Tapatalk app.
Sent from my OnePlus 3 using Tapatalk
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
Click to expand...
Click to collapse
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
tnsmani said:
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
Click to expand...
Click to collapse
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Had the same issue with my Lenovo P2. Only i didn't have debugging enabled. If you have, screen mirroring should be an easy solution. You could just see ur phone screen on ur computer that way. What helped me was to forceboot the phone to recovery with the hardware buttons, then connect it to ur pc. TWRP will automatically launch MTP. When u backed up evrything, you can wipe ur device through adb
jsaden said:
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Click to expand...
Click to collapse
I don't know about Win 7. It will work on Win 10. Most likely, this should not be needed in Win 7 at all as the drivers should install whether signed or not.
Regarding copying data, a simple command of "adb pull /sdcard" will copy all the folders, files, data etc to your PC. You can also specify where you want the data copied to, simply add the path to the command above. This will work whether your screen works or not. Of course, there are other methods of copying data, you can search for it if you need it.