Related
Ok I spent a few days searching and I just can't seem to find anyone with the same problem!
I got a used T-mobile G1, can't bypass the activation screen (touching the 4 corners in the a certain order doesn't work, believe me i tried!) so I thought of installing the recovery through adb, except adb doesn't see it!
The only thing i see in Device manager or usbdeview is "HTC Android Phone Device" "K:\" under Portable Devices. I cannot update it to the Google drivers, not from here or from the SDK. I tried un-installing it, from device manager and from usbdeview.
I thought it might have been the data cable, so I ordered another one from a different seller off of ebay.
I think i should note that when in fastboot mode, pluging in the usb does not change where it says Serial0 to anything else. I would of thought it change to USB if cable is connected like the older HTC devices.
What am I doing wrong? You're help is appreciated.
Follow this guide, it should help you fix your problem.
Thanks for the reply. But I already tried this guide, every step.
First, this phone doesn't have a custom recovery, so I can't do any fastboot updates.
Second, windows does not accept replacing the HTC Android Phone USB Device with the usb drivers from the guide. It just says "The folder you specified doesn't contain a compatible software driver...". I'm using 64bit Win7 so obviously I'm using the 64 bit drivers. I tried 3 different downloads from different sites just to be sure the drivers weren't corrupt. The other odd thing is that the HTC ANdroid Phone USB Device is under Disk Drivers in the device manager...
Third, I tried uninstalling using USBDeview, but still Windows automatically installs drivers back as soon as i replug.
Fourth, I cannot bypass the Activation screen, so I can't set USB to debuggin mode.
I know it's hard to suspect that it could be the cable, but I ordered another one from different site just in case.
Most peeps say I should see 3 HTC devices in the device manager, but I don't. Only thing that pops up in there is HTC Android Phone USB Device under Disk drivers and "K:\" under Portable Devices.
Got another cable today and it still doesn't show any other device other then the one in Device Manager... I ran of out of things to try. Anyone can advise? It's possible that my device is defective even though it boots normally.
After playing around for a few days, ended up somehow rooting and flashing Amon's latest recovery and then BAM windows detected new device and install the ADB interface.
I flashed my stock. 2.1 Milestone (rooted) preparing it for froyo. Apparently the .sbf was corrupt or wrong;
GOT_TELUS_2_2_1FULL.sbf
I am told the correct sbf is;
BL_9078_GOOD_sholes_HS_Consumer_replacer.sbf\BL_9078_umts_sholes_HS_Consumer_replacer.sbf.
- Now It’s stuck in bootloader mode
-RSD Lite seems to recognize phone but the “Start” button remains disabled, grey, it can’t be pushed (with either .sbf file.)
-I’ve loaded a fresh copy of RSD Lite v5.0 (previously had v4.7). Both behave the same; the start button is disabled.
I want to save this phone and am looking for alternative tools or methods to ultimately flash the proper .sbf…Help please!!!
BOOTLOADER SCREEN BELOW
PHP:
Bootloader
90.74
Err:A5,69,35,00,27
Battery OK
OK to Program
Transfer Mode:
USB
RSD LITE SCREEN BELOW
PHP:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x009074
DRM Version: N / A
AP Die ID: 06a0010c60720304000000000400
BP Die ID: 0000000000000000000000000000
AP Public ID: 4bd4854c5cb58e173025f2751e09441b44fa681f
BP Public ID: 0000000000000000000000000000000000000000
-----------------------------------------------------------------------
Model Port No Port Type IMEI/ESN/MEID Status
S Flash OMAP3430 1 USB N/A connected
(I’ve successfully flashed my other Millstone an many other phones)
Any help is greatly appreciated,
PK
The greyed out start button is an error in RSD. What you want to do is rename that really long sbf file to a one letter name such as a.sbf
If you are planning on rooting, you can flash the VR from android.doshaska.net/rootable but I would not try it until those bootloader errors get corrected. Be careful on the site I gave you, one sbf is for bootloader version 90.78, the other is for yours (90.74)
Hope that helped.
Sent from my Milestone using XDA Premium App
Thanks skadude66
That kinda worked, I renamed it “A” and also had to put it in the root on my C; drive. The button worked.
The bad news is it wouldn’t take. I got the following error message:
PHP:
Device Properties
EMEI/ESN: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Boot Version: N / A
DRM Version: N / A
PHP:
Status
Failed flashing process Failed flashing process (0x7100); phone connected.
(I also discovered by hunting around that I almost tried to flash the wrong ver of.sbf, 90.78 instead of 90.74. It didn’t make any difference though.) Failed.
Regards, PK
pk2 said:
Thanks skadude66
That kinda worked, I renamed it “A” and also had to put it in the root on my C; drive. The button worked.
The bad news is it wouldn’t take. I got the following error message:
PHP:
Device Properties
EMEI/ESN: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Boot Version: N / A
DRM Version: N / A
PHP:
Status
Failed flashing process Failed flashing process (0x7100); phone connected.
(I also discovered by hunting around that I almost tried to flash the wrong ver of.sbf, 90.78 instead of 90.74. It didn’t make any difference though.) Failed.
Regards, PK
Click to expand...
Click to collapse
Try using the latest version of Motorola USB drivers, your phone might not be completely recognized.
EDIT: http://androidforums.com/droid-all-...hing-process-0x7100-rsd-lite.html#post1274587
I used that to help me out when I had that error as well. It worked for me, it should for you as well.
Thanks. good read so far. Nice to know I'm not alone and there may be a way. I think the trick when I did this on my other Milestone was copying the sbf here there and everywhere. Haven't updated the latest usb drivers.
Regards, PK
Well crap,
I downloaded v.5 moto usb drivers from moto. One self installing program. RSD doesn't see the phone at all now. Tried twice. Uninstalled drivers with program "total uninstaller" (normally very good), still nothing in RSD.
Seem to recall having to manually install either HTC or moto drivers. Guess I got to hunt around and find out what the moto trick is.
crap.
Regards. PK
Finally new Moto Drivers (v5.0) installed, start button in RSD "start" button works but when pushed, RSD reads "Flash Failed"
Any help? PK
try RSD v4.7, maybe its the RSD problem.
Have you check out your system hardware manager to see if the Milestone was recognized completely?
Hi,
i got same problem 2 days ago.
at my point i just had to install a new rom.
if you get in Open Recovery try to install miui oder CM.
I got the same error when i tried to install CM7. So I installed MIUI and voila everything worked.
Thanks for the reply's!
I tried all of above and it still "failed" to flash.
I can't get into open recovery or the stock "recovery" utility (this phone was stock when this all started).
The phone shows up in "devices and printers" as "unspecified-S flash omap3430a" not as Milestone
Regards, PK
I was having a similar problem. How are you getting into the bootloader? I was using the volume button.
For whatever reason, when I got into the bootloader using the D-pad, RDS Lite found the phone.
I still can't seem to flash anything properly, but it found it.
It pretty much jumps straight to boot loader mode all by itself after powering up. No button combination takes me anywhere but the boot-loader. There's no way to get out of it either.
Thanks, pk
Stuck in boot loader milestone usb drivers
Man I've tried all of above.
The one thing someone mentioned is "is the phone was recognized by win764" . Not really, It only shows up Under "Devices & printers" as "unspecified":
S Flash OMAP3430
I have tried every Moto. USB Driver set I can find. None do anything different. I can not find any manually installable drivers.
(My working hacked milestone_eu shows up as "unspecified" ) to.
Makes me think Maybe my drivers ar screwed. How can I put them in manually without an install a pckage I wonder. Anyone had this prob?
I can't do anything with the either phone, from the computer, when tied together with USB (I.E. access sd card, portal, etc.)
Thanks PK
bump -please
Just to clarify, you have two Milestone's, one is stuck in bootloader mode, the other works. Connecting either to your computer show 'unspecified'. Is that correct?
First, the bootloader version doesn't matter, I've had 90.73, 90.74 and 90.78 on my milestone at diferent times, doesn't make any diference.
The error code you got in bootloader mode (ending in 27) means one of the signed partitions failed the signature check, probably the result of a bad flash. Reflashing usually fixes that.
Your problem sounds like a problem with your USB on your PC, either drivers or a hardware problem (most likely drivers). Fixing your pc should allow you to reflash your milestone correctly.
When connecting a Milestone in bootloader mode to RSD lite, RSD cannot extract the IMEI info etc, the display you pasted is what I would expect when connecting in bootloader mode. If you connect to RSD when the Milestone is booted up (running android), it will show the IMEI etc. All you need to check is that RSD says its connected and its usually ready to flash..
Things you can try:
1: Try flashing from another computer
2: Dual boot Ubuntu on your PC, then try flashing with sbf_flash (google it), no additional drivers are needed, should work straight out the box.
3: Uninstall EVERYTHING on your pc from motorola, then in system/device manager uninstall all the windows USB drivers, reboot and let windows reinstall the USB drivers, then try re-installing the motorola USB drivers and RSD lite.
4: Try a diferent USB cable, also try a diferent USB port. Connect directly to the computer, do not use a USB hub.
Hope this helps.
I've flashed 6-8 ROMS on a couple different phones, so not a total noob, but I bow to the vastly superior knowledge here:
My Captivate was running CM7.1 stable from October with no further mods since. I hadn't flashed anything or really messed with the phone in awhile. I was just using the same phone in the same config I had been for 6 months.
A few days ago, CM7 started to force close all my programs. Annoying, but not a problem that rebooting wouldn't probably fix. Rebooted into bootloop (skater logo). 3 Button didn't put me into CWM Recovery, nor would any button combos get me to download mode.
Homemade a jig and got the phone into Download mode, with Odin One Click up and ready to flash to stock. Odin read the phone and I started the flash, but it hung at DO NOT TURN OFF TARGET for a couple hours. I checked on this forum to see what was next. All the previous posts just said to pull battery, re-jig, and start again.
This time, I didn't get the skater, I got the comp!phone. All button & USB combos I've read here bring me comp!phone (even the "hold until two blank screens" one). My PC won't recognize the phone now (so neither will Odin or Heimdall), even after I've reinstalled the Samsung drivers. I've read here that you can flash from the comp!phone screen, but the PC has to see your phone first, obviously.
So I guess I want to know how screwed I am. Magic tips on a easy fix would be just outstanding, too! Is the fact that I wasn't flashing or anything when it bombed interesting to anyone? Thanks in advance...
not sure it's identical but this worked for me: http://forum.xda-developers.com/showthread.php?p=15330252#post15330252
OP,
Check out the "Connection Issues..." Stickied Thread in this forum.
Sent from my SAMSUNG-SGH-I777 using xda premium
Zadig won't load drivers for Heimdall 1-click
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
If you are still stuck...
Did you actually load a full version of Heimdall? Once I used unbrick as a mini-program. Another time I had to install a full version on my computer in order to get my phone and computer to communicate (that may be the missing driver step).
I know you have probably already done so but search the threads for AdamOutler and his work with Heimdall.
If you're using windows, windows update might be installing the drivers automatically. You might want to disable this feature, uninstall the current drivers and install new ones.
You can also try another pc that doesn't have any installed drivers - just to make sure...
Sent from a Captivate using XDA
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
Did you try manually installing the Samsung/Google usb drivers ? That's the usual culprit since stock are Samsung drivers and roms ( if its Aosp/Cyanogen) the Google drivers prime in that case.
Nearly Identical Problem
I've got the same problem with my Captivate...tried everything I've found in the forums but nothing works.
Background:
I had connection issues before trying to flash, but thought it was a driver issue with my Windows 7 machine. Which is why I had loaded the file onto the SD card when I attempted to upgrade to ICS. During the flash the phone hung and I eventually removed the plug and battery to see if I could reboot. I can get up to the Galaxy S I9000 screen, or the "Downloading..." screen, but I cannot get to the recovery menu or past the initial boot screen. My wife's captivate (same batch) IS recognized by the computer in "download mode" and in the USB transfer mode.
Attempts:
- Installed/uninstalled Kies many times
- Bought and tried a new data cable
- Installed/uninstalled the Galaxy S driver and the Captivate driver many times
- Tried Zadig, Odin, Heimdale, and Adb
- Used programs to remove USB devices and clean registry
- Installed Linux and tried within that OS
- Re-installed Windows 7
- Tried most of the above on my Windows XP system
Has anyone been successful in getting the computer to recognize a Captivate in this circumstance?
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
if u r still facing the problem..and problem isnt solved then just clean the pin of usb connector pin of ur phone...with a thin metal pin..or something like that...
and then u r good to go...
If all else fails...
I managed to brick my Captivate trying to get MUIU off my phone and flash back to Cognition. After many frustrating hours, I contacted Josh at mobiletechvideos.com. He fixed my phone and upgraded me to ICS for $50.00. I mailed my phone to him on a Thursday and received it back the following Friday.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
CAPTIVATE - Frozen on AT&T Boot, Unrecognized via USB, NO access to CWM - PLEASE HELP
HI - I've been fighting this captivate for over 48 hours. Being very familiar with all this, and not doing this for the first time either, the fact that I can't get this resolved drives me insane as I have never been so mentally exhausted in being incapable of resolving a problem, thus seeking professional guidance from the Gods on mobile technology!
HERE IS THE SPIEL:
Device: Samsung Captivate i897 (Device is rooted)
Software: AOKP build.38
Kernel: IcyGlitch v14
CWM: Installed v.5-----
The Problem
Device stuck at AT&T Logo - Not Looping (just stuck)
Windows XP Professional SP3 (x86) with all recommended USB drivers will not detect device. Device Manager displays the phone as unknown, regardless of drivers & upon inputting it into a USB (2.0) windows displays a message "USB Device is not recognized".
Windows 7 Ultimate SP1 (x64) brings up identical message as that of Windows XP with all proper & recommended drivers with the phone recognized as "unknown"
Device boots into download mode via holding Vol.+/- and plugin in USB cable. Both Heimdall & Odin can't recognized the device when it's in UNKNOWN state by windows. Although all drivers are installed.
Purchased new Micro USB cable - NOTHING - that's testing all USB ports on all my systems.
The Story:
The device was working flawlessly being able to mount as mass storage on both my Windows 7 Ultimate SP1 (x64) & Windows XP Professional SP3 (x86) until i've upgraded to AOKP build #38. The upgrade was successful (2 months ago). 2 days ago, i decided to upgrade to AOKP build #40. The device was not recognized as mass storage but rather "Unknown Device" or "USB Device not Recognized" - although the phone was in full working condition (USB Debugging was enabled). After some reading, I realized that the AOKP build #38 has a bug where there was a problem with mounting & the camera was not functioning since it had no access to external_sd (a problem that was very irritating since the update, but i had no time to look into it until recently). I followed a similar tutorial (http://forum.xda-developers.com/showthread.php?t=1545801) which required the editing of the vold.fstab file with Root Explorer, resolving the issue of external_sd becoming accessible on the phone with camera working, however unable to mount and copy the new AOKP Build 40 ROM through Windows to flash via CWM.
At this point I booted into CWM via holding volume +/- & power button. Wiped everything, and loaded a backup I've done a # of months ago where everything was working perfectly. There was an error when it was "...loading data image" which is normal, so I did it again and the error persisted. On the second attempt, it again re-sent me primary CWM menu where i was intending to now load another backup. I accidentally clicked the restart button, having already cleaned the devlick cache, etc, including user data which brought me this NIGHTMARE of problems.
I will be forever grateful the the kind soul which will help me resolve this, as I am at a phase of taking this samsung captivate and throwing it against a wall.
I assume you can still access recovery? Try putting CM9 on the external SD with a card reader, and flashing that...
EDIT: Just saw you can't access CWM... Try recovery again... all three until ATT comes up, immediately let off power... Try multiple times... Leave the battery out, hold all three, have someone else insert it, and let off power at ATT... When going into download mode, leave the battery out, hook it up, hold boths vols, and insert the battery...
The Unknown device issue....
Uninstall your drivers... Here are drivers to manually install, they are 64bit... so try right clicking the Unknown device in device manager and doing a manual driver update...
OP,
See this thread... Captivate Connection Issues...
Sent from my SAMSUNG-SGH-I777 using xda premium
B-Naughty: Thank you. I have tried this & that no luck. Even loaded Linux Mint 13, however heimdall is being a !*&#@ in loading the firmware...Perhaps if you would know any (proper) packages for a Samsung Captivate i897 via heimdall id be grateful. I used heimdall-suite-1.3.2 command line & frontend. Will try again tomorrow. Although still haven't figured out whether or not it read the phone in Linux (it's a different world for me)
4-2ndtwin: My friend, thank you for the detailed link. I have been doing this for over 48 hours ... nothing. I'll give it another shot via Linux, if not i'll try Ubuntu. Truly am just confused out of my mind, never had this before.
PS: The phone's data is wiped & it's stuck at AT&T when loaded via power button. Booting into DOWNLOAD MODE isn't a problem. All combination to load into recovery, did not work. I mean...there must be a way! There always is...Any further ideas or should i simply through it out and buy a Galaxy SIII?
I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click
And try all of your USB cords, I don't know what you bought, but a bad one, or a lot of times an aftermarket one won't work...
Edit:
I saw you can get into download mode. So my original post doesn't help much.
Have you tried installing the Andoid SDK and downloading the nexus drivers from there? Perhaps your device now thinks it is a nexus. It might be worth a shot.
^
+ 1
Yes... I second this ^
Sent from my SAMSUNG-SGH-I777 using xda premium
This happened to me and I just reflash the boot loader and reinstalled the same from to keep my data
Decrapitated Samsung
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
I would say you need to uninstall any/all drivers for your captivate. This includes heimdall installed drivers. Make sure to uninstall the drivers for the "unknown" device also.
kScorpion said:
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
Click to expand...
Click to collapse
Seems as though you have a hardware problem with the phone, or a s/w problem so messed up you're down to Unbrickable Mod
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
Red_81 said:
I would say you need to uninstall any/all drivers for your captivate. This includes heimdall installed drivers. Make sure to uninstall the drivers for the "unknown" device also.
Click to expand...
Click to collapse
He had a fresh Windows install and install drivers...
Unbrickable MOD - wont be able to do this my self, would need an electric to look into it. I mean the phone isn't bricked, it accesses download mode i just have to get it to connect via usb to be read as a "samsung composite device" to flash the bootloader. As now, it would be stuck at the AT&T screen without giving access to CWM.
I have installed Ubuntu 12.04 - set up java 7 - loaded Heimdall One-Click stock rom provided above via java...tried all USB's phone not detected via DOWNLOAD MODE. Phone not detected at all!
This is just insane...If it's in DOWNLOAD MODE, it should be accessible, not the contrary. Ubuntu doesn't need usb drivers, should be plug&play...Both XP & Win7Ultimate at least recognized the phone as an unknown device. On Ubuntu it does nothing at all, as if it never was plugged in.
The microusb slot on the phone is not damaged / cable is stock, also have another one from Staples. The system w/XP is reading all devices on a plug&play basis and read the captivate before flawlessly. Same applies to the Asus P43 laptop, which read the device without hesitation on Win7 Ultimate x64. The Ubuntu is now on the laptop...tried connecting the Galaxy Tab 10.1 (Samsung) it recognized it immediately...with full access to files etc.
Last plea for Ideas...before i'll send this captivate to hell, to where the journey isn't captivating at all!
It sounds like you have a bad flash. You need jtag to fix this issue. Contact mobiletechvideos and Josh should be able to repair it for you. I think at this point you've tried every other option.
Sent from my SAMSUNG-SGH-I897 using xda premium
kScorpion said:
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
Click to expand...
Click to collapse
did u try reverting back to stock using ODIN 1 Click Stock Firmware Installer? there's a tutorial on youtube by mobiletechvideos original post by connexion2005.
Samsung Captivate (ODIN 1 Click Stock Firmware Installer)
youtube.com/watch?v=UDtxnH4lFuk
I would like to have that free captivate thou :good:
Same Problem
i have the same prob and if i try to recovery mode (i.e. by pressing volume buttons and power button simultaneously)
i get following type of errors
"E:failed to mount /cache (Invalid argument)
E:Can't mount/cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log"
kindly sugeest some way out
I have done everything possible to get it connected and recognized by the PC & all is failing. I have tried to "manually" install the Samsung composite Device driver via "have disk method in Device Manager.
In XP:
I load device manager and than do the following:
Click Universal Serial Bus Controllers
Right click "unknown device" which is the captivate
Select Update Driver
Select Install from a list or specific location (Advanced)
Select Don't Search. I will choose the driver to install. (Click Next)
Select "Have Disk" with the (show compatible devices) checked
Browse to the directory of extracted 32bit Windows XP Drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
Select "ssadadb2.inf" & click open
And than i get the msg saying:The specified location does not contain information about your hardware
...WTF... I mean really...
Windows 7 Ultimate:
Same procedure as above until you select have disk, pick a proper x64 driver provided by XDA - also tried the Universal_Naked_Driver_Beta_0.6 ...there was progress that got me very excited - the Phone was detected as: Samsung Android Composite Device. Was I happy...until i clicked next and got this msg:Samsung Android USB Composite Device - This device cannot start. (Code10)...
There must be a solution: I had the phone bricked when i first tried to change from stock rom, managed to load it in download mode, and it was detected fine on all systems via USB with the same accessories, worked like a charm...so when this happened i wasn't concerned, as i thought id follow standard procedure, accept it did not work.
Anyone?
Let's try this since you seem to be stuck in a boot loop.
Code:
adb wait-for-device reboot recovery
Make sure your phone is plugged in and reboot it. If your machine recognizes the phone at any point in the boot process it will kick it into recovery.
Once there you can try to restore the backup again.
If this doesn't work, you will most likely need JTAG service. Because of the bad image flash your device might not "think" it is a Captivate any longer and that's why the drivers aren't working.
Red_81 :Thank You. Would you please be more specific & put into a 1,2,3...process?
1. Power off device
2. Plug in to computer
3. Open a command prompt
4. Navigate to adb.exe (android sdk or inside my kk4 root utility)
5. Enter command above
6. Boot up phone.
7. Hopefully go into recovery
Sent from my SGH-I777 using xda premium
Thank you. I've been endlessly fighting the achievement of the PC systems to detect the captivate & no results. Thank you all for you help...when i have time i'll JTAG this device, or probably not even going to bother and pick up a SGIII. By the way Red_81:http://forum.xda-developers.com/showthread.php?t=1680048 is an amazing app, if only my phone was detected as it's recognized as unknown device, so there isn't much it can do. Although i highly recommend it to anyone else whose phone is detected.
Hi!
I'm trying to connect Moto X in BP Tools mode, but Windows XP cannot find appropriate drivers. I have latest drivers from Motorola website, version 6.2.0 I believe, part of Motorola Device Manager 2.4.3 package. It connects without problems in MTP mode, as well as I do not have any issues with connecting my Motorola XT912 in BP Tools mode.
Any ideas where to get proper drivers or overcome this issue?
Thanks!