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.
Related
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'm trying to Root my Samsung Tab 10.1 and I'm stuck at a step in this thread:
http://forum.xda-developers.com/showthread.php?t=1130574
Section 2 step 14.
I cant get my computer to install the unsigned USB driver.
When I browse I can see it, chooses it, but it wont install.
Instructions say just bypass the errors but I don't even get those.
It just stops the install and gives me nothing.
Any help would be great.
Thanks
Try running the attached utility and remove any Samsung references or references to any other no longer needed usb devices. Then reinstall the Samsung drivers. That's what worked for me.
I installed it on my PC (win7 64bit) yesterday following the same instructions and it loaded fine.
In your Device manager do you see the device as "APX device" with questionmark.
One more thing, try uninstalling the previos one and then reboot the PC and start again.
I used Samsung Kies and it installed the USB drivers.
katlimaal said:
I installed it on my PC (win7 64bit) yesterday following the same instructions and it loaded fine.
In your Device manager do you see the device as "APX device" with questionmark.
One more thing, try uninstalling the previos one and then reboot the PC and start again.
Click to expand...
Click to collapse
I'm on 32bit. Does this matter?
And...
Do you mean to uninstall APX or the NVIDIA Boot Driver?
BobCobb said:
I'm on 32bit. Does this matter?
And...
Do you mean to uninstall APX or the NVIDIA Boot Driver?
Click to expand...
Click to collapse
I don't think 32/64 bit matters.
Yes, uninstall the APX (Nvidia recovery boot driver) and then press the buttons again on Gtab to enter APX mode and connect to PC and reinstall.
I'm trying to debrick A500 with a WinXP PC.
It can be detected by the PC as "MTD device". Installed the Acer driver for it (not sure what it does).
It can enter the APX mode, detected by the PC correctly, and installed the APX driver "Universal_Naked_Driver_0.72".
But, adb devices does not detect it, so cannot move further to PBJ20upgrade.exe and so on.
What does this mean? Bricked beyond repair?
- dd
ddbug said:
I'm trying to debrick A500 with a WinXP PC.
It can be detected by the PC as "MTD device". Installed the Acer driver for it (not sure what it does).
Click to expand...
Click to collapse
I'm assuming that you mean MTP (Media Transfer Protocol)?
I'm assuming this means that you are booting Android as I'm not aware of the device being represented as anything but an APX device (0955:7820) if you do not.
What is the problem?
ddbug said:
It can enter the APX mode, detected by the PC correctly, and installed the APX driver "Universal_Naked_Driver_0.72".
But, adb devices does not detect it, so cannot move further to PBJ20upgrade.exe and so on.
Click to expand...
Click to collapse
When in APX mode Android is not loaded so you cannot use ADB (Android Debug Bridge). It should not really matter as, from what I recall, PBJ20upgrade will only use ADB to reboot the device into AXP mode.
Thank you eppeP,
Yes, it was MTP.
So I'll try to proceed with PBJ20upgrade.
(am away now for a week or so ... )
-- dd
Hi guys,
I want to go back to stock since 4.4 is coming. However, when I try to flash the stock rom+ with Nexus Root Toolkit 1.7.3, I get stuck at the whole fastboot part. Fastboot IS working on my Nexus, but the drivers cause a lot of trouble. Installing the drivers when my device is running normally ( so no fastboot mode or whatsoever) works fine.
I have followed the Full driver installation guide where I tried options 1 till 4 but they all get stuck at the point where my device reboots into fastboot mode. At this point, my computer doesn't recognize my device and gives me an error. My nexus is shown in the device manager as unknown device and updating the drivers manually by redirecting my computer to the NRT drivers does not work. It says it cannot find drivers for the device. Does anyone know what I might have done wrong?
Or is it possible to flash a stock rom through twrp? like this one? http://forum.xda-developers.com/showthread.php?t=2376881
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
issak42 said:
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
Click to expand...
Click to collapse
Yeah, I tried the same things you did, including disabling driver signature verification but it won't work. I'll try a windows 7 machine.
Thanks for your answer!
Trying to get this tablet to work after being stuck in android boot loop. and nothing seems to have any effect. Friend needs it for their school and want to get this running again.
Downloaded a few updates and tried them all to different results but no matter what after the tablet reboots it goes to acer boot logo.
I have read around and seem to be have to use apx mode to recover it but when trying to run pbj2.0 tdv4 rollback rom i get this error message. "Your operating system isn't compatible with the upgrade application. Please download .NET Framework 2.0 or above from Microsoft website." The thing is .net 2.0 is installed and verifies using the .net verification tool.
I an running w8.1 x64 on this pc and w10 x64 on my old laptop but get that same error message on each.
I can get the tablet into apx mode but the a500 manager sees it but complains about drivers which should be installed. It shows up in device manager as APX device but no drivers installed.
Is there any way around this as i dont have access to a pc running win7 or lower. Currently downloading an ubuntu virtual box image to try and get cpuid and sbk.
Any help would be appreciated