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
Related
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?
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.
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!
I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry
larryb1951 said:
I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry
Click to expand...
Click to collapse
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.
frustrated kindle nooooob
stunts513 said:
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.
Click to expand...
Click to collapse
Revision: Well it appears some how i Have my kindle rooted if i run root checker it says it is and busybox you answered my question about twrp and a second bootloader so i guess i will wait for an update hopefully soon not sure how i accomplished this bc the last thing i did was a factory restore but i have run root checker and it says it ok. my next question is can i still load google store with the stock loader until a fix comes for twerp and 2nd bootloader??????thanxxxxxxx ps whats the old proceedure?
You can still use the Google play store as long as it is rooted, also as to the method there are 2, one is for people not familiar with command line, while the other is purely from command line. While I am completely comfortable with command line myself, I used the fire flash method, the only thing you have to make sure you don't skip is the part where you check the box either above or beside the red warning text or you will have a nice red screen brick on reboot that usually you can recover from. Somehow people don't see that checkbox. Either way the bootloader has to be downgraded first, if you do it the command line way you will definitely want to md5sum the file to make sure it is a perfect downloaded copy of the original or risk a hard brick. The guides on how to do it are here:
Fireflash
Command Line
Sent from my Amazon Kindle Fire HD using Tapatalk
Very Frustrated NOOOOOOOOOB
What should I charge to replace kfhd8-freedom-boot-8.4.6.img like my version 8.4.8
boris_m80 said:
What should I charge to replace kfhd8-freedom-boot-8.4.6.img like my version 8.4.8
Click to expand...
Click to collapse
you don't theres not a newer verison out yet, just use the old one and put the rom you want to flash on it ahead of time so when it bootloops you can flash anothe rrom instead.
stunts513 said:
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.
Click to expand...
Click to collapse
Dam I should've read this before i tried to do mine.
It was 8.4.8 and its stuck on the twrp now coz i used the old freedomboot image with it.
If anyone could tell me a way to revert back to amazon or just get out of this loop i would be very grateful. thanks!
Adb push.... See my pm that explains further.
Sent from my Amazon Kindle Fire HD using Tapatalk
only Partly frustrated noob
stunts513 said:
you don't theres not a newer verison out yet, just use the old one and put the rom you want to flash on it ahead of time so when it bootloops you can flash anothe rrom instead.
Click to expand...
Click to collapse
Well I have the rooting down and the playstore down ive done it so many times as well as restore and factory resets now my problem is
1. first i can boot to fastboot by using adb commands but if i try to boot to fast boot using for instance KFFirstAide it just sits at waiting for device but i can command fast boot and reboot to normal from ADB . Fast boot commands dont work any fix for that.
2. I have tried to load the google aps using the tutorial both automatically and manually but cant seem to get them to work during automatic it returns with not enough disk spave for half the aps and trying to do it manually there are about 6 apks it will not let me move to system aps folder and will not let me move any of the lib.so files to system/lib says copy or move failed no reason given any body have any ideas about this thx i have have done and half not lol i see a restore again in my future if i dont get this figured out. Tried to ask in the KFFirstaide Thread but i think they are gone???????
BTW kindle fure hd 8.9 8.4.8 rooted and playstore and ES3 installed THANX
You probably didn't mount the system partition as read write before you attempted to copy. BTW Don t use the MV command across partitions, it doesn't work correctly for some reason last I checked. If you are doing this from an adb or uneven if you aren't, run this:
Code:
adb shell
su
mount -o rw,remount /system
Now copying files to system should work.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You probably didn't mount the system partition as read write before you attempted to copy. BTW Don t use the MV command across partitions, it doesn't work correctly for some reason last I checked. If you are doing this from an adb or uneven if you aren't, run this:
Code:
adb shell
su
mount -o rw,remount /system
Now copying files to system should work.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks again u always have the answers how about the fast boot issue any ideas?
I'm a little confused as to what it's doing but maybe I didn't read far back enough(also I had a almost complete post in tapatalk, came back half an hour later to finish and bumped the back button and cleared my post... OK let's see if I can finish this post without throwing my kindle across the room...) Alright first things first, if it's going into fastboot and your commands aren't worming with it keep in mind you have to install the adb driver again when it goes into fastboot. If it already doesn't show up as jem or tate or w/e and shows up as an adb device when in fastboot then remember this: fastboot commands have to be prefixed on kindles with "-i 0x1949", like so "fastboot -i 0x1949 getvar product". Hope that helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I'm a little confused as to what it's doing but maybe I didn't read far back enough(also I had a almost complete post in tapatalk, came back half an hour later to finish and bumped the back button and cleared my post... OK let's see if I can finish this post without throwing my kindle across the room...) Alright first things first, if it's going into fastboot and your commands aren't worming with it keep in mind you have to install the adb driver again when it goes into fastboot. If it already doesn't show up as jem or tate or w/e and shows up as an adb device when in fastboot then remember this: fastboot commands have to be prefixed on kindles with "-i 0x1949", like so "fastboot -i 0x1949 getvar product". Hope that helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
well let me see if i can explain better using firstaide if i run diagnostic and boot to fastboot it goes in to fastboot and boots out using adb commands and if i send a fastboot command while it is off it boots into fastboot but if i run option thats says if kindle can respond to simple fastboot commands it says i have a damaged
*********************************************************
* This Option Will Use A Fastboot To Command To Simply *
* Query The Kindle To Display It's System Informtion *
* This Simple Non-Destructive Command Is A Good Way To *
* Determin If Fastboot Is Enabled And If The Kindle Is *
* Responding To Simple Commands. If The Kindle Responds *
* To This Command It Is Safe To Proceed With Other *
* Fastboot Commands. *
*********************************************************
Press any key to continue . . .
*************************************************
* OK Here We Go, We Are Beginning The Process! *
The system cannot find the file specified.
*The Kindle Is Not Responding To Simple Fastboot*
* Commands. Check The Device Manager For Yellow *
* Traingles. If You See One Or Two Traingles *
* Post The Screen Shot In Our Thread. You May *
* A Damaged Recovery Partition. *
*************************************************
< waiting for device >
and thats what i get. Thx
oh and still cant copy those files for google aps procedure just dont get it i can copy some of the apks to the system/aps folder and change permission so system must be rw but there are 7 of them i cant and cannot move any of the lib files at all to the system/lib folder im perplexed
This is why I do things manually... I get more technical output. Shift + right click kffa's folder and hit "open command prompt here"(or something like that. )Type "fastboot -i 0x1949 getvar product" and press enter while your kindle is in fastboot. See if it responds.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
This is why I do things manually... I get more technical output. Shift + right click kffa's folder and hit "open command prompt here"(or something like that. )Type "fastboot -i 0x1949 getvar product" and press enter while your kindle is in fastboot. See if it responds.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
C:\KFFirstAide>fastboot -i 0x1949 getvar product
< waiting for device >
thats the result!
Sounds like its either not showing up or is a driver issue then. If it doesn't show up while in fastboot, that's usually bad. If it doesn't show up, I believe you should be able to reflash the bootloader from inside whatever os is on it as long as it is rooted. Wouldn't suggest doing that unless you have to.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Sounds like its either not showing up or is a driver issue then. If it doesn't show up while in fastboot, that's usually bad. If it doesn't show up, I believe you should be able to reflash the bootloader from inside whatever os is on it as long as it is rooted. Wouldn't suggest doing that unless you have to.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
well i can boot to fastboot using adb if i need be so really not sure there is a real problem unless i have to use fast boot command then it will fail but as long as i have the option to boot to fast boot using ADB maybe im better off leaving things alone ?
larryb1951 said:
I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry
Click to expand...
Click to collapse
Im in your same situation, just got the same exact kindle with 8.4.8. Would you mind telling me which tutorial you finally used that worked? I have been rooting and putting custom roms on my galaxy s4 for a year, jailbreaking iphones for years, etc., but this rooting the kindle is just driving me crazy trying to figure out what instructions to follow that dont leave me with an expensive brick. All I really want to do is be able to install google play store and apps, and change the background and/or lockscreen wallpaper... Thanks,..
Solange82200 said:
Im in your same situation, just got the same exact kindle with 8.4.8. Would you mind telling me which tutorial you finally used that worked? I have been rooting and putting custom roms on my galaxy s4 for a year, jailbreaking iphones for years, etc., but this rooting the kindle is just driving me crazy trying to figure out what instructions to follow that dont leave me with an expensive brick. All I really want to do is be able to install google play store and apps, and change the background and/or lockscreen wallpaper... Thanks,..
Click to expand...
Click to collapse
welli have rooted my kindle hd about 25 times now seem, to have no problem with that and added the play store. I used the KFFirstAide Tutorial works like a champ as far as as background and lock screen thats beyound my minimal knowledge but i believe you will need to add a custom rom t for that and i am not brave enough yet to try that im sure one of the really smart hackers could answer that. I have been able to get individual apps to load but i didnt have any luck with the install google aps part of that tuturial but the rest works fine. Good Luck
Yeah I prefer custom ROMs any day over Amazon's os. The fireflash method is the easiest as it doesn't involve any command line at all. Though it seems most people for get to check off the box next to downgrade bootloader because the warning text telling you that you need to makes it hard to notice the check box... This results in a pita to fix because we have to get into fastboot. I think I heard its even worse on 8.9 inch models when this happens because sometimes the bootloader won't show up as a fastboot service briefly and since fastboot cables don't work on 8.9 models they were screwed. But I don't tend to worry about these kinda things.
As for the wallpaper, the fix in my signature should do it, its a little buggy. Sometimes it causes peoples status bar to disappear, not sure why, assuming the dalvik cache and cache need to be cleared in such a case.
Sent from my Amazon Kindle Fire HD using Tapatalk
I have a 1st gen kindle fire.. That I rooted. But when i tried to install GAPPS and TWRP, the CMD window wouldn't let me. The error: "ADB server didn't ACK... Cannot connect to daemon" would pop up. So nothing else would load.
I then tried and tried various methods of fixes ( three days now), but none would work. Same constant error message in CMD window.
To make matters worse now, In one of my attempts to fix the problem, I've managed to brick the kindle. It's stuck on load page. Just says kindle fire on the screen.
ANY ANY ANY help .. would be greatly appreciated
pistol865 said:
I have a 1st gen kindle fire.. That I rooted. But when i tried to install GAPPS and TWRP, the CMD window wouldn't let me. The error: "ADB server didn't ACK... Cannot connect to daemon" would pop up. So nothing else would load.
I then tried and tried various methods of fixes ( three days now), but none would work. Same constant error message in CMD window.
To make matters worse now, In one of my attempts to fix the problem, I've managed to brick the kindle. It's stuck on load page. Just says kindle fire on the screen.
ANY ANY ANY help .. would be greatly appreciated
Click to expand...
Click to collapse
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
Sent from my XT1028 using Tapatalk
That was exactly one of the post I was working off of. So when I got to step 4: Push Fastboot Mode File to Kindle.. in the command window, I would get the error message, " ADB server didn't ACK... Cannot connect to daemon". I tried for three days now, various fixes.. nothing seemed to work. And NOW, during one of my fixes, it bricked the Fire.
pistol865 said:
That was exactly one of the post I was working off of. So when I got to step 4: Push Fastboot Mode File to Kindle.. in the command window, I would get the error message, " ADB server didn't ACK... Cannot connect to daemon". I tried for three days now, various fixes.. nothing seemed to work. And NOW, during one of my fixes, it bricked the Fire.
Click to expand...
Click to collapse
Stuck at Boot logo?
With animation or no change?
Sent from my XT1028 using Tapatalk
---------- Post added at 03:31 PM ---------- Previous post was at 03:24 PM ----------
Does boot logo, fade in and out slightly?
Sent from my XT1028 using Tapatalk
No fading in and out.
pistol865 said:
No fading in and out.
Click to expand...
Click to collapse
It's in fastboot mode then, send the fastboot commands
Sent from my XT1028 using Tapatalk
"It's in fastboot mode then, send the fastboot commands "
Don't really know what that means?
Fastboot mode?
Send fastboot commands?
Send where?
As I said.. kind of a newbie.. I'm not familiar with all the jargon/terms.
If you have a solution.. could you spell it out like I'm a five year old.. step by step? Otherwise.. I am just going to keep being Lost.
Thank you again
pistol865 said:
"It's in fastboot mode then, send the fastboot commands "
Don't really know what that means?
Fastboot mode?
Send fastboot commands?
Send where?
As I said.. kind of a newbie.. I'm not familiar with all the jargon/terms.
If you have a solution.. could you spell it out like I'm a five year old.. step by step? Otherwise.. I am just going to keep being Lost.
Thank you again
Click to expand...
Click to collapse
There are 2 different types of commands sent from pc to an android device, adb and fastboot.
Adb is used when device is in recovery or system/Rom is running.
Fastboot is used when device is in fastboot mode or bootloader mode.
Sent from my XT1028 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
See step 6
Sent from my XT1028 using Tapatalk
sd_shadow said:
There are 2 different types of commands sent from pc to an android device, adb and fastboot.
Adb is used when device is in recovery or system/Rom is running.
Fastboot is used when device is in fastboot mode or bootloader mode.
Sent from my XT1028 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
See step 6
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
I tried that.. Got the response: Fastboot is not recognized as an internal or external command,
operable program or batch file.
Also whenever I try and run a command from CMD.. I also get "ADB server didn't ACK.. cannot connect to daemon".
pistol865 said:
I tried that.. Got the response: Fastboot is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
adb.exe and other adb files are not in the same folder that the command prompt is running from.
You need to change directory with cd\
sd_shadow said:
adb.exe and other adb files are not in the same folder that the command prompt is running from.
You need to change directory with cd\
Click to expand...
Click to collapse
Step 3 says to put them all in the same folder on my C drive.
"Step 3: Place Files
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder."
I am sooooooo confused right now!!!
I was following step by step. I got the kindle to Root... but then it all went down hill from there. And now it's bricked. ANd I can't figure out how to get out of it.
As I said.. i've been trying for three days now.. All different methods.
I keep running into problems with the CMD prompts..
That is until I somehow bricked it. Now I can't seem to do ANYTHING on it.
pistol865 said:
Step 3 says to put them all in the same folder on my C drive.
"Step 3: Place Files
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder."
I am sooooooo confused right now!!!
I was following step by step. I got the kindle to Root... but then it all went down hill from there. And now it's bricked. ANd I can't figure out how to get out of it.
As I said.. i've been trying for three days now.. All different methods.
I keep running into problems with the CMD prompts..
That is until I somehow bricked it. Now I can't seem to do ANYTHING on it.
Click to expand...
Click to collapse
Create a folder in c drive named adb
One of the methods I was trying was this : http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
However, once again, whenever it goes into the CMD phase, I get the phrase: "ADB server didn't ACK... Cannot connect to daemon"
So before I can unbrick it, I'm thinking I need to fix this other problem FIRST. The "ADB server didn't ACK... Cannot connect to daemon" problem.
pistol865 said:
One of the methods I was trying was this : http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
Click to expand...
Click to collapse
I have not got that to work with System version 6.3.3 or 6.3.4.
So before I can unbrick it, I'm thinking I need to fix this other problem FIRST. The "ADB server didn't ACK... Cannot connect to daemon" problem.
Click to expand...
Click to collapse
It's not bricked it's in fastboot mode, where it needs to be to flash FFF and Twrp, the problem is your pc and the commands you are using.
Create a folder in c drive named adb
sd_shadow said:
I have not got that to work with System version 6.3.3 or 6.3.4.
It's not bricked it's in fastboot mode, where it needs to be to flash FFF and Twrp, the problem is your pc and the commands you are using.
Create a folder in c drive named adb
Click to expand...
Click to collapse
OK.. done..
I've attached an image showing what files are in the folder.
Now I opened a cmd window in C and Started step 4. But I got an error message: * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon.
pistol865 said:
OK.. done..
I've attached an image showing what files are in the folder.
Now I opened a cmd window in C and Started step 4. But I got an error message: * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon.
Click to expand...
Click to collapse
Kindle is in Fastboot mode
adb commands will not work
Use Fastboot commands
see Step 6
sd_shadow said:
Kindle is in Fastboot mode
adb commands will not work
Use Fastboot commands
see Step 6
Click to expand...
Click to collapse
Thank you so much for your help so far..
OK.. so I went ahead and tried step 6. Although the response didn't come back as it should have. I then went to the troubleshooting page and input:
If you got to step
Code:
fastboot devices
and do not get a proper code return, and you have checked drivers in Device Manager, or drivers don't seem to install correctly
you can try
Code:
fastboot -i 0x1949 oem idme bootmode 4000
then
Code:
fastboot -i 0x1949 reboot"
But now when i try to move ahead, the cmd window says it's waiting for device.
The Kindle at first looked as if it were going to reboot, but after a couple of times where the Kindle Fire logo went on and off ( at first disjointed then normal) . then it just stayed on that . Now underneath it says : Battery is too low ( 29%) . Please wait while your Kindle charges.
So I guess I just wait for it to charge? I'm not sure.
What do you suggest my next steps to be?
Again.. Thank you so much for taking the time to help me!
pistol865 said:
Thank you so much for your help so far..
OK.. so I went ahead and tried step 6. Although the response didn't come back as it should have. I then went to the troubleshooting page and input:
If you got to step
Code:
fastboot devices
and do not get a proper code return, and you have checked drivers in Device Manager, or drivers don't seem to install correctly
you can try
Code:
fastboot -i 0x1949 oem idme bootmode 4000
then
Code:
fastboot -i 0x1949 reboot"
But now when i try to move ahead, the cmd window says it's waiting for device.
The Kindle at first looked as if it were going to reboot, but after a couple of times where the Kindle Fire logo went on and off ( at first disjointed then normal) . then it just stayed on that . Now underneath it says : Battery is too low ( 29%) . Please wait while your Kindle charges.
So I guess I just wait for it to charge? I'm not sure.
What do you suggest my next steps to be?
Again.. Thank you so much for taking the time to help me!
Click to expand...
Click to collapse
UPDATE:
Well after a while , the Kindle Fire restored itself to factory.. Had me input all my info again on the Kindle.
So I guess one problem is fixed... It's not Bricked.
Is it still rooted as it was before the problem. And if it is, can I then install FFF and TWRP?
And Finally.. THANK YOU so much for helping me UNBRICK it in the first place!!
pistol865 said:
UPDATE:
Well after a while , the Kindle Fire restored itself to factory.. Had me input all my info again on the Kindle.
So I guess one problem is fixed... It's not Bricked.
Is it still rooted as it was before the problem. And if it is, can I then install FFF and TWRP?
And Finally.. THANK YOU so much for helping me UNBRICK it in the first place!!
Click to expand...
Click to collapse
Did you use install.drivers.bat from Kindle Fire Utility? If not do so now.
Then watch my video, follow my written steps.