Related
Part 1)
I have a Kindle Fire HD 7"....
I have installed the new Stock-Rom 7.4.3 from Amazon...
After that, i have used KFFirstAide to root and install Google-Service and ADW-Launcher....
Everthing was fine....
The only problem was, that there were no wallpapers in ADW-Launcher Mode...
Then i used the stuff from this thread:
http://forum.xda-developers.com/showthread.php?t=2295750
After running the script i got some error messages in the script....
After that, my Kindle was bricked:
Switch on => 2 Times Kindle fire Logo then red triangle with two options => reboot or reset to factory defaults
I have chosen both, but nothing works
Part 2)
I have ordered a fastboot cable.....
If i plugin the cable (Kindle is off) it starts and i can read FASTBOOT Kindle Fire in the Tab-Display
If i try to revocer via KFFirstAide (Option 4 => Completely Restore the KFHD 7 7.2.3) , it ends up with : < waiting for device >
In Windows 8 64 Bit Device manager i can see the following Device with yellow triangle: Tate-PVT-08
If i try to install the Kinde Driver again it tells me, that they are allready installed....
Part 3)
crying
Can you help me pls ?
Sorry to see that my script bricked a device, would love to know why it did, because the main reason it would usually cause bricks was recently nullified by adding safeties in to prevent that. I suggest not using a PC with windows 8 on it to fix your kindle if possible. You just need to reflash the system partition like your trying to do. Windows 8 usually gives people trouble with drivers when they are unsigned or modified, that's why I suggest you use a PC with windows 7 or xp on it, because your kindle is completely fixable. :thumbup: if you have no other PC's I can always help you get it working again to the best of my abilities.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Reinstall driver(sometimes it helps), close all adb and cmd windows in task manager, and in cmd type adb kill-server, then try KFFirstAide
Sent from my Kindle Fire HD 7 using Tapatalk 4 Beta
---------- Post added at 01:04 PM ---------- Previous post was at 12:55 PM ----------
stunts513 said:
Sorry to see that my script bricked a device, would love to know why it did, because the main reason it would usually cause bricks was recently nullified by adding safeties in to prevent that. I suggest not using a PC with windows 8 on it to fix your kindle if possible. You just need to reflash the system partition like your trying to do. Windows 8 usually gives people trouble with drivers when they are unsigned or modified, that's why I suggest you use a PC with windows 7 or xp on it, because your kindle is completely fixable. :thumbup: if you have no other PC's I can always help you get it working again to the best of my abilities.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I didnt see it was windows 8, yes your best bet is redoing everything but like stunts513 says
Sent from my Kindle Fire HD 7 using Tapatalk 4 Beta
If i use KFFirstAide do i have to use the normal usb cable or the factory cable ?
i have heard, the factory cable is only to put the Fire into Fastboot mode, after the Fastboot Logo i have to use the normal cable, is this right ?
Not really I used fastboot cable for all fastboot command and when it rebooted into fastboot again I just removed cable and rebooted manually, but for adb commands use regular cable
If a woodchuck chucked wood and Chuck found out, would Chuck get mad at the woodchucks for chucking Chuck's wood?
Windows 7 also no Driver
See the attachments...
If have installed the android sdk
then the Kindle Fire USB Driver from there....
Then plugged in the Kindle with Fast Boot Cable and Normal Cable... but no working driver
Tried with Windows 7 64 Bit....
Can you give me a step by step instructions (noob compatible) incl. download links ?
System: Win 7 64 Bit
Device: Kindle Fire HD 7"
Astarioth said:
See the attachments...
If have installed the android sdk
then the Kindle Fire USB Driver from there....
Then plugged in the Kindle with Fast Boot Cable and Normal Cable... but no working driver
Tried with Windows 7 64 Bit....
Can you give me a step by step instructions (noob compatible) incl. download links ?
System: Win 7 64 Bit
Device: Kindle Fire HD 7"
Click to expand...
Click to collapse
well here's the modified google driver i made that should install with it. Just hit update driver on the tate-pvt device and point it to search in the folder that u extract from that zip file, it should do the rest by itself, minus asking are u sure u want to install a unsigned driver or something, just hit install anyway.
Edit: Trying to keep different version of my drivers from floating around on the forum, so use the link in my signature for the most up to date drivers.
Thanks to all
Kindle up again....
I had to install the driver with device manager, then show the device list, chose usb-devices then out of the manufacturer list kindle => kindle adb driver....
Then the Kindle was named Kindle in device manager and KFFirstAide did the rest....
yeehaaa
I tried installing a second bootloader with Fireflash, and apparently I missed a step. This led to my Kindle being stuck in a bootloop. I bought a fastboot cable from ebay, which arrived today. When I connect with that cable, the logo changes to the fastboot logo, but anything I try with the KFHD System.img Restore Tool doesn't work, neither does Kindle FirstAide.
With KFHD System.img Restore Tool, I always get < waiting for device >.
I'm not sure what to do now, can anyone suggest anything?
You need to install the drivers for the device, open your task manager and hit update driver on the Tate device with a triangle next to it, and download the drivers in my signature, then after extracting them, poi t the update drivers wizard to the place you extracted the drivers to and let them install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to install the drivers for the device, open your task manager and hit update driver on the Tate device with a triangle next to it, and download the drivers in my signature, then after extracting them, poi t the update drivers wizard to the place you extracted the drivers to and let them install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I just tried that, and the wizard tells me that the hash is not present in the catalog file?
Ah your on windows 8, you need to first disable driver signature enforcement, Google it and then try again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit /set testsigning on
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions
ENABLE_INTEGRITY_CHECKS bcdedit.exe -set TESTSIGNING OFF
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that.
http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
I have a Kindle Fire HD 7" I received new in Dec of 2012. Its worked well and I have never had any problem with it.. until.
Last week it was running real slow and I turned it off. When I turned it back on I only got the Kindle Fire screen after holding the button down for at least 20-30 second. It shows on the screen for maybe a minute and then goes black. It does not turn back on unless you hold it down a long time and release and then hold the button down 20-30 seconds again.
I ordered a fastbbot cable and the device enters fastboot mode when turned on and connected to my laptop; the fastboot screen stays up as long as cable i splugged in and even after until turned off. The computer makde the USB detected noise when the cable is plugged in/out. However, using the ADB tool doesn't seem to see the Kindle. I get this:
C:\SRT>adb shell su -c "reboot bootloader"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
After the first time I only get
error: device not found
I've tried 1.3.5, 1.30 and 1.2.3.
I have purchased spudgers in case I need to take it apart.
Anyone have any ideas?
Sounds like your fast boot drivers are not installed properly
Sent from my XT907 using xda app-developers app
Drivers?
mrkhigh said:
Sounds like your fast boot drivers are not installed properly
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok I found a post about the ADB interface and device manager. Downloaded and installed the drivers. I now see a ANDROID DEVICE and under that a ANDROID ADB INTERFACE. That interface driver has a driver date of 8/27/12, driver version 7.0.0.1 and has three driver files:
winusb.sys
wdfcoinstaller01009.dll
winusbcoinstaller2.dll
Still same result form that command. The Android device shows up and disapperas when the Kindle is plugged in.
Thanks for any help and the rapid response.
Color me confused.
Rane0000 said:
Ok I found a post about the ADB interface and device manager. Downloaded and installed the drivers. I now see a ANDROID DEVICE and under that a ANDROID ADB INTERFACE. That interface driver has a driver date of 8/27/12, driver version 7.0.0.1 and has three driver files:
winusb.sys
wdfcoinstaller01009.dll
winusbcoinstaller2.dll
Still same result form that command. The Android device shows up and disapperas when the Kindle is plugged in.
Thanks for any help and the rapid response.
Color me confused.
Click to expand...
Click to collapse
You need to update the drives in that short period that you can see the Kindle. What mark was stating was your fastboot drives. Those are what you need to get right to use fastboot commands. You are using a 7" KFHD 2012 correct?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Sorry; didn't type that right
LinearEquation said:
You need to update the drives in that short period that you can see the Kindle. What mark was stating was your fastboot drives. Those are what you need to get right to use fastboot commands. You are using a 7" KFHD 2012 correct?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No it stays connected and showing as an android ADK interface, it just disappears if i disconnect it. But I still get he errors when trying teh ADB command
Rane0000 said:
No it stays connected and showing as an android ADK interface, it just disappears if i disconnect it. But I still get he errors when trying teh ADB command
Click to expand...
Click to collapse
How about try what's been wrote already.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Guess I'm dense
LinearEquation said:
How about try what's been wrote already.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Guess I'm dense. the drivers are there on my laptop. Updating the driver form dev mgr doesn't find anything new. Running the command that suppose dto allow me to push a new image to it errors out.
What exactly are you referring to? Not trying to be dense but guess I am.
LinearEquation said:
You need to update the drives in that short period that you can see the Kindle. What mark was stating was your fastboot drives. Those are what you need to get right to use fastboot commands. You are using a 7" KFHD 2012 correct?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I have a 2012 Kindle Fire HD 7" .
Guess I;m too dense to figure this out. I'll keep reading.
Rane0000 said:
Yes I have a 2012 Kindle Fire HD 7" .
Guess I;m too dense to figure this out. I'll keep reading.
Click to expand...
Click to collapse
Your ADB drivers will not be recognized at all. This is different than most tablets. Only fastboot commands will at this time. Stop trying to figure out ADB at this pont. ADB is out of the picture at the moment. Only fastboot until the tablet is restored.
1) Get your tablet into fastboot mode.
2) Open a command window and type "fastboot -i 0x1949 getvar product" (with no quotes)
3) You should see product Tate-XXX-XX or something similar.
4) Close the command window.
5) Now use the system restore tool. Follow the OP. http://forum.xda-developers.com/showthread.php?t=1951254
6) Sometimes it does not work as bat tools are not perfect. Try a couple times and it will work.
7) Profit.
Thanks
LinearEquation said:
Your ADB drivers will not be recognized at all. This is different than most tablets. Only fastboot commands will at this time. Stop trying to figure out ADB at this pont. ADB is out of the picture at the moment. Only fastboot until the tablet is restored.
1) Get your tablet into fastboot mode.
2) Open a command window and type "fastboot -i 0x1949 getvar product" (with no quotes)
3) You should see product Tate-XXX-XX or something similar.
4) Close the command window.
5) Now use the system restore tool. Follow the OP. http://forum.xda-developers.com/showthread.php?t=1951254
6) Sometimes it does not work as bat tools are not perfect. Try a couple times and it will work.
7) Profit.
Click to expand...
Click to collapse
I appreciate you taking the time to write this; I'm dealing with a SCCM project right now and very time limited, which makes my kindle doing this at this time most frustrating. I hate to repay such kindness with more questions but I find I must.
When I did as you suggested I got the following (showed directory to indicate what version of files I am working with). Second command is from the OP comments from the the link you gave. I've rebooted and done it again, this time closing the command window between the GETVAR command and the ADD command with same result. Any ideas what my next step should be?
C:\SRT>dir
Volume in drive C is OSDisk
Volume Serial Number is 0E85-569D
Directory of C:\SRT
01/08/2014 07:55 PM <DIR> .
01/08/2014 07:55 PM <DIR> ..
11/13/2012 06:15 PM 815,104 adb.exe
11/13/2012 06:15 PM 96,256 AdbWinApi.dll
11/13/2012 06:15 PM 60,928 AdbWinUsbApi.dll
09/29/2012 11:50 AM 768,858 dx.jar
09/29/2012 11:50 AM 140,800 fastboot.exe
01/08/2014 07:55 PM <DIR> images
04/07/2013 06:47 AM 4,039 SR Tool.bat
6 File(s) 1,885,985 bytes
3 Dir(s) 210,208,550,912 bytes free
C:\SRT>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.001s
C:\SRT>adb shell su -c "reboot bootloader"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
follow
Rane0000 said:
I have a Kindle Fire HD 7" I received new in Dec of 2012. Its worked well and I have never had any problem with it.. until.
Last week it was running real slow and I turned it off. When I turned it back on I only got the Kindle Fire screen after holding the button down for at least 20-30 second. It shows on the screen for maybe a minute and then goes black. It does not turn back on unless you hold it down a long time and release and then hold the button down 20-30 seconds again.
I ordered a fastbbot cable and the device enters fastboot mode when turned on and connected to my laptop; the fastboot screen stays up as long as cable i splugged in and even after until turned off. The computer makde the USB detected noise when the cable is plugged in/out. However, using the ADB tool doesn't seem to see the Kindle. I get this:
C:\SRT>adb shell su -c "reboot bootloader"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
After the first time I only get
error: device not found
I've tried 1.3.5, 1.30 and 1.2.3.
I have purchased spudgers in case I need to take it apart.
Anyone have any ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2551661
Rane0000 said:
I appreciate you taking the time to write this; I'm dealing with a SCCM project right now and very time limited, which makes my kindle doing this at this time most frustrating. I hate to repay such kindness with more questions but I find I must.
When I did as you suggested I got the following (showed directory to indicate what version of files I am working with). Second command is from the OP comments from the the link you gave. I've rebooted and done it again, this time closing the command window between the GETVAR command and the ADD command with same result. Any ideas what my next step should be?
C:\SRT>dir
Volume in drive C is OSDisk
Volume Serial Number is 0E85-569D
Directory of C:\SRT
01/08/2014 07:55 PM <DIR> .
01/08/2014 07:55 PM <DIR> ..
11/13/2012 06:15 PM 815,104 adb.exe
11/13/2012 06:15 PM 96,256 AdbWinApi.dll
11/13/2012 06:15 PM 60,928 AdbWinUsbApi.dll
09/29/2012 11:50 AM 768,858 dx.jar
09/29/2012 11:50 AM 140,800 fastboot.exe
01/08/2014 07:55 PM <DIR> images
04/07/2013 06:47 AM 4,039 SR Tool.bat
6 File(s) 1,885,985 bytes
3 Dir(s) 210,208,550,912 bytes free
C:\SRT>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.001s
C:\SRT>adb shell su -c "reboot bootloader"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
I don't see the images being pushed.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Trying
LinearEquation said:
I don't see the images being pushed.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran the SR Tool even though the previous step gave an error (adb shell su -c "reboot bootloader"). I tried the clear cahe and userdata first. Afterwards the Kindle Fire logo was animated but no other change (never loaded even after 1/2 hour) and then tried pushing an image (option 2) which it said succeeded, but I get nothing on the screen but the logo. I'm going to try the latest SRT, not the 1.2.3 (which seemed to match up with my kindle best) and see if I can get it to work form that. At this point its kinda worthless and don't get the red triangle at any time.
Rane0000 said:
I ran the SR Tool even though the previous step gave an error (adb shell su -c "reboot bootloader"). I tried the clear cahe and userdata first. Afterwards the Kindle Fire logo was animated but no other change (never loaded even after 1/2 hour) and then tried pushing an image (option 2) which it said succeeded, but I get nothing on the screen but the logo. I'm going to try the latest SRT, not the 1.2.3 (which seemed to match up with my kindle best) and see if I can get it to work form that. At this point its kinda worthless and don't get the red triangle at any time.
Click to expand...
Click to collapse
\well I ran the latest SRT tool and selected "restore-factory recovery". I went through the process in under 10 seconds. I toook it out of fastboot, restarted it got the animated logo and then the red triangle and option to restore to factory specs. After about 20 minutes the progress bar was complete but it has not restarted and is just sitting there, now for an hour plus.
I would try kindle fire first aid, some have more luck using its restore feature then people that use SRT.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hey i have some problem regarding accessories can you go accessories section and solve my prob
It looks like the computer recognizes the device. You won't have adb access while in fastboot mode. Have you tried simply using the fastboot reboot command?
Sent from my KFSOWI using xda app-developers app
So I have the same issue up to now. I read tons of thread around here. Tried several ways to fix my Kindle but no luck. at one Point i had root twrp and now i have nothing. My kindle is stuck on the logo screen with no animation. I can't even get it to fastboot or anything. I can just shut it down but when I power it back up it just gets stuck on lo the white/yellow logo. My computer can't read it. tried installing driver and nothing. Tried the commands "fastboot -i 0x1949 getvar product" but just stays on "waiting for device".
What else can I do? thanks
If you don't see the blue logo then you will need a fastboot cable to get into fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If you don't see the blue logo then you will need a fastboot cable to get into fastboot mode.
Click to expand...
Click to collapse
No there is no Blue logo. Just the white/red or yellow logo.. I have a fastboot cable but it wont read it.
My Kindle Fire HD 7 is bricked... When I put the fastboot cable in it goes into fastboot mode. However it is not being detected on my PC and I have the ADB drives installed and I am using the KFHD SRT 1.3.5.. When I select option 1 it just says < waiting for device > FOREVER... I need help ASAP!
AidenOwns said:
My Kindle Fire HD 7 is bricked... When I put the fastboot cable in it goes into fastboot mode. However it is not being detected on my PC and I have the ADB drives installed and I am using the KFHD SRT 1.3.5.. When I select option 1 it just says < waiting for device > FOREVER... I need help ASAP!
Click to expand...
Click to collapse
Try using fastboot -i 0x1949 getvar product and then plug it in. Otherwise use Ubuntu
SafinWasi said:
Try using fastboot -i 0x1949 getvar product and then plug it in. Otherwise use Ubuntu
Click to expand...
Click to collapse
Do I use it on a regular command prompt?
SafinWasi said:
Try using fastboot -i 0x1949 getvar product and then plug it in. Otherwise use Ubuntu
Click to expand...
Click to collapse
Nvm I tried it on command prompt and it said unknown command (I did it at the adb file place) And when I did it KFHD SRT it just closes the command prompt... Even tho it closes it I still tried and I didnt work.. Can you tell me how to do it on ubuntu
AidenOwns said:
Nvm I tried it on command prompt and it said unknown command (I did it at the adb file place) And when I did it KFHD SRT it just closes the command prompt... Even tho it closes it I still tried and I didnt work.. Can you tell me how to do it on ubuntu
Click to expand...
Click to collapse
I meant boot into an Ubuntu live CD,try the command. And you should have the android SDK installed
Sent from my device running CyanogenMod 11
AidenOwns said:
My Kindle Fire HD 7 is bricked... When I put the fastboot cable in it goes into fastboot mode. However it is not being detected on my PC and I have the ADB drives installed and I am using the KFHD SRT 1.3.5.. When I select option 1 it just says < waiting for device > FOREVER... I need help ASAP!
Click to expand...
Click to collapse
Hi, please wait for at least 15 minutes. It is quite slow so just leave the kindle for a while.
SafinWasi said:
I meant boot into an Ubuntu live CD,try the command. And you should have the android SDK installed
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Could you give me like a full tutorial? I do not know how to boot into ubuntu..
AidenOwns said:
Could you give me like a full tutorial? I do not know how to boot into ubuntu..
Click to expand...
Click to collapse
It should not take 15 minutes for your device to be recognized. Are you running Ubuntu? Or are you running Windows 7? Or what's your OS? Your using a fastboot cord which uses fastboot commands and requires the .exe files in inside SRT to run unless you download sdk and set the tools folders in your path.
Make sure you're in fastboot.
Now open a command prompt (you must be using the admin profile of the computer) type
"fastboot -i 0x1949 getvar product"
In a few seconds you should see you device on the computer screen. If not then check your drivers.
If your drivers are not being recognized, see this post http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
It should not take 15 minutes for your device to be recognized. Are you running Ubuntu? Or are you running Windows 7? Or what's your OS? Your using a fastboot cord which uses fastboot commands and requires the .exe files in inside SRT to run unless you download sdk and set the tools folders in your path.
Make sure you're in fastboot.
Now open a command prompt (you must be using the admin profile of the computer) type
"fastboot -i 0x1949 getvar product"
In a few seconds you should see you device on the computer screen. If not then check your drivers.
If your drivers are not being recognized, see this post http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Windows 8.1 and I dont know anything about ubuntu and when I plug it in it says USB device not reginized. I already tried the command prompt and I didnt work also...
AidenOwns said:
Windows 8.1 and I dont know anything about ubuntu and when I plug it in it says USB device not reginized. I already tried the command prompt and I didnt work also...
Click to expand...
Click to collapse
Disable your Windows driver security enforcement first http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html then proceed to use the drivers in stunts signature.
Edit: Here are the drivers http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Disable your Windows driver security enforcement first http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html then proceed to use the drivers in stunts signature.
Edit: Here are the drivers http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
I disabled it and Downloaded the usb driver file... Im not that great with files so could you tell me how to install the drivers at there is no .exe file??
AidenOwns said:
I disabled it and Downloaded the usb driver file... Im not that great with files so could you tell me how to install the drivers at there is no .exe file??
Click to expand...
Click to collapse
The drivers are USB drivers that are in my post above. You don't want .exe for this install. So simply install the drivers in the device manager so your tablet will be recognized. Then move forward from there.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The drivers are USB drivers that are in my post above. You don't want .exe for this install. So simply install the drivers in the device manager so your tablet will be recognized. Then move forward from there.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Sorry if I keep asking questions but how do I install it in the device manager??
LinearEquation said:
The drivers are USB drivers that are in my post above. You don't want .exe for this install. So simply install the drivers in the device manager so your tablet will be recognized. Then move forward from there.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Im sorry I dont know more about this stuff.. But how do I install it in the device manager could you give me like a tutorial or something?
AidenOwns said:
Im sorry I dont know more about this stuff.. But how do I install it in the device manager could you give me like a tutorial or something?
Click to expand...
Click to collapse
http://pcsupport.about.com/od/windows-8/a/update-drivers-windows-8.htm
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
http://pcsupport.about.com/od/windows-8/a/update-drivers-windows-8.htm
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Which device thing do I update and which file do I select?
AidenOwns said:
Which device thing do I update and which file do I select?
Click to expand...
Click to collapse
With your tablet hooked to the PC you'll look in the device manager for a device with a yellow triangle by it. Right click on it and manually install the drivers. You will point to the folder containing all the items in the screens not, not just a single file in the folder.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
With your tablet hooked to the PC you'll look in the device manager for a device with a yellow triangle by it. Right click on it and manually install the drivers. You will point to the folder containing all the items in the screens not, not just a single file in the folder.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
This happens
AidenOwns said:
This happens
Click to expand...
Click to collapse
You're getting close. Did you verify that Window driver security enforcement is disabled? Also you must install manually, don't click the option for Windows to find and install. Make sure you're actually logged into the admin profile of your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
You're getting close. Did you verify that Window driver security enforcement is disabled? Also you must install manually, don't click the option for Windows to find and install. Make sure you're actually logged into the admin profile of your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
I disabled it again, went to the device thingy, went to the usb driver path tried the usb driver file and it did the same thing....
I'm attempting to flash android M on my nexus 6. I've installed the proper drivers from google, after checking in device manager it says the proper drivers are installed. When I enter "adb devices" into the terminal nothing shows up in the list. I've searched through forums and tried the universal adb installer which isn't compatible with Windows8x64, so I used the 15 second installer which worked but didn't change the result. Am I doing anything wrong?
Sent from my Nexus 6 using Tapatalk
semenick96 said:
I'm attempting to flash android M on my nexus 6. I've installed the proper drivers from google, after checking in device manager it says the proper drivers are installed. When I enter "adb devices" into the terminal nothing shows up in the list. I've searched through forums and tried the universal adb installer which isn't compatible with Windows8x64, so I used the 15 second installer which worked but didn't change the result. Am I doing anything wrong?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Are you using the usb cable that came with your phone? That's the only one that will allow my PC to recognize my N6.
Yes I am
Sent from my Nexus 6 using Tapatalk
I use wug's toolkit which includes easy setup for adb and has worked with both Windows 7 and Windows 10. You might try that.
Otherwise, you didn't say whether your device is recognized by the computer when you plug it in. Windows should recognize and try to install drivers for the device automatically when plugged in via USB. If it's not, there's probably something wrong with the cord you're using. If it is recognized, then it might be the drivers of you might not have debugging enabled on your phone.
Sent from my Nexus 6 using XDA Free mobile app
The computer recognizes the phone and USB debugging is enabled
Sent from my Nexus 6 using Tapatalk
Forget about adb since you don't use it for flashing anyway. Boot into the bootloader.and type "fastboot devices". That's all that matters. Check drivers and device manager in bootloader too.
Uninstall the device if you have to and set up as per my thread.. Nexus 6 general > sticky roll-up thread > adb and fastboot.
danarama said:
Forget about adb since you don't use it for flashing anyway. Boot into the bootloader.and type "fastboot devices". That's all that matters. Check drivers and device manager in bootloader too.
Uninstall the device if you have to and set up as per my thread.. Nexus 6 general > sticky roll-up thread > adb and fastboot.
Click to expand...
Click to collapse
I followed your guide and restarted my windows 8 computer accordingly. When I open the command window and type "fastboot devices" it says that is not recognized as an internal or external command, operable program or batch file
Sent from my Nexus 6 using Tapatalk
semenick96 said:
I followed your guide and restarted my windows 8 computer accordingly. When I open the command window and type "fastboot devices" it says that is not recognized as an internal or external command, operable program or batch file
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That means you didn't do the environment variables correctly or it didn't take after the reboot.
Confirm the location you have fastboot in is the location in environment variables.
danarama said:
That means you didn't do the environment variables correctly or it didn't take after the reboot.
Confirm the location you have fastboot in is the location in environment variables.
Click to expand...
Click to collapse
How do I check the location of fastboot?
Sent from my Nexus 6 using Tapatalk
semenick96 said:
How do I check the location of fastboot?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What part of my thread did you follow? How did you put fastboot on your.computer?
danarama said:
What part of my thread did you follow? How did you put fastboot on your.computer?
Click to expand...
Click to collapse
Is that the platform-tools? I'm sorry if these are stupid questions! I'm still learning aha
Sent from my Nexus 6 using Tapatalk
semenick96 said:
Is that the platform-tools? I'm sorry if these are stupid questions! I'm still learning aha
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, if you followed my thread and installed the sdk, the fastboot.exe should be in there. The full path is mentioned in my thread. Go.and check that and if it is, go onto the next step about environment variables.. Remember, the variable must be the location of fastboot and MUST start with ;
To be honest, I cheat and simply drop adb and fastboot into c:\windows\system32 as that is already and environment variable.
danarama said:
Yes, if you followed my thread and installed the sdk, the fastboot.exe should be in there. The full path is mentioned in my thread. Go.and check that and if it is, go onto the next step about environment variables.. Remember, the variable must be the location of fastboot and MUST start with ;
To be honest, I cheat and simply drop adb and fastboot into c:\windows\system32 as that is already and environment variable.
Click to expand...
Click to collapse
I redid all of the steps, but my computer is taking a long time to do the restart. Is that normal?
Sent from my Nexus 6 using Tapatalk
semenick96 said:
I redid all of the steps, but my computer is taking a long time to do the restart. Is that normal?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No.
danarama said:
No.
Click to expand...
Click to collapse
Alright, I'll look into it. Thanks for all the help!
Sent from my Nexus 6 using Tapatalk