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.
Related
Started to mess about with this earlier today, finally got the damn thing to work Turns out it is quite easy..
First, to get one thing straight, this will only boot the kernel, it will dump you at a shell which you have to remotely log on to via telnet over usb. There will be some (not so) fancy text appearing on your phone's screen but that is about it. Also, it only works on unlocked phones.
This is what you get:
On your computer you'll get this:
Cool, huh? Btw, this is running from a memory card, your OS will be untouched so as soon as you reboot the phone it will boot right back into WM2003/5/6.
1. What you need
* A HTC Typhoon running any rom of your choice (I did it on WM6).
* A miniSD memory card
* A Linux distro - I downloaded the Ubuntu Live CD and ran it through VMWare, no need to install anything or reboot your computer.
* miniSD image of Xanadux - this is the linux port for HTC devices. Grab the latest version here: http://rapidshare.com/files/92218185/Linux.zip.html
(these files are extracted from the miniSD image file found here: http://vivien.chappelier.free.fr/typhoon/download.html)
2. How to run linux on the Typhoon
1. Instead of installing linux properly on your phone which requires partitioning of the internal memory etc (a lot can go wrong) we'll put it on the memory card then a Windows Mobile program called HaRET will boot linux for us from WinCE. Completely non invasive in other words.
This bit is dead easy, just extract the Linux.zip file you just downloaded and copy the files to the root of your memory card (must be memory card, can't do this from the internal memory afaik). Next, go to the File Explorer on your phone and find the file HaRET.exe. Run it then press the run button (this button has focus when you execute HaRET.exe so just press the joystick when the windows appears) and you will see a message saying "Booting linux", then after a few seconds your screen will go black and some text will appear.
Voila! That's linux running on your phone!
2. Connect to the phone via telnet
If read the last line of text that appeared on screen you'll see that it says "Press enter to activate this console" but no matter what buttons you press on the phone nothing happens, some gibberish appears but that's it.
Solution: telnet to the phone from your computer.
Get Ubuntu to boot on your computer, then go to Applications->Accessories and run the Terminal. Next type in the following commands:
Code:
modprobe cdc_ether
modprobe usbnet
ifconfig usb0 up 192.168.9.1
and finally
Code:
telnet 192.168.9.10
Login with username root and you'll find yourself at a shell like the screenshot above. Everything you see from now on is coming linux from your phone!
I've noticed that Xanadux doesnt always initialise the USB port unless it is connected via USB when booting up so make sure you always have your phone connected via USB when you run HaRET.
Now I'm going to try to figure out how to get the GSM module to work...
LINUX based ROM??
Hi shandar,
I have read your post and I am interested to know if you are cooking a LINUX based ROM that will run in a WIndows Mobile device? That would be too good to be true.
Also another question is do you need to have Linux running on your desktop to make this tutorial work?
ryanchanmd said:
Hi shandar,
I have read your post and I am interested to know if you are cooking a LINUX based ROM that will run in a WIndows Mobile device? That would be too good to be true.
Also another question is do you need to have Linux running on your desktop to make this tutorial work?
Click to expand...
Click to collapse
Hey, well, I don't know enough to make a linux rom for smartphones. I'd love a working linux distro for Typhoons & Windows Mobile phones in general but it is way out of my league unfortunately.
Btw, I probably should clarify that I only wrote the tutorial, the actual linux port is made by someone else.
3. INSTALL DRIVERS (Windows only)
Your Windows PC will show a notification that a device “APX” has been detected. If you get a
“Found new hardware” dialog box asking where to install drivers from - choose “list or specific
location”. If you don't get this dialog, open the Device Manager via System in the Control
Panel, find and double-click the “APX” device, and click the update driver button.
Select the “usbpcdriver” folder inside the extracted Adam Recovery Kit as the driver location.
You may receive a warning that the driver is not certified or signed by Windows – choose to
install it anyway.
I'm trying to install the new update, but when i get to this portion of the instructions, I cannot for the life of me get the computer on Windows XP to recognize my device as a APX file. It's not even an option in the control panel in add new hardware. The computer keeps trying to recognize it as nvida harmony device
i saw this webpage about it and it directed me to a nvida webpage and i have absolutely no idea which one to install or whatso...
http://androidforums.com/gtablet-support-troubleshooting/253801-nv-flash-full-factory-reset.html
help :X!
Not sure if this will help, but here is some info on recovering Adam. It mentions APX...
http://www.notioninkhacks.com/forum...px&sid=91f02de37f2a51935594d9a48f299488#p2278
Also check out the GTAB forums, as the problems will probably be similar. I think Windows 64-bit and APX drivers may not play nice, for example.
NVM....i read the stupid instructions wrong. it's power button and VOLUME DOWN ........grrrrrrrrrr
Just wanted to post a notice of success story of getting SEUS and Flashtool working under Ubuntu 11.04 with Virtualbox installed from the repository running Windows XP. This means that it IS possible to use both of these tools just fine under Linux (with Windows running as a guest). Looking around the web a few weeks ago led me to believe that it couldn't be done, as some people (Mac users IIRC) were having issues getting Virtualbox to properly handle the X10 when it is in flash mode. Here are the steps that worked for me:
1. Install Virtualbox from Ubuntu Software Center
2. Create a Windows XP virtual machine and install Windows
3. Add your username to the group "vboxusers" in Ubuntu (this will allow the VM to use USB devices) and reboot to apply the change.
4. Create a blank filter under USB in the settings of the main Virtualbox menu so that all USB devices can be picked up automatically.
5. Run SEUS and check for updates, first time doesn't work because it installs the drivers for flash mode, second time worked fine for me.
6. Use Flashtool, etc. as you like - fully functional.
It was just nice to realize I didn't have to look around for a Windows machine to borrow for the amount of time it takes to test out different basebands and custom ROMs/kernels, so I thought I would share here.
Post a link to this thread in the Flashtool thread...
Should be helpful for others...
sent from x10 CM7 (FreeXperia Project)
Amazing how i was told Vbox cannot do this.
Well done.
This is awesome. My SATA connector on the mainboard just broke and the disks attatched to it was my Windows 7 installation. Now that that is gone (until I get it fixed) I'll have to use this method because I had my Linux running on the reserve/backup PATA disk (just in case **** happens, and it came in handy now).
And I really don't want to re-partition those disks, reinstalling Windows, reinstalling Mint (Fixing possible GRUB or MBR issues etc.) So this is gonna come in very very handy.
As I'm writing this I'm installing XP in VirtualBox.
I had to reboot linux after adding the username to the vboxusers group before it could pick up my USB ports.
But else it's working flawlessly...
Original post updated with reboot instructions, thanks! Glad to hear it's working for you too.
Flashtool works in VirtualBox for Mac Users
Hi Everyone,
I confirm that it works in Virtualbox for Mac. The point was: create a blank filter for USB. I did it under the windows machine.
Thank You coverup!
coverup said:
4. Create a blank filter under USB in the settings of the main Virtualbox menu so that all USB devices can be picked up automatically.
Click to expand...
Click to collapse
This is the key point
I have been using it for past 2-3 months didn't knew that general opinion was that it doesn't works.
well i don't have a filter coz i use my usb devices on linux most of the time so i manually add device.
confirmed working on both virtualbox and VMWare too.........
anantshri said:
This is the key point
I have been using it for past 2-3 months didn't knew that general opinion was that it doesn't works.
well i don't have a filter coz i use my usb devices on linux most of the time so i manually add device.
confirmed working on both virtualbox and VMWare too.........
Click to expand...
Click to collapse
Manually adding doesn't work on mac, but it works on linux.
arkedk said:
I had to reboot linux after adding the username to the vboxusers group before it could pick up my USB ports.
But else it's working flawlessly...
Click to expand...
Click to collapse
I suppose reboot is not exactly necessary for linux. You just need to logout and login again to update the granted groups.
I didn't create a blank USB filter, because I don't want to catch every USB device.
Instead I created a filter for all devices with just the VendorId '0fce' to catch all states of my X10.
Amazing great work ,,Well done.
m.maga said:
Hi Everyone,
I confirm that it works in Virtualbox for Mac. The point was: create a blank filter for USB. I did it under the windows machine.
Thank You coverup!
Click to expand...
Click to collapse
anantshri said:
This is the key point
I have been using it for past 2-3 months didn't knew that general opinion was that it doesn't works.
well i don't have a filter coz i use my usb devices on linux most of the time so i manually add device.
confirmed working on both virtualbox and VMWare too.........
Click to expand...
Click to collapse
Hmm... Not working for me with virtualbox, a mac host and a Win XP guest.
First tried manually adding. Next, I put a blank USB rule at the top of the USB filters. This time, it successfully captured and the hardware install wizard popped up. FlashTool did not recognize the phone.
Soooo.... are drivers from SEUS needed (unclear on that)? Sony pulled SEUS for x10, by the way. If needed, has someone mirrored it somewhere? USB drivers are installed - FT and adb work fine when phone normally booted.
I'm using parallel 7 on osx lion
windows 7 runs very smoothly and it can read my phone's sd card
but x10 is not recognized in flash tool
i thought virtual box and parallel are similar
so how to create a blank filter under USB in the settings ?
m.maga said:
Hi Everyone,
I confirm that it works in Virtualbox for Mac. The point was: create a blank filter for USB. I did it under the windows machine.
Thank You coverup!
Click to expand...
Click to collapse
anakinlam95 said:
I'm using parallel 7 on osx lion
windows 7 runs very smoothly and it can read my phone's sd card
but x10 is not recognized in flash tool
i thought virtual box and parallel are similar
so how to create a blank filter under USB in the settings ?
Click to expand...
Click to collapse
I figured out my problem. It was just as I expected. A different set of drivers is needed to use flashtool to flash when the phone is in flash mode. It seems that many people take this for granted, since they've had an xperia for a while, it isn't explicitly mentioned in the flashtool posts.
The flashtool folder will something called gordons gate (IIRC). If you didn't install that and try again.
Does it really work? I just found out there is a problem for ADB working under windows 7 as a guest. It is also documented as a bug
https://www.virtualbox.org/ticket/6620
Given problem with that, I am very leery to even want to flash anything with that even though it is using a different driver.
Very good! After a lot of research. I was already trying fastboot, unsuccessfully, when I found this. Worked perfectly on Ubuntu 11.10 32b & VirtualBox.
One point I'd like to mention is that even creating the blank filter, besides flashing worked on first try, adb was not finding the device. I had to manually attach it, and more than once while rooting it. Pretty easy, but was unexpected and I wasn't waiting for something like that. May help others.
I still have to try filtering by verdor ID as suggested by User Name in post #10.
Thanks!
rapchan said:
Very good! After a lot of research. I was already trying fastboot, unsuccessfully, when I found this. Worked perfectly on Ubuntu 11.10 32b & VirtualBox.
One point I'd like to mention is that even creating the blank filter, besides flashing worked on first try, adb was not finding the device. I had to manually attach it, and more than once while rooting it. Pretty easy, but was unexpected and I wasn't waiting for something like that. May help others.
I still have to try filtering by verdor ID as suggested by User Name in post #10.
Thanks!
Click to expand...
Click to collapse
Dear all guys,
Does anybody know if is possible to use MTK Flashtool under a windows xp virtual machine (host-linux from virtualbox) in order to flash ROMS ¿?
I have already do this step "4. Create a blank filter under USB in the settings of the main Virtualbox menu so that all USB devices can be picked up automatically". But when i try to flash any ROM nothing happens. The preloader is not detected.. i get an error message similat this: "The usb-device is already in use on Host-linux.."
I would like to use MTK Flashtool on linux under a xp virtual machine
Regards.
m3n3chm0 said:
Dear all guys,
Does anybody know if is possible to use MTK Flashtool under a windows xp virtual machine (host-linux from virtualbox) in order to flash ROMS ¿?
I have already do this step "4. Create a blank filter under USB in the settings of the main Virtualbox menu so that all USB devices can be picked up automatically". But when i try to flash any ROM nothing happens. The preloader is not detected.. i get an error message similat this: "The usb-device is already in use on Host-linux.."
I would like to use MTK Flashtool on linux under a xp virtual machine
Regards.
Click to expand...
Click to collapse
I though Flashtool has supported Linux, why u need virtual machine???
Check this out :
http://forum.xda-developers.com/showthread.php?t=920746
XtremX10 said:
I though Flashtool has supported Linux, why u need virtual machine???
Check this out :
http://forum.xda-developers.com/showthread.php?t=920746
Click to expand...
Click to collapse
I did not know about linux version of Flashtool. I will check it thanks a lot !!
My phone is a Zopo ZP900 and the win version of Flashtool is 4.0 on Windows. I don't know if the linux version is compatible for my device (MTK 6577).
Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq
It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.
I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was
I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq
Drivers from acer website.
I have adb installed should this not be enough?
You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.
I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq
I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq
don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.
If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App
gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.
Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try
I'm trying to get my ADB interface working via the male-to-male USB cable. I can't install the drivers. I'm running windows 7 64 bit and copying the DLL's from i386 (I have an intel processor) to c:\Windows\SysWOW64 then using the command prompt in administrator mode: regsvr32 "filename".dll and I get the message "the module 'module name' was loaded but the entry-point DIIRegisterServer was not found. Make sure that 'module name.dll' is a valid DLL or OCX file and then try again."
I've also tried installing the drivers from the device manager and selecting a path to the driver folder.
Af far as I can tell these are the universal USB drivers. Any ideas?
Phoenix4848 said:
I'm trying to get my ADB interface working via the male-to-male USB cable. I can't install the drivers. I'm running windows 7 64 bit and copying the DLL's from i386 (I have an intel processor) to c:\Windows\SysWOW64 then using the command prompt in administrator mode: regsvr32 "filename".dll and I get the message "the module 'module name' was loaded but the entry-point DIIRegisterServer was not found. Make sure that 'module name.dll' is a valid DLL or OCX file and then try again."
I've also tried installing the drivers from the device manager and selecting a path to the driver folder.
Af far as I can tell these are the universal USB drivers. Any ideas?
Click to expand...
Click to collapse
AARRGGHH! Windows and its damn' driver problems! First did you disable driver verification? If not Google it. Then install MoDaCo's drivers using the Windows GUI tools (IIRC you get there from Device Manager). If all that doesn't "take", my best advice is to wipe all trace of Windows off your computer and install a sane operating system. Too radical a fix? OK, your funeral, but here's a halfway fix: download this Puppy Linux live-CD .iso that I've doctored with Fastboot and ADB binaries, and burn it to a CD.
http://www.mediafire.com/download/62oh30gzjzvsbew/sulu2-528.007-android.iso
Make sure you know how to burn a CD from a .iso file. The end result will have files and folders, not just a single .iso file on it. It's a bootable CD, so you guessed it, boot your PC to the CD. Don't try to run it in a VM, it won't work. Click on the terminal icon on the desktop and you have a box that looks and acts like the Windows DOS box; the OS commands are somewhat different but the fastboot and adb ones are exactly the same. In fact the terminal is the same as the one in Android, and since both devices are Linux now, driver problems disappear!
Do whatever dastardly deeds you want to the MOJO with Fastboot or ADB, eject the Linux disc, reboot--and as far as your PC is concerned, it never happened. The live-CD won't leave a trace unless you specifically tell it to.
Most of the tutorials on this MOJO forum give commands like "fastboot-linux flash twrp(version), this is MoDaCo's version of Fastboot. I put this live-CD together using Google's binaries so that command would look like "fastboot flash twrp(version). Keep in mind that with the MOJO the device ID string is mandatory; see the TWRP recovery thread for details, but you can't just send "fastboot devices", it won't work, you must send fastboot -i 0x0738 devices, or go straight to flashing or booting.
Well I don't know if I just cleared the waters some or just stirred it up more, but good luck and I hope I helped a little anyway!
This was how I was able to install my drivers on my Win 7.
Assuming that you've downloaded the superboot-mmm file and you've extracted to your C: drive:
1. Go to Devices and Printers under Control Panel
2. Right Click on the Fastboot device, and click on Properties
3. Click on the Driver tab, and click on Update Driver (or click on Properties)
4. Click on Browse My Computer For Driver Software (manually)
5. Browse the following location (or copy and paste this: C:\r3-mojo-superboot-mmm\windows.driver)
6. Select Next
7. The driver will be installed
If you now replug the MOJO, you should be able to see Madcatz ADB Interface under Hardware Tab when you click Properties
Source: my blog
Hope it helps.
Yes! Thank you
Yes, the problem was I was going a folder too deep in selecting the driver from the device manager. Thank you.