Related
First off, I want to thank the wonderful amount of knowledge and help here at XDA! Not to be impolite to anyone else, but through all my searching, I have yet to find anything like this forum (and I come from a number of forums); but none have had quite the caliber of kind, knowledgeable, and often humorous: people. So thank you all. Also, another disclaimer is that I've only been on Android for about a month and half, so please bear with me as I might (and probably) misuse vernacular and/or might not completely understand some of the technical lingo' (at least the first time through, but I have spent much time here reading through help guides and threads).
Alright, here's the problem: I cannot get a computer to recognize the Vibrant. Installed all the drivers I have found thus far, followed a number of guides from here at xda, and have tried a number of different computers (two Win7 machines, a Vista, and even two XP machines); all of which recognize my personal Vibrant without a hick-up. Here is perhaps the biggest, and main, problem: the computers/odin won't even recognize it in Download Mode. That is what is stumping me..
If you do not care to know about how I got to where I am, please jump to the 'Question:' part.
Here is the back-story:
I bought a used Samsung Vibrant that came with the JI6 build. This was the second vibrant I had purchased as it was for my sister; and for the most part (other than it being horribly slow on the 'stock' build) it was running, and perfectly functioning.
However, I did notice that it was not able to connect it to a computer; usb debugging, mounting sd, and all the guides I found for troubleshooting just didn't seem to do the trick. Still no connection to the pc. I eventually educated myself on Download and Recovery mode, both of which I could execute without really any problems.
But since I wanted to run a faster OS (And I had already successfully flashed my personal Vibrant to Froyo (Build 21VE) (Here)) I decided to flash my sister's vibrant as well. And since I was unable to connect via usb to use odin to flash to the JFD build (per highly suggested here on xda), I used a nandroid image to flash the stock JFD build from Samsung (I can't find the link at the moment, but it was here from the xda forum). All went well, I was on JFD. I then used the above link to flash the Froyo21VE build via clockwordMod; again, it went smoothly. Only one problem persisted at this point: the wifi would not work.
My brother had experienced a similar issue with his Vibrant's wifi a few weeks previous, but had resolved it by flashing a different Froyo build. Naturally I thought I might do the same. This is where things went South.. Perhaps I was multi-tasking too much at the time, or possibly I just wasn't paying attention, but after a quick google search I found this Froyo build here on xda: [ROM] Froyo (RS)JP5 - "K9" [25/11/2010]. Moved it onto the internal sd card; flashed via clockworkMod; and then it froze on its boot-up after installation. Not cool..
Unfortunately, I was not aware that the build was for the Galaxy S i9000 rather than a Vibrant branded Galaxy; once realized though, my gut sank.. As now I am wondering if I completely tanked this Vibrant; or perhaps it had a problem from the bigging in that the usb wasn't connecting?
Question:
First and foremost, is there an 'advanced' way of connecting via usb from a computer, or some other way of doing it? I have tried numerous usb cables (as I've read a couple different people were having success with that) on several different computers (all of which, though, seem to be working perfectly on my personal vibrant, just not this one). Or is there a special driver that allows for just the 'Download Mode' on the Vibrant to communicate to the pc? But from my understanding, it seems as though the 'download mode' is pretty much as basic as you can get, am I correct in that assumption? Additionally, would using the android sdk help at all? (Or again, doesn't it have to be able to be recognized from the computer first?)
And lastly, just in case I thought it wasn't complex, when I had a functioning OS on the Vibrant: when I plugged in the usb, the Vibrant would show that it recognizes the pc; I even could 'mount the sd', but the computer still wouldn't recognize it apart from a few times that it would show it as 'unknown device' and would not seem to load any drivers; and I was having difficulty locating the device in Device Manager. (But that only seemed to work when I had a functioning OS, now that it only can go into ClockworkMod or Download Mode, I have yet for the computer to acknowledge its presence)
Alright, there it is. Please let me know if I missed something, or if more information would be helpful. Again, I want to thank anyone who would be able to help me out, or give suggestions. I really am at a loss for ideas; and the past week of analyzation is hardly showing any signs of improvement.
Thanks for taking the time to read.
EDIT: it occurred to me that I didn't mention that I am unable to load any *.zip files while in ClockworkMod (thus being able to flash a different build). It continually gives a 'No File Found' or Error/Wrong command. I believe that was caused by the i9000 firmware messing up the file system on the Internal_sd, does that seem logical?
Have you installed kies from samsung? I tried installing just the drivers on my win 7 pc and they wouldn't take either. I then downloaded kies and installed and it seemed to properly install the needed drivers.
Sent from my Axura injected voodoo possessed Vibrant.
I believe I have installed it twice now, but I will try again. Thanks for the suggestion, I'm pretty much all ears at this point.
EDIT: Well I installed the Samsung Kies mini Apllication and it did its update thing and now I have v1.0.0.10104_1. Doesn't appear to have helped the drivers out..
Question: would anyone think that this particular Vibrant has a defective usb port? I realize that's a long-shot, as well as I would definitely not like hearing that.. but any thoughts?
shalom24 said:
I believe I have installed it twice now, but I will try again. Thanks for the suggestion, I'm pretty much all ears at this point.
EDIT: Well I installed the Samsung Kies mini Apllication and it did its update thing and now I have v1.0.0.10104_1. Doesn't appear to have helped the drivers out..
Question: would anyone think that this particular Vibrant has a defective usb port? I realize that's a long-shot, as well as I would definitely not like hearing that.. but any thoughts?
Click to expand...
Click to collapse
It appears that you have a defective USB port on the phone.
Do you have an access to a Linux box? If a current linux distro cannot see your phone via USB it will confirm the DOA USB port on the Vibrant.
Thanks for the reply lqaddict, although it's somewhat sad to hear.. Forgive my ignorance, but by 'Linux Box' you are referring to a Linux machine, correct? If so, then I do not have access to one. Again, forgive me for not knowing, but would running linux (possibly via a bootable Linux cd) on a computer be equivalent?
Since I purchased it used (through Craigslist about three weeks ago (which he said he had purchased two weeks previous)) do you think I might be able to retrieve the receipt from the original owner and perhaps Samsung would be able to help with some sort of warranty?
Thanks again for your response.
EDIT: Well I am running Live CD of Ubuntu 10.10 on another one of my pc's, however, I'm not quite sure I know how to 'check' to see if usb port is properly functioning (sorry I'm not very familiar with Linux, but I imagine I will become increasingly more accustomed to it in the near future). Any ideas for trying out connectivity on Linux?
shalom24 said:
Thanks for the reply lqaddict, although it's somewhat sad to hear.. Forgive my ignorance, but by 'Linux Box' you are referring to a Linux machine, correct? If so, then I do not have access to one. Again, forgive me for not knowing, but would running linux (possibly via a bootable Linux cd) on a computer be equivalent?
Since I purchased it used (through Craigslist about three weeks ago (which he said he had purchased two weeks previous)) do you think I might be able to retrieve the receipt from the original owner and perhaps Samsung would be able to help with some sort of warranty?
Thanks again for your response.
EDIT: Well I am running Live CD of Ubuntu 10.10 on another one of my pc's, however, I'm not quite sure I know how to 'check' to see if usb port is properly functioning (sorry I'm not very familiar with Linux, but I imagine I will become increasingly more accustomed to it in the near future). Any ideas for trying out connectivity on Linux?
Click to expand...
Click to collapse
When you connect your phone via USB, does a USB connected symbol show up on your phone? Does the battery start charging?
You can issue the following command in the terminal window - should be in Applications->Accessories on Ubuntu (it resembles MS-DOS window under Windows OS)
Code:
lsusb
If the Samsung device shows up the USB port on your phone should be working, if however it is not showing up you might have a bigger problem with your phone
Thanks again lqaddict, I'll give it a try..
EDIT: Alright, to answer your first question: yes when I plugged it in while off, it does give the battery charging icon, as well as it does give juice to the battery.
Additionally, I ran the suggested "lsusb" in the Linux Terminal while the Vibrant was in Download Mode, and I didn't seem to get too much in the way of interest of the Vibrant except this line:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
Would that possibly be the Vibrant? Does "Linux Foundation" refer to a Linux device? Then again, I just ran it another time without the Vibrant plugged in, and it yielded the same results.. So, most likely.. dead usb port?? Or perhaps is this just a weird phenomena? Thanks again, for all the suggestions and comments; hopefully I'll be able to one day return the favours to others here on xda.
Sorry, looks like you have a faulty usb port on your phone
Sent from my Nero powered Vibrant
Thanks for helping troubleshoot that, however unfortunate it was to hear... Perhaps one last question though, as I would like to make sure I 'cover my basis', so to speak, would anyone have suggestions as to what to do when I talk to Samsung? Or would anyone know what the procedure is like; I have dealt with a faulty iPone 3gs before and basically all I did was wait for the replacement in the mail, and ship the faulty one in the same packaging. I realize I will need to contact them, but would anyone know what information they might need from me? (as in would it be a problem that I might not have an original receipt? (I contacted the seller about that, and have yet to hear back))
Simply put, while I have had Samsung products in the past (and have been for the most part very satisfied with said products); I would, however, like to make sure I don't mess something up within the warranty process for the Vibrant (at least in consideration that I wasn't the first purchaser; then again, I would hope that they would cover the 'basic' quality issues of their products for at least the normal 90 days.. but what do I know..).
Whatever the case my be, I greatly appreciate the help I've received here; if for nothing else, perhaps it will be useful in someone else's mishaps in their Android journey. Thanks again, and I will be exceedingly grateful for any further suggestions on the matter.
shalom24 said:
Thanks for helping troubleshoot that, however unfortunate it was to hear... Perhaps one last question though, as I would like to make sure I 'cover my basis', so to speak, would anyone have suggestions as to what to do when I talk to Samsung? Or would anyone know what the procedure is like; I have dealt with a faulty iPone 3gs before and basically all I did was wait for the replacement in the mail, and ship the faulty one in the same packaging. I realize I will need to contact them, but would anyone know what information they might need from me? (as in would it be a problem that I might not have an original receipt? (I contacted the seller about that, and have yet to hear back))
Simply put, while I have had Samsung products in the past (and have been for the most part very satisfied with said products); I would, however, like to make sure I don't mess something up within the warranty process for the Vibrant (at least in consideration that I wasn't the first purchaser; then again, I would hope that they would cover the 'basic' quality issues of their products for at least the normal 90 days.. but what do I know..).
Whatever the case my be, I greatly appreciate the help I've received here; if for nothing else, perhaps it will be useful in someone else's mishaps in their Android journey. Thanks again, and I will be exceedingly grateful for any further suggestions on the matter.
Click to expand...
Click to collapse
Contact Samsung what have you got to lose? The phone comes with 1 year manufacturer warranty, and it has been on the market since mid July 2010, so it is not even 6 month old.
Yea, I don't mean to be too non-committal, I just don't want to mess up a warranty; if that makes any sense. And hopefully the ~210 people who have viewed this thread thus far will find a conclusion of the situation somewhat helpful. I'll update this thread once some of the dust settles.. I'm most definitely a fan of xda! Thanks for all the help everyone!
EDIT: Contacted Samsung, and after listening to the 'did you check this list' for about five minutes, I received a free shipping label and they said it was covered by the 'repair warranty'. I'm optimistic that something good will come of it...
EDIT_2:
Well, what do you know, just got the package/phone a little under an hour ago. First of all, compliments to Samsung! Fantastic communication and customer service! I really thought that the Vibrant was unrecoverable and that I would most likely have to pay for a new one; but I was wrong! Opened the sealed package with the original Vibrant (I knew it was mine since I had already but a BestSkinsEver skin on it) and plugged it into the computer at, Wohla!, Odin recognized, Windows/drivers recognized, and I'm up and rolling!
Thank you once again everyone for the comments and helpful input! And know that Samsung rocks! (I won't be going back with apple products anytime soon..)
so yesterday at the gym i dropped my phone a few feet down of the elyptical and unfortunatly the lcd inside started bleeding, the glass was fine, but the lcd was obviously damaged inside, so after reading a few things on here i took a shot in the dark at seeing if dell would replace my cell phone for me, i guess i was one of the lucky ones and im getting dispatched a new phone, my question is, am i able to restore my new phone with a nandroid backup of my old my phone that i have saved, like would the phone then just be identicle at that point, does it work like that? and what would my steps be on getting my phone back to where it is, tho i am familiar with QDL tool to a certain extent and do have the drivers set up on my laptop am i going to have to re-root it then i could restore from nandroid? any advice would be appreciated! thank you so much!
-Davey
That is very good for you. I wonder how much longer will we be able to get a replacement on damaged or a faulty Streak? . Whats up with Dell pulling the Streak totally from their catalog? Firstthere were onlinerumors that it was pulled for internal updates. Now the Dell.com site says "farewell Dell Streak 5, its been a long ride"' or something like that as its discontinued. Posted a question on their facebook page and still cant get an official comment.
Has anyone successfully done this??
Link: http://forum.xda-developers.com/showthread.php?t=1220181
I finally hard-bricked my Vibrant, and I'm wondering if this has been accomplished, instead of sending it to a specialist to JTAG it the traditional way!!
Im trying to see if I can resurrect it myself instead of losing it for a week!
And yes I'm aware of the One guy here in the states that does JTAGing, but Id be seriously outa work for a week as my phone is my work/life line, cuz I'm an Independent contractor, so its not about the money Id spend but the time down without a way to work/communicate, I haven't contacted TMO yet and told them it was hosed using the Kies method to upgrade it to Froyo. Wish I never had done that!! Should've known better, didn't see/read any post about the horrors of using Samsungs KIES program until it was too late!!!
I was trying to purge a SH 5.0 install that went bad, I flashed back to stock Eclair. Then went to Froyo, But thats when I developed a problem with boot looping after doing Froyo, so I tried the KIES program to go to "FROYO" and that's when It bricked!!!
Anyways its bricked hard, and I'm wondering if this has actually been done successfully!
And any tips that I might need to get the Heimdall Program to actually detect it thru the USB method, would be awesome! Even though it wont turn on!!
Link to the thread: http://forum.xda-developers.com/showthread.php?t=1220181
JTAG isn't a method that can be done through usb. If you had googled jtag, you would have found out that it is a physical port built into the motherboard of our phones. In fact most electronics have a jtag port.
*Joint Test Action Group**(*JTAG*) is the common name for what was later standardized as the*IEEE
1149.1**Standard Test Access Port and Boundary-Scan Architecture*. It was initially devised for testing*printed circuit boards*using*boundary scan and is still widely used for this application.
Today JTAG is also widely used for*IC*debug ports. In the embedded processor market, essentially all modern processors support JTAG when they have enough pins.*Embedded systems*development relies on*debuggers*talking to chips with JTAG to perform operations like*single stepping*and*breakpointing. Digital electronics products such as*cell phones
*or awireless access point
*generally have no other debug or test interfaces.
In order to flash your phone, it will have to be dismantled, and hooked up to the jtag box.
Beware of angry gingerbread man
Adamcooks, I read the entire squabble about this between you and RaverXX
I downloaded your one click as well!!
So can you give me some advice on how to get my phone to even simply turn on, WO the soldering involved using traditional method of JTAGing??? Mine wont power up or show any LED activity, nothing when plugged in or do anything using traditional methods known to work with "SOFTBRICKING"
I mean, it seems my Boot loader is corrupted, or the other file you suggested, when Raver and u were arguing!! If I could even get a faint indication of life from the phone, It could be brought back to DL, but a DL Jig, as well as all the other extensive methods to get it even to power on, let alone go into DL mode isnt working at all, after many, many try's!
Can your one-click program, with the proper BL's for my T959 Vibrant be acknowledged by either yours or Heimdall's Program, so as to even be able to flash this WO, Jtaging it, even if it wont even power up in any way to handshake with my lappy???
BTW, I'm not trying to start another **** storm, after what happened with RaverXX, but it seems some of the people who had the same scenario as I do, were successful, so I'm wondering between the 2 of you, how to approach and try this, I respect both ya'll's work and contributions, but for me the bottom line is to get my phone working once again, short of either#1 JTAGing it, or trying to go thru the painful experience of trying to get TMO to replace it with a new same model, because KIES fubar'd it!!
Anyway I wish you 2 guys could lay out the proper set of instructions as you suggested, along with the proper files or links, for us to try either his method or yours. I think its possible to resurrect these phones, this way short of physical damage, and as such!! IDT you 2 fellas would've put so much effort into this theory, if there wasn't some merit to it!
So I'm all ears and eyes to your suggestion of how to get my phone to even breath again, so I can go back to DL mode, and get her working again!!
But when nothing what so ever happens, no power up, no lights, no nothing occurs, it seems to me its bricked, even though you say a truly bricked phone , has physical hardware damage, which tech is prolly correct, however in this case, mine is software bricked very hard!!!! And for purposes of communication and clarity, Ill stick with bricked, If I knew the MB was fried and or damaged, Id simply order another one, and replace it, and power up the phone, and be done with this ordeal, but my corruption occurred during using the Samsung KIES program, regrettably!!
And I'm fairly certain that either the Boot loader file is corrupted or the file you say creates a black screen usually displaying the Pc-phone logo is done for, so again, should I try the command prompt instructions to fix that, or do I use your one-click, or go to ravers method ?? I asking legitimately, because I know your knowledge in these matters has merit!! Thanks for your reply!!
Unless he changed his account, that was a different Adam in that other thread. I still say try it, cant make things any worse.
Sent from my ZenDroid, meditating on the XDA App
I may give a sharp response sometimes, but an internet squabbler I am not. connextion(sp) has a motherboard cradle that contacts the correct pins to jtag flash, without causing any damage to your phone.
Have you tried the resistance jig? I think that skorpn is the one who makes them ( 301k ohm resistor plug into the usb port can force d/l mode if the bootloaders aren't borked)
these are the last two resorts in ng phone resurrection.
Beware of angry gingerbread man
Ya My mistake Sorry
Ya I got you mixed up with another developer who has a very similar handle, so many apologies, however I wasn't flaming you anyway, shape or form, just apologizing for the mistaken ID
BTW Is the skorp resistance Jig a completely different animal from the DL Jig Tech Mobile sells doing the same result, in other words is it able to bring a phone like mine in the condition it is, into DL mode??? I saw the Skorp design, it just seems to me, its the same thing I already have from Tech Mobiles design. Accomplishing the same thing, but for phones that actually power on in some way shape or form, light off etc!!
Anyway thanks for your input, and effort, I'm still sorting all the info on everybody's suggestions and methods, short of JTaging it!!! Gonna make a move on a procedure here soon, this evening!!
Hi all. I have the SGH-i777 S2. It took a hit direct onto the concrete. The screen is cracked, but it appears that the bottom keys are lighting up when I press the power button. It's been rooted with CyanogenMod 9. I never could get DropBear SSH server to work right. At this point, I've tried installing the full Samsung USB drivers direct from Samsung's site (the one that Windows is the only option) as well as Kies from Samsung and others.
What I'd like to know is, since I can't see the phone's menu settings to turn on USB debugging and, thus, pull contacts, notes and other items off of it, I need to know what you guys would do from this point. There are some contacts and information within Notes that are critical to me so I don't mind buying another phone to cannibalize the hardware if need be. I was told the digitizer is toast. I've already bought the AT&T S4 Active and have been using that for the past couple of weeks so that I can use something in the interim as portable internet is critical for my job.
Any/all feedback is more than welcome.
Unless your are very good with this type of mechanical/electrical work, I would suggest you send it to a good shop for repair. From what I've read on the forums here, there may be a couple of good ones, but I could only recommend Mobile Tech Videos, as the owner Josh has a very good reputation here. You might give them a call to see what you can find out.
This is probably nothing since Creepy is da man, but without ADB can you just connect to your computer as USB storage and pull files from there? I'm not sure where the notes program you're using stores its data, but I didn't think it would bring too much shame upon myself to suggest it.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 4
A while ago I took advantage of a Verizon deal (big mistake). I got a tablet for a roommate as well as myself. We had a falling out, he moved away and changed his number, contact info, everything... and the tablet was returned to me..... factory reset.
The tablet wants the original Google Account to sign in before it will initiate any setup. No way past this point.
I've contacted several different Verizon and Google tech supports and QTASUN for help always to be referred to the next company (it's not our fault, etc). Over the past 6 months trying for a solution within Warranty, i'm giving up. :crying:
(Verizon - We just sell the tablet
Google - It's a Hardware safety, it's designed that way
QTASUN - It's software security, ^)
I've asked Verizon stores and techs from different locations about flashing the Tablet for me and some I even have to explain what 'flashing' is and was told 'we don't do that'. Another associate told me 'it would require a level '5' tech on site to flash it, however it's 'against the rules' anyway.'
Please help. I'm paying for a Tablet I am unable to even use, and it's physically in perfect condition. Near new.
I don't know the first thing to prepare to flash anything, however I'm not completely illiterate when it comes to computers. I only want to be able to use the tablet... don't care so much about OEM unlocking and removing bloatware (although nice option). Any help will be greatly appreciated. TY
-Very tired and disappointed Verizon customer.
Look up bypass Google frp lock. I managed to get past the screen where it asks for the previous Google account on an LG X Power I found in the street. It had been driven over but I figured out the only thing damaged was the battery. So after I replaced the battery, I did a factory reset and it asked for my old login which I obviously didn't know. There wasn't a guide that directly helped me but I managed to create my own way of getting passed it with all the different methodologies I looked up. The first thing you should find out is if you can get chrome to open up during the initial set up. It usually involves going into accessibility and finding a link to some terms and conditions page or something, which in turn opens up chrome.