Develop Bugs

A100 - ADB & Windows 7 (Virtual Machine - Virtualbox) ???

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

[Q] Rooting from tablet

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.

Does Odin work through Bootcamp or Parallels on a Mac?

Pretty straightforward question. I'm looking at going from a Windows laptop to a macbook and want to make sure some of the programs I use frequently work. Will Odin work via Windows on a Mac? Thanks.

Anyone? Really want to pull the trigger on this MBP, but want to ensure I can still tinker with my android devices...

i just used Odin and it would not work on my MBP with Parallels Win 7. I had to drag out my PC and then Odin worked fine

red321red321 said:
i just used Odin and it would not work on my MBP with Parallels Win 7. I had to drag out my PC and then Odin worked fine
Click to expand...
Click to collapse
How about boot camp? Do you think the issue has to do with drivers? Not familiar with Mac OS yet... My current laptop is the only windows machine I own and don't want to get rid of it in lieu of the MBP in case some of my programs don't work...

Haven't tried boot camp
Sent from my SM-P600 using XDA Premium HD app

Sent via PM, but finally realized why it wasn't posting in the forum (links)
...So posting here since someone else may need/want this at some point:
1) You'll want vmware fusion; there's a trial. You can easily install and uninstall it on a mac if you don't want to pay. Vbox and parallels won't work.
2) You'll need the Samsung USB drivers for phones exe from Samsung's website. You'll probably also want to separately get the Kies binaries (both windows bins).
3) MS offers pre-made VMs in virtualbox format (ova's); these aren't activated and expire in 30 days, but will still sorta work after that (they'll shut down after about 30-60mins after that point). Easy enough to just reimport; not sure how often you plan on using Odin. Kies itself is generally ok on a mac, but nothing else is (aside from like graphics-tab apps, and generic usb file stuff). You'll want to get Win7 vm images. These should work but if not you can google; MS doesn't make a secret of their VMs, they're made for developers to check compatibility between different versions of IE. Get all of these and then decompress, and you'll get an .ova file (links to Win7-IE10 VM archive files removed as I don't have 10 posts yet).
4) In VMware Fusion, you'll want to import the .ova file (.ova's are technically virtualbox images, but vmware will easily convert them to its own format). Once you've imported it go into the VM's settings and allocate 2gb of ram or so to the VM (I wouldn't go much below that; if you have a later mac that shouldn't be a problem; you might be able to get by on 1.5gb though I haven't tried). You'll also want to go into the vmware usb settings and make sure to be prompted when you add a device instead of just attaching it to one or the other or you'll wind up with issues, possibly, later on.
5) Boot the Win7 vm, install VMware tools, reboot, install samsung drivers, and then install Kies if you want Kies as well (Kies may also bridge some driver gaps, I can't remember; I do remember I had a bit of trouble with correct device recognition; I'll keep an eye on this thread and if you have a problem post publicly and I can message you with the proper driver set otherwise this should work afair); the problem, if I recall, was in detecting the specific USB devices/hub, if anything. DO NOT plug in your tablet until all of these drivers have been installed and you have rebooted the VM. You've been warned.
6) Boot the VM, plug the cable into the tablet, and then the other end into the Mac. If you've set up the USB prompting properly (btw make sure you set it to 2.0 not 3.0), you should get a prompt asking if you want to attach it to the Mac or Windows; choose Windows. The drivers should do there thing in a few minutes and eventually recognize the tablet. You may or may not want to reboot the VM one last time at this point before opening Odin, but at this point it should all work.
* A note: you'll probably want to enable a shared folder via VMware with the contents of anything you want to flash and the exes to flash them with; this is pretty straightforward in the VM settings. You'll want to copy/paste from that shared folder to the VM, not run from it; Odin and other stuff tends to hang if you try to run it directly from the share. I just keep everything I need or might want to use in the future on the VM and suspend it til I need it again, but you can just as easily shut it down and it'll retain all of the data, etc; just be mindful of the 30 day limit if you're using one of the precompiled VMs (as I said, they'll still work, but it can get naggy and shut itself down if not in use (or maybe if it is, but I haven't had it bomb out on me mid-flash (yet, knock wood)).
Good luck and enjoy.

not a single problem with parallels windows 8 or xp. while i flash 4.4.2 via odin i surf the web on mac safari.

supremekizzle said:
Pretty straightforward question. I'm looking at going from a Windows laptop to a macbook and want to make sure some of the programs I use frequently work. Will Odin work via Windows on a Mac? Thanks.
Click to expand...
Click to collapse
VMware should do.
It works very well on Linux.

That's interesting...
jpl69 said:
not a single problem with parallels windows 8 or xp. while i flash 4.4.2 via odin i surf the web on mac safari.
Click to expand...
Click to collapse
Mind if I ask what release of OSX and hardware you're on? I know I was having some USB recognition problems with the other two, but that was 2 point releases ago on Mavericks (on 10.9.3 now, haven't tried again). It could be a MBP thing also. I wouldn't mind using Parallels (I have a licensed copy) if it worked for this; as it stands I use parallels for OSX, vbox for *nix and android, and vmware for windows OSes for various reasons.

Macbook Pro 13.3 2012. Mavericks updated, parallels updated with latest version. Windows 8.1 work fine with odin, but i use mainly windows xp. both configure with usb 3.0 driver.
12GB ram, 512GB SSD samsung evo (this is just for show off not relevant to update our tablet) .
i used vmware sideways with parallels but find that parallels it's more faster, reliable and more crash proof.
after you connect the tablet to mac you get the option to connect to mac or virtual machine. afterwards you allways have the option to connect/disconect the usb periferic.

rsd2000 said:
VMware should do. It works very well on Linux.
Click to expand...
Click to collapse
That's what I use; until Ben Dobell can fix Heimdall for Linux for the P60X series I've just been booting into Win7 via VMWare from my Linux machine.

jpl69 said:
Macbook Pro 13.3 2012. Mavericks updated, parallels updated with latest version. Windows 8.1 work fine with odin, but i use mainly windows xp. both configure with usb 3.0 driver.
12GB ram, 512GB SSD samsung evo (this is just for show off not relevant to update our tablet) .
i used vmware sideways with parallels but find that parallels it's more faster, reliable and more crash proof.
after you connect the tablet to mac you get the option to connect to mac or virtual machine. afterwards you allways have the option to connect/disconect the usb periferic.
Click to expand...
Click to collapse
I'm on a late 2013 13.3 MBP. I think back when I was trying to debug the problem I'd read that USB 3.0 and how it's handled on the latest MB might have something to do with it, but I can't recall correctly. I should probably retry just for sh*ts and giggles; was always on the most recent Parallels, VMware, and VirtualBox. That said, I've found VMware in general to be more stable on my particular machine, and quicker to boot/suspend/unsuspend. It could very well just be my imagination or preference though, nosing its way in.
And talking about hardware is never showing off, as long as you're making good use of it. OS wars, however, is another story.

MTP not fully working after unlocking bootloader

I unlocked my bootloader on my pixel xl and now when I select the "Transfer Files" MTP mode on my device, I can only copy files from the phone and not to it.
I copied twrp and the other files I needed to my google drive and proceeded with installing the RC Dirty Unicorns 11 for Pixel XL Marlin and got the rom fully working.
But MTP is still not working correctly after the bootloader unlock.
anyone have any ideas?
I am using the adb/fastboot/drivers package from xda located here. https://forum.xda-developers.com/showthread.php?t=2588979
It has worked fine for me for months, I am just hoping to find a way to copy all my files back to the internal storage from my windows 10 PC.

First, I'd recommend getting ADB and fastboot directly from Google to make sure you have the current version. Having read around on the Pixel XL forums for a couple months now, that seems to be the first necessary step in troubleshooting. Check this article for a how-to if you don't want the entire Android SDK: http://lifehacker.com/google-finally-lets-you-download-adb-and-fastboot-as-st-1790840830

I downloaded the official sdk platform tools from https://developer.android.com/studio/releases/platform-tools.html as the article states.
but that is only adb, fastboot, systrace, etc1trace, dmtracedump, sqlite3, etc
this platform sdk package from google does not include the pixel xl usb driver package that is included in the link I posted.
I have replaced the platform tools on my system with the offical ones from google to make sure.
I have now done some additional research and found this url
https://developer.android.com/studio/run/win-usb.html
I extracted the driver packages from Snoop05's thread that I linked and did a file compare with beyond compare.
They are exactly the same usb drivers that google published 9/20/2014
I am going to download the SDK Manager and check back in the thread.

The pixel USB drivers are stored on the phone itself.

aholeinthewor1d said:
The pixel USB drivers are stored on the phone itself.
Click to expand...
Click to collapse
Drivers are part of your operating system. I am using windows 10 and Microsoft provides them as part of the windows operating system and via windows update as part of Microsoft's WHQL program.
It is possible that from time to time Google will release a new driver package via the link I posted above or they will provide it to Microsoft for WHQL driver certification to update via windows update.
The device uses MTP and there for acts like a Camera presenting it's sd card instead of the old classic usb hard drive emulation. All phone manufacturers started using MTP because it doesn't require the phone to unmount the storage from the phone to access it. When it was unmounted on older phones it would cause apps to crash if they were looking for files on the storage when it was unmounted.
There is no folder on the device containing inf, cat, dll files to be used for driver installation.
Your device is being accessed with the generic driver that microsoft provided with the installation of windows.

joe ferreira said:
Drivers are part of your operating system. I am using windows 10 and Microsoft provides them as part of the windows operating system and via windows update as part of Microsoft's WHQL program.
It is possible that from time to time Google will release a new driver package via the link I posted above or they will provide it to Microsoft for WHQL driver certification to update via windows update.
The device uses MTP and there for acts like a Camera presenting it's sd card instead of the old classic usb hard drive emulation. All phone manufacturers started using MTP because it doesn't require the phone to unmount the storage from the phone to access it. When it was unmounted on older phones it would cause apps to crash if they were looking for files on the storage when it was unmounted.
There is no folder on the device containing inf, cat, dll files to be used for driver installation.
Your device is being accessed with the generic driver that microsoft provided with the installation of windows.
Click to expand...
Click to collapse
I'm aware of what drivers are. I'm going off of what people on here have said previously. I never specifically looked for them but multiple people have said the drivers are on the pixel so they can install to computer when connected.

aholeinthewor1d said:
I'm aware of what drivers are. I'm going off of what people on here have said previously. I never specifically looked for them but multiple people have said the drivers are on the pixel so they can install to computer when connected.
Click to expand...
Click to collapse
please do not take this the wrong way, those people are wrong.
The drivers are not "on the pixel"
I am on the latest insider preview of Windows 10 and have other weird stuff going on with build 15007 so if the android sdk doesn't fix it I will just reimage my pc.
It is time again anyways.
Thanks for your help.

joe ferreira said:
please do not take this the wrong way, those people are wrong.
The drivers are not "on the pixel"
I am on the latest insider preview of Windows 10 and have other weird stuff going on with build 15007 so if the android sdk doesn't fix it I will just reimage my pc.
It is time again anyways.
Thanks for your help.
Click to expand...
Click to collapse
Yea I assume something didn't sound right but didn't pay attention. I did a clean install on windows 7 on a new SSD the other day and didn't have to download android studio or any drivers. I hate windows 10
Edit. Like I said I never looked into it but I found this just now. Who's knows..
"Previous iterations of Android have removed the Mass Storage capability which made the phone act as an USB. Instead of that, we have MTP (Media Transfer Protocol). These standard MTP drivers come bundled with the phone and no need for separate installation.

ok let me explain a different way.
Plug in your phone.
open device manager
expand portable devices
double click on Pixel XL
Click the Driver Tab
This will show you that the MTP driver for the Pixel XL is provided by Microsoft and written on 6/21/2006.
This is the Microsoft provided generic driver for all MTP devices.
Google provides directions here... https://developer.android.com/studio/run/oem-usb.html#InstallingDriver
for how to update the MTP driver for android devices.
I wasted the last hour downloading Android Studio to check out it's usb driver and it is the same as the ones in the other 2 packages.
Off to wipe my PC.

Cannot enter UEFI on Surface RT

I got and old Surface with windows RT 8.1. I went to settings and I reset it to factory (basically reinstalling the OS).
I wanted to upgrade to win 10 from a prepared bootable USB stick but it didn't boot from it. I tried also starting with vol-down and power button.
So I figured that I had to configure UEFI to be able to see the USB drive as boot option.
However, I can't enter UEFI. It just boots normally from the HD. After a lot of searching I tried :
- Vol up + power btn
- Shift+restart
- "shutdown /r /fw" from elevated command window
- There is no "UEFI Firmware Settings" entry found in Settings>Update & security>Recovery>Advanced startup>Troubleshoot >Advanced Options
- msifo32 shows that UEFI is present.
Any suggestions?

palosanto0 said:
I got and old Surface with windows RT 8.1. I went to settings and I reset it to factory (basically reinstalling the OS).
I wanted to upgrade to win 10 from a prepared bootable USB stick but it didn't boot from it. I tried also starting with vol-down and power button.
So I figured that I had to configure UEFI to be able to see the USB drive as boot option.
However, I can't enter UEFI. It just boots normally from the HD. After a lot of searching I tried :
- Vol up + power btn
- Shift+restart
- "shutdown /r /fw" from elevated command window
- There is no "UEFI Firmware Settings" entry found in Settings>Update & security>Recovery>Advanced startup>Troubleshoot >Advanced Options
- msifo32 shows that UEFI is present.
Any suggestions?
Click to expand...
Click to collapse
You can't, there is nothing configurable on an RT. Inserting the USB and powering on while holding volume - is all that is required.
To install 10 on an RT from USB you need to make sure you have removed Golden Keys if you had it applied otherwise the USB just won't boot. Beyond that the RT can reportedly be picky about what USB drives it will and won't boot from so I would recommend trying another drive. Have you tried booting an RT 8.1 recovery USB to confirm the drive is bootable under more normal conditions?

Thanks @jwa4
I created another RT8.1 recovery USB drive and this time I was able to boot to the 'blue' recovery screens.
It looks like the first USB stick wasn't created correctly.
I'm not particularly keen on installing win 10. I read that it runs sluggish and less snappy than 8.1 (which is not the fastest anyway on such small machine).
Is this the only way to run apps outside the MS store? Is there any way to run them in 8.1?
I found this very complete guide to installing 10
How to install Windows 10 on the Surface RT - Alexenferman
www.alexenferman.com
Would it be enough stopping after disabling secure boot to be able to install any desktop app in 8.1 or I need windows 10 to do so?
Thanks

palosanto0 said:
Thanks @jwa4
I created another RT8.1 recovery USB drive and this time I was able to boot to the 'blue' recovery screens.
It looks like the first USB stick wasn't created correctly.
I'm not particularly keen on installing win 10. I read that it runs sluggish and less snappy than 8.1 (which is not the fastest anyway on such small machine).
Is this the only way to run apps outside the MS store? Is there any way to run them in 8.1?
I found this very complete guide to installing 10
How to install Windows 10 on the Surface RT - Alexenferman
www.alexenferman.com
Would it be enough stopping after disabling secure boot to be able to install any desktop app in 8.1 or I need windows 10 to do so?
Thanks
Click to expand...
Click to collapse
It's still possible your USB was created correctly but was prevent from booting by Golden Keys jailbreak if you ever had it. To confirm you could try removing it using this (can also be used to assist in jailbreaking):
Tegra Jailbreak USB - Windows
All-in-on jailbreak package for Tegra based Windows RT tablets
jwa4.gitbook.io
The guide you linked to is out of date. Windows 10 replacing Windows RT 8.1 isn't considered all that usable, it's just for fun really but if you are interested take a look at this:
Windows Media Builder - Windows
Automated preparation of Windows RT 8.1 & Windows 10 Installation Media
jwa4.gitbook.io
To run 3rd party ARM32 apps under Windows RT 8.1 my advice is to install Golden Keys, install Yahallo and then enable UMCI Audit Mode. Using this method you don't need to test sign everything and you can keep a fully up to date Windows RT 8.1 installation.

jwa4 said:
It's still possible your USB was created correctly but was prevent from booting by Golden Keys jailbreak if you ever had it. To confirm you could try removing it using this (can also be used to assist in jailbreaking):
Tegra Jailbreak USB - Windows
All-in-on jailbreak package for Tegra based Windows RT tablets
jwa4.gitbook.io
The guide you linked to is out of date. Windows 10 replacing Windows RT 8.1 isn't considered all that usable, it's just for fun really but if you are interested take a look at this:
Windows Media Builder - Windows
Automated preparation of Windows RT 8.1 & Windows 10 Installation Media
jwa4.gitbook.io
To run 3rd party ARM32 apps under Windows RT 8.1 my advice is to install Golden Keys, install Yahallo and then enable UMCI Audit Mode. Using this method you don't need to test sign everything and you can keep a fully up to date Windows RT 8.1 installation.
Click to expand...
Click to collapse
All I really wanted is to be able to run apps outside the MS store. Not so much upgrade to win 10.
I never jailbroke the system, it's the original as far as I recall but I used recovery once to completely wipe and reinstall RT.
Is there a good guide or video for Yahallo and UMCI enabling?
Also, I imagine that I'll still be limited to ARM32 apps despite being outside the Windows store, right? So I still cant install say, firefox or regular desktop apps meant for X386.
Is it even worth the effort? Where can I find a list or repository of arm32 apps so that I can decide or not to do anything?
Thanks again

Correct, you would still be limited to ARM32 apps but these devices are really just for playing around with. As for an app repository, there is a Discord group where some ports are posted at but there isn't a massive selection: https://discord.gg/BGfMNjWX4B
There is an all in one jailbreak guide at:
Tegra Jailbreak USB - Windows
All-in-on jailbreak package for Tegra based Windows RT tablets
jwa4.gitbook.io
Alternatively there is information on them individually...
Golden Keys:
Golden Keys / Longhorn - Windows
Secure Boot Debug Policy
jwa4.gitbook.io
Yahallo:
Yahallo - Windows
Tegra 3 and Tegra 4 TrustZone UEFI variable services handler exploit and Secure Boot unlock tool
jwa4.gitbook.io
UMCI Audit Mode:
UMCI Audit Mode - Windows
Bypassing User Mode Code Integrity Check
jwa4.gitbook.io

Thanks. Nah, like you said, I was really playing with it ... I think I'll leave it as is and try to sell it.
Thanks so much!