I have been searching everywhere online for the past 3 days and have seen hundreds of posts on the subject but nothing has helped. I plug in my Kindle Fire, use KFU, use "Install TWRP...", but I get a "device not found" (ADB Status: offline, Boot Status: Unknown).
I've updated the drivers using install_drivers.bat. I've installed them manually. I've restarted my computer and kindle numerous times. The last thing I have tried is updating the adb, but I'm getting an "access denied" error for the adb_usb.ini. I've looked at the permissions and I have permission to edit it.
I'm seriously at my wit's end here since everything I've tried that people say works hasn't worked for me. Does anyone know how to fix this?
Does your device boot up?
Do you mean turn on? Yes. My computer recognizes it. I can transfer files back and forth.
Just to update: I was able to get the kindle fire utility to show adb status online. I didn't do the update adb, so I just put the "0x1949" in the adb_usb file that says
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
It recognizes it, but when I do "Install TWRP", it goes through some code, and on my kindle just says "Root enabled" with and "exit" button to press.
In KFU, after it says "Activating Burritoroot" and "elevating the shell", I get
"adbd cannot run as root in production builds" then
"mount: operation is not permitted" a couple of times
"failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system"
"unable to chmod" that file above
"mount: operation not permitted" a couple of times
It then says "root activated". "The kindle is successfully running in root mode"
<idme> invalid permission
reboot: operation not permitted
The kindle has been told to reboot in Fastboot Mode.
<waiting for device>
What does all of that mean?
Do you have 6.2.2? If you have 6.2.2 everything that happens is normal because it isn't supported yet.. You have to root with burrito root 2 and manually install the recovery.
Yeah, I have 6.2.2. When you say root with Burritoroot 2 and manually install, what do you mean? In my searching, I haven't come across this. Is there a tutorial somewhere. Also, is there a way to return to earlier versions to just use TWRP?
Check the burrito root 2 thread (first post) and the recovery thread for the exact steps you have to follow. By manually I mean that you have to type all the commands your self. There isn't a script yet that can do it for you.
Thanks. I'll try that and see if it works.
It worked for me
or patch run.bat of kfu:
http://forum.xda-developers.com/showthread.php?p=21602553#post21602553
b63 said:
or patch run.bat of kfu:
http://forum.xda-developers.com/showthread.php?p=21602553#post21602553
Click to expand...
Click to collapse
this will brick you if you try and get into fastboot mode, i'm now bricked
the_kwa said:
this will brick you if you try and get into fastboot mode, i'm now bricked
Click to expand...
Click to collapse
many people have done it and it seems to be working
but it is still kfu - means the op of kfu is still valid:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
Okay, I have root (used root checker app to make sure), but KFU still doesn't work. I get the same error. I actually think I may have had root all along. I'm still getting the:
<waiting for device> and that the adb cannot run as root in production builds
I now understand (after reading for a little longer) that Kindle Fire Utility simply doesn't work with 6.2.2 to install TWRP unless you update the run.bat file. While I'm okay with doing some of those commands, it seems that too many people have been bricked by that route. Is there any other way to install TWRP, or do I just have to wait for KFU to be updated? And does anyone have an idea of how long that will take?
you can do it manually
try to follow this post:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
Thanks for the reply, but right after posting, I found an updated version of KFU for 6.2.2.
Here's a link to where I downloaded it from:
http://pastebin.com/PV9FQYry
It worked perfectly for me. I now have TWRP installed and my system backed up using Kindle Fire Utility for 6.2.2. If anyone else is having these problems, this works (at least for me).
good ...
please mark the subject of the topic (edit first post) with [Solved]
Hi, I have the 6.2.2 OS, but I still get the 'Offline ADB Status' even after using the KFU for that version
Any hints?
maxximop said:
Hi, I have the 6.2.2 OS, but I still get the 'Offline ADB Status' even after using the KFU for that version
Any hints?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Related
Hello, brand new to the Kindle. I rooted my device just fine last night and decided to use Kindle Fire Utility to install TWRP. ADB was recognizing the device perfectly and the script seemed to be running fine until it rebooted the Kindle. At that point the script said "reboot: operation not permitted waiting for device" for an extended period of time. After waiting awhile, at this point I did something I probably shouldn't have, I unplugged the Kindle and rebooted it using the power button. It's been getting stuck at the "kindle fire" boot animation ever since. I haven't gotten a screen with a triangle and fire logo.
I tried following the instructions in the sticky but it seems adb no longer recognizes the device, so I can't push zergRush or anything past that.
Is it permanently bricked or is there a method to fix my problem yet?
Thanks for any help.
_______________________
Update: kindle was fixed by uninstalling drivers, reinstalling as android composite usb device, and switching it out of fastboot. not permanently bricked.
sounds like its in fast boot.
open the utility again, check if its in fast boot, if it is run the install command again. if u can't get it installed, use utility to change boot mode back to 4000.
I had the same problem this method worked for me http://forum.xda-developers.com/showpost.php?p=20509949&postcount=245 http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Thanks for the fast replies!
When I try to change the bootmode using the fastboot it just says waiting for device and never progresses. KindleFireUtility shows ADB Online, Boot status at 4002, and fastboot as offline. Device manager doesn't show a Kindle, just an android adb interface with a yellow ! triangle.
I did restart the PC once and the kindle a few times. No luck yet.
I installed the ADB Composite driver again for the device and got this error (attached)
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
uninstall the driverand use the driverin the utility thread? someone said leaving ur kindle connected to ur pc and rebooting ur pc will reboot the kindle? if it works su with terminal and change bootmode back to 4000
sent from my kindle fire
Alright everyone, I got it working after uninstalling the driver for the Android device, shutting down, starting up again, and plugging in and reinstalling the driver, then changing the bootmode using the instructions previously posted. Thank you all SO MUCH for helping as much as you could. Now to try this again!
terracode said:
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
Click to expand...
Click to collapse
Now I'm wondering what you mean by making sure the drivers are installed for TWRP to install correctly. Obviously I missed a step the first time, what do I do to make sure I don't miss it again? Right now when I try to install TWRP again it says "The system cannot find the filepath specified" several times.
would recomend to use following:
http://forum.xda-developers.com/showthread.php?t=1399889
download the utility and prepare according:
http://forum.xda-developers.com/showthread.php?p=20574755#post20574755
change bootmode, install twrp or whatever with the utility
Got twrp on it last night successfully and flashed CM7.
My question is somewhat related to this thread...
I'm on 6.2 (wifi turned off) and was already rooted and am trying to update to the 6.2.1 secured update with root installed update found on XDA. I'm using Kindle Fire Utility v.6, and to the best of my knowledge using the drivers included with the KF Utility program.
In the utility I show...
ADB Status: Online
Boot Status: 4000
Fastboot Status: Offline
Question is I'm not familiar with fastboot and unclear if I have everything configured in order to (safely) install TWRP. In a command prompt when I type 'fastboot devices' nothing is displayed ("adb devices" shows the device). Combined with the fact I've never seen anything but "Offline" for the Fastboot Status, I'm a little concerned I'm missing a piece of the puzzle and hesitant to install TWRP until I know better.
Any help/advice would be appreciated. Thanks!
look at my post on page 1 of this thread !
@Stevebro: I believe if you are using KF Utility v.6, then you should be good to go. As long as you installed and updated the usb Drivers and then ran zergRush, you should be at the point where you can install TWRP. Just make sure you are using the latest version of KF Utility and it should go pretty smoothly.
... After you install TWRP, I'd recommend going back to your KF OS and do a Titanium Backup of your apps and then doing a TWRP backup. When you flash to CM7 you can restore all your apps easily and painlessly using Titanium backup to restore with the Batch restore option.
Couple nervous moments, reboots and switching out of fastboot mode in the utility... but it all went well. Thanks for the help!!
glad to hear everything is fine ...
Glad to hear everything worked out. I myself sat staring at the "yellow triangle" for a couple of hours. lol, but I just kept working through it and tried not to panic and I got everything working again.
I think OP should edit the first post, or get a mod to edit the title. I keep reading random posts about "lot's of people permanently bricking their Kindle Fires" while I cannot recall a single instance of someone bricking and having to return one and it is getting tiresome.
I looked through A LOT of bricked KF threads but I can't fix the issue that I'm having. Before I found this forum and the very useful looking tools that it provides (KFU, etc) I managed to root my KF by using adb and pushing / installing burritoroot by the command prompt. Everything looked OK, I installed su and got root access to work in the adb shell as well as for apps.
I attempted, without much success, to get the Android Market working on my KF but it always crashed. I messed with some permissions like for /system/app, but I changed that one back to match the other folders in /system.
I may have deleted an apk out of /system/app that wasn't the Android Market, but I'm not sure...
Anyway, I tried to reboot my KF and it got stuck in a boot logo loop. It reports a boot mode of 4000 (normal).
I tried the fastboot recovery method and also KFU, but there are some issues:
Root access seems to have disappeared (access through adb shell cannot be elevated)
Burritoroot will not install anymore through KFU (I get the message "Error: Could not access the Package Manager. Is the system running?"
The above message also occurs when I try to use the adb install command
Fastboot never recognizes the device. It sits on <Waiting for Device> forever.
I've tried rebooting the KF while connected and reconnecting the USB.
I made a Factory Cable, but the Fastboot condition is the same.
I uninstalled my Windows drivers until it showed up as "Kindle" in the Device Manager and installed the files that came with KFU.
I tried the KF Unbrick utility, but that didn't seem to do anything that I missed.
Additionally, when I connect with adb shell I have limited file system access. I can is through /system and some other folders, but I can't access /sdcard and I can't seem to mount the sd card
After writing all this and thinking it through, I decided to compare the /system/app directory on my KF with one in an update.zip file that I downloaded.
It looks like I deleted the file ApplicationsProvider.apk from /system/app
That seems to be the only thing missing.
Is this a Try-to-return-your-KF important file? Is my KF hosed?
fonetik said:
Is this a Try-to-return-your-KF important file? Is my KF hosed?
Click to expand...
Click to collapse
Nope, if you can get fastboot working it doesn't matter how broken /system is. Try this to sidestep the Windows driver problems I think you're having:
http://forum.xda-developers.com/showthread.php?t=1430038
Once you get TWRP installed you can restore from the stock update which will wipe and replace /system.
Thanks I'll give this a shot. I had some issues with Windows when trying to install Cyanogen on my Droid X and a Linux Live-CD got me back on track. Hopefully this will do the trick. I'll report back.
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
I had a similar problem and it was my usb driver set up:
/etc/udev/rules.d/##-android.rules
the ## for Meerkat is 70
SUBSYSTEM==”usb”, ATTR{idVendor}==”0bb4″, MODE=”0666″
Vendorid is 1949 for KF
link that got me going: http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
sorry if you already know this.
I'm new to this so thanks. I'll try it tomorrow when I get a chance.
fonetik said:
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
Click to expand...
Click to collapse
Are you sure you're in fastboot at that point? Are you using your factory cable? Try doing this to get into fastboot mode and use a different USB cable to connect with fastboot. If that doesn't work, do the same but use Firekit in case the fastboot drivers are messed up.
I'm probably not in fastboot. I'll give this a shot. Thanks again.
Edit:
That seems to have gotten me into Fastboot! I'll see if I can get TWRP installed.
There's a faint pulse =)
Edit 2: TWRP installed OK and I used it to try and install the stock update.zip. It rebooted and then got stuck at the logo again, but I'm going to keep working on it. At least I have a tool I can use.
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP. I cleared all my caches and did a factory reset. Then I installed a pre-rooted version of 6.2.1. It did a little reboot dance for a while and then came up into the OS!
Thanks a ton pokey9000. I'm happy to send a couple $$ your way.
fonetik said:
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP.
Click to expand...
Click to collapse
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
krelvinaz said:
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
Click to expand...
Click to collapse
Sorry about the confusion. It was the FFF triangle, but the KF wasn't going into recovery when I held the power button down. I reinstalled with FFF using adb and it worked. Original post subject updated.
I'm pretty new at this and I'm having issues going into TWRP.
Whenever I try to install TWRP recovery using the KFU, It looks like it's going through the process, and I do end up seeing the teamwin logo popup and the device boots into the regular kindle interface (so it at least appears that TWRP was installed). The problem is whenever I try to go into recovery using the bootmode menu in KFU, the kindle will reboot, only it won't go into recovery and just goes back to the regular kindle interface. I'm not quite sure what I'm doing wrong. One thing I did notice from looking through tutorials, is that when you reboot the device it's suppose to go to a yellow triangle screen before going into TWRP. My kindle never does this. I don't ever see that yellow triangle screen and instead see the regular kindle fire logo before it loads the regular interface. One other thing is whenever i use the KFU, under "adb rooted:" it says no. I thought after I did the "Permanent Root with Superuser" that it was supposed to say yes. Anyways, any help would be much appreciated.
the yellow triangle is the bootloader (firefirefire) which you'r missing i think
i would take the newest KFU 0.9.2 (attention re-upped yesterday-redownload):
http://forum.xda-developers.com/showthread.php?t=1399889
reading the op (espacially the known tricks) is a good idea
i recommend to extract kfu to c:\ and rename "kindle fire utility" to "kfu" because it don't allways like the blanks in the path
if you are on windows7 you should run kfu and all other commands from an elevated command shell (as administator)
to install the correct drivers (espacially on win7/64bit) by running install_drivers.bat is also a good idea
now you are ready to use kfu and install twrp again
that's the easy way
if it don't work you can install fff (firefirefire - the yellow triangle) manually
ask again about this ...
Thanks for the reply - just got home and I'll try your suggestions.
I'm having the same problem as the OP here.
I originally rooted using BurritoRoot, which worked just fine.
When using KFU, option 5, it seems to run everything smoothly, the downloads are the correct size... But when it goes and starts rebooting at the "DON'T TOUCH ANYTHING! DON'T EVEN LOOK AT IT! OR ELSE!"* screen on KFU, my Kindle boots into the standard Kindle Boot Animation, then the TeamWin splash pops up for a moment.
It then reboots back to the regular Kindle Fire boot animation and KFU says "There we go. TWRP is installed. Ter-dah!"*
When I go to restart the Kindle, however, I never get the FireFireFire icon at all. Just straight into the normal KindleFire stuff.
I decided to take a look at my device manager while my Fire is plugged in. It's listed under "Android Phone > Android Composite ADB Interface"
Perhaps this is the drivers for my Android Phone interfering with the drivers for the Kindle? Iunno. I'm pretty lost on this one.
(* Paraphrased, in my own words, of course)
the driver is the you stated is the right one for kf in normal bootmode
would retry the installation with kfu and watch the output carefully
maybe copy and paste the output for later analysis
seems to be a common problem at the time:
http://forum.xda-developers.com/showpost.php?p=21316424&postcount=49
How about just download the older KU 0.9.1 that's known to work everytime. 0.9.2 had issues installing TWRP.
Once you installed it using KFU 0.9.1, you will have no proiblems getting to your TWRP recovery.
Using the 0.9.1 version did it for me. Thanks a bundle.
Now I'm drooling over ICS on the Kindle Fire. Can't wait for a stable build! +_+
Just follow this guide:
http://rootkindlefire.com/kindle-fire-root/kindle-fire-root-new6-2-1windowsmaclinux/
Sent from my Kindle Fire using xda premium
So I JUST got this thing today, and was trying to get android marketplace.
here is the list of things that have happened so far:
1. after moving vending.apk to apps folder, main GUI crashes and hitting the home button only switches through apps
2. decide to reboot since it is the next step for installing marketplace anyway
3. stuck in boot loop with shiny animations
4. manage to get TWRP installing
5. post says I need to hit 'reboot' on my kindle. I do.
6. stuck on yellow triangle, with all the drivers no longer working no matter what I do.
known fixes I've tried:
-uninstalling and reinstalling drivers
-rebooting computer and kindle multiple times
-selecting 'android driver' or whatever
-pressing the home button right after startup to try and get back into recovery mode
when looking in the device manager, it used to come up as 'kindle' with the yellow exclamation mark. now it only shows up as 'unknown device'
I JUST got this thing, and it wasn't from an official seller, so im basically on my own... anyone know what I should do?
EDIT: now the device manager IS saying 'android composite ADB interface' but it still wont how up in the kindle fire utility...
EDIT2: I was able to get it into restore mode, and get TWRP to pop up. I then have it clear the cache, and restored back to factory defaults. when I told it to reboot, it rebooted back to recovery mode. I then used the Kindle Fire Utility to set it to normal boot mode.
NOW, the problem im having is that it is stuck in a boot look with the animated 'kindle fire' logo.
Click to expand...
Click to collapse
Its working now! turns out that originally, all I needed to do was change the system permissions back to 755.
Do you have TWRP installed?
If so this link may be helpful to you. I've read a lot of jayceooi's stuff; he may be able to help you.
http://forum.xda-developers.com/showthread.php?t=1430446&highlight=jayceooi
ra0ultortugas said:
Do you have TWRP installed?
If so this link may be helpful to you. I've read a lot of jayceooi's stuff; he may be able to help you.
http://forum.xda-developers.com/showthread.php?t=1430446&highlight=jayceooi
Click to expand...
Click to collapse
Yes, I have twrp 2.0 installed. It had worked fine until yesterday.
have a .android folder in your home dir ?
should have adb_usb.ini in it with this entry: 0x1949 and 0x18D1 - if not add it
then it should show up in kfu
to test manually:
cd with an (elevated) command promt to the tools folder of kfu and do:
adb devices - should return serialnumber and bootmode
b63 said:
have a .android folder in your home dir ?
should have adb_usb.ini in it with this entry: 0x1949 and 0x18D1 - if not add it
then it should show up in kfu
to test manually:
cd with an (elevated) command promt to the tools folder of kfu and do:
adb devices - should return serialnumber and bootmode
Click to expand...
Click to collapse
When I went thru this procedure it says "list of devices attached"
and empty line (So no devices found).
I think my problem is drivers. Since my pc recognizes kf for several seconds only.
During those several seconds nothing really I can do.
Use the liux method. Worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
wigsey said:
Use the liux method. Worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
thanks. will give it a try.
So, as many new KF rooters have, I seem to have bricked my KF. I rooted it just fine, but when installed TWRP through KFU .93 the process seems to have stopped. After waiting over an hour and reading countless "I've been stuck installing TWRP through KFU .93" threads, and seeing many "I switched to .91 and it worked fine" responses, I decided to give that a shot. After unplugging and hard resetting my KF, it is still stuck on the KF logo screen. No yellow box, just the logo screen.
When I plug the KF into my computer, the device is recognized and the proper KF drivers are installed, but I can't get adb to work at all. Every attempt returns a "Device not found" or a "Server didn't ACK." The device does not show up on my list of attached devices, but in Device Manager it is loaded.
I'm unsure of what the next step should be, as I can't get the hardware to respond to anything but resets, and I can't get the software to communicate with the hardware from my PC. I really don't want to admit defeat and contact Amazon.
*edit* Through more research I've made some progress. Opening KFU and selecting the bootmode option, and then when it says "waiting for device" hard resetting the KF and letting KFU change the bootmode to Recovery has done some things. I got a message saying "Failed ..." but it flashed too fast for me to read. Then, upon several restarts, I received a message saying that the KF needed to factory reset, which it is doing now.
As of right now I have a Factory Resetted, working KF. My updated question is now "Where did I go wrong?"
I assume it had to do with TWRP, as it was working until then. Should I redo the whole process using KFU .91 instead of .93? The root went of without a hitch, but the TWRP was what killed me.
Also, do I do Root THEN TWRP, or TWRP THEN Root? I guess I might need Root access to install a Recovery console, but I'm unsure.
use KFU to root, then hit up my gscript install method in the development thread. easy peasy.
but for the record, you were in fastboot, so it won't see adb commands..
fastboot -i 0x1949 oem idme bootmode 4000 maybe woulda saved you. but avoid fast boot entirely, n use my gscript method.
heres how i did it
I was trying to unbridled my kindle fire all last night and about 5hours today.here is how I did it (don't get your hopes up too high,it might not work)
1.Download kindle fire utility
2.Unzip kindle fire utility
3.To install the driver,its easy,just plug in your kindle, when it pops up with the install wizard say pick from the location of: KindleFireUtility>drivers>kindle
4.run kindle fire utility,select 1 then select 1 again
That's it, hope it helps