Develop Bugs

KF Failed Root

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.

how to put factory rom back on

can someone point me in the right direction on how to put factory recovery and rom back on my neighbors kindle fire so he can return it im not familar with kindle fire but did many android and windows before thanks

*Go here and download software http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
*Rename file to update.zip.
*Now go into twrp and do a FULL WIPE then install the file. Thats all their is to it. Ive done it before.

powerpoint45 said:
*Go here and download software http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
*Rename file to update.zip.
*Now go into twrp and do a FULL WIPE then install the file. Thats all their is to it. Ive done it before.
Click to expand...
Click to collapse
Will take off the twrp recovery as well? He wants to return it to bestbuy for refund

maxtcee said:
Will take off the twrp recovery as well? He wants to return it to bestbuy for refund
Click to expand...
Click to collapse
yes it will remove twrp make sure you do a full wipe before attempting or you could get some mild brickage requiring a factory cable. wipe factory reset,wipe cache,wipe dalvik, wipe system, flash update.zip reboot then system if prompted...

i wipe everything like you said and for some reason it boots into logo screen then a black screen and stays black i cant seem to get it back into recovery

Use adb shell and Pokey9000's rcmode (or the command line if possible) to change your bootmode to recovery and try it again. Be sure to wipe System and Factory Reset.
If you can't open a shell, you need a factory cable.

soupmagnet said:
Use adb shell and Pokey9000's rcmode (or the command line if possible) to change your bootmode to recovery and try it again. Be sure to wipe System and Factory Reset.
If you can't open a shell, you need a factory cable.
Click to expand...
Click to collapse
dont know what pokey 9000s rcmode but i tried kfu to change the bootmode to recovery but it just reboots and hangs right after the logo
can u explain pokey to me please
EDIT i d/l pokeys fbmode and replaced it in kfu and tried to change the boot mode to fastboot but still hanging am i doing anything wrong ?
any other suggestions

maxtcee said:
dont know what pokey 9000s rcmode but i tried kfu to change the bootmode to recovery but it just reboots and hangs right after the logo
can u explain pokey to me please
Click to expand...
Click to collapse
Okay let's take a step back for a second.
Open the KFU folder and "Shift" + "Right-click" on the folder containing adb.exe and fastboot.exe, and select "Open command window here".
In the window that pops up, enter: (with the device turned on)
Code:
adb shell idme ?
And copy the output here

soupmagnet said:
Okay let's take a step back for a second.
Open the KFU folder and "Shift" + "Right-click" on the folder containing adb.exe and fastboot.exe, and select "Open command window here".
In the window that pops up, enter: (with the device turned on)
Code:
adb shell idme ?
And copy the output here
Click to expand...
Click to collapse
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface

maxtcee said:
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
Click to expand...
Click to collapse
im not seeing that option to open cmd prompt here
im using kfu 9.6 dont know if that makes a difference

maxtcee said:
im not seeing that option to open cmd prompt here
Click to expand...
Click to collapse
Shift + right-click...at the same time

soupmagnet said:
Shift + right-click...at the same time
Click to expand...
Click to collapse
im trying that but its not showing my that option
i see open and run as administrator
if i click on any of them comand prompt opens real quick and closes

maxtcee said:
im trying that but its not showing my that option
i see open and run as administrator
if i click on any of them comand prompt opens real quick and closes
Click to expand...
Click to collapse
I don't know anything about Windows, so I'm just guessing here. You're using Windows 7, correct? Do you have administrator privileges?
No matter, that's just the easy way, try...
Code:
cd /actual_path/to/kfu_folder/containing/adb
...then enter your commands.
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
Let me reiterate, just in case it isn't clear. You don't actually type "/actual_path/to/kfu_folder/containing/adb"

maxtcee said:
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
Click to expand...
Click to collapse
ok it says no C:\android-sdk-windows\platform-tools>adb shell idme
- exec '/system/bin/sh' failed: No such file or directory (2) -

soupmagnet said:
I don't know anything about Windows, so I'm just guessing here. You're using Windows 7, correct? Do you have administrator privileges?
No matter, that's just the easy way, try...
Code:
cd /actual_path/to/kfu_folder/containing/adb
...then enter your commands.
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
Let me reiterate, just in case it isn't clear. You don't actually type "/actual_path/to/kfu_folder/containing/adb"
Click to expand...
Click to collapse
i know but its telling me
its not recognized

maxtcee said:
ok it says no C:\android-sdk-windows\platform-tools>adb shell idme
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
That's a bad thing. Your shell is missing or corrupt. You need the shell to change your bootmode to recovery to fix your problem. Without a shell, you need fastboot to be able to change bootmodes. But you need a shell to change the bootmode to fastboot. Darn.
The only way you get into fastboot now is with a factory cable.
http://forum.xda-developers.com/showpost.php?p=20380015

soupmagnet said:
That's a bad thing. Your shell is missing or corrupt. You need the shell to change your bootmode to recovery to fix your problem. Without a shell, you need fastboot to be able to change bootmodes. But you need a shell to change the bootmode to fastboot. Darn.
The only way you get into fastboot now is with a factory cable.
http://forum.xda-developers.com/showpost.php?p=20380015
Click to expand...
Click to collapse
thanks dude time to get drunk and worry about this in the am

Nevermind

Thepooch said:
Nevermind
Click to expand...
Click to collapse
Yeah, that page #2 is a tricky one, eh?

Yeah my bad didnt realize you were that deep yet lol

[Q] KF2 Rooted with cm11 and kitkat running

My kf2 was working fine but I ran out of room to install apps. I deleted unneeded apps still not enough room. I booted into twrp did a full wipe and now I can't side-load any roms to install. Twrp shows no OS installed. It will boot into twrp fine but nothing else. I have a fastboot cable. My computer recognizes my kf2 as an adb device but I can't seen to get anything to load. Some of the commands in KFFAID work but not all. I am trying to load cm11 and kitkat back. Any help would be appreciated.
James

getnby said:
My kf2 was working fine but I ran out of room to install apps. I deleted unneeded apps still not enough room. I booted into twrp did a full wipe and now I can't side-load any roms to install. Twrp shows no OS installed. It will boot into twrp fine but nothing else. I have a fastboot cable. My computer recognizes my kf2 as an adb device but I can't seen to get anything to load. Some of the commands in KFFAID work but not all. I am trying to load cm11 and kitkat back. Any help would be appreciated.
James
Click to expand...
Click to collapse
if sideload doesnt work then just do this, put the rom you want to flash and its gapps in the folder that adb is in, and run this while booted into twrp: adb push romnamegoeshere /sdcard/
then you can install the rom from inside twrp

didn't work
stunts513 said:
if sideload doesnt work then just do this, put the rom you want to flash and its gapps in the folder that adb is in, and run this while booted into twrp: adb push romnamegoeshere /sdcard/
then you can install the rom from inside twrp
Click to expand...
Click to collapse
Here is what happened. It said the device was not found. In the device manager it shows adb device under kindle fire.

Look on your task manager and kill every instance of adb.exe that you see and try again, I had that happen before when multiple instances were running. As long as it is in twrp then adb should work. If it continues to not work then uninstall the adb driver and if you see the MTP kindle device still there remove it as well, there might be a composite device that needs removing too, I find it a pita going between fastboot, recovery and whatever ROM os flashed if I use windows because of this, the drivers constantly have to be reinstalled when you change modes for me, hence why I avoid working with my kindle in windows and instead just use Linux. If you see any USB composite devices, check the hardware id's for a vid of 1949, if it has that then feel free to uninstall it. This may sound a bit complex, if you need more of an explanation just tell me.
Sent from my Amazon Kindle Fire HD using Tapatalk

No luck
stunts513 said:
Look on your task manager and kill every instance of adb.exe that you see and try again, I had that happen before when multiple instances were running. As long as it is in twrp then adb should work. If it continues to not work then uninstall the adb driver and if you see the MTP kindle device still there remove it as well, there might be a composite device that needs removing too, I find it a pita going between fastboot, recovery and whatever ROM os flashed if I use windows because of this, the drivers constantly have to be reinstalled when you change modes for me, hence why I avoid working with my kindle in windows and instead just use Linux. If you see any USB composite devices, check the hardware id's for a vid of 1949, if it has that then feel free to uninstall it. This may sound a bit complex, if you need more of an explanation just tell me.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
My computer only recognizes the kindle as an adb device in fastboot mode. I haven't been able to use any of the adb commands on it with any luck. It says device not found. This only shows in kffaid version 4.1.87-beta.

*facepalm* you don't use adb commands with fastboot, you use fastboot commands with fastboot. When it is in twrp it should have adb access though...
Sent from my Amazon Kindle Fire HD using Tapatalk

I think I have a driver issue. I forgot to thank you for your help. If I could send the zip rom and gapps I could get it back to where it was. Is there anyway to start all over from the original kindle OS at this point?
Thanks you

You coukd restore it in fastboot using kffa but it seems like unnecessary work. I would boot a ubuntu 13.10 live cd/usb and just attempt it from there since there won't be any driver issues.
Sent from my LG-P769 using Tapatalk

I tried Ubuntu 12.04 LTS and it was to much trouble. I will try Ubuntu 13.10. I will have to learn the commands to use it.
Thanks

getnby said:
I tried Ubuntu 12.04 LTS and it was to much trouble. I will try Ubuntu 13.10. I will have to learn the commands to use it.
Thanks
Click to expand...
Click to collapse
these commands should do the trick assuming the repos are all active in the downloadable section of the software updates control panel.
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
and after that the fastboot command will work but keep in mind to give it superuser privis with sudo or it probably wont work, i had forgotten that recently on my own pc since i don't deal with fastboot too often. ex: sudo fastboot -i 0x1949 getvar product

I had to work all weekend. I tried to get access through ubuntu 13.10. I used the commands you provided (sudo apt-get update). This command worked fine. When I used this command (sudo apt-get install android-tools-fastboot) It said I had to enable universe. I did some research and got that working and tried to use this command again (sudo apt-get install android-tools-fastboot) then this one worked fine. Then I tried the last command with my kindle in fastboot mode flashing green light (sudo fastboot -i 0x1949 getvar product ). The message was cannot connect to otter-2 ... device. Same thing I have been getting all along.
I think when I wiped the system I cleared all the software to connect to any external device. I don't know if I can even get access to restore the original OS. If you haven't guessed by now I an a noob. I think you realized that with my adb commands with fastboot enabled. I got the impression you knew when I saw the *facepalm* comment the the beginning of you post. When my kindle is booted to twrp my computer does not recognize it. My computer will recognize as an adb device when in fastboot mode. My computer will recognize it as a kindle (with a yellow triangle in the device manager) when it is trying to boot with the white and blue logo. I don't know what to do at this point. Here is a screen shot with adb side load from twrp.

Interesting, seems that data didn't want to mount. Have you tried adb from Linux while in twrp? Just run "sudo apt-get install android-tools-adb" to install the command, if you can get adb access at least then I may be able to help fix this depending on what exactly is wrong. BTW I didn't exactly think you were a noon with that facepalm, I just see people get that misconception a lot about adb and fastboot commands. What exactly did that fastboot command report back, I was surprised it was an error when I saw otter2 in the error considering that was what that command was sort of supposed to report back.
Sent from my Amazon Kindle Fire HD using Tapatalk

Here is where I am. See below. Now where do I put the file in ubuntu so I can access it from the terminal window. I am running ubuntu from a live CD. I tried the push command but it says no such file or directory. I told you I was a noob!
[email protected]:~$ adb devices
List of devices attached
0123456789ABCDEF recovery

Since adb is in a system path must out it in the current directory you are CD'd into, if you left the terminal alone it should be in ~ (the home folder of the Ubuntu account) so photo the home folder and drop it in there and run "adb push filename /sdcard/"
Considering that /data doesn't want to mount and that /sdcard os technically in /data, that command might not work depending on what's going on. I reccomend seeing if you can first and if not goto the months and mount /cache if its not mounted already, and they pushing a twrp update into it to try to reflash twrp, its small enough I think it should fit into the cache, though I don't think a ROM would fit.
Sent from my Amazon Kindle Fire HD using Tapatalk

I installed ubuntu on my laptop with windows 7. It seems to work better. I put the files in the home folder and the user folder. I mounted the cache and ubuntu said instead of unable to mount it was unable to access kindle now. Here is the terminal window results.
[email protected]:~$ sudo apt-get install android-tools-adb
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
android-tools-adb is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[email protected]:~$ adb push cm-10.2-20130908-UNOFFICAL-otter2.zip /sdcard/
cannot stat 'cm-10.2-20130908-UNOFFICAL-otter2.zip': No such file or directory
[email protected]:~$

Um OK well the filenames are case sensitive in Linux so lookout for that. Also if it was in your home folder then it should have worked as long as you didn't CD anywhere else in the terminal first.
Sent from my Amazon Kindle Fire HD using Tapatalk

Problem Fixed
I fixed my problem. I had to restart my kindle into recovery mode and connect the fastboot cable to the computer and kindle before it booted into TWRP. At that point while booted into TWRP I used the push command in ebuntu terminal to sideload cm11 and gapps. After I loaded them I installed them with TWRP and rebooted. Now it is restored to where it was when I wiped it. I will not do the advanced wipe again.
adb push cm-11-20140202-NIGHTLY-otter2.zip /sdcard/
adb push gapps-kk-20131119.zip /sdcard/
Thanks for your help stunts513
Click to expand...
Click to collapse

[Q] HELP: ADB server didn't ACK... Cannot connect to daemon

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.

[Need Help] D850 - No recovery, no download mode, no fastboot

On a fresh device, I used KingRoot and obtained Flashify to try to flash on the TWRP for my device with the intention of putting on Cyanogenmod. Plain and simple, the result was this: anytime I try to enter Download Mode or Recovery Mode, I get flashing red and blue lights.
I've tried rooting with KingRoot additional times, but it always seems to go away on reboot. To make it worse, I can't even get rid of KingRoot.
Anyone got ideas? And please don't link any "D855 ONLY" threads, because I've looked through those.

i would suggest you flash TWRP from an adb shell.
If this fails you could try and flash CM13 and then flash TWRP.
---------- Post added at 10:45 ---------- Previous post was at 10:43 ----------
Plus I don't think G3 has a fastboot / bootloader mode anyway. I haven't been able to figure it out. Maybe someone else can comment and correct me.
So, as I see it all should be worried about is getting the right recovery on your phone.

G3 has fast boot.so you can also use adb to flash the recovery.the problem might be due to mismatch of recovery and your model number.first make sure the model and then flash accordingly.

inasar said:
i would suggest you flash TWRP from an adb shell.
If this fails you could try and flash CM13 and then flash TWRP.
---------- Post added at 10:45 ---------- Previous post was at 10:43 ----------
Plus I don't think G3 has a fastboot / bootloader mode anyway. I haven't been able to figure it out. Maybe someone else can comment and correct me.
So, as I see it all should be worried about is getting the right recovery on your phone.
Click to expand...
Click to collapse
From what mode can I flash it? I thought you had to be in download or fastboot mode to execute ADB shell commands.
Jahanzaibawan said:
G3 has fast boot.so you can also use adb to flash the recovery.the problem might be due to mismatch of recovery and your model number.first make sure the model and then flash accordingly.
Click to expand...
Click to collapse
It's the correct recovery file for the model. I can't get to fastboot mode.

Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery

inasar said:
Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery
Click to expand...
Click to collapse
I've got ADB set up on my Windows PC back at home already, so I may have to wait until I get home from traveling (next Friday). All I have available to me right now is my Chromebook with Linux.
Thank you for the steps, though. I'll try that as soon as I get home. Might even try to borrow someone else's computer to give it a whirl.

inasar said:
Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery
Click to expand...
Click to collapse
I get "/system/bin/sh: adb: not found" when I do this. Can't seem to figure out what that means.

Do you have adb setup on your pc?

inasar said:
Do you have adb setup on your pc?
Click to expand...
Click to collapse
Yes, and when I use the adb devices command, my phone shows up.

Ok can try the same but skip the point where you type adb shell

btothemose said:
Yes, and when I use the adb devices command, my phone shows up.
Click to expand...
Click to collapse
Did you try it again. I think it should work. If it didn't then there is a very helpful post by thecubed over here which you can follow and it will work.
The thread is here. Just go through the first post which has a tutorial and steps you need to take:
http://forum.xda-developers.com/lg-...lg-g3-twrp-d852-d852g-f400-t2900614?nocache=1