Develop Bugs

[Q] ADB for Windows RT

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

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.

Surface RT (and probably other WoA tabs too!) vhd boot

I have successfully managed to get vhdboot to work on my surface rt, using a seperate external USB hard drive.
The annoying thing was trying to figure out why setup bombed out, but I got past that!
You'll want a brand new drive, or anything where you have nothing to lose, as you need to repartition and reformat the USB hard drive you want to use.
1) Follow this technet article: hxxp://technet.microsoft.com/en-GB/library/hh825686.aspx#RecommendedConfiguration - to set up the partition layout and assign drive letters to the partitions. Remember to update the partition sizes as suits your hd. You don't need to follow the part about the recovery image.
2) Create a new vhd on drive W: (going by the drive letters in that technet article!) and mount it. Use diskpart or computer management.
3) Prepare the install.wim of whatever build of Windows RT you wish to install (add your driver pack using dism). Remember that the build of Windows RT you want to use needs to be signed with the PRODUCTION certificates, NOT the test ones, otherwise secureboot won't let it run! (if you're using any public preview or RTM, then you don't need to worry as it's obviously signed with the prod certs)
4) Apply the new install.wim to the vhd using dism.
5) bcdboot W:\windows /s S:
6) With your initial Windows RT install running, insert the drive into your Surface RT. Boot from that usb drive (use a reboot, not holding volume down). It should go right into second stage setup.
7) When it reboots again, make sure to boot to your initial RT install, then reboot back into the USB. If you get a BSOD here, and you have rebooted into the usb drive from a running Windows RT, you might need to mount the SYSTEM hive of the VHD (Windows\System32\config\SYSTEM) and change HKLM\[mounted SYSTEM hive]\ControlSet001\services\FsDepends\Parameters\VirtualDiskExpandOnMount from 1 to 4.
8) After rebooting successfully, third stage setup and oobe should go without a hitch.
After installation, remember you need to boot to your initial Windows RT install on C: and then reboot to the USB, not boot from USB by holding down volume down, or you'll most likely get a BSOD. I'm still not sure what causes the BSOD, and if you wanted you just install WinRT raw on the hd, instead of inside a vhd, there'd probably be no BSOD issues.
It's been a while since I last set up another VHD install on my surface RT, but if you have questions or problems reply and I'll do my best to help you!

Why are we don't look on it just like on generic "arm" device?

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

How to flash Gemini!?

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