Develop Bugs

TWRP officially released!

rootzwiki.com/_/articles/twrp-20-touchscreen-recovery-officially-released-r236
Thanks for all the hard work guys.
Sent from my Kindle Fire using Tapatalk

really want to flash this but I cant get adb to recognize the device. dont know what the issue is can anyone help

wtphoto said:
really want to flash this but I cant get adb to recognize the device. dont know what the issue is can anyone help
Click to expand...
Click to collapse
Do you have Droid Explorer installed? If so, either find a way to disable it starting, or uninstall it.

sl0ttedpig said:
Do you have Droid Explorer installed? If so, either find a way to disable it starting, or uninstall it.
Click to expand...
Click to collapse
I have root explorer will that cause it as well?

wtphoto said:
I have root explorer will that cause it as well?
Click to expand...
Click to collapse
You mean on your device? No, that would make any difference. I'm talking about software installed on your PC.

no I dont, running mint 12 and can connect to my evo no problem but doesnt see the fire for some reason

wtphoto said:
no I dont, running mint 12 and can connect to my evo no problem but doesnt see the fire for some reason
Click to expand...
Click to collapse
Make sure you don't have any command windows open, then open Task Manager, and see if adb.exe is running. If it is, then you have a program that is using it's own version which is potentially overriding yours. Stop it or uninstall it.
At this point, I'm also presuming that you are rooted and so have 0x1949 in your adb_usb.ini file?

do i need to put the "twrp-blaze-2.0.0RC0.img" in a certain folder before flashing?

Did you add the edited USB vendor id?

Have someone tried to boot normally from this recovery
Sent from my Nexus One using XDA App

sl0ttedpig said:
Make sure you don't have any command windows open, then open Task Manager, and see if adb.exe is running. If it is, then you have a program that is using it's own version which is potentially overriding yours. Stop it or uninstall it.
At this point, I'm also presuming that you are rooted and so have 0x1949 in your adb_usb.ini file?
Click to expand...
Click to collapse
I am rooted but when I open the usb_.ini file there is nothing listed there, this is all I have in it
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.

wtphoto said:
I am rooted but when I open the usb_.ini file there is nothing listed there, this is all I have in it
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Click to expand...
Click to collapse
Add 0x1949 to it. Not sure how you could be rooted without having done this step at some point!
---------- Post added at 11:44 PM ---------- Previous post was at 11:43 PM ----------
devastater said:
do i need to put the "twrp-blaze-2.0.0RC0.img" in a certain folder before flashing?
Click to expand...
Click to collapse
Put it in the same directory as fastboot.exe, which generally goes in the same directory as adb.exe.

sl0ttedpig said:
Add 0x1949 to it. Not sure how you could be rooted without having done this step at some point!
Click to expand...
Click to collapse
yeah i did that and it worked, when I rooted I was running mint 11 and then my HDD fried and I had to reinstall and when I did I switched to mint 12 but never updated the usb.ini. I feel about retarted now
thanks for the help

I decided to flash this a different way then said in their post - the way JackpotClavin has us, it sounds a bit firmer. Also, I have FIREFIREFIRE installed, in most cases installing this recovery is pointless unless your have FIREFIREFIRE, so assuming you have FIREFIREFIRE installed you can skip some steps.
This method does NOT require fastboot, so you don't have to go searching around for a bin! (then again, if you have FIREFIREFIRE installed I assume you already have a bin, >_<)
Requirements for my instructions:
FIREFIREFIRE installed
ADB up and running!
adb push *DIRECTORY OF YOUR IMG*\twrp-blaze-2.0.0RC0.img /sdcard
You may need to put the path in parentheses if you have a space anywhere in the path!
adb shell
cd /sdcard
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
reboot
Now it is installed, and it rebooted so press the power button to get into recovery! It'll install it then reboot again, just go into recovery again.
There, you successfully installed it.

Help!!!!
I flashed it according to the instruction in their homepage.
But the KF doesn't wake up,just hangs on the yellow fire picture.
I think it's in fastboot mode(because i set bootmode to 4002)
But my PC can't recognize it,so I can't use fastboot to change the bootmode.
Anyone can help me?

adam900710 said:
Help!!!!
I flashed it according to the instruction in their homepage.
But the KF doesn't wake up,just hangs on the yellow fire picture.
I think it's in fastboot mode(because i set bootmode to 4002)
But my PC can't recognize it,so I can't use fastboot to change the bootmode.
Anyone can help me?
Click to expand...
Click to collapse
How could you make those instructions work?
Mine doesn't go further than the below ...
adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ su
su
# idme bootmode 4002
idme bootmode 4002
<idme> write 4002 to offset 0x1000
# fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot: not found
#
Click to expand...
Click to collapse

andTab said:
How could you make those instructions work?
Mine doesn't go further than the below ...
Click to expand...
Click to collapse
You should reboot you KF and the KF will boot into fastboot.
Then you type fastboot command in you terminal.
It will be a screen showing that the recovery is installing and will reboot.

edit: fixed myself

adam900710 said:
You should reboot you KF and the KF will boot into fastboot.
Then you type fastboot command in you terminal.
It will be a screen showing that the recovery is installing and will reboot.
Click to expand...
Click to collapse
I'm rebooted once i set the bootmode and the kindle fire logo is showing, but when i type
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
all i get is a list of fastboot options

loki154 said:
I'm rebooted once i set the bootmode and the kindle fire logo is showing, but when i type
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
all i get is a list of fastboot options
Click to expand...
Click to collapse
Change "twrp-blaze-2.0.0RC0.img" to the path of the img you downloaded.
Not just "twrp-blaze-2.0.0RC0.img".

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.

[Q] hot to get into fastboot mood!!!!

hi guys,,
love your forum....
simple NOOB question plzzzzzzzzzzzzz...
how do i get into fastboot,,,,
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..

http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1668159

thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks

My Kindle is never recognized by KFU . Here's what you need:
Android SDK
Working adb and fastboot
KFU
On windows 7 shift+right click in your KFU tools directory and click "open command window here"
Here are the commands:
adb devices (your device should be listed)
adb shell (make sure it shows up as root, there will be a #, if not su)
idme bootmode 0x4002
reboot
Then your device should be booted into fastboot mode

He could be having the same problem I had, no /system/bin/sh so the adb technique will not work. I had to make a factory cable, which got me into fastboot mode (but ROMS still are not applying right, that question is in another thread).

gdjy said:
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
Click to expand...
Click to collapse
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.

SLOmtb said:
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
Click to expand...
Click to collapse
Thanks for the KFFB plug. Just as an FYI, fastboot doesn't look at the adb_usb.ini file... adb is the only thing that looks at it.
gdjy said:
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
Click to expand...
Click to collapse
I just updated my fastboot guide (the second link I gave you) with details on how to get the hardware IDs and identify whether or not you are in fastboot mode. Take a look again and see what your hardware IDs are. If that doesn't help you, post a more detailed description of what you are doing, what the device is doing, what errors you get, etc. The more details you can provide, the easier it will be for your helpers to determine what's happening. Look at the sticky post at the top of this section.

i know this is also a stupid question, but how do i issue the "fastboot oem format" command? i tried partitioning my kf but it failed....

Kindle bricked - Can't find the solution anywhere

Hey guys,
so I'm pretty new to the whole android scene and thought it would be a good idea to root my kindle fire. So, i went and downloaded the kindle fire utility and hit install permanent root with superuser.... but didnt put on twrp. oops. I was one of the few unfortunate ones whos rooting didnt work so smoothly. Now i have a kindle that is stuck on the stock start up screen indefinitely. When i plug it in it says windows does not recognize the device - just install the drivers, no big deal right? wrong. i installed the android sdk and all that jazz, and i installed the drivers packed with the kindle fire utility, and still my computer recognizes it as a universal serial bus controller.
every guide for unbricking either assumes you have twrp, or that the re installation of drivers will fix it. im at a complete and utter loss

Josepho1997 said:
Then, in cd to fastboot in cmd and type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
So, i installed the drivers, and opened up the cmd window, but i have no idea how to navigate to the correct directory through cmd now. sorry about my ignorance, really, but could you break t down a tad more?

cellophanemask said:
So, i installed the drivers, and opened up the cmd window, but i have no idea how to navigate to the correct directory through cmd now. sorry about my ignorance, really, but could you break t down a tad more?
Click to expand...
Click to collapse
Navigating to a directory is very easy.
Type cd and then put the file path after it.
Example:
cd c:\Program Files\ Adobe

Shift+ right click on the tools folder in kindle fire utility select open command window here.

trying to root, got adb shell error "/sbin/sh: idme: not found"

Hello,
I am in the process of rooting my Kindle Fire. I have followed all of the directions in the How-To guide and I've run into a problem that I can't solve. I've had several problems along the way, but with perseverance I've been able to get past them.
I'm on step 6 of the section entitled "Rooting the stock software". Since its getting late, and this process has taken me much longer than I expected, and I haven't decided which ROM I want to load, I decided to just root the stock software and call it a day. I am down to the final step in the process of rooting the stock software and I'm stuck.
When I execute the command in step 6:
adb shell idme bootmode 4000​
to set the bootmode back to normal, I get the following error:
/sbint/sh: idme: not found​
I have searched the forums for a similar error and haven't found any posts by anyone with the same problem.
I am doing this from a PC running Windows XP
All of the adb command have worked just fine up till now.
The "adb shell" command works fine. It seems to be the parameters to the command that are causing it to choke.
My current $PATH is /sbin as indicated by the command "adb shell echo $PATH"
Does anyone have any ideas? And what exactly is "idme"?
Thanks in advance, and I will be posting (once I'm finished with this process) many many thanks and kudos for the wonderful rooting instructions that are posted on this forum.
Valerie

idme is the program that reads/sets a number of device parameters from/to the NVRAM. Things like the serial number, wi-fi MAC address, and others reside there. In your example, idme is setting the bootmode that tells the bootloader how to proceed in the boot process. The following should explain the problem you are having and how to work around it...
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
I've reported the problem to the developer and hopefully it will be resolved with the next release.

It worked! Thank you!
Thank you very much. You are awesome. :victory:
My stock KF is now rooted! Yay!

kinfauns said:
idme is the program that . . . resolved with the next release.
Click to expand...
Click to collapse
Thank you! I'm a total noob, and just ran into this issue. Thank you for your guide and your help!

You save my day. It worked
My wife has been on my behind since I got her kindle stuck two day ago. Thanks again

i need help
kinfauns said:
idme is the program that reads/sets a number of device parameters from/to the NVRAM. Things like the serial number, wi-fi MAC address, and others reside there. In your example, idme is setting the bootmode that tells the bootloader how to proceed in the boot process. The following should explain the problem you are having and how to work around it...
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
I've reported the problem to the developer and hopefully it will be resolved with the next release.
Click to expand...
Click to collapse
this did not work for me

I have been at this damn thing for a day now. I can see that the commands are being sent to the tablet via SuperUser app. I am just getting the same error and when I use the Fbmode instead of setting it to 4002 it still says it can't find the command. Google is yielding nothing for me and would really like to not use this crappy amazon OS

taknoverme said:
I have been at this damn thing for a day now. I can see that the commands are being sent to the tablet via SuperUser app. I am just getting the same error and when I use the Fbmode instead of setting it to 4002 it still says it can't find the command. Google is yielding nothing for me and would really like to not use this crappy amazon OS
Click to expand...
Click to collapse
[How To][Root] Kindle Fire 1 update 6.3.4 [2014]
Sent from my XT1080 using XDA Labs