The drivers have been tricky with the Amazon Fire to say the least, and this seems to be because windows recognizes the driver as unsigned. To get around this issue, you will need to temporarily enable installation of drivers that are unsigned.
First go to Settings>Update and recovery.
from there click on advanced startup.
Your PC should say "please wait" then pull up a menu.
In this menu click on "troubleshoot" then click "start up settings"
Your PC will now restart
The PC will now boot into Startup Settings. Click 7 on your keyboard to disable driver enforcement then hit enter.
Your PC will restart once more.
Now your fire drivers should install as they are intended. Allowing installation of unsigned drivers can be a security risk, so once you have completed this process and installed the drivers reboot your PC and windows will automatically turn Driver Signature Verification on once again.
its smart to uninstall the fire drivers and reinstall them using the driver signature mode to make sure theyre installed correctly.
its also worth noting that in my case, the device needed a different driver from the downloaded for each mode (normal/on, fastboot, sideload), there is another thread on here for this but Ill add it here just in case someone else stumbles upon this first.
when installing the drivers in device signature mode, youll want to put the device in all 3 states while in signature mode to make sure you dont run into any problems trying to return the device to stock or moving on from fastboot etc. ( i did this, it was scary..)
1. when installing the drivers in signature mode youll come across 3 different drivers to choose from, the first driver "android ABD interface" is for when the device is in normal/on mode.
2. youll need to next boot the device into fastboot mode, i used the rootjunky amazon fire supertool and booted the device to fastboot, then disconnect and reconnected it to my pc and chose the second adb usb driver "android bootloader interface"
2. after installing that driver disconnect the device from the computer and power it down. power the device into the recovery mode by shutting it down then holding volume down and power (when holding the device in portrait orientation the volume down button is the one to the left) and navigate to the option that requires you to connect your device to a PC to load software (sorry i cant remember what option it is) it will say something like its waiting for a connection, connect the device to the PC and install the final driver "android composite ADB interface" now every facet of operation should have a driver, reboot your PC out of driver signature mode and if you were in the same boat as me, you should be able to sideload back to the android os, and flash roms or whatever else.
Related
I too, had issues at first. I fixed them by a few easy steps.. (well, not so easy to figure out at first.)
1) Uninstall your device drivers for your phone. You can do this in Windows 7 by plugging your device in and going to Control Panel > Hardware > Devices and uninstalling the SAMSUNG_android. Once this is done, unplug it and plug it back in. An attempt to install the drivers will be made and the ADB one will most likely fail. Double click the SAMSUNG_android to bring up the properties for this device. Click the 'Hardware' tab. Click the 'SAMSUNG Android Composite ADB Interface' and hit properties. Then Driver > 'Update Driver'. Then select 'Browse my computer for driver software'
2) Download the drivers here: mediafire.com/?t9koyznu5ryygyt and extract them somewhere. Point the driver installation wizard to these drivers with 'Browse'. Hit 'Next.
Congratulations, your drivers are installed! Have fun rooting your Vibrant. I recommend the one click rooter, although it is just a copy of the update.zip and reboot function.
I guess I'm confused. What do drivers have to do with booting into recovery?
Power off
Hold Down Vol +/- and power at the same time.
Walla you have Recovery
----------------------------------------------------------
If your talking about Download Mode
Install your drivers
Plug in USB to PC, but not phone
Turn off Phone
Hold Vol +/-
Plug in USB to phone
Hold +/- for a second
Release Vol
Walla you are in Download Mode
That wasn't exactly working for me and others. I couldn't get into that mode by holding the buttons. The method I listed above managed to get me into recovery via adb, however.
Double helix
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.
I am sure I have properly installed usb driver for my nexus 7, since I have unlocked and rooted my device.
When I reboot my device to bootloader, my PC detected a new device connected, but fail to recognize it.
Also, I can't do anything when I am in fastboot mode, e.g. no effect for pressing power, vol + or vol - button.
Now, I want to return to 4.1.2 stock image, but I cannot do that on fastboot mode.
Any solution/ work arround to save my device??
Looks like drivers got screwy.. Install PDANet and let it install the drivers for your device..
http://junefabrics.com/android/download.php
One your drivers are up to snuff and you can access your device when in the bootloader again you can remove PDANet and the usb drivers will stay in place.
styckx said:
Looks like drivers got screwy.. Install PDANet and let it install the drivers for your device..
http://junefabrics.com/android/download.php
One your drivers are up to snuff and you can access your device when in the bootloader again you can remove PDANet and the usb drivers will stay in place.
Click to expand...
Click to collapse
I re-installed driver by PDANet, still I can connect Nexus 7 on normal state, but not in bootloader/ fastboot mode.
I am guessing the fastboot is dead and not related to usb driver issue.
Since there is no any response when I am pressing the button. The fastboot mode is hanged.
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
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.