I have two Nook Colors auto-nooted with 1.0.1 and both are running fine. I used my Nook to install the Android SDK on my computer and enable Nook USB ADB. ADB is working great for my NC and I can do everything in the command line that I want.
However, I plug my brother's NC (rooted and worked like mine) into my computer and it doesn't show up in ADB ("adb devices"). I even tried rebooting, shutting down and restarting the Android SDK. I'm a noob and I'm wondering is there a setting in the SDK that only allows one Android device based on serial number to be connected with the SDK?
Hi,
I bricked my kindle after I accidentally used an app for a different Kindle. It boots up with the orange logo, then blue artifacts flash and it goes blank.
I purchased a Factory Cable from ScOrPn and it boots up into flashboot mode. At first, it installed the wrong driver entitled "adb interface device" or something. Adb wouldn't recognise it. I uninstalled the first driver, and I replaced it with a driver which had worked for me previously entitle "Adb composite interface device" <not exactly but it's the composite part that's important, I think. Anyway, I thought that would fix it but it doesn't. Adb doesn't recognise it so I can't unbrick it. Any help would be greatly appreciated.
Things that I have tried:
Installed composite interface driver
Kill-server
EDIT: Hi, after reading for several hours I installed KindleFireAide and it seems to be doing the job.
no adb recognition
Neither the standard cable works for kindle fire hd KFFA (kindle fire hd first aide) it does not find path since adb is not recognizing the unit and using homemade factory cable still does not recognize it . Unit starts system recovery and reboot but fail each time. KFFA path not found while running program. Any ideas?
I rooted ages back, and it always connected to my PC normally, no problems.
I flashed CM10.1 to it the night before last - had some difficulties and have to push the ROM to the bootlooped Kindle Fire HD. had to reinstall some drivers also - Under Kindle Properties > HArdware > Device Functions, it's listed as Android ADB Interface.
The Kindle recognises it's connected (Connected as media device), and my Computer recognises it's there (Safely remove hardware and Eject Media icon is in the bottom right taskbar).
The problem is it's not showing up under devices - do I need to replace my drivers again?
---------------------
FIXED:
Just go to properties > Driver > Update Driver... > Sorted!
So here's the situation; I don't want CM on my Kindle Fire HD 7 anymore.
I thought I had a backup, but after applying that backup from TWRP, I get a reboot (orange/blue/orange/TWRP).
I've installed adb on my PC, as well as SDK tools etc - ADB is running succesfully. I've installed latest drivers from someone's sig (thanks to that guy btw! )
I just want to get back to stock, then reroot (to have google play).
- ADB works
- Kindle Fire HD 7 is recognised when in TWRP
-have the file i want to push in platofrm-tools folder, named "kindleupdate.zip" - it's stock amazon firmware.
What am I doing wrong? When pushing the file, I just get the list of commands in the cmd interface (explaining adb etc). So I know it's working. I've tried using this in both ADB sideload feature and without. Any hints?
Thanks guys.
When you push using ADB, you have to use the source location and the destination in your arguments. Example:
Code:
adb push "C:\Some Folder\update.zip" "/sdcard/some folder/update.zip"
Where the first argument is the file on your PC, and the second argument is the location on your Kindle.
And if you want to go back to stock, use this. It comes pre-rooted with the OTA updates disabled.
>>Sent from my homebuilt TARDIS running Android 4.0.3... or maybe it's a rooted Kindle Fire HD<<
Hi all,
I'm new here, and I've been trying for the past few hours to root my Kindle Fire HD 7" so I can install a CM10.1 ROM and turn it into a google tablet. I've been searching the web for information, and I kept getting directed here so I decided I might as well join.
Anyway it seems the one method that works is the Bin4ry one, and I started following the instructions given on this site and others. However when I installed the driver, it said the installation was successful but when I clicked "Finish" a window popped up and told me the driver didn't install properly. Then I tried to execute the "Run Me" file, but it gave me this:
"Please connect device with enabled USB-debugging to your computer.
the system cannot find the path specified
doing a backup first, please confirm this on your device
the system cannot find the path specified
Done!"
Nothing happens on the Kindle Fire. But I checked the Device Manager, after I downloaded and installed a driver linked in a thread on this forum, it said the Kindle was USB-enabled interface. Anyone have any idea what the problem is, here? Thanks
Ok did you enable usb-debugging in the kindle's security settings? If you have try opening a command prompt and CD into the directory of the adb command in binary's root tool, run adb devices and see if the kindle is listed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok did you enable usb-debugging in the kindle's security settings? If you have try opening a command prompt and CD into the directory of the adb command in binary's root tool, run adb devices and see if the kindle is listed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yep, USB-debugging is enabled. It's the same thing as enabling ADB, right? This is what I've done thus far. I'm running Windows 8, so I've disabled driver signature enforcement, and also installed the drivers. I've checked Device Manager---the system has recognized the Kindle as a Google Android ADB interface, and if I check adb devices in cmd prompt, the serial number of my Kindle is listed. Also created an adb_usb.ini file according to these instructions:
"open adb_usb.ini with notepad
(add on one line each!)
0x1949
0x006
save file."
The problem now is not that nothing happens on the Kindle when I run the root tool, I do get the option to restore data but it prompts me to enter a data encryption password. I researched this and a techleopard article said to enter my Amazon password, which I did but nothing happens. The data restore options (Restore or Do Not Restore) just grey out and the root tool just says "Running" for ever and ever. Tried some other root tools such as Quemp and Kindle Fire Utility, but neither worked and besides the more recent information I've seen have Bin4ry's as the only one that works on 7.4.6 which is the OS I am using.
EDIT: Okay, tried it again and for some reason this time the root tool ran successfully. I did a power reset, and ran a RootChecker, and it says it's rooted but I can't find the SuperUser app (the checker also could not find it). Was the root still successful?
Probably though I am throwing a guess that only the such binary is installed, look in the /system/xbin folder and see if the such binary is there, if you want to to retry the process just delete that file. I was going to mention the encryption password is whatever your lock screen code is set to.
BTW don't ever use kfu to try to root your kindle, it will hard brick it. Its designed only for kf1's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Probably though I am throwing a guess that only the such binary is installed, look in the /system/xbin folder and see if the such binary is there, if you want to to retry the process just delete that file. I was going to mention the encryption password is whatever your lock screen code is set to.
BTW don't ever use kfu to try to root your kindle, it will hard brick it. Its designed only for kf1's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Heh, actually after a LOT of messing around, and perusing several articles across the web and on xda, I've got it working. KFU didn't brick anything, just didn't work. My only regret is that I now can't access the HD quality movies I'd bought from Amazon because Amazon only allows downloading to the Kindle and the Kindle only, and my internet isn't fast enough to stream HD.