Can I root my nexus from a Microsoft Surface? It has a USB port. I'm trying to do this because my nexus drivers won't install properly on my laptop.
Surface or Surface Pro? I ask because I don't know about you being able to load the appropriate drivers to recognize your tablet on Widows RT. Are you able to run command prompt? That's the biggest factor here.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
aarsyl said:
Surface or Surface Pro? I ask because I don't know about you being able to load the appropriate drivers to recognize your tablet on Widows RT. Are you able to run command prompt? That's the biggest factor here.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
Click to expand...
Click to collapse
It's the 1st gen surface. And I'm not sure if i can run a command promt. I'm sort of a noob.
If it's a surface 1/2 then no/not easily at all.
The drivers dont require custom code from goog to install on winrt, they only require generic usb libraries to make the fastboot driver work.
It would be as simple as ms releasing the missing pieces to driver devs, which they have much less reason to do as there's no expectation of support for arbitrary devices on winrt.
(I dont have a winrt device so I could be mistaken but) winrt generally requires you to obtain drivers straight from ms, I don't think they generally allow manufacturers to distribute windows/arm drivers like they do for windows/x86.
You need to be able to use fastboot, and there isnt a windows/arm version available.
It might be possible to compile an arm version, but it's highly unlikely anyone has actually done this.
Even if there was, you would need to use the hack to enable unsigned desktop apps to run on winrt.
Related
Hey guys, I have been trying to get Windows 7 Drivers to work properly with adb on my A100. I have a Virtual Machine of Windows 7 and I have manually added the USB device ID's to the VBox settings for the VM client, Windows 7 sees the device ok and will mount the device fine via MTP. I can even get the drivers to say that they are working properly for the device, but when it all comes down to it they aren't.
I have tried using the ADB driver from the Android SDK which of course won't work out of the box since the device ID's aren't made for the Iconia A100, however I modified them to match the vendor/device IDs, but still - no go. I can do ' adb devices' and it will either show the device as offline or will just say the name and serial#, but when I try to connect it either says 'device offline' or it will give me a adb protocol error.
I don't know what else to really try, and at this point I am really thinking Virtualbox isn't passing the USB properly to the Guest OS, but what is odd, is my HTC WildFire S will work fine with adb (same binary).
I have also tried the Acer drivers that are available on the Acer Website, as well as a few other device drivers that I can't recall off the top of my head.
I guess some people are wondering if this is working in Linux why am I so concerned about getting it to work in a Virtual Machine running Windows. In short the answer is: I am developing kernels and recovery for the A100 as many may already know, and I am working on some automated installers that are cross platform compatible and I need to test the Windows side of things before I make releases, yet it's a bit hard to do when Windows is such a PITA when it comes to anything Android.. Yea, I'm a Linux person I know it's obvious - but I need this working somehow in a Virtual Machine because I'm not willing to do a native install of Windows on any of my machines, simple as that lol..
Anyone who may have a Virtualbox install of Windows 7 (or vista) that has adb working with their A100, please let me know the adb drivers you used and if at all possible attach them here, or give me a direct link. I greatly appreciate the help guys!
Here is a snippet of the troubles:
Code:
List of devices attached
037c624643a033d7 device
C:\Users\Lance\Downloads\godmachine81-Acer-A100-TWRP-Installer\godmachine81-Acer
-A100-TWRP-Installer-c8ccd42>adb shell
error: protocol fault (status 72 6f 6f 74?!)
**Edit: I kinda found a solution to my own problem, but not a great one. The problem was with EHCI 2.0 in VirtualBox, when this setting is disabled it will allow adb to work correctly, however on Windows 7 it will break the USB host so there is no possible way to use the tablet period, with Windows XP however it works fine. Windows XP has the exact same issue, but the USB Hub will actually work without EHCI 2.0, not really sure if there is a workaround to the Windows 7 problem, but I didn't really mess with it long - I'd say one might be able to uninstall the USB adapter and reinstall it after disabling EHCI and then also reinstall the Acer drivers. I got tired of fooling with windows 7 and just installed a copy of XP, wrote the batch script for windows, and will soon be uninstalling most likely haha.. Hope this might be some good info for others who run into a similar issue
Can ADB run on a windows rt device?
Given the nature of this site, I'm going to guess you mean Android Debug Bridge, though there are far too many three-letter abbreviations in the computing industry for it to be smart to not give the full form once.
Short answer: No.
Slightly longer answer: Not right now, possibly never.
Real answer: RT can't run x86 programs, and the version of adb.exe that comes with the Android SDK for Windows is a 32-bit x86 program. However, it might be possible to either re-compile the program for ARM (I assume it's open source), or to run it under the win86emu dynamic recompilation tool (most likely not supported yet, but possibly in the future). However, there's no guarantee that the drivers needed to connect to an Android device for debugging will ever be available for RT, in which case it doesn't do any good to run the program because it can't connect to anything. I believe at present RT can browse an Android device connected in USB Mass Storage (UMS) or Media Transfer Protocol (MTP) mode, and can charge one (but probably slowly), but that's about it.
GoodDayToDie said:
Given the nature of this site, I'm going to guess you mean Android Debug Bridge, though there are far too many three-letter abbreviations in the computing industry for it to be smart to not give the full form once.
Short answer: No.
Slightly longer answer: Not right now, possibly never.
Real answer: RT can't run x86 programs, and the version of adb.exe that comes with the Android SDK for Windows is a 32-bit x86 program. However, it might be possible to either re-compile the program for ARM (I assume it's open source), or to run it under the win86emu dynamic recompilation tool (most likely not supported yet, but possibly in the future). However, there's no guarantee that the drivers needed to connect to an Android device for debugging will ever be available for RT, in which case it doesn't do any good to run the program because it can't connect to anything. I believe at present RT can browse an Android device connected in USB Mass Storage (UMS) or Media Transfer Protocol (MTP) mode, and can charge one (but probably slowly), but that's about it.
Click to expand...
Click to collapse
You may be able to run ADB over the network with the x86 emulator, if it has the network part implemented.
The ADB is open source but the windows port uses cygwin so we would need to wait for cygwin on RT which would be alot to ask for right now.
There's a way
1) Install an X 86 Emulator. Ref - http://forum.xda-developers.com/showthread.php?t=2095934
2) Test and Install the apps you like. Ref - http://forum.xda-developers.com/showthread.php?t=2092348
You might want to try running ADB, and see if that works.
Note - Whatever I posted here is not guaranteed to brick/unbrick your device or any related actions. So it is purely left to you on what you do with your device and has nothing to do with my update(s) here, even if it renders your device unusable or inconvenient or similar by any means and extent.
Update: Just realized that
1) The emulator doesn't work for Win RT 8.1 as Jailbreak doesn't work for WinRT 8.1
2) Hence no way for ADB to run on Win RT 8.1
vcsekhar said:
Update: Just realized that
1) The emulator doesn't work for Win RT 8.1 as Jailbreak doesn't work for WinRT 8.1
2) Hence no way for ADB to run on Win RT 8.1
Click to expand...
Click to collapse
And that the thread is old and that your solution was already addressed above
Hello XDA,
I am having issues getting ADB set up on OSX Lion. My end goal is to root my G2 and downgrade it to 2.2, but, for now, I just need help setting up ADB.
The G2 is running 2.3.4 and my MacBook Air, Lion 10.7.5.
I have USB debugging, Stay awake, and Allow mock locations checked in Development settings.
The USB cable is fine, I think, because 1.) it worked fine on my PC two weeks ago, and 2.) the phone charges just fine.
I do not have EasyTether (or anything else, similar to it) installed, nor have I ever. I have, essentially, a "clean" OSX Lion install.
I installed the ADT Mac Bundle from Google and everything appears to be in order, except that, when I run "./adb devices", none are listed.
Unfortunately, I do not have access to a Windows or Linux machine, otherwise all of this would be a non-issue.
I don't know if it's supposed to, but the G2 doesn't seem to appear in System Profiler/Information in OSX. I could be looking in the wrong place though.
I think that covers pretty much everything I've done up to this point. Does OSX just not support G2/Vision? Would running Ubuntu in a VM make a difference?
Any help would be greatly appreciated!
Hi folks, i'm going thru all this posts about unlocking bootloader on Surface RT and I see that everyone is focused on OS platform, which is Windows RT. Why are we don't look on it just like on generic "arm" device? I thought a lot about that and I got an idea that it should be possible to unlock it in same way like onther tegra 4 devices.
Unfortuanelly I don't have a second pc to let it try this way... In my opinion It would do.
1 - step - booting with secureboot patch (Debug mode)
2 - step - connect Surface RT with other pc (need to have male/male usb cable) with ADB and FASTOOL.
3 - step - run in command prompt "adb devices", "fastboot oem unlock".
4 - step -Theorytically bootloader shoud be unlocked, we are able to install new OS.
Who dares to try ??
This is not going to work, as surface RT simply does not have fastboot (which is only usable for android).
robcie1058 said:
Hi folks, i'm going thru all this posts about unlocking bootloader on Surface RT and I see that everyone is focused on OS platform, which is Windows RT. Why are we don't look on it just like on generic "arm" device? I thought a lot about that and I got an idea that it should be possible to unlock it in same way like onther tegra 4 devices.
Unfortuanelly I don't have a second pc to let it try this way... In my opinion It would do.
1 - step - booting with secureboot patch (Debug mode)
2 - step - connect Surface RT with other pc (need to have male/male usb cable) with ADB and FASTOOL.
3 - step - run in command prompt "adb devices", "fastboot oem unlock".
4 - step -Theorytically bootloader shoud be unlocked, we are able to install new OS.
Who dares to try ??
Click to expand...
Click to collapse
We talk about OS, because they aren't generic arm devices. Nearly every RT device uses a different CPU. Generic ARM images require specific drivers for the device. ARM is extremely fragmented, it isn't like x86.
Also, this isn't an android device. It doesn't have Android Debug Bridge
Hi all,
I purchased a gemini wifi recently, but a 4g version arrived! I'm now trying to flash Linux on there, but I cannot get the flash tool to do anything.
I'm pretty sure that this is a driver issue, but I'm not sure what to do about it. I've tried windows 11 and 10, as well as ubuntu 20.04 to flash this thing and nothing is working.
On the windows 11 host I even disabled memory protection to allow the drivers to work correctly, but that made no difference.
Following the guides on planet computer, it's not clear what state the device should be in, but I've tried normally booted into android as well as in recovery mode (booted with Esc and side button depressed on boot}
What am I missing here? Does flashing this device just no longer work?
Thanks in advance for your help!
it still works presuming you are referring to this guide: https://support.planetcom.co.uk/index.php/Linux_Flashing_Guide
I unfortunately don't think I am able to help you debug the situation from the information you provided.
I am not sure where most of the users congregate, but I have seen some sporadic recent activity here: https://www.oesf.org/forum/index.php?board=192.0
From my own experience, windows 7 and windows 10 have worked flawlessly, ubuntu worked for me in the past, but had trouble recently. win7 and win10 in virtualbox requires delicate usb device setup adding device during gemini reboot, and still gives some trouble.
I haven seen any updates or security patches from planet on neither android nor debian, so got myself a sailfish X license to support their development, it looks like a lot of updates (most recently yesterday: https://forum.sailfishos.org/t/release-notes-vanha-rauma-4-4-0-72/ )
good luck