I didn't know where to post this but I need a little bit of help. I try all the steps to get into shell and after some time I start getting an error message that says: "error device offline". The device shows up on adb devices as well. It also shows that it is offline. Also when I try to boot the phone back up into recovery it comes back up saying: error more than one device and emulator. Help anyone...
if you search the "Unrevoked team: Incredible Root process" thread in this forum, you will find information on "error device offline" issue. I don't recall seeing anything about the "more than one device and emulator" problem though.
craigmack said:
I didn't know where to post this but I need a little bit of help. I try all the steps to get into shell and after some time I start getting an error message that says: "error device offline". The device shows up on adb devices as well. It also shows that it is offline. Also when I try to boot the phone back up into recovery it comes back up saying: error more than one device and emulator. Help anyone...
Click to expand...
Click to collapse
If you're trying to root?
1)
adb kill-server
2)
adb start-server
3)
Done... you can start trying adb shell again.
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
Hello, I've been trying to root my device, i tried Framaroot, but on opening it error occurs saying "your device is not vulnerable to exploit included in framaroot"
Then i tried superoneclick 2.2, i installed ADB drives and my device gets successfully connected by Pda Net, but when i try to root from superoneclick, it gets stuck in "waiting for device".
Please help me is there any other way to root my deivce?
I have attached a screenshot of my "About Tablet"
I've been going through quite a lot of headache just trying to root this old LG G2 (D801) of mine, and would really appreciate some help. First, I tried to go through the normal steps of ioroot. After having to perform some unknown button combination to access the stock recovery (which I could only do with random, continuous button mashing), I am greeted with an error about adb being outdated whenever I try to sideload the "datroot.zip" file. I eventually realized that, somehow, after trying to (and failing to) sideload adb is temporarily changed from 1.0.32 (as required) to 1.0.31, as I can see when I simply enter "adb" in the command prompt before and after attempting to sideload. Some Googling later eventually reveals that renaming adb.exe to something else (in this case I changed it to androiddb) fixes the problem, as it indeed does for that. I then, however, get it to sideload to what seems to be between 50-60% before it fails and the phone spits out the following:
"E: failed to verify whole-file signature
E: signature verification failed
Installation aborted"
On the command prompt's side, it says this at the same time:
"loading: 'datroot.zip' adb server is out of date. killing...
* daemon started successfully *
Total xfew: 1.22x"
After every attempt of Googling around for this, everyone seems to say that I need to use TWRP or CWM instead of the broken stock recovery, and from there just install the file as I've done before on different devices. The problem here is that, to my understanding, I actually need root in order to install a custom recovery, is that not the case? If so, how can I root in this situation if I can't install a recovery, which in turn requires me to root beforehand? If I could get any sort of guidance and hopefully regained sleep, I'd be greatly appreciative, as I'm sure you guys know far more about this kind of stuff than I do. Thank you.
try LG one click root .
Install latest adb drivers, enable USB debugging . connect USB to computer ,put the device on mtp interface. now click on the start button on LG one click root . If the tool stuck at 90% on computer (0% on firmware update screen on mobile) and if this happen couple of times just restart the phone by long pressing the power button while it's connected to the computer . It should then show 100% . After reboot look for supersu in device menu . It should get installed on your phone. If u cant then try the same procedure again. Use root checker to confirm .
And AUTOREC to install TWRP
rajkatiyar07 said:
try LG one click root .
Install latest adb drivers, enable USB debugging . connect USB to computer ,put the device on mtp interface. now click on the start button on LG one click root . If the tool stuck at 90% on computer (0% on firmware update screen on mobile) and if this happen couple of times just restart the phone by long pressing the power button while it's connected to the computer . It should then show 100% . After reboot look for supersu in device menu . It should get installed on your phone. If u cant then try the same procedure again. Use root checker to confirm .
And AUTOREC to install TWRP
Click to expand...
Click to collapse
I can't believe this actually worked! Thank you so much!
yami759 said:
I can't believe this actually worked! Thank you so much!
Click to expand...
Click to collapse
There is a thanks button in the bottom of my post too
rajkatiyar07 said:
There is a thanks button in the bottom of my post too
Click to expand...
Click to collapse
Done
Hi. I read all of the other threads and I've been browsing forums and solutions for a week now, but nothing has worked so I'm going to try to make a thread of my own.
I started an official update a week ago and my phone went into a booting loop. I decided not to mess with it, beyond using eRecovery which fails and trying to re-download the update that fails over and over again. Recovery gets stuck at 5%... same old same old.
The phone is unlocked, but the FRP is locked. I tried every twrp img I could find, tried to fastboot with several utilities and nothing works.. I also tried the dload method with so many packages... it all usually fails with the "Command not allowed" message.
Also, my PC doesn't recognize the phone no matter what drivers I install... HiSuite can't connect to it either. I can try recovery from HiSuite even when it says the phone isn't connected, but it fails too.
Is there anything I'm missing or that I could try? I really would rather not get rid of my phone.
Thanks!