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.
Related
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
Hello everyone, I totally pulled a noob earlier, with all the excitement going around with the official ICS update going around, accidentally I pushed a 19100 ROM into my sgs2 by sprint; and now my device is semi brick, neither Kies, Odin nor SimpleDownloaderTool for SPH-D710 recognizes the device, after downloading the correct drivers into my computer.. now what do I do?
If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.
sgs4g SGH-T959V always reboot into download mode, even after successful oneclick
lumin30 said:
If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.
Click to expand...
Click to collapse
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.
Pro tip: Open a new thread if you need to ask a question or need help. Don't "hi-jack" other threads. (considering that the original thread is from 2012)
But it's done...
teevoo said:
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
Click to expand...
Click to collapse
Did you follow @lumin30's guide?
teevoo said:
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Click to expand...
Click to collapse
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
teevoo said:
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.
Click to expand...
Click to collapse
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.
bhundven said:
Did you follow @lumin30's guide?
Click to expand...
Click to collapse
Yes. Oh and I made several posts (not hijack ) regarding this issue elsewhere in the forum but got no response. One thing I forgot to mention in this version is that originally, the download mode on phone was triggered physically somehow. My uncle accidentally dropped the phone in water. He then blew it dry with a strong fan and must have turned it back on too early. Since then the phone's been in download mode.
bhundven said:
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
Click to expand...
Click to collapse
I'm now wondering if there is a program that can do a reset like heimdall/odin without going through the whole reflashing process. Assuming the phone's memory components haven't been physically damage, at least this would mean I can restart the phone to normal mode quickly.
bhundven said:
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.
Click to expand...
Click to collapse
Ok, I'll try to find a different computer to do this with, although right now I'm thinking USB is not the case as I have successfully performed the same flash on a different sgs4g and it works just fine (the difference was that phone was never stuck in download mode to begin with). For the problem phone, I have tried a couple of ports and 2 different cables on my Mac. From what you just told me, perhaps the phone's usb port is the culprit.
Thanks for your reply, and thanks for all the programming work you've contributed to this forum :good:
I was previously running MIUI (not sure which version) and something went wrong with it. Random processes just kept "unexpectedly stopping." I found the Heimdall One-Click and tried it. The process never finished (failed to upload FACTORYFS everytime :/). I tried checking the Flash Bootloaders option. It got the FACTORYFS upload percent a bit further along, but still failed. Opened up Odin, and it wouldn't find any device plugged in.
After a couple more tries at this, suddenly, no matter which USB port I plug in to, my computer fails to recognize the device when previously it would on a couple specific ports. Odin will not recognize it, either.
Am I screwed?
Edit:
I've gotten the USB to recognize. I'm scared to do anything now, for fear I won't get it to recognize again. Odin still does not see the device. What other tools can I use to unbrick this?
I believe the driver for heimdall "takes over" the port. You have to use a different port or uninstall the driver to use Odin on it again. Also it seems when the upload won't complete most have success with another cable....nothing wrong with qksters uclb3 return to stock. I've used it several times.
Sent from my SGH-I897 using Tapatalk
I had the same issue a few days ago. SCARED me to...
Powered the phone off.
Unpluged USB
Rebooted Windows PC
Rebooted phone
Started at step one again
This time try another USB Port on computer
This time everything worked
I've had this happen before. After much panicking, I used GTG unbrick.
Thread located here → http://forum.xda-developers.com/showthread.php?t=1116251
download is here → http://www.mediafire.com/?i57410xodydx5l1
Follow it verbatim. Worked like a charm!
unistall
i had the same thing happen the other day i opened device manager and unistalled the driver for the phone then pluged the phone back in let it reistall and away i went may have to reistall drivers from kies
All you need to do is install Samsung drivers again or switch USB ports. The LibUSB Zadig drivers are installed on a single USB port. No need to uninstall anything at all. Heimdall drivers are only installed to the USB port you had the device plugged into when you installed the drivers.
A better option would be to dual boot into Linux and One-Click just works every time.
It sounds like you are using a bad cable. Try using Heimdall one-click with a good cable. It works every time.
AdamOutler said:
All you need to do is install Samsung drivers again or switch USB ports. The LibUSB Zadig drivers are installed on a single USB port. No need to uninstall anything at all. Heimdall drivers are only installed to the USB port you had the device plugged into when you installed the drivers.
A better option would be to dual boot into Linux and One-Click just works every time.
It sounds like you are using a bad cable. Try using Heimdall one-click with a good cable. It works every time.
Click to expand...
Click to collapse
That works if you don't have to jumble things around to switch USB ports and/or your computer is set up for dual boot the other option would be to run a virtual disk that runs linux
cobraa783 said:
That works if you don't have to jumble things around to switch USB ports and/or your computer is set up for dual boot the other option would be to run a virtual disk that runs linux
Click to expand...
Click to collapse
No. The device is controlled by windows in a virtual machine.
AdamOutler said:
No. The device is controlled by windows in a virtual machine.
Click to expand...
Click to collapse
Actually ur windows didn't even need drivers for the device ur using in a vm
cobraa783 said:
Actually ur windows didn't even need drivers for the device ur using in a vm
Click to expand...
Click to collapse
It does. Otherwise it will be an unrecognized device and you can't connect it to the VM.
just wanted to chime in here and verify. had a similar problem with odin not working after using heimdall.. used another usb port and odin now sees my infuse.. no problems. thanks guys
Also, wanna say that, for some reason, I had better luck using different version of Odin. Can't remember exactly but I think 1.7 worked & 1.8 didn't - not at PC right now to verify.
Sent from my SAMSUNG-SGH-I997 using XDA
once you install zadig...driver installation for heimdall, it takes over that 1 port.
you can always go back to that 1 port or designate it for heimdall.
odin will not be usable for that port unless you re install samsung drivers again.
I have an (old -6yrs) pc with 1 usb same cord ($1) and 1 usb back port...same 1 for 6 months with heimdall - never had to mess with anything else...successful restore everytime...
use what you're comfortable with.
save that 1 configuration as your rescue if possible.
This topic was as close as I could find to my issue... Heimdall One-Click Kernel...
First of all, let me say that I appreciate all the work everyone has done on the Infuse forums. It has expanded my knowledge by leaps and bounds just by reading for about 5 hours today. I know this will be a long post, and I apologize. I am just trying to show that I have done everything (so far) that is within my ability to try.
I inherited a "mostly working" (sound doesn't work at all) AT&T Infuse 4G, and am trying to install CWM and root the bugger in order to use it on WiFi as a mini tablet. I Do Not have a SIM card for it (I am on SIMple Mobile, not AT&T), and do not plan to use it for calls (already have a phone for that). It was already running UCLB3, but I wasn't sure if that was how the phone came, or if it had been upgraded from Froyo at some point with or without the bootloaders. I had planned to play with this phone some and maybe try out some Jelly Bean since my T-Mobile G2x has lost most of the wonderful devs that it had.
First, I used the Settings>Privacy>Factory Data Reset to clear all the information on my phone and my internal SD card. I made sure that Java was the latest version on my laptop and DL'd qkster's [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3. I spent the next 2 hours reading and re-reading the OP and all the resulting posts to make sure I had a firm grasp on how to do everything. I first booted into stock Recovery and did another Factory Reset from there and also cleared Cache. I booted into Download mode on the Infuse 4G and ran Heimdall One-Click. Installed the Heimdall driver, closed all programs, rebooted the computer, went back into Heimdall One-Click, put the phone back into Download mode, clicked Flash, waited for phone to reboot, turned phone off, went back into Download mode and flashed again, this time with BL checked.
This entire process went off without a hitch. Phone boots into GB and all is glittery gold. It's when I come to the next step in the thread that I started having the issue. Again, from an overabundance of caution, I made sure that I read the thread again, absorbing all the information pertinent to loading the Kernels from One-Click. Deciding to try InfuZen-A16 Kernel, I downloaded it and ran it just as I had the previous One-Click. Opened the .jar, booted the phone to Download mode, clicked Flash, and let the phone reboot. Uh oh. Samsung splash screen is staying on my screen now...
Maybe it just needs a while to process. Left the phone plugged in so it wouldn't lose too much battery life and went and did some more reading on the forums. 5 minutes, still Samsung screen. 10 minutes, still Samsung... No biggie, I'll just read some more. Maybe this is just a longer process than I thought. 30 minutes later, still Samsung. Okay, something must be wrong... Hold down power button to shut it off. 3 minutes holding button, still on. Battery pull...
3-button workout for recovery... Nope, no such luck, still showing the persistent Samsung screen. Back to Heimdall One-Click for recovery to UCBL3. That works. Back into stock recovery. Again, Factory Reset, clear Cache. Download mode, try again. Flash InfuZen-A16 Kernel a couple more times (flashing back to Stock between attempts), using a different USB cable and different USB ports, but still same thing each time, leaving the phone for at least 15 minutes on the Samsung splash screen to see if it moves anywhere. I then tried the ENTROPY512's 4.4.2012 kernel, hoping for different results. Same thing. Tried it 2 more times with different cables and different ports. Each time that I flashed back to Stock, it worked on each USB port and cable I was trying, so I don't "think" it could be the cables or the ports that are causing the issue.
Any help is greatly appreciated. It is my understanding that to get root on UCLB3 and above, I need to have CWM installed, but other than Heimdall One-Click Kernels, the only way to get CWM on a phone is by having it already Rooted. If I am erroneous in this understanding, please point it out and I will happily do my due diligence to fix my own problem.
Thanks in advance for any help anyone gives me.
The custom GB kernels for infuse start a file system conversion immediately upon reboot (from rfs to ext4). If your sound was working, you would hear a robotic female voice providing status updates. This process typically takes no more than 20 minutes to complete, usually less.
If the phone is just sitting there at a samsung logo, try leaving it longer to see if it completes and boots the phone OS.
If it still doesn't work, try the jscott30 Odin package instead:
http://forum.xda-developers.com/showthread.php?p=27286083
Here are the custom kernels in Odin packages:
http://forum.xda-developers.com/showthread.php?t=1698367
IMPORTANT: If you try Odin, use a different USB port than the one you set up for Heimdall. Reserve the Heimdall port for only Heimdall flashing.
For Heimdall, make sure you are using this one (kernels in posts 2 & 3):
http://forum.xda-developers.com/showthread.php?t=1524081
(looks like you are based on the files you referenced above)
Regardless, make sure your USB connection is 100% reliable and you do not interrupt the flashing process - otherwise you may brick the phone.
Thanks for the reply, Zen. I'll try it again when I get home and just let it run for at least an hour.
I have a minor aversion to using Odin, just because it is closed source as opposed to open source for Heimdall. I will take it under advisement, though.
Thanks for all the words of wisdom you give to all the members of xda. :thumbup:
*edit* - Well, decided to just let it ride for over an hour. Took an extended nap after I got home, so after flashing, the phone has been on the Samsung screen for well over 3 hours. I am going to presume that the Heimdall kernel install packages are a no go for me. I will read up on Odin and give it a shot. Thanks again. - *edit*
Sent from my LG-P999 using xda app-developers app
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.
Let's see, where shall I begin?
Got my phone back from my girlfriend since she bought the Nexus 4. Battery was extremely swollen and because of that, the phone basically didn't work. Constantly restarting, couldn't use data, etc... Bought a new battery and decided that I would get a nice fresh ROM installed to get this thing running nice again. It has been on Valhalla for about a year now, and I tried to jump straight to the ICS milestone ROM that I saw in Development. Unfortunately, I didn't know of the new CWM that I was supposed to have, which results in a nice little brick. Frozen at the Boot screen. I was able to get it back into download mode with the volume buttons+cable method and luckily Odin recognized it. I installed a really old KD1 Rom that I had which appears to be all the way back to Froyo.
Now that you are up to speed, the phone boots up fine and seems to be working, but nothing in CWM works at all. Everything fails to mount, which means I can't flash any zips to get off this ROM. To top that off, Odin stopped recognizing it in download mode after I installed that other ROM.
It's been too long since I have been on this phone, and within a couple hours of messing with it again, I can see that I have obviously fallen behind on the development. Any suggestions as to what I should do next? My goal is the get it up to the newest ROMs and see how well it runs. I have the Basic with a twist kernel and ICS milestone ROM ready to go, but no way to flash them.
Thank you to anyone who took the time to read this.
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
th3controller said:
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
Click to expand...
Click to collapse
I didn't even realize it was a Froyo rom, to be honest. I would go and search for a Gingerbread Rom, but the "All roms/rooting/FAQS....." sticky in the development section has been updated in such a long time. I decided to take my chances on that one instead of looking through tons of threads. Froyo was the only one I had for Odin at the moment unfortunately, and Odin was all that I could use.
Thank you so much for the help! This phone should be up and running again in no time!
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
th3controller said:
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
Click to expand...
Click to collapse
Just the Samsung Drivers? I'll try to find them all.
Well, looks like the guide isn't going to work very well for me. I got all the way up to installing drivers with zadig. Heimdall opened automatically like I installed it before ( I may have, it has been forever), but zadig never did. I had to trick it into opening. Once it did open, my phone never shows up in the list of devices as a Samsung device. It only shows up as "Unknown device" and there are no drivers for it to install.
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
TwitchyEye said:
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
Click to expand...
Click to collapse
Finally got around to working on my phone again. Unfortunately, I am unable to follow the guide how I was supposed to. Fortunately, on the other hand, it appears that I successfully got it to flash gingerbread.
Here were my steps to get it work if you want a laugh. My computer didn't like the procedure that the guide had.
1. Update Java, download file, place file into C drive, etc... Everything up to this point worked fine.
2. Open command prompt and execute command. (This is where it all went crazy)
3. Command says false. (instead of opening Zadig, my computer immediately opened Heimdall. So how do I install drivers?)
4. Went to Heimdall help menu and selected install, which froze heimdall completely. Upon Heimdall crashing, Zadig opens.
5. Open Zadig. All drivers are uninstalled, but my device can't be found in the list. (Right after here is where to told me to reboot.)
6. Reboot. Windows keeps automatically installing drivers and I can't do anything about it, so I just uninstall them and try again.
7. Same process. Command prompt, heimdall opens early, crash heimdall, open Zadig, SUCCESSFULLY install drivers.
8. Command prompt again, because that is my only way of getting heimdall open
9. Heimdall finds device, try to flash, but it fails.
10. Unplug phone, and plug in again. Heimdall finds it again.
11. Try to flash again, and success.
It was kind of a nightmare getting it to work, but it looks like it will fix it finally. Thanks for the help everyone!
Double-flashing with Heimdall seems fairly standard. When that happens, sometimes you don't actually have to unplug the phone again, just repeat the same flash-command and it should work the second time. If that doesn't work, reboot the phone, it should go to panic-download mode where it doesn't boot to launcher anymore, just shows the yellow exclamation mark screen, and there the flash should work.
Both my SGS4G and my wife's have done this since we first got them. Sometimes.