I've tried every way on the kfu post and no go. anyone have a simple method they r willing to share?
did you have the .android in your home directory?
how windows recognize your kf?
what room do you have installed?
ADB not recognize KF
deathisonlyfreedom said:
I've tried every way on the kfu post and no go. anyone have a simple method they r willing to share?
Click to expand...
Click to collapse
I am having the same problem, tried all methods, tried all different windows OS.
Device manager recognize KF as ADB device/interface, but when check list under ADB command prompt, it's not there. Can't run KFU to root.
Please help, anyone.
.android folder in your home dir and adb_usb.ini with 0x1949 and 0x18d1 entries in it in the folder
b63 said:
.android folder in your home dir and adb_usb.ini with 0x1949 and 0x18d1 entries in it in the folder
Click to expand...
Click to collapse
I don't know, I am at work, when I get home I will check for those. Thanks.
Have you installed the Android SDK and the Android USB Drivers? I was rooting my KF and forgot about this, installed it and it worked perfectly.
mugabuga said:
Have you installed the Android SDK and the Android USB Drivers? I was rooting my KF and forgot about this, installed it and it worked perfectly.
Click to expand...
Click to collapse
I did install USB driver but not Android SDK. I did install Kindle ADB though.
just a hint: if you download the latest kfu there is everything you need - the drivers and all necessary commands in the tools folder (ie with sdk you have to get the fastboot command as it is not included) - you don't need the sdk at all and save a lot of time and space
The newest Krupp does indeed fix the not found issues
Sent from my Kindle Fire using Tapatalk
jgdovin said:
The newest Krupp does indeed fix the not found issues
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Where can I find that "newest Krupp"???
@b63: Attached are the pictures I captured, please look at them and tell me what I did wrong, how to fix it?
Thanks, bro
Related
ADB was working for awhile then quit.
Can someone please help me?
In command prompt it says "ADB is not an internal or external command, operable program or batch file"
Do you install the Sync software?
laufine said:
Do you install the Sync software?
Click to expand...
Click to collapse
Yes, I've tried it with and without.
I recently deleted the Sync, should I reinstall it?
I'll post the drivers. Here is the link.
http://www.megaupload.com/?d=PU08Q26S
You can try manual install the drivers.
Hero's Hero said:
ADB was working for awhile then quit.
Can someone please help me?
In command prompt it says "ADB is not an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
smw6180 said:
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
Click to expand...
Click to collapse
i was just about to type this up then saw this as the last post. Good work man
laufine said:
I'll post the drivers. Here is the link.
http://www.megaupload.com/?d=PU08Q26S
You can try manual install the drivers.
Click to expand...
Click to collapse
I have all the drivers
smw6180 said:
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
Click to expand...
Click to collapse
I have them in the path, but no beauno
Hero's Hero said:
I have them in the path, but no beauno
Click to expand...
Click to collapse
Where is your SDK installed to?
DevinXtreme said:
Where is your SDK installed to?
Click to expand...
Click to collapse
It's in C:/
Hero's Hero said:
It's in C:/
Click to expand...
Click to collapse
And you've tried running this before any adb commands, right?
Code:
cd C:\android-sdk-windows*\tools
*Or whatever you named that folder
I've Had this issue. I Had to un-install the sync And sdk. Then install them right back on lol.Reloaded the vista drivers then Im back Tim. That is if its a Driver issue
-------------------------------------
Sent via the XDA Tapatalk App
Do you still need help with this? I can help you out
regaw_leinad said:
Do you still need help with this? I can help you out
Click to expand...
Click to collapse
Yes I do.
Would really appreciate it.
It seems you're on your way to receiving help. However, if you're still in limbo, locate your android folder or adb executable, right click, copy the location, and paste it into a follow-up reply. This is with respect to the diagnosis process.
Either way, I hope you're headed in the right direction to solve your slight dilemma.
Im sorry, I have tried everything to get my Kindle Fire up and running again. Ive read forum after forum trying to get it up and running. Ive tried the KFU the newest one and the older one. I tried to root my kindle fire and I some how got it stuck on TWRP 2.0. Here are the details of whats going on.
1. I am stuck on TWRP 2.0.
2. My PC does not recognize this device at all.
3. Ive tried deleting the drivers and re-installing the drivers.
4. None of the KFU devices see my KF on the pc.
5. I cant communicate with my KF device through ADB because the PC doesnt see anything.
6. I made the mistake of system restore through the OEM Amazon menu.
7. I dont have any custom roms on my KF device when I scroll through the TWRP menu.
8. I was a dummy and didnt backup the oem device version.
9. I cannot seem to push update.zip because there is no communication between my PC and the KF device.
10. The KF device is not even recognized for a quick second on my PC.
Any help would be greatly appreciated. I tried changing the INI file with the recommended numbers on the forum. Thanks for your time and thank you community in advances. I just wanted to get some better features on the device and i ended up paying the price. Once (i hope) it is restored I will never mess with the device again.
Mount your kindle like USB Storage ("Mount" in TWRP) download any rom and flash it!
animefun135 said:
Mount your kindle like USB Storage ("Mount" in TWRP) download any rom and flash it!
Click to expand...
Click to collapse
can you explain a bit more? i pressed mount in TWRP, and i dont see my fire appearing in "My Computer"
Thanks
in twrp press mount - select sdcard - mount it
in device manager it should show up
if not you should update your drivers
you can use the ones from the newest kfu 0.9.2 http://forum.xda-developers.com/showthread.php?t=1399889
extract it to c:\ and rename to something like c:\kfu\ - sometimes it don't like spaces in pathname
if nothing shows up remove your old drivers: http://support.microsoft.com/kb/315539/en-us
and power down and power up your computer (no restart)
then it should detect something - use the drivers you downloaded - select them manually !!!
once you see the sdcard from your pc you can copy one of the prerooted roms (would take the secure version) or cm7 to the sdcard and install with twrp
prerooted stock images: http://forum.xda-developers.com/showthread.php?t=1402440
b63 said:
in twrp press mount - select sdcard - mount it
in device manager it should show up
if not you should update your drivers
you can use the ones from the newest kfu 0.9.2 http://forum.xda-developers.com/showthread.php?t=1399889
extract it to c:\ and rename to something like c:\kfu\ - sometimes it don't like spaces in pathname
if nothing shows up remove your old drivers: http://support.microsoft.com/kb/315539/en-us
and power down and power up your computer (no restart)
then it should detect something - use the drivers you downloaded - select them manually !!!
once you see the sdcard from your pc you can copy one of the prerooted roms (would take the secure version) or cm7 to the sdcard and install with twrp
prerooted stock images: http://forum.xda-developers.com/showthread.php?t=1402440
Click to expand...
Click to collapse
hey sorry but im having the same problem.. i can get it mounted and everything fine but when i move the prerooted stock you provided in the post it doesn't show up in twrp i have know idea what to do.
bradlier said:
hey sorry but im having the same problem.. i can get it mounted and everything fine but when i move the prerooted stock you provided in the post it doesn't show up in twrp i have know idea what to do.
Click to expand...
Click to collapse
try following:
rename the file to update.zip
copy to root of sdcard
sdcard is hopefully mounted in twrp since you don't see anything
b63 said:
try following:
rename the file to update.zip
copy to root of sdcard
sdcard is hopefully mounted in twrp since you don't see anything
Click to expand...
Click to collapse
i tried that and on my computer it shows up as a zip file but it wont show up on twrp but the other zips i have on the sd card do..
bradlier said:
i tried that and on my computer it shows up as a zip file but it wont show up on twrp but the other zips i have on the sd card do..
Click to expand...
Click to collapse
can you open the file on your computer ?
i would try to re-download it - i think it has to be bad
b63 said:
can you open the file on your computer ?
i would try to re-download it - i think it has to be bad
Click to expand...
Click to collapse
yes the zip opens on the computer. i redownloaded and i got the zip to show up on twrp then flashed it then rebooted.. but all it does is show the yellow triangle thing and then the power button turns orange for a second and it goes right back to twrp.. im staring to think it might be bricked but i really hope not
bradlier said:
yes the zip opens on the computer. i redownloaded and i got the zip to show up on twrp then flashed it then rebooted.. but all it does is show the yellow triangle thing and then the power button turns orange for a second and it goes right back to twrp.. im staring to think it might be bricked but i really hope not
Click to expand...
Click to collapse
don't worry you'r not - it's simply the wrong boot mode
open adb and enter the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot
b63 said:
don't worry you'r not - it's simply the wrong boot mode
open adb and enter the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot
Click to expand...
Click to collapse
sorry, but how do i do that?
command prompt? or something else?
bradlier said:
sorry, but how do i do that?
command prompt? or something else?
Click to expand...
Click to collapse
do you have kfu available ? http://forum.xda-developers.com/showthread.php?t=1399889
if not download, extract to c:\ and rename "kindle fire utility" to "kfu"
you can let it kfu do for you:
run kfu by "run.bat" and select option 1 - change bootmode to normal
or do it manually by opening an (elevated) command prompt in the tools folder of kfu and issue the commands
b63 said:
do you have kfu available ? http://forum.xda-developers.com/showthread.php?t=1399889
if not download, extract to c:\ and rename "kindle fire utility" to "kfu"
you can let it kfu do for you:
run kfu by "run.bat" and select option 1 - change bootmode to normal
or do it manually by opening an (elevated) command prompt in the tools folder of kfu and issue the commands
Click to expand...
Click to collapse
hey man that was it.. thanks alot
Thanks for all the help. My actual problem was the drivers needed to be reinstalled and the USB cable I was using was no good. Go Figure!
Just wondering if it is possible to use adb to reroot 6.2.2 without installing the Android SDK, because it takes up so much space. I have installed the drivers, and have the adb.exe and dll files, but nothing shows up under ADB Devices.
Can someone help?
You do not need to install the entire sdk!!!! Just install kfu and thats all you need. You only need the drivers adb fastboot and a minimal installation is tiny.
Sent from my Kindle Fire using xda premium
Ok, does KFU root 6.2.2?
yes - if you patch it to br3:
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
I am getting things set up to root my Nexus 6p using a Macbook Pro. I have Android Studio installed & I see the platform-tools folder like the tutorial says. But my phone isn't showing up as a device on my Macbook nor is the terminal command "adb devices" showing it.
Has anyone successfully rooted their Nexus 6p using a Macbook Pro?
Thanks!!
Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237
lyall29 said:
Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Totally agree! I used this to get a handle on ADB/fastboot and have been good ever since. Which version of OSX are you using, OP? I followed the above guide and use manual command on OSX 10.10.5. I have heard there are some issues on 10.11 though.
Sent from my Nexus 5X using Tapatalk
I used ruby (built in with osx) inside the terminal to install homebrew. Then install android-platform-tools using homebrew. This installs fastboot and adb, AND adds these programs to PATH so you can use adb or fastboot command no matter which folder the terminal has open. Hope this helps!
EDIT:
Link providing steps for how to do this:
http://macappstore.org/android-platform-tools/
Yes I have rooted my 6p using macbook pro. You have to CD to platform-tools and make the command ./adb devices
That was my problem. Adb wasn't even recognized unless I did ./ before the adb command
andrewnelson23 said:
Yes I have rooted my 6p using macbook pro. You have to CD to platform-tools and make the command ./adb devices
That was my problem. Adb wasn't even recognized unless I did ./ before the adb command
Click to expand...
Click to collapse
That means your search path was not set up.
Even executables in ./ not found? Path really messed up.
BTW : I only use a Mac so I've rooted everything from Samsung to LG and now Nexus on my Macs.
lyall29 said:
Have you ever rooted a nexus with a Mac? If not, you might not have installed adb and fastboot correctly. If you have no experience rooting with a mac, this is a great tutorial for ...http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
WOW!!! Thanks!!! I just posted in the when did you root thread that I haven't seen a tutorial on rooting with a mac!!! I did a search and it didn't show up in the results. I figured people assume that if you have a Mac you also have an iPhone! Thanks for posting this tutorial!!!
mikespe said:
WOW!!! Thanks!!! I just posted in the when did you root thread that I haven't seen a tutorial on rooting with a mac!!! I did a search and it didn't show up in the results. I figured people assume that if you have a Mac you also have an iPhone! Thanks for posting this tutorial!!!
Click to expand...
Click to collapse
I don't make that assumption.
I have been using Macs exclusively for 15+ years.
I have never owned an iPhone. I like MacOS because it's got BSD Unix under the hood.
I had a NeXT before that.
Here is the easiest way to install adb/fastboot on a Mac, also installs it correctly in your PATH.
Also if you are running El Capitan, see this.
I have been using Fedora Linux to root my devices and as long as the path is setup you do not need the "./" but once you are booted into fastboot, even with proper path, you need the ./fasboot (Don't ask me why, haven't figured it out). You may also have to execute fastboot as
sudo ./fastboot
dratsablive said:
I have been using Fedora Linux to root my devices and as long as the path is setup you do not need the "./" but once you are booted into fastboot, even with proper path, you need the ./fasboot (Don't ask me why, haven't figured it out). You may also have to execute fastboot as
sudo ./fastboot
Click to expand...
Click to collapse
If you use the link at the top, the ./ isn't required any longer, not sure why.
Everyone thank you so much for all the information. I have been a Windows guy all my life. I bought this macbook about a year ago and I'm still learning. Windows I can go into the registry and tweak almost anything....Mac I fee like a rookie. As I mentioned earlier I think I will use my Surface Pro 3 this weekend to root the phone. This way I won't have to worry about doing anything wrong or get frustrated!
jawmail said:
If you use the link at the top, the ./ isn't required any longer, not sure why.
Click to expand...
Click to collapse
The issue is that I need to use sudo to execute the command fastboot. Since it's sudo it doesn't have the proper path, hence the need to add the ./
Hey everyone, was hoping for some help here. Just sold my 6P and need to return it to stock and relock bootloader. I had no issues flashing all stock images but when I go to issue the command "fastboot flashing lock" I get this http://hastebin.com/iqideleloy.xm Not sure why this is happening but any insight would be appreciated, thanks.
Triscuit said:
Hey everyone, was hoping for some help here. Just sold my 6P and need to return it to stock and relock bootloader. I had no issues flashing all stock images but when I go to issue the command "fastboot flashing lock" I get this http://hastebin.com/iqideleloy.xm Not sure why this is happening but any insight would be appreciated, thanks.
Click to expand...
Click to collapse
That means your adb/fastboot isn't up to date, it doesn't recognise the command.
Heisenberg said:
That means your adb/fastboot isn't up to date, it doesn't recognise the command.
Click to expand...
Click to collapse
Thanks for the reply Heisenberg. I had a feeling that was the issue so I updated everything on my Ubuntu machine and its still not working. I have an older windows laptop that I'm going to try on next. I have a feeling there are leftover bits of the old adb/fastboot.
Triscuit said:
Thanks for the reply Heisenberg. I had a feeling that was the issue so I updated everything on my Ubuntu machine and its still not working. I have an older windows laptop that I'm going to try on next. I have a feeling there are leftover bits of the old adb/fastboot.
Click to expand...
Click to collapse
How did you install adb/fastboot on Ubuntu? If you're using the package that is in their official repos it won't update properly, you need to download the SDK package and install it that way.
Heisenberg said:
How did you install adb/fastboot on Ubuntu? If you're using the package that is in their official repos it won't update properly, you need to download the SDK package and install it that way.
Click to expand...
Click to collapse
Yea, that's how I updated. I'm not sure, I will try the other method and let you know.
Triscuit said:
Yea, that's how I updated. I'm not sure, I will try the other method and let you know.
Click to expand...
Click to collapse
Grab this zip:
https://dl.google.com/dl/android/studio/ide-zips/2.1.3.0/android-studio-ide-143.3101438-linux.zip
Create an SDK folder in your /home directory and extract the zip there. Once extracted open the tools folder and then run the Android program (this is the SDK manager). Install the platform-tools package and now you'll see a platform-tools folder in the SDK folder that you extracted the SDK zip into. Within this platform-tools folder are adb and fastboot. You need to open a terminal window from within that platform-tools folder (right-click, select open in terminal), then prefix any command with "./" so that it's using the fastboot within that directory and not the Ubuntu one. So the commands would be like this:
Code:
./fastboot devices
Code:
./fastboot flashing lock
Heisenberg said:
Grab this zip:
https://dl.google.com/dl/android/studio/ide-zips/2.1.3.0/android-studio-ide-143.3101438-linux.zip
Create an SDK folder in your /home directory and extract the zip there. Once extracted open the tools folder and then run the Android program (this is the SDK manager). Install the platform-tools package and now you'll see a platform-tools folder in the SDK folder that you extracted the SDK zip into. Within this platform-tools folder are adb and fastboot. You need to open a terminal window from within that platform-tools folder (right-click, select open in terminal), then prefix any command with "./" so that it's using the fastboot within that directory and not the Ubuntu one. So the commands would be like this:
Code:
./fastboot devices
Code:
./fastboot flashing lock
Click to expand...
Click to collapse
Thanks very much, this is just about what I did, but I will try it!
Triscuit said:
Thanks very much, this is just about what I did, but I will try it!
Click to expand...
Click to collapse
No worries, let me know how you go.
Heisenberg said:
No worries, let me know how you go.
Click to expand...
Click to collapse
Well I ended up using a windows laptop that has never had adb/fastboot installed on it. Followed your guide to the word.....and boom locked bootloader. Thanks for the help Heisenberg.
Triscuit said:
Well I ended up using a windows laptop that has never had adb/fastboot installed on it. Followed your guide to the word.....and boom locked bootloader. Thanks for the help Heisenberg.
Click to expand...
Click to collapse
Cool, glad you got it done.