The vibrant was running CM7 for a few hours until I noticed that it wouldn't charge via USB. It wouldn't charge from the wall outlet nor when plugged into a computer (the computer did recognize that it existed but didn't have the drivers for it).
I tried to recover it but then the process failed and it was stuck in boot menu. The vibrant only loads to the first splash screen. I can put it into download mode however ODIN doesn't recognize it. Nothing shows up. I've installed the Samsung Vibrant drivers and I've tried Kies Mini however Windows 7 32bit won't recognize the device. How can I install the stock ROM if Odin doesn't recognize it?
if u can get into dl mode but cant get pc to recognize ur phone use aio toolbox or get a usb jig that may help!!
or since your on CM7 ..try the Nexus S drivers and see if it recognizes it.
Could it be that maybe USB Debugging is turned off? At this point there is no way I can boot up to turn it on.
All of the drivers I install end up not being installed correctly, I get errors.
jmcghee1973 said:
or since your on CM7 ..try the Nexus S drivers and see if it recognizes it.
Click to expand...
Click to collapse
This. You can find them here.
CyanogenMod 7 for Vibrant Q&A
Just press Ctr+F and search ''Nexus S'' and you will find the instructions on how to get them.
I'm having some difficulty. I don't have a phone under my device drivers. All that's showing up is PCI Simple Communications Controller. I click on update driver and direct it to the SDK. Nothing happens.
Edit:
Downloaded the Intel ME: Management Engine Interface driver for the PCI problem. It seems to be fixed. Now my phone is showing up as unknown device. Working on it some more.
I was following the exact step-by-step guide here:
http://forum.xda-developers.com/showthread.php?t=1196808
and after I flashed the kernel downgrade, unplugged USB, power up the phone and immediately plug in after the vibrate, I never got the message in the next step that says "Connected Device: X10", and the "Root" button on the flash tool never became available.
Now my phone is permanently stuck at the "Sony Ericsson" black screen, it won't even turn off. I checked device manager and there are 2 hardware without any drivers. one of them says "Modem Device on High Definition Audio Bus", and the other says "SM bus controller". Does this have anything to do with my problem?
I'm running Win XP SP3, I tried to let it automatically search for drivers but it didn't find anything. I went to:
http://forum.xda-developers.com/showthread.php?t=1193066
and downloaded those drivers, but have no idea how to use them. Tried to use device manager to look for drivers in the downloaded folder and it doesn't recognize anything.
What now? At this point I don't care if I can still root my x10 or not, I just want to fix it so I can use it again. I tried PC Companion but it won't even recognize my phone, keeps telling me to enable USB when I can't even get past the SE screen.
You should try flashing a new ftf firmware bundle, then try the steps again.
ok finally fixed... had to use a friend's computer who is running win7 and actually automatically installed the drivers. everything went as explained on the guide... I guess the guide is not win xp friendly then
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
johnny12times said:
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
Click to expand...
Click to collapse
Sorry. That did not work. It just doesn't recognize it in ODIN when in download mode. My computer doesn't even see it. But it does say "Safely Remove Hardware" -- "SAMSUNG USB Composite Device"
Sounds really odd. Do you have any roms you can try reflashing from recovery?
Using XDA premium, you should be too!
depaer said:
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Click to expand...
Click to collapse
Sounds like you used the wrong odin files. if your screen is showing a galaxy s 4g logo then you must have mistakenly flashed a galaxy s 4g odin/heimdall package. on the back of your phone what is the model number. What on earth is JFS? ive heard of JFD which is the stock firmware that the phone shipped with.
If you flashed the wrong bootloader you are more or less stuck between a rock and a hardplace and will require a jtag. now the fact that teh screen does turn on is a good thing.
You need to keep trying to get it into download mode maybe try using a jig. Once youve gotten it into download mode try every single usb port you can find on your pc. When i need to odin i need to use one of my usb ports on the rear io panel none of the others will work. Once you get odin running and recognizing your device use the files posted in my sig as the odin files. any others and i cant help you cuz i dont know what your source is. Odin should be able to recover your device if it is still booting to the splash screen.
If for whatever reason you cant boot into download mode but can get into recovery here is what you do: make sure you have the android SDK installed (dont know what that is go here: http://developer.android.com/sdk/index.html and follow their directions) then open up command prompt while in recovery type the following command: adb reboot bootloader this should put you into download mode. If nothing ive mentioned works you may require a JTAG there is a company called MOBILETECHVIDEOS (http://mobiletechvideos.mybigcommerce.com/) that has a JTAG service.
Good luck
-Cheers
Hi
My Acer A100 does not boot and gets stuck at android(written not logo). It was having HC.
I tried Hard reset, but no use
Tried copying update.zip file in formatted sdcard and tried to power on the tablet with volume buttons pressed, it shows reading file from update.zip file and then when android logo shows up and starts, it looks if its going to flash from update.zip file, but then after 30% scan, it shows warning sign and aborts progress bar.
I never unlocked bootloader or never upgraded from HC.
Can not be detected when connected to windows 7 home premium laptop or desktop. Tried installing USB driver on laptop from acer, but it gives an error while trying to install and after that it says successfully installed. On Windows XP, USB driver gets installed and MTP device id detected but does not show any drive in my computer.
Please advise if this tablet can come back to life. This has been a good tablet for last 5 months..
Thanks
Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.