My watch is rooted and my phone isn't. Is there a way to sideload apps from the phone? I adb install from my computer straight to the watxh from PC, and app2wear requires root on phone which I don't get?
Must android wear devices cannot connect directly to a pc, that is why all the tutorials require a phone. This one is different and does not
Sent from my SM-T810 using Tapatalk
Just adb sideload what you need from your computer. No phone needed.
I do, I was wondering why the guides do it via Bluetooth, but I got my answer.
Related
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
I know my way around fastboot, adb, command line pretty well, but I just got my N7(2013) last night, so in that sense, I'm a Noob.
Questions:
Can I just root with SuperSU without TWRP? Or will the stock recovery not let me do that? i.e. is there a signed SuperSU? I would rather keep my stock recovery, if possible.
After I root, do USB storage devices connected via an OTG cable "Just Work"? Do I have to manually mount them? Does it enable a Menu?
Is there any way to enable USB Storage (The other way, when N7 is connected to PC) once I root? Is anybody working on this?
Linuxslate said:
Can I just root with SuperSU without TWRP? Or will the stock recovery not let me do that? i.e. is there a signed SuperSU? I would rather keep my stock recovery, if possible.
Click to expand...
Click to collapse
Suggest you do
fastboot boot twrp.img
instead of flashing twrp onto the tablet's recovery partition
This will run twrp temporarily to install SuperSU's update.zip but will leave stock recovery on your tablet untouched.
Linuxslate said:
After I root, do USB storage devices connected via an OTG cable "Just Work"? Do I have to manually mount them? Does it enable a Menu?
Click to expand...
Click to collapse
Recognition is automatic. Mounting is not. So yes, you need to mount them. Whether you do that manually or through a helper app like stickmount is up to you
Linuxslate said:
Is there any way to enable USB Storage (The other way, when N7 is connected to PC) once I root? Is anybody working on this?
Click to expand...
Click to collapse
Doubtful. N7 doesn't have a real sdcard partition formated fat32. It has a simulated sdcard kept in the /data/media folder. MTP/PTP are the only ways Google wants to support storage going forward.
Thanks, sfhub;
Great trick about running twrp once.
That way I can have root, and my stock recovery.
Thanks for the other info, too.
No MTP or Storage show on PC
I am running windows 7 64 bit and I have managed to get root on my new Nexus 7, but now when I plug my tablet into the PC it says on the tablet connected as media device, but it never shows up anywhere on my pc so that I can transfer files on to it. The nexus 7 never shows up as an extra drive or as an media device. Please help. can not seem to find any info on this problem. the usb icon at the bottom of the screen does say eject nexus 7 when I click on it, and if I have usb debugging turned on it says ADB device connected but I still can not see it anywhere on the pc. Please help
Are you running stock or custom ROM?
If you running stock, you can try disabling USB debugging or try this:
http://forum.xda-developers.com/showthread.php?t=2391236
If you are on custom ROM, it appears there may be an MTP issue with some ROMs.
Yes I am using the stock rom .all I did was root it and I have tried with no success with usb debugging turn Off as well. I have even tried to uninstall the drivers I used to root the tablet , but can not find them to uninstall or delete them
In devmgmt.msc the device is either listed under
Android Phone
Imaging device
Portable device
Unknown
Do you see any ? or unknown devices?
In Devices and Printers in the control panel its listed under Unspecified as Nexus 7 but you can not do anything with it there but right click on it and hit eject or properties and it says Google Nexus ADB interface ___ Android Device ___ status working properly and that's it .In Device manager it listed as Android Device ___ Google Nexus ADB Interface.
I Got it Thank you Thank you. I was able to uninstall the drivers there in the Device manager, unpluged the Nexus 7 plugged it back in it install the correct drivers and I am now able to mount my device as a MTP device and transfer files. Thanks again for the Help.
I put Android File Transfer on my Macs:
http://www.android.com/filetransfer/
and gmtp on My Ubuntu Ultrabook, and on my old Xubuntu desktop.
I put the SD card in the Ultrabook, and copied everything I wanted to the N7(2013).
In all cases, it worked pretty much plug and play, but I still consider it a work-around.
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed
I was having issues with adb not finding my device. These drivers worked for me...
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app
Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all
confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless
If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2
Hello everyone, been a while since I have been on this site.
I am in a dilemma which I hope you guys can help me with.
I have a samsung galaxy nexus, and I just wiped the phone. But there is no recovery, so I have no OS atm.I have tried the Android Toolkit, however, everytime I try using it I get problems. It says , " waiting for adb mode" . I downloaded SDK and have runned the adb.exe file, but a command prompt pops up, and a bunch of stuff pops up and scrolls down, and then it closes. It does nothing.
I have read that my drivers for ADB are not installed properly or whatever. So I tried uninstalling them from " device manager" and I tried reinstalling them. That didnt work. I tried uninstalling again and than downloaded a samsung galaxy nexus usb adb driver, which also did not work.
I just want to be able to place a ROM on my phone from the computer. If I can get that far, I can install it from recovery mode. But I cant even get it fully detected on my computer. Whenever I plug in the USB, it detects it, but drivers fail.
Also, in device manager, the universal serial bus controller, SM bus controller, and ethernet controller all have a yellow triangle over them. They always fail to install..
I have tried updating them from the device manager. But that has failed aswell..
Please someone help me. I am at a dead end and unsure what to do.
-Andrew
Try a different cable or different drivers. And please learn to use adb yourself and stop using toolkits.
Sent from my Galaxy Nexus using XDA Premium HD app
Can you enter in bootloader?
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
I can go into bootloader and recovery mode. I also tried a different computer and usb. It looks like its a bit better now because it actually says Galaxy nexus, instead of android device. However, I still cant go into ADB mode.
Everywhere I go, people say you need to enable debugging....but I dont have an OS. I am stuck in recovery or fast bootmode.
In the meanwhile, I tried installing zip file via sideload using Android Toolkit by skipsoft.( option 16) ....it looked like it was going to actually work...but it didnt. It says i dont have a recovery for TWRP or any of the other options.
You need to install fastboot drivers, and download 4.3 (or any you like) Google factory image for maguro. Flash that image, and install prefered custom recovery
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
I downloaded the fastboot usb drivers, however, I am not sure what to do with them.
Here's a pic of the files. I also download the adb files, and installed them, even though it said I had existing files.
andrewb71 said:
I downloaded the fastboot usb drivers, however, I am not sure what to do with them.
Here's a pic of the files. I also download the adb files, and installed them, even though it said I had existing files.
Click to expand...
Click to collapse
Enter bootloader on phone and connect it to PC. Phone probably wont be recognized. After that go to Device manager and find your phone ( as I remember it will say Android 1.0 or something similar), right click on it and press Update driver. In new dialog it will ask you whether you want to automaticly find drivers or manually. Press manually and select that usb_driver folder.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Hello. Im trying to root my N7 but my PC doesnt see it when I manually run adb or when I try auto root. I have done this before (when I first got it) without issue. Also I do have the drivers installed and the sdk so I am unsure why its not working. Additionally I tried on a 2nd pc and same thing. What am I missing? THanks!
RoachForLife said:
Hello. Im trying to root my N7 but my PC doesnt see it when I manually run adb or when I try auto root. I have done this before (when I first got it) without issue. Also I do have the drivers installed and the sdk so I am unsure why its not working. Additionally I tried on a 2nd pc and same thing. What am I missing? THanks!
Click to expand...
Click to collapse
Are you using the latest version of the Nexus Root Toolkit? It's got a driver installation guide to help these kinds of problems.
I often run into this with my Nexus 7. The two settings that have to be properly configured are enabling Android Debugging AND disabling Media device (MTP) in the storage settings (upper right hand corner - USB computer connection). Doing that usually allows the computer to detect the tablet as an ADB device, and go forward from there.
Good luck! Let us know how it goes.
thanks. downloaded the app but getting errors on my laptop (win8). will try on my pc tomorrow. also i should note that i have no problem seeing the nexus 7 in file explorer. i can move files without issue. Its only for adb that i cannot see it. i tried disabling mtp and going into fastboot mode but still no luck
thanks