[Q] Download Mode from MIUI - Captivate Q&A, Help & Troubleshooting

There should be a [NOOB] tag for forum posts...
I'm a long time windows mobile user, rather than jump into windows phone I'm making the switch to Android.
I bought my captivate on eBay, it shipped unlocked with a clean gingerbread rom. Not sure which. After reading through a number of threads and articles I was able to:
Setup ADB - Win7 x64
ADB to download mode, Odin 1-click back to stock
Flash CWM, again via ADB to recovery, and then flash the latest MIUI
3br does not seem to be working for me. At first I was able to get to recovery with Vol up + Home + plug into USB. I can no longer get to recovery or download mode at all. MIUI, has the reboot to Download/Recovery mode options, but neither work and just boot back to the OS. When plugged into my computer, the device drivers are not recognized. So it no longer works with ADB. I haven't been able to get the drivers re-installed. When I attempt to ADB, it says "Error: No device connected" (or along that wording). I tried installing the USB drivers straight from Samsung and the galaxy S x64 drivers posted online. Not having any luck.
I can't seem to find my answer searching the threads and web...maybe I'm not using the right terms (I avoided making a new post as long as I could). Everything else works fine otherwise, the phone isn't bricked...but where's the recovery? Any ideas?
I'm assuming if I can get into download mode, then I can Odin-1-click to stock and everything is peachy again? I'm not quite understanding the 3BR fix guides...I thought since I could get to recovery with other methods when I got the phone, that I was fine, but maybe that's my problem.

The combo is all 3 buttons for recovery and both volumes and plug in a usb fire download. Sometimes odin one click will disable the combo.
As for adb not working miui is an aosp (android open source project) build not based on samsung firmware so you need the google drivers installed for it to work.

studacris said:
The combo is all 3 buttons for recovery and both volumes and plug in a usb fire download. Sometimes odin one click will disable the combo.
As for adb not working miui is an aosp (android open source project) build not based on samsung firmware so you need the google drivers installed for it to work.
Click to expand...
Click to collapse
It must have gotten disabled somehow then...
By Google drivers, you mean the USB package you can select from the Android SDK Manager? I didn't mention this but I think I tried those as well. But I'll remove everything I've installed, restart and try re-installing fresh to double-check.

Thanks for the suggestion, that worked with the drivers from the sdk. So if I end up flashing a touchwiz based rom, will I have to go back to the samsung drivers?

That's correct

Related

[Q] USB doesn't recognize download mode. Stuck after installing speedmod kernel

I had rooted my phone previously running 2.1 and yesterday decided to try cm7. (I've flashed many G1 roms but none for Captivate)
Sorry this is quite long but wanted to give as much detail as possible
I was reading and watching the guides. Installed rom manager and flashed ClockworkMod Recovery 2.5.1.0
Rebooted the phone and tried to see if I can get into download mode by holding vol up + down and plugging the USB cable.
Once it booted tried to copy some other roms (zips) to the phone but the USB wasn't working on windows for some reason so rebooted in Linux. Phone mounted at first (for about a minute) but something happen and I lost the mount. I unplugged/plugged the usb cable but wasn't able see the phone as a drive even with fdisk.
So I ftped to the phone:
3buttonFix.zip
captivate-efsbackup.zip
cm7-captivate-initial-20110304.zip
speedmod-kernel-i897-k13c-500hz-CWM.zip
Installed 3buttonFix.zip (should let me enter download mode) from recovery, rebooted but still couldn't get in download mode.
Installed speedmod-kernel-i897-k13c-500hz-CWM.zip from recovery. Not sure if I had to do anything special like reformat the filesystem with the new kernel?
After reboot the phone gets stuck on Galaxy S sgh-i897 screen. Got back in recovery and installed captivate-efsbackup.zip and cm7-captivate-initial-20110304.zip
The cm7-captivate-initial-20110304.zip fails when trying to write the modem
'assert failed: write_raw_image("/tmp/modem.bin", "radio")'
I plugged the phone into another computer at that point and was able to get into "Download mode" for the first time. Odin didn't recognize the phone though. Download mode is very flaky. It starts sometimes, sometimes it doesn't (battery charger starts) even on the same port with the same cable. I have tried installing captivate drivers and/or kies on 7 different systems (5 laptops 2 desktops) but Odin never recognizes the phone and windows trows out a "USB Device Not Recognized" msg
I think my usb is not working properly but the guides how to recover assume working Download mode with Odin. Any suggestions on what to do for that? Or I guess I can download a different rom and/or kernel on my sdcard than mount the sdcard through recovery and install that way?
Any advise is appreciated as I'm not very familiar with the kernel and rom differences for captivate
Well you messed up on the instructions but that is a separate point.
I went through your post quickly so if I am saying something you grave tried I apologize
What drivers are you installing
Have you tried multiple ports
Are you using oem cord
Have you restarted your computer
Have you ever used odin before
CM7
I have used the following drivers:
SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe (just the usb modem driver)
2 different versions of samsung kies which include usb drivers (don't have the software versions handy but I can get them if that will help)
Ports:
Multiple computer and multiple ports. Will try few more options
Cables:
Used 3 different usb cables. 1 of them is from a BB phone. 1 of the other 2 is the one which came with the captivate (not 100% sure though)
Reboots:
4 of the 7 computers I tried on were rebooted. One version of kies requires this anyhow.
Odin:
Haven't used Odin at all. I think when the phone gets connected and odin recognizes it one of the top left blocks changes color right ? I tried to flash even when it didn't (just to make sure I wasn't missing something) and saw 0 successful / 0 failed
Do you have android sdk installed on any of the computers?
CM7
So many red flags that something wasn't right with your phone and you still tried to flash it? I just don't get it.
@Miami_Son: Yeah but i'm too thick headed - living dangerously but yeah you're right.
@mcord11758: I have android sdk installed on my linux build at home. I'll put it on a windows system at work and see if it can see the phone. Anything in particular I should do / look out for ?
At least you've got a good attitude.
I think if you have kies installed it conflicts with the samsung drivers odin uses. Try uninstalling them and flash odin.
Sent from my i897
Edit damn swype
1tontomato said:
I think if you have kies installed it conflicts with the samsung drivers odin uses. Try uninstalling them and flash odin.
Sent from my i897
Edit damn swype
Click to expand...
Click to collapse
Try this first
Sdk to install updated drivers if this fails
CM7
I've done almost the exact same thing...having the same issues. Phone would not connect to computer. Other captivates connect fine. The phone is now stuck on a boot screen and I can put it into download mode but Odin or the computer will not detect it at all. I don't think I can get into recovery mode, nor can I get into a rom...pretty much just download mode or a boot screen.
@1tontomato: Tried uninstall kies, reboot, install samsung usb drivers, reboot still don't see the phone connected in odin
@mcord11758 The sdk is trying to download the repository directly and I'm behidn a proxy server at work. I'll update tonight, it will be most likely very late by the time I get home.
@kwhee07 Yeah sux to see a download mode but not being able to download. I can get at least into recovery so I guess I can at least flash something that way. The ports really make difference, I've seen many would just charge the phone and some will get your phone into download mode at least. Try a different pc and cable if you can.
I have the sdk...I've tried about everything else I can find. Is there a possible method of fixing this via the SDK? I feel like if I could make the computer force [odins] data out the usb port, it would work, the phone would be in download mode awaiting data....but I cant get odin to see it
There is a package you can install in sdk for usb drivers. Dl it
Open odin
Get into dl mode
Unknown device pops up
Click on it
choose custom drivers
Navigate to c drive/program files/android/extras/google add ons/usb click ok (the path may be slightly different) the computer should try to install the correct drivers
If it works odin should now recognize your device. If not I got nothing
CM7
Got the USB drivers from the SDK and tried to force them when it sees an unknown device, but I get "The specified location does not contain information about your hardware"
I tried to force it to use the samsung drivers also but without success.
Is it possible to just download a rom or kernel and update my current state? So that the phone at least boots. I can install stuff through recovery. Download mode is nice and everything but I'm giving up on it, don't have any more ideas to try
I have been trying to see data on my sdcard from ClockworkMod Recovery 2.5.1.0 I go to
Mounts and Storage -> mount /mnt/sdcard
Install *.zip from sdcard -> choose zip from sdcard
I don't see /mnt at all I try and go under sd/ but it says No files found.
bestivo said:
I have been trying to see data on my sdcard from ClockworkMod Recovery 2.5.1.0 I go to
Mounts and Storage -> mount /mnt/sdcard
Install *.zip from sdcard -> choose zip from sdcard
I don't see /mnt at all I try and go under sd/ but it says No files found.
Click to expand...
Click to collapse
Under mounts and storage do you see the option for mount usb this might be able to force your computer to see it as a removable drive. If out does you should be able to copy another rom to the sd and flash. This may or may not work for you because you might still need to repartition which you only do with odin. Take this advise with extreme caution I really think you need odin If you do decide to flash another rom, use cognition because Dg's includes the fixed boot.bin. Probably because so many people use the one click and kill their button combos and don't know it. Other devs don't include it in their roms, because it's dangerous to over write something that doesn't need to be overwritten. Good luck
Sent from my Fusion 1.8 SAMSUNG-SGH-I897
I tried already the usb mount option from recovery at home and now at work also on few different systems/ports including a linux machine. I don't see the drive connected.
My only option left is to get somehow the sdcard mounted and install a rom from there. Or maybe just repartitioning/changing the filesystem might fix the getting stuck problem.
I ended up bringing my phone back to att, and they said that the 1010 batch was under product advisory..they exchanged my phone with almost no questions asked.
Now i have a 1008 and am running CM7
Finishing up the story in case it might help somebody in the feature.
I called AT&T to get my phone replaced and it turns out it has liquid dmg. There's a little white sticky that turns red when there's liquid dmg. Mine was pink but wasn't wait so no warranty for me. Turns out most of the time people get liquid dmg is if they leave the phone in the bathroom or close to the kitchen's sink, which is kinda bs but whatever.
I've tried few more times. Tried even on a Mac and on a Linux system (using http://forum.xda-developers.com/showthread.php?t=755265 )
I was about to give up and go seek one of the 'professional rooters' but last thing I tried was to use an 'air duster' and clean the usb port on my phone. After that Odin was able to see my phone. The connection was dropping on/off but it successfully finished a flash.
Not sure if I should even try to put another rom or the official froyo update but at least for now I'm up and running
Thanks all

Need Help for Captivate, Wont Install Any roms and Usb debugging is OFF

I try to install newest custom rom supernova 4 infinity and message is above:
Formatting SYSTEM:....
Formatting CACHE:....
Formatting DATADATA:....
Formatting DATA:....
Deleting files...
Copying files...
e:failure at line 17 :
copy_dir PACKAGE:system SYSTEM:
installation aborted
now my phone is bricked (Expensive stone) because my usb debugging is off and the odin do not recornize my captivate in downloading mode!!
What i can do now? How i fix debugging ON that i can flash my phone again to stock etc..
USB debugging has nothing to do with it.
you need to get ODIN to recognize your phone. sounds like driver problems
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
In CWM, check to see if you have the option to Root. If you do, apply Root and try flashing the rom again.
I had similar issues with 2 roms with similar errors and I had to apply root in CWM and re-flash and it went trough fine.
energy83 said:
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
Click to expand...
Click to collapse
USB DEBUGGING HAS NOTHING TO DO WITH DOWNLOAD MODE!
usb debugging only has an effect if you are ALREADY booted or currently BOOTING beyond the splash screen. it doesnt matter for download mode...period.
Elisha said:
In CWM, check to see if you have the option to Root. If you do, apply Root and try flashing the rom again.
I had similar issues with 2 roms with similar errors and I had to apply root in CWM and re-flash and it went trough fine.
Click to expand...
Click to collapse
this is one of the most ridiculous things i have read today. root also only applies to the OS....from within recovery or download mode, you arent in the OS...so root doesnt mean SH** within recovery
Pirateghost said:
this is one of the most ridiculous things i have read today. root also only applies to the OS....from within recovery or download mode, you arent in the OS...so root doesnt mean SH** within recovery
Click to expand...
Click to collapse
Don't be a dip****,. I was stating my experience.
From stock 2.1 I could not install Continuum v4 in recovery and got a similar error for E:/
I had to flash a SpeedMod based kernel in recovery and root first before the rom would go all the way trough to flash properly!
It only happens to certain roms...other roms can just flash in recovery from stock no problem without rooting first.
Elisha said:
Don't be a dip****,. I was stating my experience.
From stock 2.1 I could not install Continuum v4 in recovery and got a similar error for E:/
I had to flash a SpeedMod based kernel in recovery and root first before the rom would go all the way trough to flash properly!
It only happens to certain roms...other roms can just flash in recovery from stock no problem without rooting first.
Click to expand...
Click to collapse
This statement thus proves you have no idea what you are talking about. When you understand how a Rom flash works, then you can come back to the discussion. In the meantime, try reading an update-script or 2
Sent from my HTC Vision using Tapatalk
energy83 said:
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
Click to expand...
Click to collapse
You said that you installed the 32 bit drivers for windows 7? Unless you are running a netbook or installed Win 7 on an older computer you probably need the 64 bit drivers. Most newer laptops these days are 64 bit OS. You can check by right clicking on "my computer" and selecting properties. It will say whether you are running 32 or 64 bit.
I also recommend downloading kies (samsung sync software). You can get it off the Samsung website under downloads. Once it's installed and opened, under tools, you can select install drivers. Go through that process and then close kies (make sure it isn't still running in your system tray), open odin and try to connect in download mode again. Don't forget basic troubleshooting like trying a different USB port if the first one doesn't work the first time.......

[Q] Stuck on boot screen... how to use recovery mode?

My I9000 is stuck on the boot screen, after trying to install EZbase (was stock eclair). Odin/heimdall don't see the phone in download mode. I CAN get into recovery mode.. i have Clockwokmod recovery 2.5.1.0 speedmod ULFK on there. I have tried a factory reset, but this didn't help.
So what do i do here?
I am under the impression i need to flash with an update.zip; but i don't have a clue what should be my update.zip.
Sorry if this has been asked many times, but i searched and have read many threads and got nowhere.
ok well download the android SDK tools and isntall all the USB drivers. Unplug your USB cable and change the port from the one you are using, boot your phone into download mode, once in download mode fire up ODIN v 1.7 and plug your phone in, it should find it in odin, once you can see it in odin you should be able to continue flashing EZbase and then onto Cyanogen if that is what you were trying to do
Once you get odin to recognize your phone in download mode you need to flash a Kernel/Rom
http://forum.xda-developers.com/showthread.php?t=991792
since you were trying to do that try the link above
Thanks for the quick response!
spectre85 said:
download the android SDK tools and isntall all the USB drivers.
Click to expand...
Click to collapse
do you mean Android SDK Starter Package? Or?
http://developer.android.com/sdk/index.html
This is what i downloaded; what do i do now? Do i have to run SDK Manager.exe and install java (i would like to avoid this, if i can)??
Thanks for your help.
ya unfortunately you have to install java. so maybe your phone isn't being recognized because your doing it in the wrong order....try this before you install anything, unplug the phone, boot into download mode, fire up odin then plug the phone in. you should see it on some com port on the top left
Ok; Java installed, ran SDK Manager and added Google USB Driver for Windows, Revision 4. [ as developer.android.com/sdk/win-usb.html ], which is in \android-sdk-windows\extras\google\usb_driver
The directions provided by google (url above) suggest plugging the phone in first. This installed the samsung drivers automatically, however.
Odin3 1.7 now showed a port; but the flash stalled at 'SetupConnection..'
I tried using 'update driver' via Device Manager, but all that i see is;
Modems -> SAMSUNG Mobile Modem
Universal Serial Bus controllers -> SAMSUNG USB Composite Device
Neither would update with the drivers in \android-sdk-windows\extras\google\usb_driver
[Also, Yes, I am opening odin and booting in download mode before connecting the USB cable]
Ok try flashing just a kernel go to the Dev section and find a kernel from hardcore it is called speedmod kernel. That should flash in 20 seconds or so. Flash the froyo one he has one for gingerbread so don't use that one they are separate threads so its easy to tell which is which
Sent from my GT-I9000 using XDA App
..now if i try to turn the phone on it shows a phone and a PC with a /!\ warning symbol between them, and i can't boot in to recovery mode. I CAN boot into download mode, and the PC makes a noise to acknowledge something has been connected, but Odin doesn't see it.
EDIT: I reinstalled Keis, and selected 'install drivers' on the menu from within the app.. this meant Odin was able to see the phone and i have sucessfully (apparently) updated the kernel to speedmod froyo. The phone is back to the 'Galaxy S' screen again. Now what? How long should the phone take to boot if it is sucessful (ie. how long should i wait before restarting?)
EDIT 2: Ahh, EZbase flash worked too! .. thank F, a working phone!
So i guess the key was to get the drivers (again) from the submenu in the Keis App NOT the android SDK.
Glad it worked out, sorry it took so long to reply, ya after you get a kernel on there then you need to flash a rom again, which is exactly what you did later

[Q] odin not recognizing my captivate

I have a Samsung Captivate and its running cyanogenmod 7. I notice the bad battery life so i want to flash back to stock. I usually use odin but with this rom odin is not recognizing the phone. I put my phone in download mode and gadget serial pops up at the bottom and thats it. Now my phone isnt getting past the att logo. idk what to do for odin to recognize my phone. I have all the captivate drivers. Does it has something to do that my phone thinks its a nexsus S now.
PLEASE HELP
Yes your missing the correct drivers. Check for AOSP or Google usb drivers. CM7 is not based on the SGH-i897 so the drivers wont recognize your phone.
where can i find that. i think i did all of that. today i downloaded android sdk and something google revision 4.some site told me to do that but nothing working. my phone is stuck at the att logo, wont go in recovery, and odin wnt recognize the phone in download mode. idk what to do !
ballkidray said:
where can i find that. i think i did all of that. today i downloaded android sdk and something google revision 4.some site told me to do that but nothing working. my phone is stuck at the att logo, wont go in recovery, and odin wnt recognize the phone in download mode. idk what to do !
Click to expand...
Click to collapse
First, uninstall all the captivate-related USB drivers you currently have installed (best to start clean), and reboot your computer.
Then, try doing the instructions on this page. Once you have those drivers installed, reboot your computer and then hook your phone up again. That should (in theory) get you going.
my phone only going in download mode. i tried all that. every time i connect the phone in download mode it says gadget serial
jmtheiss said:
First, uninstall all the captivate-related USB drivers you currently have installed (best to start clean), and reboot your computer.
Then, try doing the instructions on this page. Once you have those drivers installed, reboot your computer and then hook your phone up again. That should (in theory) get you going.
Click to expand...
Click to collapse
Just install SDK and you will have the drivers. CM7 is based of Nexus S, SKD has those drivers.
then ill be able to use odin ?
I think I have the same problem now..Odin not recognizing my phone..
Tried different cables and different computers with no luck..
Did you guys find a way to fix it?

CAPTIVATE - Frozen on AT&T Boot, Unrecognized via USB, NO access to CWM - PLEASE HELP

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.

Categories

Resources