Related
I've looked everywhere for an answer to my question and have yet to find an answer. Probably because my Kindle Fire is truly bricked for good. But here is the series of events that lead to my current predicament.
1. I used Kindle Fire Utility 0.9.1 to root and install TWRP.
2. I was ignorant of the uses of TWRP so when I wanted to restore the Kindle to factory settings I did it within the kindle.
3. I ended up in TWRP so I looked up how to force the amazon update to the kindle. I cleared both caches and factory restore and then installed update.zip.
4. When I rebooted I am now stuck on the boot up screen with no access to TWRP. My computer still recognizes the kindle fire, but I can't access the directory of the kindle.
5. I've tried to use fastboot, Kindle Fire Utility, and anything else to knock it out of the boot logo, but I always am stopped by the error: exec "system/bin/sh": No such file or directory
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
b63 said:
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
Click to expand...
Click to collapse
I´m in the same situation. We can´t use kfu because everyrthing it does needs adb shell, wich isn´t working.
I´d love to be wrong, but the only solution we have is getting a factory cable.
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
b63 said:
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
Click to expand...
Click to collapse
The problem is we are not in fastboot mode. We have normal boot enabled.
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
b63 said:
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
Click to expand...
Click to collapse
Thanks, but it doesn´t work. Factory cable is the last hope.
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
qv775219 said:
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
Click to expand...
Click to collapse
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
osozraz said:
It reboots the device but not to recovery.
Click to expand...
Click to collapse
It looks like flashing the stock rom erases FireFireFire and recovery
osozraz said:
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
It looks like flashing the stock rom erases FireFireFire and recovery
Click to expand...
Click to collapse
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
(Recovery image needs to be named recovery.img)
After flash is done
./fastboot reboot recovery
If have issues from fastboot, reboot the device and from bootloop screen
./adb reboot recovery
qv775219 said:
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, thank you very much for your help.
I type
adb reboot bootloader
and the device reboots, but
fastboot flash recovery recovery.img
gives the same result as before
< waiting for device >
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
b63 said:
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
Click to expand...
Click to collapse
If I am not mistaken, to execute fastboot you have to boot in fastboot mode. My fire is always booting in Normal mode so all fastboot commands i execute have the same result:
< waiting for device >
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
edit2: just for info: kfu uses this to switch to fastboot:
adb shell "idme bootmode 4002"
adb shell "reboot"
don't think that this works
b63 said:
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
Click to expand...
Click to collapse
Adb works. If I type adb devices it shows my Kindle is connected. BUT when executing adb shell or commands that use the sh like adb logcat it fails with the message from the topic title.
If adb shell were working i could use pokey9000´s program to boot in fastboot.
would need a command like "adb reboot bootloader" but never saw such one
could be creative and try "adb reboot fastboot" but it's a shot in the blue ...
sorry
I think we have the same problem
I think we have the same problem @osozraz. I'll share my experience and add more information that I feel is relevant.
1. I also used Kindle Fire Utility to root my Kindle and install TWRP 2.0.
2. I tried installing CM7, it worked, but figured I'd like to get back to stock firmware.
3. In TWRP, I too cleared both caches, factory restored and then proceeded to install update.zip.
4. When the Kindle rebooted it was stuck on the Kindle Fire boot screen.
Now, I researched and tried a couple of unbricking/debricking methods and failed. Here is what I've observed:
a. My device drivers are fine. If I do 'adb devices' it's recognized by the PC. However if I try 'fastboot devices' it returns nothing at all. I assume
b. I also tried the Kindle Fire Utility. Any command I try to do gets stuck on <waiting for device>. I figured that while KFU commands work on the PC's end, it doesn't work on the Kindle Fire. It's basically as if the Kindle is not connected to the computer (try running some of the commands in KFU with the Kindle disconnected, such as changing the bootmode. It'll still say <waiting for device>).
c. I can't to 'adb root' as it will say I don't have permission. Same with adb 'remount' or even 'adb shell', which from what I've gathered is crucial to this process. I can do 'adb reboot' though. I haven't tried rebooting into restore mode but I will try when I get a new MicroUSB B cable.
d. I can't change the bootmode, it gets stuck on <waiting for device> as I've said in point b. Is there a way to actually know what bootmode your device is in? I'm just assuming it's in normal bootmode because I can get fastboot.exe to detect it on the PC. In addition, KFU returns 'unknown'.
Factory Cable
Of course, there's the method of using a factory cable. I'm trying to create one and from what I've gathered there are two ways to do so: 1) use a breakout board (this one I think is the safest way to go) or 2) hack together one using your existing cable: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html. I'm also still scouring the forums for additional information that may help debrick/unbrick my device without the use of the cable. I'm afraid that I might end up damaging my PC or Kindle if I create the cable incorrectly. I've been following this thread though http://forum.xda-developers.com/showthread.php?t=1392693 because I'm thinking of actually just buying one.
Hopes these all help.
You are probably out of luck and need a factory cable at the moment.
You wiped /system/ or killed its permissions, and thus it is unable to load shell.
@osozraz and @jkspn looks like we all have the same problem. Thanks for all the suggestions. I've tried everything. Looks like the only option left is the factory wire. Only problem is that I have 0 skills with smoldering. I guess I could buy one but the site doesn't look like it will be restocking anytime soon. I'll see if I can't return it to Best Buy.
shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
When it says waiting for device, what happens when you unplug and plug in the device?
I have just bought Kindle. So i try to root and install TWRP recovery for my Kindle. After installing TWRP, because don't look Super User icon in Kindle; I took hard-reset my device in Settings. And Now My Kindle boot Logo Kinder Fire stuck on here.
What problem ???? Please help me....... i don't know i had just done nothing. Thanks guys !
I try to text in command dos: "add shell" but it show may Laptop Screen:
- exec '/system/bin/sh' failed: No such file or directory (2) -
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
I'm having this same problem. It's apparently stuck in fastboot. I can't even figure out how to type in adb commands or fastboot commands (meaning I could before and now when I tried it says command not found, but I didn't change anything. It won't recognize my device and when I try installing the android-winusb.inf it says it won't let me. I don't know what else to do. Any help would be appreciated. My Kindle is listed as unspecified device.
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
g1no23 said:
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But Boot Status show: Unknow, so when i type this text comandos show: waiting device
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
lovejoy777 said:
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
thanks guy much. But i tried all, i used KFU to try installing Recovery ( CMW, or TWRP), try to plug in USB Kinlde, press power button, etc. But It'S seem not working, all show: " exec- system/bin/sh failed ; not such file orr folder "
i also use tool KF Unbrick on XDA, but it's too. Reply show: " -exec- "system/bin/sh"...
Can U know that what problem in "system/bin/sh" of Kindle Fire ???????
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
works perfectly for me too! awesome!
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
thanks but my kindle don't have TWPR recovery after i've just flashing office room 6.2.1 from Amazon. Now it stuck in my logo Kindle
tunglx1988 said:
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Serinety said:
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
thanks for repl. But My Kindle Logo is Stuck in here. open KFU then show : Boolloader: UnKnow. So i don't know it bootmod ??? ( recovery, Normal, or fastboot).
b63 said:
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
he is absolutely right, this happened to me and nothing would work until I got a factory cable
This is a typical problem with KFU.
You need to go to your device manager and uninstall both the adb and android drivers then reinstall them manually. Sometimes it helps to restart your computer and Kindle afterwards. Make sure your device manager says both "Android Phone" and "Android ADB Interface" NOT "Other Device" and "Kindle".
When you are stuck at the boot screen it means you are in fastboot mode. In fastboot mode your device will only recognize fastboot commands. If your device doesn't recognize fastboot commands (KFU uses fastboot commands to change boot modes), 99 times out of 100, it's a driver issue.
A factory programming cable, while nice to have, is not usually necessary. A factory programming cable does two things. It provides power directly to the device instead of the battery AND forces the device into fastboot mode (stuck at boot logo). Since most of you with this problem are ALREADY in fastboot mode, a factory cable would be pointless.
Make sure you are 100% certain that you have the correct drivers installed and configured properly and then use the command prompt to change your bootmode to 4000.
In command prompt, navigate to the folder that contains fastboot.exe and enter the following commands...
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Sent from my Amazon Kindle Fire using xda premium
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
soupmagnet said:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Click to expand...
Click to collapse
jingcleovil said:
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
Click to expand...
Click to collapse
i have the same problem as you it fills good to not be the only one
My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!
i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks
Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?
Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.
Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?
GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!
my kindle is stuck on the boot screen (not fastboot) and when i plugged it into my computer it would show as an android phone, please help me get the unbricking utility to recognize my device. when i run command and i type "cd computer/users/etc." then type in "adb kill-server" then "adb devices" and nothing shows. yes i am a noob so please help.
jbQsad said:
my kindle is stuck on the boot screen (not fastboot) and when i plugged it into my computer it would show as an android phone, please help me get the unbricking utility to recognize my device. when i run command and i type "cd computer/users/etc." then type in "adb kill-server" then "adb devices" and nothing shows. yes i am a noob so please help.
Click to expand...
Click to collapse
What were you doing when it got stuck at the bootlogo? Have you tried some fastboot commands to see how it responds?
Even if it's not in fastboot mode, see if you can get it there...
http://forum.xda-developers.com/showthread.php?t=1668159
If you can get it into fastboot mode and issue fastboot commands to it, you can change bootmodes, flash a recovery, or whatever else to get the device booting again. There's also a part in the above post to figure out what hardware ID is getting sent to Windows. That will be important in determining what your KF is doing.
kinfauns said:
What were you doing when it got stuck at the bootlogo? Have you tried some fastboot commands to see how it responds?
Even if it's not in fastboot mode, see if you can get it there...
http://forum.xda-developers.com/showthread.php?t=1668159
If you can get it into fastboot mode and issue fastboot commands to it, you can change bootmodes, flash a recovery, or whatever else to get the device booting again. There's also a part in the above post to figure out what hardware ID is getting sent to Windows. That will be important in determining what your KF is doing.
Click to expand...
Click to collapse
i was rooting and ran out of battery. and i would fast boot it but my kfu wont recognize my kindle even when its in adbinterface
Is it charging?
im not sure
Thepooch said:
Is it charging?
Click to expand...
Click to collapse
its plugged into the computer but since its at the boot logo i cant tell. the light is green on the bottom if that means anything
Maybe try another machine and attempt to reset the bootmode
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
kas782000 said:
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
Click to expand...
Click to collapse
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
sd_shadow said:
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
Click to expand...
Click to collapse
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
kas782000 said:
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Should be able to do it either way but I press enter, before the power button
This will not work if drivers are not correct
could try
Code:
fastboot devices
as a test should get something like
Code:
123456789 bootloader
back in command prompt
I finally got it to work and I can't thank you enough. You were right. I knew my computer recognized the device with adb in normal boot but my computer wouldn't recognize the device in fastboot mode until i reinstalled the android driver while it was in fastboot mode. Now I have a custom ROM running Google Play apps! Again, thank you!
Hey, I don't know if this will help others, but I had a hell of a time trying to get my kindle to recognize while in the bootloader/fastboot mode... It frustrated me so much that I had to write about it.
I recently switched to Windows 10, so it seems like my computer is relearning drivers and stuff...
My kindle was fine when on, and I could issue adb commands from the main screen, but when in fastboot mode, I couldn't get it detected. I knew the drivers were an issue, but I couldn't figure out how to do it. I looked at Amazon's support pages, went through the SDK route, tinkered with the adb.ini and so forth... to no avail.
Post after post said that the easiest way to install the drivers was through the Kindle Fire Utility, but for some reason, the drivers in the .bat file kept failing and would not load. It took a good few hours to figure out the solution.
When I asked the Web why the drivers kept failing, I came across a post that said Windows was actually blocking unknown drivers from loading onto my system. I really wish Windows had told me that instead of just saying "Fail"...
I had to hold down the shift button and click restart on the start menu, and when the computer restarted, I when through: troubleshoot -> advanced options -> startup settings and clicked on Restart. It eventually gave me the option to disable that signature verification [F7]
My explanation is crude, because I want you to look it up properly. Just search for "disable driver signature enforcement" and you should be fine.
Hope this helps others out. I may have to revisit my own post just to see how to do this again.