My vibrant is stuck on the vibrant logo after I tried to use the one click unroot program. The only solution I found after two days searching on the net, is to use odin. The first problem is that my phone is locked, so I can't use the vol up+down+power button combo to get into recovery or download mode.
Now comes the issue, I want to use adb to reboot the phone, but adb can't see my device. After installing the samsung USB Drivers, I see that the adb drivers are not installed (The drivers for this device are not installed. (Code 28)), and even when I try to manually install them from the SDK drivers (I checked the "include subfolders) it says that it can't find them.
I have windows 7 x64
Anyone have suggestions to how to install the adb drivers and make the adb see my device?
Can you get into download mode? Have you tried to Odin back to stock? If you want to set up ADB type ADB for dummies in search and you should find everything you need.
Here is the link from the sticky thread for help with drivers:
http://forum.xda-developers.com/showthread.php?t=728929
I just figured out a neat trick to get phone to work even if it's stuck on the vibrant screen.
Just connect it to the usb, wait until the grey battery picture appears.
After 5 seconds, take the battery out and put it right back, (leave usb in) and wait again. Do it once more, until you see that the battery picture turns green. After that take the battery out and unplug the usb, and turn the phone on.
It should work now.
The thing is that, next time you turn the phone off and on, it would be stuck again, so do something to fix it like odin.
That how it worked for me.
And about the adb driver problem, I just pointed manually the driver update to the "USB Drivers" that TGA_Gunnman posted here (I can't post link. just search usb drivers here in the forum) and after that adb worked like a charm, rebooted instantly to download mode - it's crucial for those like me that have hardware locked phones.
The thing is, that all the other posts say to point it to the sdk drivers, but that dosen't work.
Good luck to all others.
installing the samsung drivers and installing adb are two different things. the samsung drivers should install normal by double clicking the driver package (you may have to still tell windows where to look). installing adb is simply downloading the sdk, however, if you want adb to work everywhere (instead of just the sdk/tools folder) you need to put the sdk/tools folder in your path.
then 'adb devices' should show your device in win powershell, but will only work if you are in the sdk/tools folder or have added it to your environment variables.
Related
hello gyes!
i'm in great jeopardy...............
spent 2 days searching-> only 1 thing & its-> how to install a 3 button download mode on my sgs gt i9000.
I crashed my froyo 2.2.1 while debranding it.so i revert it back to eclair 2.1 but now kies won't recognise it for updates
i downloaded every thing i needed-> .pit file\gingerbread file\odin3 v 1.82\the adb a k a sdk what ever.(sdk manager)....even played in commandpromt.1 click root\unroot. decorder update with kies
but all seems worthless unless i don't get the 3 button download mode
i tried all XDA forums-tutorials.....but nothing to come in way of sucess.
so please give some suggestions & links that could save my babe
You really should try to get download mode working, as it will make your life MUCH easier, but if all you need download-mode for is flashing some stock images which Odin, you can force your phone into download mode using ADB.
You said you've installed the SDK, so I'll take your word for it. What you need to do is the following:
1. Locate adb.exe. Open windows explorer, point it to C: and search for adb.exe.
2. Connect your phone with USB Debugging enabled. This setting needs to be enabled before you connect it to your PC (Settings/Applications/Development)
3. If this is the first time you are using USB debugging, you might have to wait for drivers to install.
4. Open a command prompt
5. Change the directory to the one where adb was found in step 1.
6. Type "adb devices" and press enter in your command prompt.
7. Verify that adb actually runs and that your device is listed.
8. Type "adb reboot download".
Your phone should now be in download mode and you can flash things trough Odin.
Beware though: Without the 3-button download mode accessible, you will have much fewer options for recovering your phone later should you mess anything up in the flashing process.
Hope this helps.
Try out the home made JIG
As explaind in thread 819551 if you have a soldering iron, you can put together a micro usb jig to force the phone into download mode.
Yuotube has some clips to show you how to make it. Looks simple, though I haven't tried it personally.
Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!
Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program
Thanks for the info!
I am away until tomorrow evening. I will try it then.
Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!
it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver
Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.
Sorry, noob here. Please help!
My computer keeps on installing the wrong drivers everytime I plug in my Nexus 7. I don't know how to stop it.
When my tablet is in bootloader mode, Windows will try to install a bootloader interface driver that does nothing.
I have already:
- Went to Devices and Printers Installation settings and clicked on never install driver software
- Went to gpedit.msc and enabled: Prevent Installation of Devices not described by other policy settings,
So now my policy will block the auto install. But when I try to manually try to try Naked Drivers, it'll say it can't find any drivers.
When my tablet is in normal mode, the adb drivers comes back on.
I'm just trying to boot to recovery so I can install a new rom through the command prompt. Current rom is too unstable to do anything, new rom is already on the internal sdcard.
If any has any solutions, please let me know.
Thanks!
It sounds like you did things to prevent driver installation. But you need to install the correct drivers for things to work. Getting the correct drivers installed seems to be the biggest issue people have in being able to connect to a pc or use adb or fastboot. I know I installed the drivers from a root toolkit, installed rsd lite, android sdk, motohelper, etc. and still couldn't connect. Then I installed the pda.net app on the N7 and installed pda.net for android on my pc. Finally it worked and I can reliably connect to the pc, use adb and fastboot, and recognize the N7.
If all you are trying to do is get into recovery, why don't you just power off, hold the vol down and power until the screen comes on, use the up vol to change the menu to recovery, then hit the power button to enter recovery. Then you can wipe and flash. I hope I got those commands right. I'm using cwm recovery and I can get there like that. Usually, I just use Rom Manager to boot into recovery.
pdanet was what worked for me as well. none of the others did.
Sent from my Nexus 7
Thanks guys. that did the trick!
Sent from my Nexus 7 using xda app-developers app
I tried rooting my G2 using this guide, and seem to have f'ed up somehow.
The phone now won't boot (stuck at the "LG" screen, with rainbow LED), and I can't get into download mode.
The strange thing is that I do get into recovery mode, but it seems to exit abruptly. When I try to recover (by selecting yes twice), the Android recovery icon shows up for a couple of seconds, but then it goes back to the "LG" boot screen again.
I would be grateful for any help.
I've tried connecting to a computer with Ubuntu, as per this guide: http://forum.xda-developers.com/showthread.php?t=2582142, but I was unable to mount the phone.
It does show up in the device manager in Windows, under "Portable Devices".
I've disovered that the guide I followed for rooting was for G3 phones (and the G2 D805). I'm guessing this could be part of my problem.
But the guide said that I should be safe, since I had Lollipop. The Download mode should be able to save me if anything went wrong. But alas.
Before starting the rooting process I had the latest Lollipop update from LG (it was performing poorly, that's why I wanted to install a custom ROM).
Is it possible to save this phone? I'll probably look for a good deal on the 5X at Black Friday if I can't fix the G2, but I'd rather keep this phone working for a while anyway.
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
no connecting to pc
FonderPrism said:
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
Click to expand...
Click to collapse
bro install adb driver or qualcomm driver.
link:https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0
kalpesh patil said:
bro install adb driver or qualcomm driver.
link:
Click to expand...
Click to collapse
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
FonderPrism said:
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
Click to expand...
Click to collapse
bro i think ur phone is hard bricked.
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.
chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.