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
I always get error 0x000024b when trying to root my phone. And then, superoneclick freezes on "starting adb server". I have tried a million different ways, none of them work. Please help?
Please help!
I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device.
Can you suggest how best I can revive N10?
Regards,
Contnuing further, my main problen now is how to make my device visible in computer. I tried to install universal driver/ pda net driver etc. but no success. I feel unless this is done, I can not even use recovery options.
Kindly guide me. I keeps on wasting time on futile excercises.
Regards,
I got the same error last night - went straight for the wugs tool kit - problem is now solved
trriley5 said:
I got the same error last night - went straight for the wugs tool kit - problem is now solved
Click to expand...
Click to collapse
What did you do with the tool kit? Use it to install drivers or what? I've tried it and it does nothing for me except give suggestions on how to install drivers.
I've got ADB &SDK installed on my PC that works with my HTC One M8, so I imagine the drivers should work with my Nexus 10, don't you think?
Sent from my HTC6525LVW using XDA Free mobile app
I Have this problem also. I forgot that I had unlocked the Nexus 10, and let the OTA update install. It failed. I cannot get WUGs to talk to the tablet. If I let it boot I get "No Command"
If I go into Download Mode??? "Power + Sound Up" I get Start and an Robot laying down, says Downloading... but WUGs is never able to talk to it.
Atul Kaji said:
I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device.
Can you suggest how best I can revive N10?
Regards,
Click to expand...
Click to collapse
please refer to my post from another thread regarding the fix for your nexus 10, I also encountered the same problem with you guys.. Below is the link. Thank you. :good:
http://forum.xda-developers.com/showpost.php?p=57001773&postcount=134
Thanks. Problem is solved now. Your guide is perfect.
Regards,
I tried rooting. I checked with rootchecker so it didn't root. Update notification came and I clicked on update. The next screen I know said "your device is unlocked and can't be trusted" and after that a dead Android logo and "
error!" Message.
How did you try to root, and with what versions of what software? Did you follow the tutorials here, there are specific ways to go about rooting this device...
How to unlock bootloader? Modaco tools, but getting "error: device not found"
Hello everyone,
(Windows 10; Android 5.0 or 5.1)
(For the record, this is probably related to bootloader unlocking or samsung devices in general, but the device I have is a Tab 4 so I'm making this post here.)
I picked up a new Galaxy Tab 4 Active (SM-T365F0) dirt cheap at a Samsung store in Korea, and I'm trying to root it to get rid of all the bloatware.
Anyways, trying to root it through Odin and the CF-Auto-Root package failed, I believe because the bootloader was still locked.
Now I'm trying to unlock the bootloader using the Modaco tools here:
https://forum.xda-developers.com/ga...otloader-samsung-galaxy-t3409080/post67558470
and following those steps, I run
Code:
abd-windows.exe reboot bootloader
'but I get a "error: device not found" message.
Device manager recognizes the phone, showing it as "SAMSUNG Mobile USB CDC Composite Device". Regular old file explorer don't show anything, but the 'device connected' Windows alert sound plays every time I plug the device in.
So, the device is connected and recognized (properly?), but the boot unlocker doesn't recognize it. What should I do? Should the boot unlocker being looking at a different port? (It always tries port 5037)
Any help you can give would be most appreciated.
How do I unlock the bootloader of my SM-T531?
Having the same problem here, but my device is a SM-T531 running 4.4.2 (ZTO/Brazil).
Anyone please help :fingers-crossed: