Database Info

Having trouble with "fastboot"

Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?

haltemien said:
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
I'm on skype ATM, so if anyone is gentle enough to try an errorsearch with me, call me on my username snorre.andre.nergaard
Click to expand...
Click to collapse
When I reinstalled my SDK i hadnt noticed that ./adb had been moved to a different directory, and the SDK no longer comes with ./fastboot. If you do a quick google search, or a search on XDA, there are forums out there with links and uploaded copies. Actually I'll just put mine up here in a .zip archive. I moved ./adb and ./fastboot back in to my tools folder since it's what I'm used to.

Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.

haltemien said:
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
Click to expand...
Click to collapse
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.

krohnjw said:
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
Click to expand...
Click to collapse
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands

The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium

Esteway.619 said:
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It's fastboot oem unlock
Sent from my Nexus S using xda premium

krohnjw said:
It's fastboot oem unlock
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium

Esteway.619 said:
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It doesn't use ADB at all. That may be what you have your local binary named, but it's fastboot. You need to be in the bootloader (where adb cannot work).
Fastboot is the utility used for unlocking the bootloader, flashing/erasing partitions, booting images (such as a kernel or recovery) without installing to the device.
ADB is the Android Debug Bridge.
This is just for clarity here, there's seemingly a lot of confusion.

Thanks for the clarification bud
Sent from my Nexus S 4G using xda premium

kdepro said:
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
Click to expand...
Click to collapse
Yeah. I was in bootloader mode. So then i guess the fastboot "path". that could be the problem then. Ill check it out when i get back from work. Thanks

[Q] code name android ics fastboot issue

hey guys, the issue I am having is that I am trying to side load rom manager touch but when I enter fastboot reboot bootloader it just says waiting for device. everything worked fine while running GB but now this. I also tried booting into fastboot and running the command, but still nothing. I downloaded the latest version of pda net. dont know if that makes a difference. also usb debugging is selected in developers options. any ideas?

Is ur phone in recovery mode? If not u need to turned off and hold power + volume up then try to flash it
Sent from my Nexus S using Tapatalk

gm` said:
Is ur phone in recovery mode? If not u need to turned off and hold power + volume up then try to flash it
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Can you flash a .img file? I haven't tried that. But this still doesn't answer the question why fastboot commands or adb doesn't respond with this rom.

Yes u can via flashboot.
Flashboot recovery newrecovery.img
Sent from my Nexus S using Tapatalk

CaptEvo said:
Can you flash a .img file? I haven't tried that. But this still doesn't answer the question why fastboot commands or adb doesn't respond with this rom.
Click to expand...
Click to collapse
Because is not in fastboot mode
Sent from my Nexus S using Tapatalk

I get that, any idea how to get into fastboot now?

In order to issue a fastboot command the phone needs to be in fastboot.
You would not issue that command. You would issue adb reboot bootloader. Or just reboot boot loader on the terminal on the phone with su privileges
When the phone is in the bootloader put it in fastboot mode then you issue fastboot commands from a computer that is properly set up to do. Like fastboot devices. Or fastboot flash recovery recovery image name.img etc

I would love to do that except when I go into boot loader there is no option for fastboot

albundy2010 said:
In order to issue a fastboot command the phone needs to be in fastboot.
You would not issue that command. You would issue adb reboot bootloader. Or just reboot boot loader on the terminal on the phone with su privileges
When the phone is in the bootloader put it in fastboot mode then you issue fastboot commands from a computer that is properly set up to do. Like fastboot devices. Or fastboot flash recovery recovery image name.img etc
Click to expand...
Click to collapse
Dear lord, I guess I forgot a bunch of stuff. Thanks for refreshing my memory
Got it done.

CaptEvo said:
I would love to do that except when I go into boot loader there is no option for fastboot
Click to expand...
Click to collapse
The bootloader IS fastboot, just run the flash commands
Sent from my ice cream powered Nexus S

DarkhShadow said:
The bootloader IS fastboot, just run the flash commands
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes thats true. But before running the commands run : fastboot devices. If you see a long number youre jn fastboot mode and the drivers are correctly installed.
Then you can run the commands
Sent from my Nexus S using xda premium

[Q] MAC Nexus Unlock + Root Guide?

Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.

Willz said:
Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.
Click to expand...
Click to collapse
I can help you out.
Download and install Android File Transfer, which will install the necessary drivers for your phone to connect to your computer. http://www.android.com/filetransfer/
Enable developer options on your phone by going to Settings > about phone and tapping the build number 7 or so times. Then go to the developer settings and enable USB debugging.
Once this is done, in your folder entitled your "username" in your Mac (the same folder that has Desktop, Documents, Downloads, etc.), create a folder titled Android.
Inside that Android folder, put these two files: http://cl.ly/SMwW and http://cl.ly/SMiC These are adb and fastboot.
Once that's done, open Terminal, type:
Code:
cd /Users/yourusername/Android
and hit enter.
Then type:
Code:
./adb devices
hit enter, and you should see your phone's serial number so long as you enabled USB debugging as described above.
Then type:
Code:
./adb reboot bootloader
hit enter, your phone will reboot to the bootloader
Download this file and place it inside the Android folder we created earlier: http://cl.ly/SMw9 This is the latest TWRP for our phones.
Into the same Terminal window, type:
Code:
./fastboot oem unlock
hit enter, WARNING: your phone will be returned to stock and your storage erased, once that's done, type
Code:
./fastboot reboot-bootloader
and hit enter to reboot back into the bootloader that is now unlocked.
Then to install TWRP, type:
Code:
./fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
and then reboot the bootloader again. I would then suggest hitting your down arrow a couple of times and booting into recovery, where TWRP will prompt you to root your device with SuperSU. Alternatively, here is the SuperSU zip that you can put onto your phone's storage and flash in TWRP. http://cl.ly/SMlk

Not sure if you missed it, but alternatively there's a Mac toolkit that's recently been posted.
http://forum.xda-developers.com/showthread.php?t=2515640

I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?

stelv said:
I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?
Click to expand...
Click to collapse
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237

0dBu said:
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.

stelv said:
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.
Click to expand...
Click to collapse
When you're in bootloader and you type: fastboot devices what does it return?

0dBu said:
When you're in bootloader and you type: fastboot devices what does it return?
Click to expand...
Click to collapse
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number

stelv said:
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number
Click to expand...
Click to collapse
If adb devices shows your device you're in recovery, not bootloader

It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5

stelv said:
It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5
Click to expand...
Click to collapse
Use fastboot devices if you're in bootloader

Anyhow, the link I posted is a good tutorial, it should get you sorted. Although, even though I have ADB and Fastboot in my Path (ADB works fine), I still have to cd into the platform-tools directory to get fastboot to work. If anyone has some insight into that's I'd be all ears, but I still make it work.
Sent from my Nexus 5 using Tapatalk

Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7

stelv said:
Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7
Click to expand...
Click to collapse
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk

0dBu said:
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks. I saw a fix in the twrp thread as follows, so i did this. Twrp is working as normal now and no bootloops. I have the factory image downloaded too just in case. Thanks again! Everything seems to be working now.
Dees_Troy said:
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
To root, when you select to reboot from the GUI in TWRP, you will be asked if you want to install SuperSU. Swiping to confirm will root your device.
Click to expand...
Click to collapse

adb push filename.xxx not working for me!

Hi all,
I want to learn to push files to my phone through adb push command, so I load into bootloader, then type "fastboot devices" , my phone showed up with no problem, but then i type
adb push rom.zip /sdcard/rom.zip
it gives me a message
"error: device not found"
did I do something wrong?

Can't use ADB in bootloader.
Sent from my Nexus 5 using Tapatalk

0dBu said:
Can't use ADB in bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
didn't I use adb in bootloader to install the teamwin recovery? ( i mean as i remembered)
ok, now its another issue, assuming i need to use adb in recovery mode. when i boot into recovery, my win 7 own't recongnize my device, but when i am in the 4.4 operatiing system or bootloader mode, my pc recongnize my device with no problem

david0916 said:
didn't I use adb in bootloader to install the teamwin recovery? ( i mean as i remembered)
ok, now its another issue, assuming i need to use adb in recovery mode. when i boot into recovery, my win 7 own't recongnize my device, but when i am in the 4.4 operatiing system or bootloader mode, my pc recongnize my device with no problem
Click to expand...
Click to collapse
Force install the driver. I had the same problem.

david0916 said:
didn't I use adb in bootloader to install the teamwin recovery?
Click to expand...
Click to collapse
No. You used fastboot. Fastboot commands in fastboot. Adb commands in recovery or android
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

Dr Tone said:
Force install the driver. I had the same problem.
Click to expand...
Click to collapse
Thanks for your reply, what do you mean by force install the driver? and do you have the link to the driver or is it included in the SDK already?

david0916 said:
Thanks for your reply, what do you mean by force install the driver? and do you have the link to the driver or is it included in the SDK already?
Click to expand...
Click to collapse
The one in the SDK.
Sent from my Nexus 5 using Tapatalk

If you're still having problems I recommend reading this guide. How to Use “adb sideload” to Update a Nexus Without Root or Custom Recovery
But when you get to the part of the guide where you have to type in "adb sideload <filename.zip>", you might have to refer to this to solve it.
I myself have just installed 4.4.2 using this method. Camera SO much faster now.

[24/06/2014][TOOL]Flasher v2.0 for the Kindle Fire HD 7

Disclaimer: I am not responsible in any way if using anything I've made causes hard bricks,bootloops,alien abductions or any other problems.
Hey guys!
It's been some time that I've been seeing people having problems flashing the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7". So,I decided to create this tool. May I present to you,
Flasher
By SafinWasi​
This is a batch file which can flash the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7",complete with ADB and Fast boot executables,stack override,disable auto-recovery update script as well as the 7.2.3 Bootloader downgrade to prevent red screens.
Working features:
Device verification through fastboot.
Flashing Freedom boot and TWRP/CWM Touch/CWM Stock (thanks r3pwn)
Downgrading the Bootloader to 7.2.3
Stack override
Disabling auto-update recovery script
Reboot into TWRP(optional)
Backing up boot,recovery and system partitions.
Restoring previously made backup
Click to expand...
Click to collapse
Steps to use:
Download the zip and extract it.
Read the ReadMe.txt carefully.
Install the Kindle Fire ADB drivers(if needed)
Run Flasher.bat as Administrator.
Follow the on-screen instructions.
Click to expand...
Click to collapse
Changelog:
[01/02/2014]Initial Release
[19/02/2014]Fixed a bug in the backup script
[17/03/2014]Added restore backup option
[24/06/2014]Added support for CWM Touch Advanced Edition and Stock CWM;updated TWRP to 2.7.0.0
Click to expand...
Click to collapse
Download link:
Link 1:flasher-v2-20140624-tate.rar - 31.23 MB
Link 2:flasher-v2-20140624-tate.rar
MD5 Checksum:84313f4b18008f63346853a8666523d5
Click to expand...
Click to collapse
Notes:
This tool is designed to work for Amazon OS version 7.4.6. So,using it on any other software might get you into a bootloop,but the recovery and Freedom-boot will work.Because of this,it is recommended to do the following things before using this tool:
Rooting the device.
Backing up any important data.
Placing the ROM and GApps zips on the sdcard in case you get a bootloop,so that you can just flash those in recovery after doing a complete wipe.
Preparing to lose the Amazon OS
Click to expand...
Click to collapse
Source:
https://github.com/SafinWasi/Flasher.git
Click to expand...
Click to collapse
Credits go to Hashcode,seokhun,BuQQzz,fattire,very green,r3pwn and anyone else whose work helped me.
​Please hit the Thanks button if this tool helped you. Feel free to comment below to suggest any modifications,report any issues or for any help.
Thanks.
XDA:DevDB Information
Flasher, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
Anonymous.123, SafinWasi
Version Information
Status: Beta
Beta Release Date: 2014-06-24
Created 2014-03-18
Last Updated 2014-07-01

Reserved

bump

Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!

GMattZ said:
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
Click to expand...
Click to collapse
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?

Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?

Anonymous.123 said:
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Click to expand...
Click to collapse
I do have all the Fastboot and ADB drivers installed.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
You might want to use this Bin4ry's Root Toolkit to root your Kindle. I've attached the link for you to download.
Root_with_Restore_by_Bin4ry_v33​
As for fastboot, adb reboot-bootloader will not work. You'll need to issue this command:
adb shell
su
reboot bootloader
​

FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
Well,you could use the Root with Restore by Bin4ry to root the device. But since you have OS version 7.4.8,you should keep the ROM and GApps zips on the sdcard since using my tool on any OS other than 7.4.6 might get into a bootloop.

FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460

LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.

FillTheVoid said:
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
Click to expand...
Click to collapse
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.

FillTheVoid said:
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
Click to expand...
Click to collapse
No problem bro.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app

Bump

Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app

vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It should because it looks like it flashes the same files you would flash were you to do it manually complete with bootloader downgrade. You still want to rot first. Root Many Android v31 for that http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Most probably it will work,but you can never be too careful. Be sure to make a backup by option 2.

Bump

Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app

vampir4997 said:
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My tool will boot you into Fastboot. And the preferred (and probably only) root method for 7.4.8 is the Root with restore by Bin4ry v31. LinearEquation answered this question a while ago.

Ty,sorry guess i didnt read back far enough
Sent from my Nexus 5 using XDA Premium 4 mobile app