I flashed the 6.3 update from TWRP and after reboot it gets stuck on kindle fire logo. I have tried Kindle Fire Unbrick Utility with no success. Whenever I choose an option on there, it says waiting for device. When I plug my kindle fire into my computer it makes the connecting noise. In kindle fire utility it shows that adb is online, but the boot status is shown as unknown. When i try to have it reboot into normal mode from kindle fire utility, I get exec '/system/bin/sh; failed : no such file or directory. Then the kindle fire resets itself and im back at square one.
I've uploaded a screenshot of what I get when I use kfu and try to get into fastboot
u were supposed to wipe data after flashing but before rebooting. what rom were you on before you flashed it? usbboot or factory cable.
Sent from my HTC Glacier using xda premium
I was rooted stock. Do you think I should order a factory cable?
yes. unless your comfortable removing the back cover.
Sent from my Kindle Fire using xda premium
If you type "adb devices do you see your kindle?
sent from my ever evolving kindle fire
when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.
chris_m128 said:
when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.
Click to expand...
Click to collapse
Personally I don't think it will show up in adb devices.but you don't need android sdk for adb.if you downloaded kfu then you have it.first look in kfu folder till you find adb.exe. then use the cd command and move into the folder with adb.then you can do adb devices.good luck bro.I've bricked 2 kindle fires and I still don't have enough money for a third.
Sent from my Droid using XDA
chris_m128 said:
when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.
Click to expand...
Click to collapse
like he said, but u can also navigate to the folder and do shift+control+right click and open cmd prompt. from there do adb devices
Sent from my Kindle Fire using xda premium
thank you!
when i type in adb devices after following your instructions I get a bunch of numbers, then they are followed by "device" I can post a screenshot if it will help
You said your computer makes a noise when u plug it in.. its not bricked. What does it show in device manager.
Sent from my Kindle Fire using Tapatalk
it shows android phone
chris_m128 said:
it shows android phone
Click to expand...
Click to collapse
Delete those drivers and run the driver pack from kfu. Then manually select the driver device manager. You have to choose adbcomposite device
You are not to bricked you only have the wrong driver
Sent from my ADR6425LVW using XDA
that's what's keeping my device from booting up?
chris_m128 said:
that's what's keeping my device from booting up?
Click to expand...
Click to collapse
No it is what is preventing you from fixing it
Sent from my ADR6425LVW using XDA
they are all wrong.
when u do adb devices and it shows numbers your golden.
do it again
then do
adb idme bootmode 4000
adb reboot
Sent from my HTC Glacier using xda premium
smirkis said:
they are all wrong.
when u do adb devices and it shows numbers your golden.
do it again
then do
adb idme bootmode 4000
adb reboot
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Well, I don't want to argue. I just know that for the 2 kindles that had the same problem as the OP, any adb command I sent just sat "waiting for device" It was not until I got the right driver (adb composite) that it started taking adb commands again.
if he can push a 4000 reboot without the driver, great. But if he is getting "waiting for device", as he stated in OP, then my suggestion is to get the right driver installed in there.
most soft bricks happen when the fire gets stuck in fastboot mode and loses connection via driver issues and fails to take adb commands.
chris_m128 said:
when i type in adb devices after following your instructions I get a bunch of numbers, then they are followed by "device" I can post a screenshot if it will help
Click to expand...
Click to collapse
but, this.
so, I don't wanna argue either. fastboot is one thing, but adb is another.
his waiting for devices in the op is from kfu, and if you know how it works, it chains a fastboot command and pings it at waiting for devices awaiting reboot. his adb works fine.
Sent from my Kindle Fire using xda premium
Sorry for hijacking your thread bro but im having the same problem. ADB is online but boot status is unknown. On top of that, its stuck at the kindle logo. Any help?
Related
Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.
AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!
soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA
AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.
soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.
I keep getting an error when trying to adb sideload a rom to my TWRP no OS Kindle Fire 2. In device manager my kindle fire says needs troubleshooting and that it has no driver but it wont let me install Kindle Fire HD adb drivers to it. How can I get the ROM over?
If there's anyway to install the adb drivers to it I think it would work but Its just not working.
Also can anyone help me tonight I need my kindle for school?
Never mind I bricked it trying to get it ready in time.:silly:
Did you read this post?
http://forum.xda-developers.com/showthread.php?t=2117224
How to get adb work in TWRP?
Sent from my Amazon Kindle Fire2 using Tapatalk HD
narms72 said:
I keep getting an error when trying to adb sideload a rom to my TWRP no OS Kindle Fire 2. In device manager my kindle fire says needs troubleshooting and that it has no driver but it wont let me install Kindle Fire HD adb drivers to it. How can I get the ROM over?
Click to expand...
Click to collapse
Mount the Kindle while in TWRP.
While plugged into your computer, open cmd.
Enter < cd /(location of your adb files)
Then "push" the files to your sd card by entering < adb push (file name) /sdcard
This should do the trick and allow you to install your rom from your sd-card.
Ichigo said:
That post was from 5 months ago.
Click to expand...
Click to collapse
... and another two years later I honestly wonder, how close mankind is acually to the edge if someone obviously finds it appropriate to answer an usefull support with a subtle nagging concerning "it came to late".
But as this wouldn't be enough: there is not even a merest hint of a scrap of decency - such as kicking back a pleasantry like "thx" - to some guy, who rather made time for reposting a bit late instead of starving you to death.
Holy Moly ... O! Say can you see?
Or saying it in your words:
TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?
DSH said:
TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?
Click to expand...
Click to collapse
i have figuerd out what must i do!
now i have ADB and ADB doesnt find my device to push the rom on it!
plz plz plz help me
i had Drivers installed but when in fastboot connected to pc windows cannt find JEM-Prod... (something like this)
i neeed your help im so confused
Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thanks for your help but adb doesnt recognize my kindle fire! when in CMD i type "ADB Devices" no devices showd up and when "ADB usb" error shows
i think this is the cuase why your tip doesnt work for me (
ive tried this but step 3 give an error
Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
Click to expand...
Click to collapse
Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you very much, but how must i install that?
in device manager i select update driver and locate this folder and it says windows was unable to install you kindle fire HD
i put my kf in recovery mod and plug in the cable!
why have i these problems ?
but again i wanna say thank you bro:good:
So in the task manager is showing a device with an exclamation mark over it right? If so right click the device and hit properties, then goto the details tab, and choose hardware id's from the drop down menu and post them here, I'll see about modifying the driver if I can. Don't know why mine wouldn't work I had the old and new vendor id's for twrp in that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
When i connect to pc in fastboot, in device manager shows as Other devices "Jem-PVT-Prod-04" and the Hardware Ids is:
USB\VID_1949&PID_0008&REV0100
USB\VID_1949&PID_0008
and when just plug the usb cable in recovery mod task manager show it as Portable Device and "Amazon Kindle Fire HD" with a yellow mark! and the hardware Ids is:
USB\VID_1949&PID_0008&REV_0216
USB\VID_1949&PID_0008
thank you bro
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
OMG OMG OMG you saved me and my KINDLE FIRE
i have best wishes for you bro best wishes :good::good::good::good::good::good:
Help!?!?!?
stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
i flashed recovery.img to my kindle using flashify and than i rebooted it than it came up saying kindle fire than the red screen slides across the screen. the app says that you may see a red screen.so im stuck now.
You probably just need to reflash the recovery partition from fastboot.
Hey All!
I had a nice post written up, but XDA decided that it didn't like me and signed me out while I was writing so it's gone now... in any case....
My problem is this: I have set up my linux machine to do adb/fastboot and I'm fairly certain that there's nothing wrong with it on that front. I have no problem with adb, I use shell and then change the bootmode to 4002 and then quickly send a fastboot command to attempt to catch it before it loads FFF. I have FFFv.1.4a which I believe is still the newest version but I want to flash a newer version of TWRP (currently on 2.1.1). I tried using the flashable zip on HashCode's CM11 thread, but it doesn't seem to be making any change (if there's a special way to flash a recovery via recovery I would appreciate any advice) but at this point I'm stuck because I don't remember needing the factory cable to get to the point that I'm at but I don't know of any other way to enable fastboot mode. Is there a way that I can do this without the factory cable? I have one at home, but not with me at school
Thanks in advance,
Sparkplug
In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It appears that even though I'm running MoDaCo, I'm no longer rooted. Very odd.... Perhaps that has something to do with my weird situation. I'll try rooting and report back!
stunts513 said:
In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I should have been more clear. I have no trouble getting to FFF and having it stay there as though it is waiting for commands, but my computer just continues to say <waiting for device>
Does that mean that I'm doing something wrong or do I just need to use the factory cable and that's the beginning and the end of it?
I'm mainly from the 2nd gen kindles and was a little bored so I ventured into the 1st gen forums... But if you are saying that its going into fastboot mode, but you PC can't issue commands then I would guess it's a driver problem, last I checked my drivers in my signature also work with 1st gen kindles. I thought fastboot had its own screen outside of FFF, but if it doesn't then check your device manager for a device with a triangle next to it, I'm guessing it will say otter, like I said though 1st gen kindles aren't my forte but they are similar in certain aspects.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I'm mainly from the 2nd gen kindles and was a little bored so I ventured into the 1st gen forums... But if you are saying that its going into fastboot mode, but you PC can't issue commands then I would guess it's a driver problem, last I checked my drivers in my signature also work with 1st gen kindles. I thought fastboot had its own screen outside of FFF, but if it doesn't then check your device manager for a device with a triangle next to it, I'm guessing it will say otter, like I said though 1st gen kindles aren't my forte but they are similar in certain aspects.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I think that it is supposed to have a separate screen but I wound up doing what I forgot existed because I'm so used to doing everything manually; using ROM Installer by JRummy to flash the image after I had rerooted. I appreciate the help either way!
Hey guys, so my story:
I have a Kindle fire hd 7
I tried to install cyanogenmod on it, i bricked it. When i turn on the kindle, appears the logo and restarting, again and again and again....
I bought fastboot cable, works well, appears the Fastboot text on kindle, when i plug in the usb to laptop.
Downloaded Android SDK, installed the adb driver. U see in the picture, works well.
When i write adb devices, shows nothing device.
And when i write adb kill-server, write nothing.
If i write adb start-server.
Check attachments.
What should i do?
Adb commands don't work with fastboot mode, you need to run fastboot commands. Try "fastboot -i 0x1949 getvar product" and it should report back something if it works. BTW this is the wrong section, I only mention this because I have been seeing a lot of misplaced threads in here lately.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Adb commands don't work with fastboot mode, you need to run fastboot commands. Try "fastboot -i 0x1949 getvar product" and it should report back something if it works. BTW this is the wrong section, I only mention this because I have been seeing a lot of misplaced threads in here lately.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
I attached the pic.
OK good its working fine then, restore the device with kindle fire first aid or srt and it should boot into amazon os. From there you can start the 2nd bootloader procedure again.
Sent from my Amazon Kindle Fire HD using Tapatalk
Thanks for the reply!
I downloaded the first aide. When i choose the Display the fastboot status.
In the next step i see that: the system can not find the path specified
I'm not one to use kffa since I just do all the stuff it does manually so my knowledge of it is fairly limited, but did you follow its instructions, only thing I could guess at is I think the instructions mention setting up its paths. I'm guessing it couldn't find the fastboot binary so it displayed that but I'm not sure.
Sent from my Amazon Kindle Fire HD using Tapatalk
i don't know what to do :/ But i read now, i not follow'd the steps i hope it will be the problem, i not made to desktop the icon, run as administrator, etc etc... if yes, facepalm...
When i start to restore my kindle, just waiting at daemon progress, and nothing happen, i checked the task manager and i see the adb.exe.
Why? why i need to wait more?
That's probably be cause you answered a question wrong, i know that it asks a question when you goto restore it, something like "is it in fastboot mode" or "would you like to put it in fastboot mode", but since it is already in fastboot mode there is no need to tell it to because adb commands don't work with fastboot.
Sent from my Amazon Kindle Fire HD using Tapatalk
i know, but when i try to restore my kindle with first aid, that stops in daemon process and nothing happen.
Check the attached pics.
Kill the adb process then, if the script doesn't check for error codes it should just continue to the flashing process.
Sent from my Amazon Kindle Fire HD using Tapatalk
I did, i got the first message on the 1. pic.
after that i got second picture, and the window closes :/
byAPEX said:
I did, i got the first message on the 1. pic.
after that i got second picture, and the window closes :/
Click to expand...
Click to collapse
well that's just great... try it again, md5sum if you didn't know is basically a way of verifying a files integrity, to make sure it is exactly like the original, if we didn't do these kinda checks and flashed a bad image like for instance the bootloader it would hard brick. Anyways it means it just had a bad download. It could have been a random packet drop, maybe something to do with admin rights, or perhaps the file was down on the site it was hosted on, you will just have to try again and see if you can get it to work. I don't have a copy of kffa handy or i'd check the url it downloads form for you.
Okay thank you