I looked through quite a few threads with the "stuck at samsung logo" problem, but none seems to be the same as mine...
I tried several roms (Vegabond, Zeus ZTR for ~2 months, Aeon, Legend 3 for ~2 weeks), and then tried to flash MIUI (specifically MIUI.us.Aries_v4_2.7.20_Eng_Deo_ZipA_Signed_TMT.zip). After installing the zip, I thought I tried reflashing it again for good measure, so I went into advanced / reboot recovery in CWM, and that's when the phone get stuck at the samsung logo.
This seems a bit different than others in that it won't turn off. Holding the power button will shut down, then get back to the same place one second later. Nothing I did can get the phone to anything but the Samsung logo. I decided to just leave the phone plugged in last night, at least to charge the battery. This morning it looks like I can finally get the phone into download mode, but neither Odin nor the Heimdall one-click recognizes the phone (I did install Kies). I start with the battery out, phone unplugged. Then press and hold the v+/v-, plug in USB (the PC blips the "USB sound" a couple of times, but shows the "device not recognized" message), and then insert the battery. As soon as I do that, the phone gets into download mode (ask to press v+ to download or v- to reboot) but the PC then blips the "USB disconnect" sound, and neither Odin nor Heimdall one-click can see the phone. The phone just shows the yellow triangle with andoid shoveling, and on top it says "CUSTOM BINARY DOWNLOAD: YES (1 counts)"
I'd really appreciate any pointers...
fishline said:
I looked through quite a few threads with the "stuck at samsung logo" problem, but none seems to be the same as mine...
I tried several roms (Vegabond, Zeus ZTR for ~2 months, Aeon, Legend 3 for ~2 weeks), and then tried to flash MIUI (specifically MIUI.us.Aries_v4_2.7.20_Eng_Deo_ZipA_Signed_TMT.zip). After installing the zip, I thought I tried reflashing it again for good measure, so I went into advanced / reboot recovery in CWM, and that's when the phone get stuck at the samsung logo.
This seems a bit different than others in that it won't turn off. Holding the power button will shut down, then get back to the same place one second later. Nothing I did can get the phone to anything but the Samsung logo. I decided to just leave the phone plugged in last night, at least to charge the battery. This morning it looks like I can finally get the phone into download mode, but neither Odin nor the Heimdall one-click recognizes the phone (I did install Kies). I start with the battery out, phone unplugged. Then press and hold the v+/v-, plug in USB (the PC blips the "USB sound" a couple of times, but shows the "device not recognized" message), and then insert the battery. As soon as I do that, the phone gets into download mode (ask to press v+ to download or v- to reboot) but the PC then blips the "USB disconnect" sound, and neither Odin nor Heimdall one-click can see the phone. The phone just shows the yellow triangle with andoid shoveling, and on top it says "CUSTOM BINARY DOWNLOAD: YES (1 counts)"
I'd really appreciate any pointers...
Click to expand...
Click to collapse
First thing I suggest is to uninstall Kies, it has been known to cause issues. Second get the drivers back on the computer, you will find them here http://forum.xda-developers.com/showthread.php?t=1610374
thanks to bigjoe2675.
From this point,there is more than one way to do this, my choice is this, because it always works for me http://forum.xda-developers.com/showthread.php?t=1524081 all credit to qkster and Entropy512.
Should you wish to give MIUI another try please post in that thread and I will help.
BTW, it is normal to get stuck on the Samsung screen when you go from GB to ICS. There are instructions posted in the OP of the ICS rom for proper way to flash.
I un-installed Kies and all the other samsung drivers from win7, rebooted win7, re-installed the Infuse driver from ISET thread, rebooted win7 again, then tried connecting the Infuse (battery out, hold v+/v-, plug in USB, then insert battery). Infuse will ask whether to go into download mode, and win7 complained about unrecognized USB device. If I press v+ to go into download mode on the infuse (shows the yellow triangle and "Downloading... Do not turn off Target!!!" message), win7 blips the USB disconnect sound. The Heimdall one-click 1.3.1 shows "Device state: Disconnected" the whole time. Tried it several times with the same result. Any more ideas/suggestions?
Can u get to CWM?
Pony Express said:
Can u get to CWM?
Click to expand...
Click to collapse
Like pony said, ur supposed to get stuck at Samsung logo after flashing ics ROM from GB. Try to hold both volume keys and power button to turn on ur phone. Hopefully this will get u back to recovery, then u just need to flash miui again.
I'm thinking this might b ur problem bc the previous ROMs u mentioned were GB.
Sent from my SGH-I997 using xda app-developers app
fishline said:
I un-installed Kies and all the other samsung drivers from win7, rebooted win7, re-installed the Infuse driver from ISET thread, rebooted win7 again, then tried connecting the Infuse (battery out, hold v+/v-, plug in USB, then insert battery). Infuse will ask whether to go into download mode, and win7 complained about unrecognized USB device. If I press v+ to go into download mode on the infuse (shows the yellow triangle and "Downloading... Do not turn off Target!!!" message), win7 blips the USB disconnect sound. The Heimdall one-click 1.3.1 shows "Device state: Disconnected" the whole time. Tried it several times with the same result. Any more ideas/suggestions?
Click to expand...
Click to collapse
Once you install Kies or any Samsung driver to a port, Heimdall previous device recognition is erased.
If you want to use Heimdall in that specific usb port again, you need to reinstall heimdall drivers.
You can also move the usb cord to a different usb port or try a different usb DATA cord and reinstall the Heimdall drivers
benbos_06 said:
Like pony said, ur supposed to get stuck at Samsung logo after flashing ics ROM from GB. Try to hold both volume keys and power button to turn on ur phone. Hopefully this will get u back to recovery, then u just need to flash miui again.
I'm thinking this might b ur problem bc the previous ROMs u mentioned were GB.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
@Pony_Express: No CWM. Can only get into download mode.
@Benbos_06: I did try volume up & volume down (that's what I meant by v+/v-). If I add the power button to the mix I only get the Samsung logo. If I do any button combo without plugging in the USB, I also get only the Samsung logo. I have to do exactly v+/v-, plug in USB, then insert the battery, to get anything other than the Samsung logo.
@qkster: By Heimdall drivers, do you mean the one in the ISET thread (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)? That's the one I re-installed after removing Kies and all other samsung drivers I saw. I just un-installed it again, reboot, re-install, reboot, change to a different cable and different port. Still the same problem: As soon as the usb cable is plugged in (while v+/v- are held down), the PC blips USB connect but displays the "USB device not recognized" message. If I then insert the battery to have the phone power up to the screen where it asks if I really want to go into download mode, as soon as I hit the v+ to go into the download mode, the PC blips the USB disconnect sound. Is the device recognition supposed to happen before or after going into download mode?
Looks like as long as the PC does not recognize the phone, neither Heimdall or Odin can work. Is this right? From what I gathered, as long as I can get into the download mode, it's a soft-brick and the situation isn't hopeless. However, I'm really at my wits' end as to how to move further ahead...
fishline said:
@Pony_Express: No CWM. Can only get into download mode.
@Benbos_06: I did try volume up & volume down (that's what I meant by v+/v-). If I add the power button to the mix I only get the Samsung logo. If I do any button combo without plugging in the USB, I also get only the Samsung logo. I have to do exactly v+/v-, plug in USB, then insert the battery, to get anything other than the Samsung logo.
@qkster: By Heimdall drivers, do you mean the one in the ISET thread (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)? That's the one I re-installed after removing Kies and all other samsung drivers I saw. I just un-installed it again, reboot, re-install, reboot, change to a different cable and different port. Still the same problem: As soon as the usb cable is plugged in (while v+/v- are held down), the PC blips USB connect but displays the "USB device not recognized" message. If I then insert the battery to have the phone power up to the screen where it asks if I really want to go into download mode, as soon as I hit the v+ to go into the download mode, the PC blips the USB disconnect sound. Is the device recognition supposed to happen before or after going into download mode?
Looks like as long as the PC does not recognize the phone, neither Heimdall or Odin can work. Is this right? From what I gathered, as long as I can get into the download mode, it's a soft-brick and the situation isn't hopeless. However, I'm really at my wits' end as to how to move further ahead...
Click to expand...
Click to collapse
Okay, I wasn't sure if it was soft bricked or if u still had recovery but were looping.
The device is supposed to b recognized by Heimdall/Odin while it is in download mode. I don't even think my computer showed it being recognized until I started Heimdall then Heimdall recognized it.
I would keep trying with different Heimdall/Odin versions and different combinations of cords and ports or a different computer if that's an option. Even if the computer doesn't show it as recognized try to open the Heimdall one click or Odin to see if it shows the device. For me, it took like afew hours of messing around with different combos of these to finally get it recognized.
The last option is to get a usb jig (believe that's what it is called). They r cheap and r supposed to give u a much better chance of having ur phone recognized. But I would keep trying different ports, cords, computers (if that's an option) first.
Sent from my SGH-I997 using xda app-developers app
qkster is offline but will most likely be back soon. To answer your question @qkster: By Heimdall drivers, do you mean the one in the ISET thread (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)? - he is actually talking about the latest Java drivers, you will find his link right under How To Install. After installing, it would be a good idea to restart your computer and then follow the rest of his install instructions. You are in a good place, be patient, you are doing great.
Edit: Just re-read your post - qkster can correct me if this is incorrect- In order for your computer to recognize your phone after you have the drivers installed, you should power the phone on and let it display the Samsung screen. At that point connect your usb cable but do not press volume keys to enter download mode at this time. Once your computer recognizes your phone then you can proceed.
fishline said:
u mean the one in the ISET thread (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)? That's the one I re-installed after removing Kies and all other samsung drivers I saw. I just un-installed it again, reboot, re-install, reboot, change to a different cable and different port. Still the same problem: As soon as the usb cable is plugged in (while v+/v- are held down), the PC blips USB connect but displays the "USB device not recognized" message. If I then insert the battery to have the phone power up to the screen where it asks if I really want to go into download mode, as soon as I hit the v+ to go into the download mode, the PC blips the USB disconnect sound. Is the device recognition supposed to happen before or after going into download mode?
Looks like as long as the PC does not recognize the phone, neither Heimdall or Odin can work. Is this right? From what I gathered, as long as I can get into the download mode, it's a soft-brick and the situation isn't hopeless. However, I'm really at my wits' end as to how to move further ahead...
Click to expand...
Click to collapse
As long as you can get into download mode, you don't really need a jig. It is a handy tool, though. No battery pull. Just plug in the jig.
http://forum.xda-developers.com/showthread.php?t=1524081
Here is the heimdall 1 click uclb3. Read the op a few times. You will need to flash it 2 times...the second time with boot loader checked.
the drivers you mentioned is for odin or samsung..not for heimdall..it has it's own self contained drivers.
Try a different pc or a usb port with a known good usb data cord.
After you run the jar file, look thru the options. you should see option to install drivers - via zadig
Okay man i had the exact same problem
And your right no one has the answer but after a week off research i noticed that its easier to go to an at&t store and get a new one. I was worried that they would find out but they didn't and just gave me a new one
Sent from my SGH-I997 using xda app-developers app
OK. I un-installed the Samsung drivers and reboot the PC. Re-download the Heimdall one-click back to stock jar. Ran it, clicked on "install Heimdall 1.3.1" from the Help menu. It first complained that I have a newer VC++ redistributable than what it tried to install. Closed that dialog, then it ran zadig. With the phone connected and in d/l mode, the "list all devices" option does not find the phone. Tried a different cable and port to no avail.
Moved to another PC (WinXP instead of Win7). The VC++ redistributable installs. Zadig finds an unknown device (which I'm quite sure is the phone), but driver install fails. I guess it really needs to find the SAMSUNG USB composite device? Would I be able to use the "create a new device" menu to force it? If so I guess I need to put in the usb id?
Yoshiikim said:
Okay man i had the exact same problem
And your right no one has the answer but after a week off research i noticed that its easier to go to an at&t store and get a new one. I was worried that they would find out but they didn't and just gave me a new one
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I don't think I have that luxury: I bought the phone used off craigslist about 2-3 months ago. I doubt AT&T would exchange the phone w/o receipt.
fishline said:
OK. I un-installed the Samsung drivers and reboot the PC. Re-download the Heimdall one-click back to stock jar. Ran it, clicked on "install Heimdall 1.3.1" from the Help menu. It first complained that I have a newer VC++ redistributable than what it tried to install. Closed that dialog, then it ran zadig. With the phone connected and in d/l mode, the "list all devices" option does not find the phone. Tried a different cable and port to no avail.
Moved to another PC (WinXP instead of Win7). The VC++ redistributable installs. Zadig finds an unknown device (which I'm quite sure is the phone), but driver install fails. I guess it really needs to find the SAMSUNG USB composite device? Would I be able to use the "create a new device" menu to force it? If so I guess I need to put in the usb id?
Click to expand...
Click to collapse
It's been a while for me but try to install the samsung usb composite device to see it it makes any difference.
The other thing you can try is a newer usb hub (if you have one) between your pc and the phone.
qkster said:
It's been a while for me but try to install the samsung usb composite device to see it it makes any difference.
The other thing you can try is a newer usb hub (if you have one) between your pc and the phone.
Click to expand...
Click to collapse
I've tried it on all USB ports of a third PC with the same result. Tried both USB cable I have (one stock Infuse, the other stock SGS2, look identical). Does it matter exactly when I put the phone into d/l mode? If I leave the phone on the "warning" screen, zadig can see the "Unknown device" but can't install driver. As soon as I press volume + on the phone to go into d/l mode, the "Unknown device" disappear from the list. If I put the phone into d/l mode first before zadig starts, it doesn't even see the "unknown device".
Does anyone know if there's a way to force zadig to install the correct driver? Would that help?
fishline said:
I've tried it on all USB ports of a third PC with the same result. Tried both USB cable I have (one stock Infuse, the other stock SGS2, look identical). Does it matter exactly when I put the phone into d/l mode? If I leave the phone on the "warning" screen, zadig can see the "Unknown device" but can't install driver. As soon as I press volume + on the phone to go into d/l mode, the "Unknown device" disappear from the list. If I put the phone into d/l mode first before zadig starts, it doesn't even see the "unknown device".
Does anyone know if there's a way to force zadig to install the correct driver? Would that help?
Click to expand...
Click to collapse
It has been a while since I had to install heimdall. I keep that specific pc, that usb port and that usb cord sacred.
I install nothing else as I treat this as my infuse life line.
I found a few links that may help:
http://www.thegalaxytabforum.com/index.php?/topic/4757-how-to-use-heimdall/
http://forum.xda-developers.com/showthread.php?t=1113195
http://www.glassechidna.com.au/products/heimdall/
All I can say is persistence pays off.
If not, try Odin...if you use Odin, just remember to reinstall samsung kies device drivers and use a different usb port.
gl
qkster said:
It has been a while since I had to install heimdall. I keep that specific pc, that usb port and that usb cord sacred.
I install nothing else as I treat this as my infuse life line.
I found a few links that may help:
http://www.thegalaxytabforum.com/index.php?/topic/4757-how-to-use-heimdall/
http://forum.xda-developers.com/showthread.php?t=1113195
http://www.glassechidna.com.au/products/heimdall/
All I can say is persistence pays off.
If not, try Odin...if you use Odin, just remember to reinstall samsung kies device drivers and use a different usb port.
gl
Click to expand...
Click to collapse
Thanks very much. I really appreciate your help!
All three links talk about the step where the phone is put into d/l mode and then zadig would find the SAMSUNG USB Composite device for driver installation. That's the step that's not happening for me. If I boot the phone into the download mode warning screen (i.e., before pressing volume up), zadig shows an "Unknown device", and as soon as I press volume up to go into download mode, it disappears from the list altogether.
Tried Odin: doesn't recognize the phone either.
Will keep trying though, and report back if I ever get any where with it.
Having the same exact issue as fishline
I'm glad I could find this thread, because I'm having the exact same trouble as fishline regarding multiple PCs (and multiple USB cables) not allowing me to mount USB storage, and each PC giving me a "USB Device Not Recognized" message. My girlfriend originally had this phone on stock AT&T 2.2 (Froyo). I rooted it, installed CWM Recovery (red), and installed the Serendipity VII rom (I believe this is a GB rom). I had never used Odin or Heimdall, so no rom has ever been "flashed" to this phone. My gf didn't have any trouble with this ROM for some time, including mounting the USB on several occasions.
She then bought an HTC One X, and I got this phone. I immediately upgraded the rom to Dark Knight (Android 4.0.4, ICS?) which screwed up the recovery screen (adding static-y rainbow artifacts and changing the recovery to blue instead of red). To correct the recovery issue, I reverted to AT&T Froyo by using a recovery ZIP. This rom now runs OK, but USB mounting has completely disappeared. I have tried 2 Windows XP desktops and 2 Windows 7 laptops, and 4 different USB cables (including 2 verified data cables) with no success. I have installed Kies, Kies Mini, and just the Samsung drivers by themselves. I even installed Samsung PC Studio due to a suggestion in another thread. No luck at all. Every time I connect the phone to the PC (whether in D/L mode or just from the home screen) I get a "USB Device Not Recognized" message. When I originally flashed Dark Knight, I noticed there was some issue with the naming of the external SD card. I'm wondering, could this issue be related to a bad partition of some kind in the internal memory? And is there any way to fix this without the use of Heimdall or Odin (which I cannot get to work)? I can flash through CWM Recovery just fine (since it's fully fixed now).
If there is still anyone that can give me some suggestions, I would reaIly appreciate it. I can use the phone as is until February, when we're due for another upgrade, but the lack of USB mounting is extremely inconvenient. Thanks to fishline for originally starting this thread, and to everyone that has offered suggestions.
Maybe try this... Good luck !!
http://forum.xda-developers.com/showthread.php?t=1389375
It has worked on various Infuse roms.
Thanks
Pony Express said:
Maybe try this... Good luck !!
http://forum.xda-developers.com/showthread.php?t=1389375
It has worked on various Infuse roms.
Click to expand...
Click to collapse
Thank you for the suggestion. Unfortunately, I am currently on the AT&T stock Froyo rom (rooted with recovery, of course), so I don't think it's allowing me to install the APKs in your link. It says "there was a problem parsing the file" or something similar. I appreciate the help.
Related
So, I bricked my Infuse last night at work when I tried installing MIUI from ROM Manager. I've been trying to unbrick using gtg's Ultimate Unbrick method, but no luck. I believe it's something to do with the Samsung Drivers since my phone is not recognized in Odin. Tried to redownload the Drivers from Samsung's website, but still doesn't work.
Any ideas?
BTW, running Windows 7 32bit
why would you install a rom that's for a different phone?
can you boot into recovery mode? did you try the "jig"?
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
the reason other roms pop up in rom manager is because you are using the galaxy recovery. unless it says "for infuse" (there is only one, gtg's rom) it wont work. bummer dude. im all out of ideas, never had this happen. hopefully someone who's been through this can chime in and provide some info that will help you.
on a side note, why cant you take it to an att branch and have them exchange it for you?
Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
I hope u have USB debugging turned on. If yes, u cud try this:
1. Download and install android SDK (search google for this if don't know how to).
2. Open a command prompt
3. Type in "adb reboot recovery" without quotes, and don't hit enter
4. Connect phone to PC
5. Turn the phone on
6. Wait for "samsung" to appear, and hit enter in command prompt
7. If it says "device not found", use the up arrow to get the command from history, and hit enter again. At some point, it should issue the command to the device.
8. If u can get to recovery, well, u have a way to now try to flash any other ROM.
Don't give up. Samsung has strong phones that could be got out of soft bricks most of the time.
Delete/reinstall the drivers.
Infuse 4G
Just tried Diablo's method, and it tells me command not recognized...
Download Kies on your pc to have it recognize ur phone. Run odin. Put ur phone in download mode (pull out battery, put it back in, hold both volume buttons down, plug in ur usb) and use gtg's unbrick.
Sent from my SAMSUNG-SGH-I997 using XDA App
Tried Kies before and it would never recognize the Infuse. Should I pick Galaxy?
UPDATE!!
Redownloaded Kies and installed the drivers (for the 500th or so time) and now Odin is recognizing a device. It's showing [COM3] instead of COM## but I'm letting Odin do its thing. Seems to be working... Crossing my fingers!
EDIT::
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
****in A! Thanks for the help guys!
Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251
Misterjunky said:
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251
Click to expand...
Click to collapse
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D
Pat713 said:
Just tried Diablo's method, and it tells me command not recognized...
Click to expand...
Click to collapse
That means u do not have android toolkit installed on ur system. You should install it first for the adb commands to work.
I would recommend downloading and learning the basics of adb. This could be a life saver in many no-so-happy situations.
Pat713 said:
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D
Click to expand...
Click to collapse
Had this same problem and it turned out to be a hardware problem. There was no gix for it. Also youll notice that gtgs recovery includes a preroot. If you need to send your phonr back like i did youll need to get that off. It was tricky for me because the hardware was so screwey. I got it off after a few reboots of the phone and a couple of trys with superoneclick.
Sent from my SAMSUNG-SGH-I997 using XDA App
So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.
I pull out my battery and let it discharge for about 15 secs and hold volume buttons then connect USB cable and finally insert battery while still holding volume buttons of course, it'll get you into download mode. Never failed me. I've had my phone not even turn on the screen, it stays dark during a screwed up flash with odin. I then flash UCKI2 with bootloaders and then flash to gingerbread ROM I like. If you plan on installing custom ROMs your phone will semi-brick numerous times. If its showing a phone, exclamation mark and computer with a message saying firmware flashing failed. That is perfect! Just make sure you have Samsung USB drivers and simply flash using odin, it'll show COM and a number like 5 (COM5) then just flash. I'd advise you to remove any external SD card and restart before using odin it acts up. Hope this helps
hupo224 said:
So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.
Click to expand...
Click to collapse
The "Phone - ! - PC" will be your download mode screen. Just download from there.
However, if a flash goes foul somehow, you may be left with the infamous "phone--/!\--PC" screen.
If you see this, don't panic. Although it's not technically the download mode screen, many users (including myself) have been able to successfully flash from that screen. Give it a try.
Click to expand...
Click to collapse
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.
asasione said:
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.
Click to expand...
Click to collapse
100% - I had similar experience with my first flash but after a few goes at it and 3 or 4 "soft-bricks" all has been great!
Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..
It seems I got it in download mode this morning with the jig. Just trying to get my damn pc to read it. Sometimes the right drivers work sometimes they don't. ugh
Connection issue in my sig
Any chance you have another pc to try it with? Or possibly another cable?
Going to try one click on ubuntu...
Ive had issues in the past before with certain USB ports on my PC not reading the phone.
Try plunging in your phone to a different USB port and it can make a world of difference with the driver issue (even if you have to plug it in the back of your PC).
try one click unbrick in the android development page
hupo224 said:
Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..
Click to expand...
Click to collapse
Are you running x64? If so are you running the 64 bit drivers?
I also had the same issue a couple of times, which is technically called a "soft brick" . You could resolve this issue using ODIN flasher and reverting back to stock. Now coming to USB problem in windows, this is a known issue with windows (especially Vista and Win7) and samsung!! The remedy which I found is as follows :-
1.Disconnect the phone from USB
2.Remove samsung USB driver software from your windows PC.
3.Reboot and then navigate to C:\Program Files\ (assuming that C:\ is your windows OS partition)
Delete "samsung" folder.
4.Download latest samsung USB Drivers for captivate and install.
5.Reboot the phone.
6.Open ODIN and connect your Phone to PC.
It should detect the COM Port by now. Try this and get back
"Thanks" , If I helped U
I am in desperate need of help .. I am not a noob to flashing roms and rooting, however I have a one-off situation w/ no precedents to my knowledge. I have read these and other forums for days to no avail.
I was flashing Infintium Rom 4.0.4 from MIUI 2.3.6. I followed the steps listed in the post (http://forum.xda-developers.com/showthread.php?t=1661690). After flashing I rebooted and waited however the phone was/is stuck on the Samsung logo and never progressed. I then pulled the battery and attempted to go back to recovery mode to reflash make sure I did flashed correctly. However, upon going back into recovery I was greeted by the below image.
Clockwork Mod is extremely distorted and flat out unusable !! As I read further down it advised to use Heimdall (http://forum.xda-developers.com/showthread.php?t=1331381). I downloaded and attempted to use, however my PC (Which by the way is Windows 7 64-Bit) recognized the phone but the Heimdall software did not. I already had the right drivers for the PC and phone. After a few tries I deleted the files and reapplied them. On the 2nd menu after selecting list devices, on the drop down the option for Samsung USB Composite Device neeever ever appears. I also tried on a different PC that ddnt have the drivers and started brand new. Still, Heimdall ddnt recognize.
I also tried to flash numerous files including but not limited to GTG Ultimate Unbrick via Odin. Again, PC recognized USB connection however program ddnt. At this point, I do not know if it is because the status of Clockwork Mod on my phone, but I know it is not because of the drivers or the USB ports on my PC.
In addition to that, I have just scrapped the idea of flashing or getting in CWM and just wanted to do a hard reset (While phone is off held Vol down and Power, once started released power and contimued to hold Vol down. This should take the phone from the Samsung logo to an alt menu that will give the option to do a factory reset. But again w/ my luck .. that screen neeever appears.
In short I have tried at least 3 different ways and many maaany variations to get the phone back into recovery or into a full boot and had NO success.. Please help and ask as many questions as needed to diagnose and resolve this issue .. Thanx in advance and apologize in advance if posted in the wrong thread.
Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse
andros11 said:
Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.
ohsirus said:
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.
Click to expand...
Click to collapse
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
http://d-h.st/sKF
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
I will try again .. Downloaded, rebooting then will go thru the process again .. standby
Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
no change .. still shows disconnected
The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2
rkkaranrk said:
The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I just did that to post a pic as an example .. I did go to download mode and not recognizing it
The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!
drnecropolis said:
The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!
Click to expand...
Click to collapse
I know I need to get the bootloader and a kernel on it however I cant = ( .. yet .. I have 4 different ports on my PC and have tried them all. i have tried phone on then run programs and programs on 1st then phone on and no new results.
I found this short video and it describes my exact situation .. please watch to futher understand http://www.youtube.com/watch?v=OHLUYckTlug
So u have odin and heimdal both on the same PC and drivers for them if yes then try this.
On the PC/Laptop uninstall all the drivers for samsung or any other phone and follow this.
Go to accessories> system tool> system restore and check the restore point where the drivers for heimdall were installed restore to a previous restore point after restore finishes install the drivers for Infuse and see now Odin recognizes ur phone, It should.
I had the same exact problem, do you have another phone on which you can install the same CWM recovery on? ...Because the clockwork mod recovery still works, it's just that you can't see it. So just flash a new ROM, by going back n forth between phones, clock how many clicks it takes to get to 'choose zip to install' then 'download' on the not messed up phone, then do the same on the screwy one, just keep doing that till u flash the new ROM.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Well i was running super CM7, which was beastly at saving battery, and last night i get the hankering to flash entropy's CM9 ICS.
So as per the instructions, i had the blue CWM, so i just flashed the rom and cleaned up. It first booted up fine, with a little rainbow distortion at the start. I then rebooted into CWM to see if it was all good, and its rainbow distorted across the entire screen. I then hit the power button to reboot and it rebooted into CWM with the distortion (tried about 20 times). So i search on XDA and find a thread where something similar happened but he was able to fix his with hemidall. At this point I have tried Odin (dosnt recognize my device), Hemidall (recognized my device but errored out until i installed their drivers, after the reboot no longer sees my device).
So now i am able to get into download mode but neither odin or hemidall recognize my phone. So i guess the question becomes, Am i totally boned on this one? Do i have to bite the bullet and get a new phone? :crying: Thanks, just for taking the time to look over my insignificant problem, and a Thank You Very Much in advance for any advice/replies.
Try going into devices on your PC, delete the Samsung USB composite if it is there. Go get Heimdall Suite and reinstall drivers. Should reboot PC. Go to download mode (vol +/-, battery in, then plug USB in or vol +/-, USB in, then battery and no power button on either). See if your phone is recognized. If yes, find instructions for flashing GB bootloaders. Be careful, flash incorrectly and you might end up with a brick.
Sent from my SGH-I997 using xda premium
I installed the drivers over the samsung composite but now hemidall doesnt recognize my phone anymore, and when i try the drivers again "samsung usb composite" doesnt appear in the list anymore just "unknown device". I've started looking at new phones online, might just have to go with one of those lol.
Can you try a different computer?
Sent from my SGH-I997 using xda premium
I tried with my parents computer and with a different cable on my computer, and neither heimdall or odin would recognize my phone. So i guess its new phone time, im thinking about the lumia 920, has anyone had serious usage with one, how are they? Sorry for sorta changing the topic.
Have you tried installing Kies
Sent from my SGH-I997 using xda premium
yep, it still didnt recognize it, i even downloaded the specific drivers for my phone and still, no device connected in download mode error.
Hey guys,
I've got a Galaxy S 4G currently running the CM 9 build Release 8 (from August) and here are the problems I'm experiencing:
- random failure to reconnect to the phone network after I've been in the subway (have to reboot)
- just plain random reboots, though they're rare
The lack of reconnectivity is driving me up the wall. How likely is it that this problem is just with the OS? I don't want to have to get a new phone but maybe I've dropped this one too may times. :silly:
You might try a different modem to see if reconnecting works better or put airplane mode in you status bar toggles and toggle it off/on when you get off the subway for a fresh connection.
Thank you, lumin!
edited: I'll direct other questions to the CM9 thread.
Sorry guys, returning to this thread rather than clogging up the Heimdall thread or the CM9 thread.
I'm having a very basic problem and am feeling very stupid and very frustrated. I can't get Heimdall to recognize my phone.
Last attempt steps I took:
- Installed Win64 Samsung drivers
- Rebooted PC
- Connected phone to computer when in each of regular, recovery, and download mode.
- Ran Zadig as administrator and selected List All Devices
- Phone does not show up as Samsung anything, just as Gadget Serial
- Hit Install Driver (Note: this has never changed to "Reinstall Driver" or anything
- Ran Heimdall as admin
- Doing a test for compatible devices turns up nothing.
Use the Odin one click here http://forum.xda-developers.com/showthread.php?t=1500427
Use a different USB port and you should be fine
Sent from my SGH-T959V using xda app-developers app
Additionally, installing the official drivers will make the phone not connect if you're using one of the MTD (ICS/JB/newer-CM7) roms. Since they use the generic Google Android driver rather than the Samsung one.
Another thing is, zadig includes (for me) 3 or 4 different driver options, and only one of them actually works. For me, that's WinUSB. For you, might be something else. But try installing one, rebooting the computer, restarting the phone, and seeing if it works. Then move on to the next one. Once you figure out what works for you, write it down somewhere and use it for the future.
Thanks, I'll give that a shot.
Theraze said:
Additionally, installing the official drivers will make the phone not connect if you're using one of the MTD (ICS/JB/newer-CM7) roms. Since they use the generic Google Android driver rather than the Samsung one.
Click to expand...
Click to collapse
Can you elaborate on that for me? By connect, what do you mean? Connect to the computer?
P.S. is this the driver you're referring to? So I should be using this and not the Samsung one?
http://developer.android.com/sdk/win-usb.html
I meant that uninstalling the Kies/official drivers, rebooting, and only using the zadig drivers is likely to give you better results if you're using newer roms. Since the Kies drivers are only helpful if you're on GB and can only cause you problems otherwise.
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works. If not, run zadig, list all devices, select the phone, install libusbK driver, reboot, unplug, reboot phone into download, plug back in, check if flashing works. Repeat with libusb0 if needed.
Theraze said:
I meant that uninstalling the Kies/official drivers, rebooting, and only using the zadig drivers is likely to give you better results if you're using newer roms. Since the Kies drivers are only helpful if you're on GB and can only cause you problems otherwise.
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works. If not, run zadig, list all devices, select the phone, install libusbK driver, reboot, unplug, reboot phone into download, plug back in, check if flashing works. Repeat with libusb0 if needed.
Click to expand...
Click to collapse
Aaaaahhh. Ok, I'll try that.
Oh, and when having zadig/driver issues... always try to flash twice. And when it gives you an error, after the second failed flash, reboot the phone and flash again. Then move on to the next driver/attempt.
When this phone gets finicky, you need to get the yellow-caution flash screen to bypass its paranoia about your flashing.
Theraze said:
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works
Click to expand...
Click to collapse
Ok, one question about this:
- you've plugged the phone in while it's in download mode
- then in the second sentence you wrote "REBOOT phone into download mode" but the phone was in download mode before, so was a reboot actually necessary?
edit: And, I haven't actually tried flashing at all in Heimdall, I've just been checking to see if it sees a compatible device. Would you suggest I just try to go ahead with the flash, with each driver? (I'm not sure if I've seen the option to select anything more than Windows USB, but at least with that?)
Specially, shut down the phone and boot into download mode again. Easiest way to do it is probably to unplug USB, pull the battery, plug in USB, put the battery back in, etc... Guarantees that you've got your full phone-reboot cycle.
And regarding alternate drivers, there's a little up-down arrow next to the driver name. Click that to override the current best-driver-guess and manually pick your choice.
Damn, there's a bunch of reboots I was missing... I really hope I haven't screwed anything up permanently.
Theraze said:
And regarding alternate drivers, there's a little up-down arrow next to the driver name. Click that to override the current best-driver-guess and manually pick your choice.
Click to expand...
Click to collapse
Yeah.......... I don't have that. I looked again, it's not there.
edit: it would appear that Heimdall 1.3.1 came with Zadig 1.0 only... I just grabbed 2.0 from github.
Personally, I'm using Heimdall 1.3.2 and that's been working fine for me. But some people have issues with that one, so... no comments/complaints about Heimdall 2.0 RC1 yet on his site.
Theraze, if you could speak more specifically about one point here: all I have been doing is changing drivers (I've just tried all three) and then I've used Heimdall's Detect Device utility to try to detect the phone. Which has failed.
You have repeatedly said "try flashing". Do you think that can work even if Detect Device isn't working? I got the impression that was dangerous.
edit: well that's obviously what you're suggesting, but - how safe is this? Perfectly? Mostly?
If it doesn't see your phone, it won't flash. If it does, it should work or at least do... something. At which point, it probably hit the half-flash yellow screen I get every time I use Heimdall to flash a new kernel.
That's basically how complicated as I see this... Regardless of how well the detection tool is working, if it actually succeeds...
The 959V is nifty in that it's ALMOST impossible to hard-brick. If you're flashing bootloaders and pull the cord there, maybe... but if you screw up the kernel or one of the other things that make normal phones into depressing paperweight reminders, it just means reboot and flash again.
Thanks, man. Going to try flashing now.
Zilch. Can't see the phone with any of the three drivers.
Starting to give up hope of fixing this, honestly.