I am attempting to root this device (the Cricket variant) using the instructions on this forum, but have run into a serious problem. While Ubuntu sees the device when booted regularly and will pass control over to Virtualbox, Ubuntu (14.04) seems unable to see the device when it is in Odin mode, making it impossible in turn to see it in Virtualbox and perform the root. Has anyone successfully gotten Ubuntu to see the device while in Odin/Download mode?
why don't you install Windows as native os and get this over with?...
I mean, you DO have a way to install it or how did you install it in virtualbox in the first place?
Sent from my SM-G530H using XDA Free mobile app
Related
possibly silly question, seeing everyone is saying the rooting problem is something different(drivers(htc/pdanet/android sdk), sdcard, computer(OS)). you guys that have gotten ADB to successfully get the phone recognized in recovery mode:
Did the phone show up in the device manager for windows?
i feel like windows has to register the phone under a certain driver in order for ADB to pick it up(otherwise the OS doesn't recognize it like any other piece of hardware). maybe part of the problem is some people don't have a recovery driver?
just throwing it out there since I have tried every method on the forum except using the original sdcard that came with the phone(it's my my gf's phone at the moment and i haven't been able to get it from her)
also, does anyone know what eugene's setup is? OS, drivers, sdk version? or eugene if you see this, it would be wonderful if you could chime in.
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
What OS are you using? 32 or 64 bit? Do you have HTC Sync installed?
i've used winxp pro 32bit, win7 pro 64bit, win7 ultimate 64bit. i tried the htc drivers, the pdanet drivers and the sdk drivers. i just made a ubuntu boot drive, i think im going to try that later tonight.
and i think chrisinaz is trying to root his friends phone on the same computer he did his on if i'm not mistaken.
Using xp 32 bit and fedora 13. Neither work for his, both work for mine.
-------------------------------------
Sent via the XDA Tapatalk App
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
Where it says android 1.0 this is the driver that you need to update. I used the PDANet driver to update it.
I recently soft-bricked my Vibrant so now it get stuck at the Vibrant screen and it is hardware locked. I can get my phone into download mode using adb but then it does not show up in ODIN. When I plug the phone in during the Vibrant screen, it shows up as COM 6 but then it is removed when it gets to Download mode.
I searched around for a while looking for a solution and tried a bunch of things but nothing worked.
Also, when I plug my phone in during download mode, it says "The USB device attached to the computer has malfunctioned and Windows does not recognize it."
I'm on Windows XP 32-bit
PC Not Recognizing Vibrant in Download Mode
My stock, rooted Vibrant was soft-bricked by the latest update. I've been following the instructions on this thread: forum.xda-developers.com/showthread.php?t=803492, but cannot get Odin to recognize the device in Download Mode.
One caveat of my current situation is that I'm running Windows XP (32bit) on VMWare on a Mac. Not sure if this is the cause of my pain, but I simply don't have a PC handy.
Currently, when the phone is connected via USB in Recovery Mode, it mounts and everything is cheery. Even on the Mac side, adb recognizes the device and lets me tunnel into it. But the instant I boot into Download Mode the computer no longer recognizes it.
I've reinstalled drivers, tried using 64-bit versions of drivers, tried Kies, but Odin simply does not see the device in Download Mode.
Has anyone experienced this and resolved the issue? Should I hunt down a PC and ditch VMware? That's pretty much my final option prior to heading down to T-Mobile.
theorginazation said:
I recently soft-bricked my Vibrant so now it get stuck at the Vibrant screen and it is hardware locked. I can get my phone into download mode using adb but then it does not show up in ODIN. When I plug the phone in during the Vibrant screen, it shows up as COM 6 but then it is removed when it gets to Download mode.
I searched around for a while looking for a solution and tried a bunch of things but nothing worked.
Also, when I plug my phone in during download mode, it says "The USB device attached to the computer has malfunctioned and Windows does not recognize it."
I'm on Windows XP 32-bit
Click to expand...
Click to collapse
What version of Odin were you using 1.0 or 1.3?
ckalima said:
My stock, rooted Vibrant was soft-bricked by the latest update. I've been following the instructions on this thread: forum.xda-developers.com/showthread.php?t=803492, but cannot get Odin to recognize the device in Download Mode.
One caveat of my current situation is that I'm running Windows XP (32bit) on VMWare on a Mac. Not sure if this is the cause of my pain, but I simply don't have a PC handy.
Currently, when the phone is connected via USB in Recovery Mode, it mounts and everything is cheery. Even on the Mac side, adb recognizes the device and lets me tunnel into it. But the instant I boot into Download Mode the computer no longer recognizes it.
I've reinstalled drivers, tried using 64-bit versions of drivers, tried Kies, but Odin simply does not see the device in Download Mode.
Has anyone experienced this and resolved the issue? Should I hunt down a PC and ditch VMware? That's pretty much my final option prior to heading down to T-Mobile.
Click to expand...
Click to collapse
It's the Mac....sounds like you've done everything correctly. do you have the option for Parallels?
Download mode uses a different usb driver. If you are running in a vm you need to set the vm app to pass that usb device thru to the guest os.. i use odin in virtualbox on linux just fine. I haven't tried it on osx though. There's also an app in development in the i9000 dev forum that runs natively on osx.
@shinybuddha unfortunately parallels is not an option, but I could likely hunt down a PC
@ttabbal thanks for the tip, I've been suspicious of the drivers. Currently I have version 5.2.0.5 installed, and when connecting the Vibrant in download mode, a "Generic Serial Device" appears, but fails to connect.
Unfortunately the device exhibits the same behavior on the Mac side, and isn't being recognized in Download Mode, at least not by "adb devices".
Is there a specific driver I should install in the virtual XP os? Or could you provide a link to the osx app?
I think I need to find a PC. After scouring the forums it appears there has been no successful Odin use on a Mac via VM.
forum.xda-developers.com/showpost.php?p=7854560&postcount=12
Also discovered this interesting bit from the Heimdall developer:
After some serious investigation and a bit low-level debugging it appears as though there is very little I can do to correct the GT-I9000's lack of USB specification compliance when in download mode. When in download mode the GT-I9000 is using an embedded Gadget Serial driver and not the one provided by the linux kernel (zImage). As such I have made Samsung aware of the issue although I don't know if they will resolve it or how long it will take.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=755265&highlight=heimdall&page=16
Found a Windows Vista 64-bit installation and followed the directions on the following thread:
forum.xda-developers.com/showthread.php?t=803492
My Vibrant is back! Done in 30 minutes, after spending 3 days trying to get it to work via VM on a Mac. Sometimes iCan't.
Just to help out anyone else with a similar problem using Windows directly... I also found that Odin would recognize my phone when on normally but not in download mode. To solve, what I did was put the phone in download mode, then open up device manager and there was a new unknown device... gave it the path to the downloaded drivers and let it install. Then another unknown device popped up (might have to close and reopen device manager, or refresh, or unplug and plug phone). Pointed it to drivers download again and it magically appeared in Odin.
Aerankas said:
Just to help out anyone else with a similar problem using Windows directly... I also found that Odin would recognize my phone when on normally but not in download mode. To solve, what I did was put the phone in download mode, then open up device manager and there was a new unknown device... gave it the path to the downloaded drivers and let it install. Then another unknown device popped up (might have to close and reopen device manager, or refresh, or unplug and plug phone). Pointed it to drivers download again and it magically appeared in Odin.
Click to expand...
Click to collapse
What drivers did you "point" too. Im having the same issue as you, except in my device manager is says "Gadget Serial." Either way, I need my PC to recognize my phone in download mode so please help!
I had the same proble. It showed Gadget serial in device manager. I uninstalled all other samsung and keis related drivers and installed 5.2.0.4 and it worked out fine. You can download them from here. Good luck.
http://forum.xda-developers.com/showthread.php?t=728929
omg thanks
ya, the other drivers were screwed somehow, switched to these and bam... odin sees the vibrant. Thanks in bunches, lifesaver move there
I only have a mac at home, so i was wondering if there is any way to flash i5800 in os x? I would flash with fastboot, but atleast adb doesn't recognize i5800. Its a shame that neither clockworkmod recovery nor heimdall is ported to i5800.. Please post any ideas!
Sent from my ZTE-BLADE using XDA App
You can't. Yet.
On OSX I use adbWireless for development (you can find it in the market but it needs root), because it just won't work with the USB cable. If I boot into Windows XP, the cable works flawlessly.
But naturally this solution isn't good for flashing.
I'm trying to follow the "Retail 3.1 CWM Recovery, Root..." instructions from the dev forum and have hit a big roadbump. I'm trying to install CWM and root using XP via Parallels from my iMac (which I've read others have done before) but for some reason XP is not recognizing the APX device (and the device is indeed in APX mode because a pop up comes up on the Mac). The other odd thing is that when the tab isn't in APX mode, it connects just fine in Windows, and I can even access it through adb. I'm hoping maybe someone has a tip or trick on how I can get Windows to recognize the device in APX mode so that I can then point it in the direction of the proper drivers, and eventually flash CWM. Any ideas?!?!
anybody?
Ugh...
Hmm, now I've connected and apparently successfully flashed CWM...but when I go to reboot to recovery via ADB, it just sits at that huge battery graphic on the black background. WTF
I could never get windows xp running in vmware (on a windows 7 x64 box) to recognize my tab.
Hello! I'm trying to install TWRP in my Galaxy s8 (SM-G950F European Version), but I'm unable to get Odin to recognize the phone in download mode. In Windows Device Manager, the phone pops up as SAMSUNG Mobile USB CDC Composite Device, but it has a warning symbol, and in details it says Error Code 10 (Unable to start the device).
I'm doing all of this in a Windows 8.1 virtual machine in VirtualBox (I'm using a MacBook), so maybe that's the problem, but I've seen other people having success inside a VM. Does anyone have any tips on how to fix this, or did this procedure before?
Thanks in advance!
Have you installed the samsung drivers? Can be downloaded from the link below.
https://forum.xda-developers.com/showthread.php?t=961956
krashprocess said:
Hello! I'm trying to install TWRP in my Galaxy s8 (SM-G950F European Version), but I'm unable to get Odin to recognize the phone in download mode. In Windows Device Manager, the phone pops up as SAMSUNG Mobile USB CDC Composite Device, but it has a warning symbol, and in details it says Error Code 10 (Unable to start the device).
I'm doing all of this in a Windows 8.1 virtual machine in VirtualBox (I'm using a MacBook), so maybe that's the problem, but I've seen other people having success inside a VM. Does anyone have any tips on how to fix this, or did this procedure before?
Thanks in advance!
Click to expand...
Click to collapse
http://rootmygalaxy.net/install-odin-jdoin3-for-mac-osx/
Specific mac compatible version of odin
sofir786 said:
http://rootmygalaxy.net/install-odin-jdoin3-for-mac-osx/
Specific mac compatible version of odin
Click to expand...
Click to collapse
Hey! Thanks for the link. In the end I've managed to do it with VirtualBox, I just needed to enable USB2.0 support in the VM.