Possibly. You could try to remove the sim/sdcard/battery and leave it out for 5m or so. Then try to get back into DL mode with ONLY the battery
Did Kies kill my vibrant?
I reverted to stock rom via odin so that I could use kies to get the official update. It said the update was successfull but my phone never rebooted and its showing no signs of life. It wont turn on at all. Any idea how to fix it other than calling Samsung?
1 - 16 of 16 Posts
sim and sdcard where out the whole time.roman said:Possibly. You could try to remove the sim/sdcard/battery and leave it out for 5m or so. Then try to get back into DL mode with ONLY the battery
Yea, sounds like your outta luck =(
Main reason i never use kies.
Main reason i never use kies.
You might try the jig. team whiskey forum have a detailed description
Sent from my GT-I9000 using Tapatalk
Sent from my GT-I9000 using Tapatalk
I tried a jig. Didn't work. I took it into a T-Mobile store and they checked it out and ordered a replacement via warranty. Was shipped today and should be here Tuesday.
I was using kies so I could get the "official" update.Zach said:Yea, sounds like your outta luck =(
Main reason i never use kies.
I never use KIES, I removed that as soon as possible
Kies should be avoided at all costs, unless you do want to permanently lock your phone (pun intended). lol
Oh man, you are out of luck I'm afraid. I did the exact same thing about 3 months back. The good news is that if you bring it in, they will exchange it for a new one, the bad news is that it still sucks."miharkula said:I reverted to stock rom via odin so that I could use kies to get the official update. It said the update was successfull but my phone never rebooted and its showing no signs of life. It wont turn on at all. Any idea how to fix it other than calling Samsung?
I assume this phone was debricked or replaced via rma a long time ago, but one option to try is Heimdall OneClick UnBrick. It can debrick a phone even without using a JIG as a friend of mine proved to me. Ubuntu is a free download and can be run from a flash drive, so its something to try I think.
Well GREAT! I am using the Kies drivers right now and flashing my Vibrant back to stock as we speak, what am I gonna do! And it seems to be hanging at factory.fs.rfs. Oh boy.
If they cause bricks, then why was I linked to those drivers, you should definitely remove that or change it.
EDIT: Tried to restart the phone after it was still hung there after a very long time, and now its completely dead...great.
If they cause bricks, then why was I linked to those drivers, you should definitely remove that or change it.
EDIT: Tried to restart the phone after it was still hung there after a very long time, and now its completely dead...great.
What are you talking about and who are you talking to??? This person already fixed or replaced his phone a long time ago and the Samsung drivers do not cause bricks, the Kies end-user software does, which is a well known fact. The OP did not provide any drivers that I can see so why should he change links that do not even exist in the first place? Your post is very strange and needs further clarification of what you are talking about, because after reading the thread again your comment makes ZERO sense.Zemnexx said:Well GREAT! I am using the Kies drivers right now and flashing my Vibrant back to stock as we speak, what am I gonna do! And it seems to be hanging at factory.fs.rfs. Oh boy.
If they cause bricks, then why was I linked to those drivers, you should definitely remove that or change it.
EDIT: Tried to restart the phone after it was still hung there after a very long time, and now its completely dead...great.
Yeah, I misunderstood the OP and what he was referring to, I thought he was referring to the Kies drivers you download to your computer to communicate with the device. I meant that I was linked to those drivers while going through the sticky thread guide. I thought he meant that the drivers he installed to his computers is what caused the brick. So yes, you were correct, my post made zero sense.SkOrPn said:
What are you talking about and who are you talking to??? This person already fixed or replaced his phone a long time ago and the Samsung drivers do not cause bricks, the Kies end-user software does, which is a well known fact. The OP did not provide any drivers that I can see so why should he change links that do not even exist in the first place? Your post is very strange and needs further clarification of what you are talking about, because after reading the thread again your comment makes ZERO sense.
Ok, good enough then. Who really knows what causes bricks anyway? Momentary lapse in computer-phone concentration perhaps? LOL... I have seen many many many phones get bricked by Kies, so I have never once even tempted myself to use it.Zemnexx said:Yeah, I misunderstood the OP and what he was referring to, I thought he was referring to the Kies drivers you download to your computer to communicate with the device. I meant that I was linked to those drivers while going through the sticky thread guide. I thought he meant that the drivers he installed to his computers is what caused the brick. So yes, you were correct, my post made zero sense.
1 - 16 of 16 Posts
- This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Android OS Forum
A forum community dedicated to Android phone owners and enthusiasts. Come join the discussion about applications, recovery, developments, styles, reviews, accessories, classifieds, and more for Unbuntu, Google Nexus, HTC, Motorola, Samsung or other Android models!
Full Forum Listing
Explore Our Forums
Recommended Communities
