Related
So you're a user of that hot-from-the-oven Ubuntu 11.10 (it's improved tremendously from 10.04!) and you have a Xperia phone.
Natively on Ubuntu, you can do the following:
Manage its SDcard's contents with the system's file manager
Use ADB (provided that you install the SDK)
Use Fastboot
However, you can't:
Update and manage your phone with the PC Companion Suite or SEUS
Use Flashtool to flash FTF files
Those things need Windows, because neither PC Companion, nor SEUS or Flashtool work in Linux. Does it mean you have to ditch Linux and come back to old Bill's bordello? Nope! Does it mean you have to waste more than half your disk space with a dual-boot solution? Nope!
Virtualize Windows! This means that you can play a Windows virtual machine on your computer, not very different from good old console emulation. The advantages are obvious:
It doesn't eat half your disk space just because
You can fire it up when necessary
It doesn't need a whole lot of ressources from your host computer
The disadvantage is that you can't really do this on a very low-powered computer like a cheap netbook. A dual-boot solution makes more sense there.
However, we'll focus on the virtualization solution here. The main requisite, aside of a legally obtained ISO and key of Windows 7, and a computer with enough muscle to lend some RAM and processing power to the Windows 7 guest system, is that you have superuser access to your Ubuntu system.
1. You'll need Oracle's Virtualbox, which you can download here. Pay attention: VIRTUALBOX OSE EDITION WON'T WORK. If you have it installed, uninstall it before installing Oracle Virtualbox: you won't lose the VM's you had created, and they're compatible with both versions.
2. Once you've installed it, DON'T OPEN IT YET. install the Virtualbox Extension Pack. Without it, you won't have USB capabilities in your VM, so you won't be able to connect your phone.
3. You also have to register your user name. Fire up a terminal and write:
sudo usermod -G vboxusers -a
Click to expand...
Click to collapse
Restart your computer afterwards.
4. Open Virtualbox and create your own Windows 7 VM. It's pretty straightforward and you have a great wizard assistant to help you, so you won't get lost. Once it's created, install Windows. Once the process is finished, shut down the VM.
5. Select the VM in Virtualbox's main menu, and click on Configuration. Click on the USB tab. Toggle on USB 2.0 support, and the other checkbox below. Now you'll have to add "filters" for devices. Connect your switched-on phone, and click on the green + symbol in that tab. You'll see that you have a new possible filter: [SEMC HSUSB Device]. Mark it and check it. This will rerout the phone's connection so that, when you connect your phone, it is recognized by Windows instead of Ubuntu.
6. Switch off your phone, and connect it in Flash mode (holding the Back key while you plug it to the USB cable, it gives you a green light). Add a new filter, and select [Sony Ericsson Mobile Communications AB S1 Boot Download]. This is the most important one, as it will allow you to use PCCompanion, SEUS and Flashtool.
6-1. Optionally, you can connect it as well in Fastboot mode (holding the Search key, or the Menu key in other Xperia phones; it gives you a blue light) and add the filter [Sony Ericsson Mobile Communications AB S1 Boot Fastboot]. Paired with the appropiate drivers, that will allow you to use your phone in Fastboot with the VM (I have done it myself, it's less confusing if every operation is done in the same environment).
7. Fire up the VM now, and install EVERY SINGLE DRIVER. PC Companion, Gordon's Gate, and the Fastboot one if you choose to use Fastboot on your VM (which, again, I recommend if we're going through this virtualisation route).
8. Connect your phone normally and in Fastboot and Flash mode so that everything goes smoothly. You have to do a little workaround to install the Fastboot drivers. Your device won't be automagically recognized like in the Flash mode, so you will have to enter the VM's device manager in the Control Panel. A device called S1 boot Fastboot will appear with a warning sign. Right click on it and click on Update driver. Pick the manual option, and point the explorer to the folder where you've extracted the Fastboot driver. it will give you a warning, you will install it anyways, and once it's done...
9. Once it's done, you can do anything you need.
If you've followed this tutorial properly, you should be able to manage your Xperia phone on Ubuntu.
enjoy!
Couldnt you just install WINE and run the Exe from that?
Thats the way I've always done it for .EXEs anyhow.. but I'm yet to update to 11 "...TONIGHT WE FEAST!"
Flashtool doesn't work on Wine as of the latest version.
There is now a version of flashtool for Linux http://forum.xda-developers.com/showthread.php?t=1308862. I'am now having trouble mounting my R800i I get this error: Unable to mount R800i - Error initializing camera: -60: Could not lock the device any help would be much appreciated.
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable
When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2
download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium
i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium
You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.
Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.
bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.
I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?
Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC
Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app
I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app
Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse
rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
maigre said:
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
Click to expand...
Click to collapse
Crazy as it sounds, try another USB cable. Reboot everything, plug in fresh, and try again. Failing that, use WUGS to reinstall all your USB drivers. Use the stock Google.
The cable was the culprit. I tried another and it worked. Thanks so much!
I'm having a similar problem that's driving me insane.
Nexus 7 wi-fi version
I've loaded every driver on the planet and in recovery mode it simply will not show up. And I'm not talking won't show up using ADB, I get absolutely nothing in device manager. So before anyone tells me to point to the device and manually change the driver, there is no device to try and point a driver to.
In "normal" mode, it shows up perfectly fine in Device Manager as Android ADB Composite Device. ADB will list it in devices with no problem. It will accept the "adv reboot recovery" command perfectly and reboot the tablet into stock recovery. The minute it does that, the device disappears from the Device Manager list and nothing takes it's place. I've tried to have it search for new hardware, I've tried the Google USB drivers kit, I've used Koush's Universal Driver install. I've used 3 different cables on 2 different USB ports.
This is a completely stock N7 running 4.4.4 plugged into a Windows 8.1 64 bit PC.
The last thing I'm wondering is do I have to unlock the bootloader at all? I don't want to because it'll wipe the tablet. If so I guess I'll just wait out the actual OTA rather than try to sideload it.
Any suggestions would be appreciated.
Yaz75 said:
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Any suggestions at all?
Ummm... does the Stock Recovery actually run "adbd" by default? If it doesn't (or it doesn't start adbd until you execute the sideload menu item), then you wouldn't normally see anything on the other side of the cable with a stock Recovery. (I don't have my tablet with me to check)
Here's an extra "any suggestion at all":
Get rid of Windows and use Linux; there are no drivers to screw with in the latter case.
No, seriously. But probably not what you are thinking.
If you can get a "live CD" to boot** on your PC, you can (as root) run the "lsusb" command to see what devices are enumerated on the USB bus, port by port.
In conjuction with the decoder ring at the end of this post, you can determine from inspection of the USB VID/PID identifiers whether or not all the hardware is behaving, and whether or not the tablet is in the mode you think it is supposed to be in.
The reason this is valuable is that it allows you to take drivers completely off the table; if everything is as it should be, then you know that all the hardware and cabling are functioning correctly, the tablet is behaving correctly, your PC hardware is behaving correctly, and that 100% of the problem is Windows driver issues.
If you want to go the extra 1/4 mile, you can put a copy of (Linux) fastboot & adb plus your flashables on a USB key, and run adb or fastboot from the Live CD boot. It won't matter that the live CD doesn't have them preinstalled, they will be on your USB key. It will be easier on you if you can find statically-linked fastboot and adb binaries; if not you will have to copy one or two supporting shared libs (.so files) along with the binaries, and find out what LD_LIBRARY_PATH is all about.
suppose the USB key mounts at /media/usb1; then
$ sudo /bin/bash
# mkdir /tmp/tools
# cp /media/usb1/fastboot /media/usb1/adb /media/usb1/*.so /tmp/tools/
# chmod 755 /tmp/tools/*
# export LD_LIBRARY_PATH='/lib:/usr/lib:/tmp/tools:.'
# cd /tmp/tools
# ./fastboot devices
OR
# ./adb devices
Good luck; as you are using Windows you are going to need it. Hahaha LOL
**depending on whether your BIOS on your win 8.x PC can be toggled between UEFI and Legacy modes or not, this can be either trivial (Legacy boot mode) or complicated (UEFI) requiring a "Trusted Computing" crypto boot shim from MisterSoftie.
Ok this works for me
Use USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
delete all the associated drivers like Google, Samsung, etc for ADB, etc
Restart Computer
Reconnect N7 without MTP and USB debugging
Wait for PC to recognise device and install driver
*If you see something like PC unable to recognise device, go into device and Update Driver and choose "Automatic....."
Disconnect and Reconnect with MTP and USB Debugging
Wait for PC to recognise device and install driver
Restart N7 in bootloader
Wait for PC to recognise device and install driver
Profit
* My PC OS is Win 8.1 Pro 64bit
make sure mtp is switched off, i couldnt get adb or fastboot on my nexus just now . switched off mtp and works fine
Any Linux users managed to get LG Bridge working? I've tried running the Windows version with Wine but it crashes immediately.
I got it to run on Arch by installing lib32-libldap, but I can't get it to recognize the device via USB. (I'm working with an LG 360 camera.)
Solutions?
Running on Antergos but it cannot detect my phone via USB... Same problem. Any solutions? I'm running it in Wine and I installed the Windows LG K30 drivers for my phone.
Dual boot using grub?
I mean, some things are more trouble, to get them to work, then they are worth (assuming you even can). I hate windows, but I can boot it, not connect to the internet (thus no malware concerns), run specific things, reboot linux. It works for me.
Using a virtual machine worked fine for me.
well not certain about bridge but to get adb + fastboot + mtp working
sudo apt-get install adb
sudo apt-get install fastboot
*enable usb debugging on phone & connect as usual
for mtp file or photo just google install instructions for libdl
i got here searching for lgup on linux ... thought I'd leave a bit of useful advive & leave
guess I'm sol in regards to LG tool to flash .kdz file on linux ...
aaah well life after windows
As a Mac user, my options seem limited. The only way I found to install ubuntu touch on my fairphone 2 is ubports. Am I missing something?
However, ubports recognizes my phone but does not start with installation. I am asked to connect the phone via USB. Of course this already is the case – otherwise it would not have been recognized
(I followed the instructions for preparation – developer mode: on, oem unlock, usb debugging: on. I also checked the usb mode to be transfer mode and I tested another usb chord)
I would appreciate any help.
Try this
Download and install the latest installer for ubports.
Open terminal type and enter these 2 lines:
cd /Applications/ubports-installer.app/Contents/MacOS/
sudo ./ubports-installer
When prompted enter your Mac is admin password.
The installer should work correctly now (has something to do with admin privileges for adb and fastboot).
I had the same problem installing on my nexus 4, then it worked perfectly after entering the 2 command lines in terminal.
Hope this helps.
Sent from my LG-V500 using Tapatalk