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.

Kindle Fire stuck in TWRP because system files wiped out.

I tried to install android 4.1 and messed it up my KF. I wiped out everything and KF can no longer restore because the files needed has been wiped out although I did save them into my laptop. The problem is how can I copy the restoration files from my pc into the KF since my PC no longer can connect to KF and see the folder structure. I can still do all the operations in TWRP but that does not help because the system folders are all empty. I tried Kindle Unbrick UtilityV1.1 and it can not connect to the KF, My battery is about to run out.
Can someone please offer any help?
Thanks so much
Ling

bookreader said:
I tried to install android 4.1 and messed it up my KF. I wiped out everything and KF can no longer restore because the files needed has been wiped out although I did save them into my laptop. The problem is how can I copy the restoration files from my pc into the KF since my PC no longer can connect to KF and see the folder structure. I can still do all the operations in TWRP but that does not help because the system folders are all empty. I tried Kindle Unbrick UtilityV1.1 and it can not connect to the KF, My battery is about to run out.
Can someone please offer any help?
Thanks so much
Ling
Click to expand...
Click to collapse
Okay Ling the very most important thing is to put your in recovery and plug it to the stock wall charger till your battery is 100% or you will compound your problem by ten fold. Then you need at least a 4 gig USB flash drive to create a live Linux with persistence to run Soupkit on to solve your problems with drivers and repair the mounting problems with your Kindle Fire.
You install Soupkit onto a live usb that is running ubuntu with persistent. The persistent allows the live usb to save data between reboots. What you need: Preferably Ubuntu 12.04 precise pangolin found here http://releases.ubuntu.com/precise/ use desktop cd image PC (intel X86) Desktop CD, Pendrive Universal USB installer found here http://www.pendrivelinux.com , a USB flash drive between 4-6 gigs.
Select 12.04 desktop from the dropdown in Universal Usb installer, select your usb by drive letter , select format, drag bar for persistent to 1500 mgs or so, then click create, when finished eject cruiser safely, unplug usb flash drive, shutdown computer, insert usb flash drive, power on computer, it will auto boot at startup on Windows 7 but XP takes more work for instance on my XP machine at first boot splash hit escape for advance startup options, then F9 for boot menu, then scandisk cruiser or whatever your USB is by name, it will then boot ubuntu without installing on your Windows machine.
When booted into Ubuntu: setup your network connection, download Soupkit move it from its containing folder to the desktop, right click select extract here, open folder, double click on the file marked installer, select run in terminal, select option 1 in terminal menu, hit enter for sudo password prompt as there isn`t one, when its finished working it will return you to the main menu, select option 2 it will detect a 32 bit operating system and skip the work for 64 bit then it will launch Soupkit, close all open windows, click the gear icon upper right, select restart, If on windows 7 it will simply restart the Ubuntu system, if on Xp hit Esc. at first computer splash, then select again the cruiser reboot is not near a clean an action on XP sadly.
When booted back back to Ubuntu open a terminal Ctrl+alt+t type soupkit.sh in the terminal now you can use all the features of Soupkit if everything went right and communication has been established with the Kindle.
Soupkit thread http://forum.xda-developers.com/show....php?t=1850038
Edit: a 2 gig flash drive will work but 4 is better.

Thanks so much!
Thepooch said:
Okay Ling the very most important thing is to put your in recovery and plug it to the stock wall charger till your battery is 100% or you will compound your problem by ten fold. Then you need at least a 4 gig USB flash drive to create a live Linux with persistence to run Soupkit on to solve your problems with drivers and repair the mounting problems with your Kindle Fire.
You install Soupkit onto a live usb that is running ubuntu with persistent. The persistent allows the live usb to save data between reboots. What you need: Preferably Ubuntu 12.04 precise pangolin found here http://releases.ubuntu.com/precise/ use desktop cd image PC (intel X86) Desktop CD, Pendrive Universal USB installer found here http://www.pendrivelinux.com/univers...easy-as-1-2-3/ , a USB flash drive between 4-6 gigs.
Select 12.04 desktop from the dropdown in Universal Usb installer, select your usb by drive letter , select format, drag bar for persistent to 1500 mgs or so, then click create, when finished eject cruiser safely, unplug usb flash drive, shutdown computer, insert usb flash drive, power on computer, it will auto boot at startup on Windows 7 but XP takes more work for instance on my XP machine at first boot splash hit escape for advance startup options, then F9 for boot menu, then scandisk cruiser or whatever your USB is by name, it will then boot ubuntu without installing on your Windows machine.
When booted into Ubuntu: setup your network connection, download Soupkit move it from its containing folder to the desktop, right click select extract here, open folder, double click on the file marked installer, select run in terminal, select option 1 in terminal menu, hit enter for sudo password prompt as there isn`t one, when its finished working it will return you to the main menu, select option 2 it will detect a 32 bit operating system and skip the work for 64 bit then it will launch Soupkit, close all open windows, click the gear icon upper right, select restart, If on windows 7 it will simply restart the Ubuntu system, if on Xp hit Esc. at first computer splash, then select again the cruiser reboot is not near a clean an action on XP sadly.
When booted back back to Ubuntu open a terminal Ctrl+alt+t type soupkit.sh in the terminal now you can use all the features of Soupkit if everything went right and communication has been established with the Kindle.
Soupkit thread http://forum.xda-developers.com/show....php?t=1850038
Edit: a 2 gig flash drive will work but 4 is better.
Click to expand...
Click to collapse
I was able to restore my KF following your suggestions.
Thanks so much.
Ling

You`re welcome Ling.

This was very helpful. Many thanks, Thepooch.

You`re welcome .

Same problem.
bookreader said:
I tried to install android 4.1 and messed it up my KF. I wiped out everything and KF can no longer restore because the files needed has been wiped out although I did save them into my laptop. The problem is how can I copy the restoration files from my pc into the KF since my PC no longer can connect to KF and see the folder structure. I can still do all the operations in TWRP but that does not help because the system folders are all empty. I tried Kindle Unbrick UtilityV1.1 and it can not connect to the KF, My battery is about to run out.
Can someone please offer any help?
Thanks so much
Ling
Click to expand...
Click to collapse
I did the same thing. My little brother accidentally wiped everything off of my kindle fire. Including my OS. I've tried almost everything. I've been searching on this site for weeks for a solution, but all have not succeeded. I would appreciate if there was a way to fix my kindle.
Please help me.

Adam1998 said:
I did the same thing. My little brother accidentally wiped everything off of my kindle fire. Including my OS. I've tried almost everything. I've been searching on this site for weeks for a solution, but all have not succeeded. I would appreciate if there was a way to fix my kindle.
Please help me.
Click to expand...
Click to collapse
How about some more information? Like...
Do you have FFF installed?
Do you have access to recovery?
If so, are you able to mount your sdcard to USB in recovery?
Do you have an adb connection in recovery?
After weeks of searching, you should have amassed some knowledge of your situation. How much do you actually understand about the problem?
I could go on, but if you're not willing to spend the time to help us help you...

I do have info.
soupmagnet said:
How about some more information? Like...
Do you have FFF installed?
Do you have access to recovery?
If so, are you able to mount your sdcard to USB in recovery?
Do you have an adb connection in recovery?
After weeks of searching, you should have amassed some knowledge of your situation. How much do you actually understand about the problem?
I could go on, but if you're not willing to spend the time to help us help you...
Click to expand...
Click to collapse
Well i don't have FireFireFire. I only have access TWRP v2.2.2.1. I'm not able to mount SD card. Though Ive tried so many times. I might have adb connection in recovery.
When i open device and printers and find my kindle. here is what it says.
Amazon Kindle USB device
Android Composite ADB Interface
F:\
USB Composite Device
USB Mass Storage Device
What are me options.
ALSO: I've been trying to open a Linux LiveUSB on this thread forum.xda-developers.com/showthread.php?t=1850038

In twrp select mount and transfer a rom to your sdcard to flash.

So what you're saying is, since you don't have FFF installed, you must be accessing TWRP via command line...correct? So you should have an adb connection in recovery.
If you can't mount your sdcard in recovery, you'll need to see this thread:
http://forum.xda-developers.com/showpost.php?p=33109015
But make sure you understand it before trying anything. Feel free to ask questions.
"That's a special kind of stupid. The kind that makes me laugh"

Thepooch said:
In twrp select mount and transfer a rom to your sdcard to flash.
Click to expand...
Click to collapse
As previously stated it wont mount to my SD card on my kindle fire, or i would happily FLASH a ROM to my kindle. I want to fix this kindle. I am open minded to any answers that you may have to my problem.
Thank You
---------- Post added at 07:14 AM ---------- Previous post was at 07:10 AM ----------
Thepooch said:
In twrp select mount and transfer a rom to your sdcard to flash.
Click to expand...
Click to collapse
Cant do that due to the fact that it wont let me mount my device!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
soupmagnet said:
So what you're saying is, since you don't have FFF installed, you must be accessing TWRP via command line...correct? So you should have an adb connection in recovery.
If you can't mount your sdcard in recovery, you'll need to see this thread:
http://forum.xda-developers.com/showpost.php?p=33109015
But make sure you understand it before trying anything. Feel free to ask questions.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
I have access to TWRP. My kindle lets me into the TWRP menu. It says mount but my computer wont pull up my SD card.
What do you mean via command line?
Sorry for being so ignorant on this subject but nothing seems to work!
---------- Post added at 07:27 AM ---------- Previous post was at 07:19 AM ----------
soupmagnet said:
So what you're saying is, since you don't have FFF installed, you must be accessing TWRP via command line...correct? So you should have an adb connection in recovery.
If you can't mount your sdcard in recovery, you'll need to see this thread:
http://forum.xda-developers.com/showpost.php?p=33109015
But make sure you understand it before trying anything. Feel free to ask questions.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
ALSO: I havent been able to get your "SoupKit" to work. I've downloaded the linux liveUSB onto a usb drive, but don't know what to do further. How do i know if the Linux liveUSB worked or not? And when i try to extract SoupKit to LinuxLive Key (E: (<<< this is how it shows up on my computer) it says that the folder is empty and that i have to put documents into the compressed file to Extract.

Adam1998 said:
I have access to TWRP. My kindle lets me into the TWRP menu. It says mount but my computer wont pull up my SD card.
What do you mean via command line?
Sorry for being so ignorant on this subject but nothing seems to work!
Click to expand...
Click to collapse
Okay, before we go any further, you really need to educate yourself a little more about what's going on so you can ask more appropriate questions. If you aren't using the command line to access TWRP, then you must obviously have FFF installed (using power button at startup?).
The best place to start is the Kindle Fire for Beginners guide posted here:
http://forum.xda-developers.com/showthread.php?t=1552547
Then, with a better understanding, you can fix your mounting issue with the tutorial posted earlier in this thread. The information in that tutorial is not to be taken lightly. There is a good chance you will cause much bigger problems for yourself if you don't fully understand exactly what you are doing and why you're doing it.
And if you're not comfortable using the command prompt, I think it's time you get comfortable with it, pretty quickly.
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
Okay, before we go any further, you really need to educate yourself a little more about what's going on so you can ask more appropriate questions. If you aren't using the command line to access TWRP, then you must obviously have FFF installed (using power button at startup?).
The best place to start is the Kindle Fire for Beginners guide posted here:
http://forum.xda-developers.com/showthread.php?t=1552547
Then, with a better understanding, you can fix your mounting issue with the tutorial posted earlier in this thread. The information in that tutorial is not to be taken lightly. There is a good chance you will cause much bigger problems for yourself if you don't fully understand exactly what you are doing and why you're doing it.
And if you're not comfortable using the command prompt, I think it's time you get comfortable with it, pretty quickly.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I want to know if my ADB is working. I want to know how to install soupkit and linux onto my computer. I want to know how to flash roms onto my kindle. I Iwant to know how to fix my kindle in the current state its in.
I've been trying to enter in the commands that http://forum.xda-developers.com/showpost.php?p=33109015 thread has told me. Command prompt tells me that "adb" is not a function. Why is that? Can we talk about this in a faster way. MAYBE we could chat on a different website and you could walk me through my problems.
Thanks Dude for all the help you have already given me.
---------- Post added at 05:59 PM ---------- Previous post was at 05:30 PM ----------
Adam1998 said:
I want to know if my ADB is working. I want to know how to install soupkit and linux onto my computer. I want to know how to flash roms onto my kindle. I Iwant to know how to fix my kindle in the current state its in.
I've been trying to enter in the commands that http://forum.xda-developers.com/showpost.php?p=33109015 thread has told me. Command prompt tells me that "adb" is not a function. Why is that? Can we talk about this in a faster way. MAYBE we could chat on a different website and you could walk me through my problems.
Thanks Dude for all the help you have already given me.
Click to expand...
Click to collapse
soupmagnet said:
Okay, before we go any further, you really need to educate yourself a little more about what's going on so you can ask more appropriate questions. If you aren't using the command line to access TWRP, then you must obviously have FFF installed (using power button at startup?).
The best place to start is the Kindle Fire for Beginners guide posted here:
http://forum.xda-developers.com/showthread.php?t=1552547
Hey I was just running KFU and my ADB status was online. Is this a good thing? I also typed in 5 on KFU and it said that FFF was successfully installed. Does this help my situation and how do I know if FFF was really installed.
Then, with a better understanding, you can fix your mounting issue with the tutorial posted earlier in this thread. The information in that tutorial is not to be taken lightly. There is a good chance you will cause much bigger problems for yourself if you don't fully understand exactly what you are doing and why you're doing it.
And if you're not comfortable using the command prompt, I think it's time you get comfortable with it, pretty quickly.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Hey i was just running KFU and my ADB status is online. Is this something we can work with. I clicked on the number 5 in KFU and it said FFF was successfully installed. How do i know if FFF was really installed.

Hrm when you restart the device you will see a white kindle blue fire that is the fff bootloader. When you see that quickly depress your power button a few times select recovery it should take you to twrp.

Thepooch said:
Hrm when you restart the device you will see a white kindle blue fire that is the fff bootloader. When you see that quickly depress your power button a few times select recovery it should take you to twrp.
Click to expand...
Click to collapse
Ok now what

Adam1998 said:
Ok now what
Click to expand...
Click to collapse
Seriously? That's your response?
How about giving us an idea of what's going on on your end, since we obviously can't SEE IT.
Are you able to access recovery via the boot menu? If so, are you able to send ADB commands? What commands have you tried? What error messages, if any, are you receiving? Are you able to use ADB to push files to your sdcard? When you navigate to your sdcard in recovery, what do you see? Are you able to mount your sdcard in TWRP? If not, what error messages do you receive? Have you read through the guides/turotials linked to earlier in this thread? Do you understand them? If not, what don't you understand? Reading through this thread, do you have a general idea of what you need to do to resolve your problem? If not, what don't you understand?
You should bombarding us with details if you expect anyone to want to spend the time to try and help you resolve your problem.
Quick one or two line responses to our questions only serve to prolong your ordeal, lead to more questions, and possibly cause those who are willing to help, to lose interest and walk away.

soupmagnet said:
Seriously? That's your response?
How about giving us an idea of what's going on on your end, since we obviously can't SEE IT.
Are you able to access recovery via the boot menu? If so, are you able to send ADB commands? What commands have you tried? What error messages, if any, are you receiving? Are you able to use ADB to push files to your sdcard? When you navigate to your sdcard in recovery, what do you see? Are you able to mount your sdcard in TWRP? If not, what error messages do you receive? Have you read through the guides/turotials linked to earlier in this thread? Do you understand them? If not, what don't you understand? Reading through this thread, do you have a general idea of what you need to do to resolve your problem? If not, what don't you understand?
You should bombarding us with details if you expect anyone to want to spend the time to try and help you resolve your problem.
Quick one or two line responses to our questions only serve to prolong your ordeal, lead to more questions, and possibly cause those who are willing to help, to lose interest and walk away.
Click to expand...
Click to collapse
I am able to acess recovery via the boot menu. When i open command prompt and try the commands it tells me that " adb" is not a command. Ive tried all of the commands that you have posted. None have succeeded. I don't know how to use ADB to push files to my SD card. I don't know if mounting my SD card in TWRP is working. Because no error messages appear. I have read through your guides but i am puzzled. I dont fully understand them. If i am correct i believe i need to get a new OS cause my little brother accidentally erased everything on it. I have complete access to TWRP. And in the KFU it says that my adb status is online.
..................

Code:
adb push <filepath> <rom.zip>/sdcard/
Code:
adb push <filepath> <gapps.zip>/sdcard/
after a full wipe minus the external storage/sdcard flash rom.zip,flash gapps.zip select reboot then system. Pretty sure that is all you will have to do by the sounds of it.

Thepooch said:
Code:
adb push <filepath> <rom.zip>/sdcard/
Code:
adb push <filepath> <gapps.zip>/sdcard/
after a full wipe minus the external storage/sdcard flash rom.zip,flash gapps.zip select reboot then system. Pretty sure that is all you will have to do by the sounds of it.
Click to expand...
Click to collapse
If im correct you wanted me to enter this in command prompt right? when i did this is what popped up
Code:
C:\windows\system32>adb push <filepath> <rom.zip>/sdcard/
< was unexpected at this time.

[Q] TWRP problem

I was just messing around with TWRP trying to flash a new ROM. I forgot to make a backup and wiped the internal storage + system (in other word I wiped everything) I have the files in my computer but I don't know how to access them since the computer can't recognize my device. Any suggestions? :crying:

You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/

Thepooch said:
You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/
Click to expand...
Click to collapse
Since the device can't be recognized I would try to search for the ADB drivers. This happened to me on my kindle fire hd 7" and the only way I could fix it was by doing "adb sideload filenamehere.zip" after going into Advanced > ADB Sideload.
Hope I could help!

I'm very grateful
thanks

you rock bro
Thepooch said:
You need to enter recovery and adb push the files to your sdcard. Open a command window where adb is located
Code:
adb push rom.zip/sdcard/
Click to expand...
Click to collapse
Im new to this world of tablets and all the commands and prompt, etc... but I thought that I would never solve my problem lol. I'm still a noob but
Thank you for all what you did for my kindle fire hd. I just wanna let people know you helped me unbrick my kindle ( you worked more than 4 hours to be exactly on my kindle) not many people in this forum would do that :good: and thanks to all the developers and mods you nailed it quite well on unbricking my kindle using the programs they have developed.
Editing the drivers so they could work on my machine (I live in El Salvador so my region is a problem when i try to install the drivers) was no easy quest and using teamviewer for letting you work was cool, but the best part is that you installed the cm10.1 by Hash which I had before bricking my device. You saved my kindle bro, thanks A LOT!!!!! I appreciate it. :victory:

[q] SOLVED: ADB ROM PUSH ERROR: DEVICE NOT FOUND

EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1

lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways

lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app

when i tried to push error device not found lol

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.

If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.

Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks

lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.

sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.

tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*

xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.

UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1

Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again

[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