Database Develop

Help- Accidental No OS on Kindle Fire HD7

Hello all.
Was tinkering around with my KF- And accidentally wiped everything from my internal storage and system. When it boots up I get the blue KF logo and it stays stuck there- Can't boot into recovery.
ADB doesnt recognize it.
Have a fastboot cable.
How do I atleast push files to it /boot into recovery??
Many thanks.

To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.

SilverRoxas said:
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
Click to expand...
Click to collapse
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.

LinearEquation said:
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
Click to expand...
Click to collapse
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.

SilverRoxas said:
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
Click to expand...
Click to collapse
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.

LinearEquation said:
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
Click to expand...
Click to collapse
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?

SilverRoxas said:
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
Click to expand...
Click to collapse
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.

LinearEquation said:
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
Click to expand...
Click to collapse
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.

SilverRoxas said:
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
Click to expand...
Click to collapse
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
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
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).

SilverRoxas said:
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
Click to expand...
Click to collapse
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
Is adb still recognized in you device drivers?
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, my Kindle is still recognized.

i dont os on my kindle fire hd 7
I am having a mare with my kindle fire hd 7
It all starrted when anything google related kept crashing.
I tried to find solutions to the problem but no joy.
I then tried to install a different update to cyanogenmod nightly software but i then had a major problem with not being able to turn on my wifi.
I went into Twrp and tried to restore to my previous software but when my kindle re-booted i got stuck with a flashing teamwin logo
After trawling for days i managed to get out of that but im now in a situation where i dont have any OS on my kindle.
I have followed instructions on how to push files onto my kindle but despiote finding some files on my sdcard i am unable to reboot past the blue and white Kindlefire logo.
I have tried using the kindle un-brick java option but no joy either
I would really appreciate some help solving this proble as it is really driving me crazy.
I can still access twrp and i can access bootloader to get the orange and white fastboot logo.
If someone can help guide me through how i can get my kindle working again id really appreciate it
cheers
JJ

Might be able to help.
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.

Hey Danny101
Danny101 said:
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Click to expand...
Click to collapse
Thanx for your response.
Sorry its taken me a while to reply but have had loads going one recently.
Shortly after making my post i did find that exact same youtube vid tutorial and was able to solve my problem.
I just wanted to say thanx for taking time to respond even so.
All the best.
JJ

[Q] HTC vivid AT&T drivers not recognised

My vivid mobile when it is connected in fastboot mode , drivers are not recognised. I need to root my mobile

Is it recognized when not in fastboot? What os are you using, and so you run into the save issue on a different PC?
Sent from my Vivid 4G using XDA Free mobile app

projectisaac said:
Is it recognized when not in fastboot? What os are you using, and so you run into the save issue on a different PC?
Sent from my Vivid 4G using XDA Free mobile app
Click to expand...
Click to collapse
It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it

It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it

saiviru said:
It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it
Click to expand...
Click to collapse
Hmmm.... I'll have to test this with my girlfriends comp first, as I'm using win7x64 myself.
Sent from my Vivid 4G using XDA Free mobile app

test as fast as you can .I want to root my mobile

fastboot doesn't work on windows 8.1
using a virtual machine also doesn't work as the vm reads the host system's usb
you'll have to find a different machine to use fastboot
or you could try using a linux live cd (but i haven't done this myself, so i don't know if it works)

stuffed_tiger said:
fastboot doesn't work on windows 8.1
using a virtual machine also doesn't work as the vm reads the host system's usb
you'll have to find a different machine to use fastboot
or you could try using a linux live cd (but i haven't done this myself, so i don't know if it works)
Click to expand...
Click to collapse
I just saw this post today.
adb, fastboot works on my windows 8.1 64 bit machine though.
Win 8.1 has command prompt program. You have to run that command prompt "run as administrator".

sway8966 said:
I just saw this post today.
adb, fastboot works on my windows 8.1 64 bit machine though.
Win 8.1 has command prompt program. You have to run that command prompt "run as administrator".
Click to expand...
Click to collapse
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me

saiviru said:
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me
Click to expand...
Click to collapse
In the development settings... Make sure that you've granted root to adb and try again...
Sent from my Vivid 4G using Tapatalk

any solution yet?
saiviru said:
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me
Click to expand...
Click to collapse
same problem here... wondering if you could solve your problem...

I guess I wasn't clear enough.
Windows 8.1 doesn't load the driver for the Vivid while it is in fastboot mode because of a change in the way Windows handles USB devices. ADB and fastboot may work on Windows 8.1, but you'll never be able to "fastboot flash" anything because the device isn't recognized while the phone is in fastboot mode. It is not a phone driver problem, it is a USB controller driver problem.
Also, like I said before, you can't use a virtual machine becuase the the vm reads from the host system's usb.
You will have to use an operating system other than Windows 8.1 to do any fastboot flashing.
Trust me, I've dealt with this problem since 8.1 was released.

[S] How can I repair /system/build.prop ?

Hello to everyone,
I was looking how to install Amazon Store on my Kindle Fire HD 2012 running CM11, when I noticed that I have to change something in /system/build.prop
I had troubles to edit this file because root privileges, so I copied it to emulated SD, then I edited it and copy again to its original path.
It seems than anything went wrong. The tablet gets stucked with "Kindle Fire" blue logo on the screen.
Notes:
My laptop (W7) doesn't recognize the tablet. ADB drivers are correctly installed (or, at least, it seems it). It tries to install "MTP USB device" but it fails before complete setup.
How can I repair /system/build.prop?
EDIT: Nevermind, I ****ed it up.
I have made a wipe of cache, davik and system with "team Win Recovery Project" and it screwed everything. It looks like it is erased, so I'll try to install a new CM version.
--
I know that I make mistakes writing in English, I'm Spaniard.

elRufo said:
Hello to everyone,
I was looking how to install Amazon Store on my Kindle Fire HD 2012 running CM11, when I noticed that I have to change something in /system/build.prop
I had troubles to edit this file because root privileges, so I copied it to emulated SD, then I edited it and copy again to its original path.
It seems than anything went wrong. The tablet gets stucked with "Kindle Fire" blue logo on the screen.
Notes:
My laptop (W7) doesn't recognize the tablet. ADB drivers are correctly installed (or, at least, it seems it). It tries to install "MTP USB device" but it fails before complete setup.
How can I repair /system/build.prop?
EDIT: Nevermind, I ****ed it up.
I have made a wipe of cache, davik and system with "team Win Recovery Project" and it screwed everything. It looks like it is erased, so I'll try to install a new CM version.
--
I know that I make mistakes writing in English, I'm Spaniard.
Click to expand...
Click to collapse
You can ADB sideboard onto TWRP. Easier than starting over.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
You can ADB sideboard onto TWRP. Easier than starting over.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe it's a noob question, but... how I could do that? I had tried several times to install ADB drivers (W7) and it doesn't install correctly. Installer says that it can't write 0x1949 in users/MYUSER/.android/adb_usb.ini file

elRufo said:
Maybe it's a noob question, but... how I could do that? I had tried several times to install ADB drivers (W7) and it doesn't install correctly. Installer says that it can't write 0x1949 in users/MYUSER/.android/adb_usb.ini file
Click to expand...
Click to collapse
To install the adb driver you need the drivers in my signature. I haven't seen people even messing with the adb_usb.ini file in a while. If you are trying to install it while in twrp and you still happen to see a MTP device then you will need to find a USB composite device in the device manager and if you have more than one, it's simple enough to find the right one, just right click one and goto details and then choose hardware id's, if one has a vid of 1949 then uninstall it and scan for new devices and it should pick it up correctly.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
To install the adb driver you need the drivers in my signature. I haven't seen people even messing with the adb_usb.ini file in a while. If you are trying to install it while in twrp and you still happen to see a MTP device then you will need to find a USB composite device in the device manager and if you have more than one, it's simple enough to find the right one, just right click one and goto details and then choose hardware id's, if one has a vid of 1949 then uninstall it and scan for new devices and it should pick it up correctly.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Right Click>Install (w/ Administrator rights)
My Windows 7 (x64) says "This install metod is not valid for this .inf file"
I tried to install original ADB under Administrator account and it looks like are correctly installed, but after that, my pc detects the Kindle Fire HD on "printers/other (and a picture of a mainframe as icon)", so I don´t have access to internal storage to copy CM11 rom and gapps zip.
Note: I own a fastboot cable, I don't know if it could be usefull in this case.

You don't install my drivers like that... open the device manager and if you see a device with a triangle next to it, right click it and hit update drivers, then point it to where you extracted them and it should install.
Sent from my LG-P769 using Tapatalk

stunts513 said:
You don't install my drivers like that... open the device manager and if you see a device with a triangle next to it, right click it and hit update drivers, then point it to where you extracted them and it should install.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Done! Thank you for your patience explaining something thousand times

Kindle Fire HD Bircked Help

Ok I bricked my Kindle Fire HD 7.... Ive heard you needed to order a fastboot cable to fix it and I did.. Now I just need help to fix it as im not the best when it comes to this stuff. Again I have the fastboot cable and the tablet goes into fastboot mode but I dont know what to do... Could someone give me instructions on how to fix it?

AidenOwns said:
Ok I bricked my Kindle Fire HD 7.... Ive heard you needed to order a fastboot cable to fix it and I did.. Now I just need help to fix it as im not the best when it comes to this stuff. Again I have the fastboot cable and the tablet goes into fastboot mode but I dont know what to do... Could someone give me instructions on how to fix it?
Click to expand...
Click to collapse
2012 or 2013 model? Camera or no camera?
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

LinearEquation said:
2012 or 2013 model? Camera or no camera?
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
2012 And it only has a front camera

AidenOwns said:
2012 And it only has a front camera
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

Ok well on my tablet it shows the Fastboot logo... On the KFHD SRT Thing I selected the first option (Restore Factory Rooted With SuperSU)
And all it shows is < waiting for device >
Is there something else I need to do before this???

AidenOwns said:
Ok well on my tablet it shows the Fastboot logo... On the KFHD SRT Thing I selected the first option (Restore Factory Rooted With SuperSU)
And all it shows is < waiting for device >
Is there something else I need to do before this???
Click to expand...
Click to collapse
Make sure you are logged in as admin on your computer. Open a command prompt and type "fastboot -i 0x1949 getvar product" without the quotations. Wait 10 seconds and tell me what the screen says.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
---------- Post added at 11:03 AM ---------- Previous post was at 10:57 AM ----------
Make sure your drivers are installed properly. Windows 8/7 64bit need to be put in test mode so your drivers will install right. Windows is not going to let you do this until you disable device driver signature enforcement.
Disable device driver signature enforcement in Windows 7 read on. Windows 8 has different steps.
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 type these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -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. To exit test mode follow steps 1,2 and 3 in part B of my writeup and type 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
Now restart computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:03 AM ----------
Here are the modified drivers http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9 if you have <still waiting for device> use the guide above and the drivers in this post.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

AidenOwns said:
Ok well on my tablet it shows the Fastboot logo... On the KFHD SRT Thing I selected the first option (Restore Factory Rooted With SuperSU)
And all it shows is < waiting for device >
Is there something else I need to do before this???
Click to expand...
Click to collapse
Please wait for at least 20 minutes. the process takes a long time

Windows terminal not finding adb device

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