Related
So after searching the vast horizons of XDA I haven't found an answer that really helped me. Nor have I found someone with this distinct issue. I have an unlocked Samsung Vibrant. I have not rooted it. I updated to J16 with that P.O.S. Kies Mini a few months ago. I hadn't noticed this problem until the last month or so but I haven't had time to sit down and curse at my computer long enough or offer supplications to Google until now. I've just been using Awesome Drop to get what few files I wanted onto my phone. I've had enough of that now. And...I also want to update it to Froyo but I can't do that if I can't get my computer to see my phone. I'm running a Toshiba Satellite A205 with Windows Vista 32bit.
I have checked the drivers and as far as I can tell, I'm using the right ones. I downloaded Kies Mini again today (I deleted it after I was finished with J16 because I wanted it as far away from me as possible) and it seemed to say something about downloading drivers as well. I tried plugging in my phone. Nothing new. So, I went in search of drivers again. I have searched and tried a few different ones but nothing has solved my problem.
The phone charges fine from my laptop. It hooks up immediately and charges without a problem. Unfortunately, my phone seems to regard the PC as a complex wall-wart. Debugging on/off, USB Settings on Mass Storage, Kies, or Ask on connection, it doesn't matter. It doesn't give me the option to "mount" as it has in the past. It doesn't do anything except charge. I've seen some people say it's a problem with their cables (I've only got one at the moment) but since my phone charges fine, how can it be a problem with the cable?
Only thing I hadn't tried was a factory reset. So, I sucked it up and tried that. Nope. No change. At this point I'm wondering if it's a hardware problem, not a software problem.
I'm out of ideas. Anybody else?
Well you can always root it, install ROM manager from the market, install clockwork recovery, download the ROM you want to install in flashable .zip format from your phone and flash away. A new ROM might fix your USB issue.
If you don't want to root it, see if you can get into download mode, and flash a new ROM using Odin. I would check with a different cable first, just to be sure that's not the problem though. It might save you some headaches.
If it was me, I would just root it and load a custom 2.2 ROM. I would also get Titanium Backup from the market and backup my apps and would do a nandroid backup from recovery before flashing anything new just to be on the safe side.
There's some good info on how to do most of that in this sticky post.
http://forum.xda-developers.com/showthread.php?t=849028
I have been perusing these forums for weeks, trying to discover a way to return to stock or at least get my root access recognized (no longer have su in system/bin). For quite some time I have been unable to get my laptop to recognize my fascinate/USB (after dozens of reinstalls drivers etc). It may be the computer, or phone, or both. At this point, I want to just get it back to stock, so I can send it back to Verizon since I am one of those people with the weird call issues. But I digress..
If I boot into recovery (via 3 finger salute) is there any file that I can use to start the process towards regaining my root access or going back to a stock ROM. My permissions are all screwy, and at this point I am terrified to do anything, since ODIN is out of the question.
Thanks before hand.
Firmware - 2.2.1
Baseband -S:i500.04 V.DL09
Kernel - 2.6.32.9
Build Number - SCH-I500.DL30
melzilla said:
I have been perusing these forums for weeks, trying to discover a way to return to stock or at least get my root access recognized (no longer have su in system/bin). For quite some time I have been unable to get my laptop to recognize my fascinate/USB (after dozens of reinstalls drivers etc). It may be the computer, or phone, or both. At this point, I want to just get it back to stock, so I can send it back to Verizon since I am one of those people with the weird call issues. But I digress..
If I boot into recovery (via 3 finger salute) is there any file that I can use to start the process towards regaining my root access or going back to a stock ROM. My permissions are all screwy, and at this point I am terrified to do anything, since ODIN is out of the question.
Thanks before hand.
Firmware - 2.2.1
Baseband -S:i500.04 V.DL09
Kernel - 2.6.32.9
Build Number - SCH-I500.DL30
Click to expand...
Click to collapse
Do you have a custom recovery installed, or just the stock Samsung version? If ODIN is a no-go and you have the stock Samsung recovery in place, I'm not sure how much you can do here. Any chance of trying another computer to see if ODIN will work? In order to do what you want, ODIN, heimdall, or a non-OEM recovery is going to be required.
Does the phone at least go into Download mode if you pull the battery, hold VOL DOWN, and plug in the USB cable? If you can get that far, I think it's pretty likely that a different PC or perhaps even a different USB cable would be able to get you working with ODIN.
I have an eBay Fascinate I use for development with a broken USB port, and it's hella hard to get the thing working once it's been powered off. In that device's case, it *always* thinks a USB cable is connected, making a lot of things difficult to accomplish. To resurrect it with ODIN, I had to get it into Download mode using a wall plug adapter first (PC wouldn't work) with the battery IN, then move it over to the PC quickly and ODIN recognized it. It took more than one try to make this happen .. way more than one try ... but in the end I was victorious and it's been working great ever since. Moral: maybe try some other ways of getting it into Download mode and see if with luck the PC will recognize it long enough so you can flash it.
I suppose if push came to shove you could run the thing over
Have you downloaded your Samsung USB drivers as an Administrator on your computer? Also, there are some different methods for getting these drivers to work. One of which I had to use was going through PDANet. It just installs them differently and somehow they may work over the traditional installation.
Link: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
was messing around in cwm and formatted boot among other things i'm sure, because my phone wasn't able to be recognized by my pc due to what I believe was debugging not working... tried onecosmics ics and my debug just malfuntioned? Now I'm stuck at the Vibrant screen and although I can get into download without a problem, no computers recognize it... therefor I cannot odin. No CWM no nothing... just vibrant boot or download mode. Phones a year old, absolutely loved it and i messed up bad... If anyone can help me get her up and running through odin I will donate something to ya lol... Have all drivers needed just wont recognize... Geez I just can't leave things alone haha
thanks for reading and replying in advance
Make sure you are plugging the USB on the back end of your computer, closer to the motherboard. I never had any luck with ODIN when plugging into the front USB ports; seems not enough power goes to those.
Try a different version of ODIN. The link is available in a sticky around here somewhere. If you're entering download mode, all is not lost. I would try to click Start on ODIN just in case.
Try using the Toolbox. It has all the drivers, pit/tar files and Odin too. I use it all the time. I agree, if you can get anything to even show up on your screen, you are not "hard" bricked. Just have to find that sweet spot.
Remember that you don't have to have Download showing up on your screen, just a yellow COM box in Odin. Sometimes people forget that and freak out but I know you said it (the computer) doesn't recognize. Is this bc you are not seeing any Mass Storage devices? Just keep trying to get that little yellow box.
Edit:: Try to keep one thread on the subject so that you aren't getting confused.
I agree with the comments above.I recall going into DL mode and just hooking up the phone to the pc and it wasn't recognizing it but I flashed the 512 pit and it worked without the COM.
Try a different USB cable
You can always use linux, that's an option at this moment
I'm sorry for making two threads, didn't want people coming into the last thread and answering an old issue... I'm gonna keep trying...
I guess my days with the Vibrant are sadly over, although I can get into download mode, tried 2 cables, 3 computers... Can't get anything recognized or ODIN to work period... I'm 16 days past my tmobile warranty for the phone and they refuse to help me... onecosmics rom was the biggest mistake I made. I lost the ability to debug because of it, which is now my downfall. Nothing gets recognized and I believe it wont because debug is broken...
AIO couldn't help me... I would have much rather bricked my phone essentially than this because I would at least know where I stood and knew a Jig may work, this issue I'm having is just false hope... There are no answers anywhere that have a happy ending in my case, just threads that get left without a true method or answer, I have looked. I don't know if a Jig would work for a device that can boot in download mode but can't get recognized? I don't know anything, I just know I wish wouldn't have tried that rom and then lose my cool because of it.
We root and change ROMs because we can. We make our ****s faster or slower if we wish, i could run porn ,the newiest movies, dl songs.there is nothing better than freedom my bro
How about reinstalling the drivers while phone is connected to PC with Odin running.
And what buttons are you using to get into CWM?
I am using the standard 3 button combo for CWM cant get past vibrant logo just resets and does it again... I tried everything with odin no dice... Lol, it's my own damn fault truthfully lol... I was irresponsible in CWM due to a bit of anger and this is the result. shouldnt have formatted everything and reset. Dumb dumb dumb... especially after I knew debug was broke and disabled...
Yo are, you good finally
---------- Post added at 02:23 AM ---------- Previous post was at 02:16 AM ----------
YO if you can't fix it nOOOb,don't waste our time.I /They have gave u great advice.
---------- Post added at 02:27 AM ---------- Previous post was at 02:23 AM ----------
I say blow your phone up
Have you tried the jiggy yet? Last time, I was messing around with CWM and other ported GB and things didn't go well to the point where I got no download screen at all - just black screen after power up. Download finger combos didn't work anymore. I thought I hard brick it and about to be real brick. Since jiggy was only around $5, so I thought why not and got it off ebay (something like this one). After I hooked it in, boom I get download mode. I was so glad and didn't bother going forward anymore. I just load back old stock eclair rom with all the files in it then reload froyo.
If you odin it before, I assume driver still good. If it still good, IMO, you shouldn't try new driver. If you install other drivers over it, you can't tell if good one still there. Do you have another vibrant phone that you can hook in just too see odin and driver works good (in recognizing the phone)? This is to isolate issue if limited to your pc/odin/driver or limited to your phone only. If odin can recognize another vibrant phone, then everything on your pc is good and just need to get your phone in download mode. If your pc can't recognize other vibrant or other galaxy s phone, then it's likely your driver messed up and just need to uninstall all the sgs driver and reinstall only the one that worked for you before all this mess. I'm saying other galaxy s, because my pc was able to recognize my sister Verizon Fascinate phone and I can odin through it with the samsung driver i installed for my vibrant.
Just idea...
Thanks, but I have tried a million drivers to no avail lol... It's the ICS rom I flashed... It disabled my debug mode (although it said it was enabled). I believe with debug off, your phone is not recognized by ODIN... I can get into download mode, the only thing I need the Jig to do is get debug to be enabled lol, and I don't think it can do that?...
You ought to find another member near you and see if they can look at it. Sometimes another set of eyes can make a difference. You could also try mobiletechvideos.com. They do JTAG repairs (unbrick phones).
Penvision66 said:
Thanks, but I have tried a million drivers to no avail lol... It's the ICS rom I flashed... It disabled my debug mode (although it said it was enabled). I believe with debug off, your phone is not recognized by ODIN... I can get into download mode, the only thing I need the Jig to do is get debug to be enabled lol, and I don't think it can do that?...
Click to expand...
Click to collapse
Are you saying the "debug" inside the ICS rom? I don't think that matter, because I have ODINed mine to stock eclair rom before which has debug disabled by default if I remember correctly, then I just ODINed over other rom and it work...if that work, the debug setting shouldn't matter. Ok maybe driver...
If you strongly believe it is a driver, why not just try remove ALL samsung driver then start back with the one that work for you initially. Or use only driver from more trusted reliable site. Try one at a time. Or even reboot to safe mode and remove all the drivers. Don't install anything sparingly on your machines. Do you have another pc to try? Or have another friend with ODINed already installed w/ working samsung driver...so you reload eclair rom over it? You should have test it in VM or Virtualbox or Sandboxie.... If you can get into download mode, it should work...
Also make sure your machine is virus or spyware free. Spyware can affect other apps on your machine. If you haven't already have a good one, go to download.com and download Avast and Malwarebytes Antispyware. Then reboot into safe mode (F8), then scan virus and antispyware with both of the lattter programs. Anything it find, just delete them and keep scan until it finds 0 under safe mode. Then boot back normally and reinstall a good trusted samsung driver executable. That's what I would do if i were you.
This happened to me a while back onky thing different was my phone was working fine, but computer didnt recognize. Like others say COMPLETELY uninstall all samsung drivers, and I dont know if it will change anything for you but odin 1.7 and 1.1 didnt work for me but 1.3 was perfect, in other words try to get your hands on as many different odin files as possible, and if you have to heimdall has worked for me once before too
Sent from my SGH-T959 using XDA Premium App
Have you tried nexus s or galaxy nexus drivers yet? Your running ics you might need them....
Sent from my T959 using XDA App
update to the ICS drivers, they are in the i9000 cm thread, also then connect your phone open odin with admin privileges, install usbdeview, run it in admin privileges and uninstall any driver that starts when you plug the phone in, then un plug and plug back in your phone, should work
Hey guys just wanted to say thanks for all the help you provide on a daily basis, for all the people trying to unlock the potential in their phones. However with that being said I might have tried too hard and messed up my phones. I have a Samsung Vibrant SGH-T595 with 2.1 (update 1) updated officially by Samsung.
I rooted the phone, used clock work recovery mod and then downloaded and installed cyanogenmod 7.1 RC. However in the end I did not like so I tried to go back using my backed up copy created by clockwork mod. Doing this has now what you would call "soft bricked" my phone.
The phone is currently stuck on the Samsung boot screen when trying to power on the device. I am unable to put it into download mode via the three button setup, but I bought a USB jig and it sets it into download mode.
Everything seems great at this point but the Odin program is unable to recognize my phone. I have downloaded the official Samsung Kies, and 64 bit drivers as well for my windows 7 system but it is unable to detect my phone. I believe it maybe a defective USB issue with this phone but not sure since it can be charged through USB but I can't remember the last time I was able to connect it to the PC and transfer files via the USB cable.
My question is what else can I do other then sell it for scrap?
Try another USB cable and different ports. It will recognize it eventually.
As you have a windows 7 x64 bit version i guess Odin may need to be opened by giving Administrator permissions.
Try right clicking odin and click Run as administrator. I guess this should work.
Ran into this issue last night with my wife's Nook Color and moving some file and driver issues. Guess what? It was a bad cord. Actually used my Vibrant cord and it was instantly recognized. Yes sometimes it IS actually THAT simple.
I also suggest you go to the Dev section and download the AIO Toolbox (links are live again and don't forget the .Net files too). Uninstall the drivers you have installed and run to toolbox. It has all the correct drivers, pit/tar files and Odin. It is an invaluable tool.
Sidenote: Kies is notorious for hardbricking devices. You should stay away from it altogether.
Woodrube said:
Sidenote: Kies is notorious for hardbricking devices. You should stay away from it altogether.
Click to expand...
Click to collapse
Exactly. And that is how i tried updating my vibrant to froyo and ended up hard bricking it..
Yeah like someone in here said, download aio vibrant toolkit.. its a surefire way to know your drivers are good and right.. once youve ruled them out, try a diff usb port and cable (mentioned above as well). If nothing works, then you may begin to entertain the idea that your phone is in difficult position.
Probably not hardbricked tho, vibrants are very resilient; just keep trying.
Then ttheres jtag and unbrickable mod if youre absolutely sure lifes over
Sent from a cell tower to the XDA server to you.
Thanks guys I ended up recycling my phones cause nothing I did worked. I did try AIO toolbox got the drivers, tried different cables. My SG II is able to be recognized by odin 1.85 with no issues but not my vibrant. I believe it is an issue with the vibrant's usb port. I originally rooted it by doing the update.zip fix from its external sd card, did not use my usb cable at that time. My other vibrant is completely hard bricked since it wont power on with two different fully charged batteries. Anyway thanks again and next time I will research more before modding my phones.
Hey OP,
I did the same exact thing as you and soft bricked it in the same manner. Then when I tried to get Odin to recognize the phone it wouldn't with my Samsung cable. I thought I was out of luck but I went and bought a USB cable made my Belkin from Meijer and Odin recognized it! I looked at the Samsung cable and the Belkin cable and the black plastic inside the microUSB in the Belkin is thicker than the Samsung. I think that helps create a tighter contact between phone microUSB and the cable. I thought I was screwed like you and I fixed the issue with a new cable!! That simple
I used the Samsung Galaxy S II usb cable which looks like it has a very tight connection with the contacts like you said. Thanks anyway I will try that brand of cable, if I ever run into that issue.
My phone has the AT&T installed ICS, using odin and the ics .tar files my friend found for me the phone went through most of the process, and failed right at the end. It is now stuck at the recovery mode screen and I can't get Kies to recognize it at all, but it is recognized by both computers I have tried it on. I am really not sure what exactly I can do to get it back running again. I have tried to read all I can, but honestly I just don't know what I am doing enough to be sure of what to do next to recover it and if that relates to other problems people have had that have been solved.
I found this post about odin tips for better success - http://forum.xda-developers.com/showthread.php?t=1863995, but nothing I have seen has helped me from it. I found a few other occurrences of the same thing, but no solution within those threads, so I have no idea how even to proceed.
Any help is appreciated!
Make sure you reboot your pc, start odin, put phone in recovery, then connect usb cable. Make sure Kies isn't running in the background.
Agreed....
Run the process again........but you must ensure a clean working environment, and "NO" kies running while Odin is running....g
I did those steps multiple times on two separate computers. The first initially didn't even have kies installed, just the samsung drivers, but Odin failed repeatedly without even really starting. I restarted computers no USB hubs, tried different cables, different USB ports, nothing changes. Even the kies recovery doesn't recognize the phone at all, but it does still appear to the computers. I appreciate the responses, but what other steps can I take to ensure I am doing this properly? Could it potentially have been the tar file I have, and if so, can I just do the process from this screen, and where can I find the correct files if it wasn't include in one of the tons of threads on here about it?
722ish said:
I did those steps multiple times on two separate computers. The first initially didn't even have kies installed, just the samsung drivers, but Odin failed repeatedly without even really starting. I restarted computers no USB hubs, tried different cables, different USB ports, nothing changes. Even the kies recovery doesn't recognize the phone at all, but it does still appear to the computers. I appreciate the responses, but what other steps can I take to ensure I am doing this properly? Could it potentially have been the tar file I have, and if so, can I just do the process from this screen, and where can I find the correct files if it wasn't include in one of the tons of threads on here about it?
Click to expand...
Click to collapse
Go to samfirmware.com, and restore the device from the website direct...
It appears that you may have the download mode drivers, or a portion of them damaged or unreadable...( due in large part, to the fact that Odin "must" complete the flash process, then disconnect and reboot the device, in order for the flash to stick, and this didnt happen)
Be very careful here my friend, you are one step away from needing a JTAG repair....(BAD)
The website will push a recovery rom image to your device without the need for Odin drivers....and should give you a factory rom that functions correctly....
I dont have a direct link...(sorry) but this is the last attempt before the device is needing much deeper attention....g
Again..its samfirmware.com, or very near that....g
Edit: I'm very sorry you are having this issue, but we are here to help you through it.....So take a few deep breaths, and relax a bit, then hit the website I gave you..
then look in the tools section at the top, and go from there.....you got this....g
Ok, I will take a look at that when I get home! typical of me to push it to the limits. Thanks for the help, much appreciated!
722ish said:
Ok, I will take a look at that when I get home! typical of me to push it to the limits. Thanks for the help, much appreciated!
Click to expand...
Click to collapse
Always welcome my friend.......g