Can 7.15 Be rooted? - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Trying to use Qemu to root a kindle fire hd but I'm not having any luck (adb device not found..." . The adb drivers are installed and the setting to allow adb is checked on the device itself. Is there anything I could possibly be doing wrong? Or is the tool not compatiable with the 7.15 update

this tool is fully compatible with 7.1.5 update.
You should re-check if adb drivers installed.
Then switch-on adb on kindle and be shure new device (smth like "android adb device") appear at your windows device manager.
Then you can start Qemu

kashei said:
this tool is fully compatible with 7.1.5 update.
You should re-check if adb drivers installed.
Then switch-on adb on kindle and be shure new device (smth like "android adb device") appear at your windows device manager.
Then you can start Qemu
Click to expand...
Click to collapse
Uninstalled and reinstalled several times, tried on windows 8 windows 7 and xp. no luck

I cant remember how I got mine to work. but after hooking it in i uninstalled the adb drivers and re installed to get it recognized

Related

unlocking bootloader panic

I can't get the adb devices to recognize the device and tried everything.can someone please walk me through this so I can root?
This?
http://forum.xda-developers.com/showthread.php?t=613217
And this?
http://forum.xda-developers.com/showthread.php?t=636795
Is not enough?
tried both of those step by step to no avail. im running windows xp 64. in the device manager under android phone it says "android composite adb Interface" when i plug my phone in. installed the drivers and uninstalled the 50 times still when i open up cmd i get nothing listed when i type in adb devices. anything im missing? im in debugging mode and ive installed the drivers many times, im done it with sdk setup running and with it not running. cant get this crap to work
Some ADB help
flabinall said:
tried both of those step by step to no avail. im running windows xp 64. in the device manager under android phone it says "android composite adb Interface" when i plug my phone in. installed the drivers and uninstalled the 50 times still when i open up cmd i get nothing listed when i type in adb devices. anything im missing? im in debugging mode and ive installed the drivers many times, im done it with sdk setup running and with it not running. cant get this crap to work
Click to expand...
Click to collapse
Check the path in your CMD, the androidsdk needs to be in that path to have adb access. Unless you changed your path values, but it should go something like this(users/nameofuser/documents and settings<). If your path is like that, then your SDK folder needs to be in the folder @ the end of that path or whatever path you have set in your CMD. Also did you run the android.exe and update your SDK. Get back to me and let me know exactly where your @.

[Q] Adb working with one Kindle, but not the other

I have 2 Kindle Fire 2nd generations. I'm trying to root them. So far, I have successfully rooted one, using qemu, and Bin4ry's Root as laid out here: http://forum.xda-developers.com/showthread.php?t=2075959 . In order to be successful with this, I already have the drivers installed, and the SDK for this. I have already made sure that ADB was enabled on the device, but it is not being detected when trying "adb devices" from the command line. I have also already tried to kill-server, and start-server, I've rebooted both the Kindle, and the PC. Also, my PC is running Windows Vista. My computer detects both devices as a Kindle, and I am able to transfer files to and from both devices fine. The only apparent difference between the 2 is that adb will detect one fine and not the other. When I run "adb devices" with my other Kindle connected, it detects that one just fine. If anyone can help, I'd really appreciate it!
Chr0nos77 said:
I have 2 Kindle Fire 2nd generations. I'm trying to root them. So far, I have successfully rooted one, using qemu, and Bin4ry's Root as laid out here: http://forum.xda-developers.com/showthread.php?t=2075959 . In order to be successful with this, I already have the drivers installed, and the SDK for this. I have already made sure that ADB was enabled on the device, but it is not being detected when trying "adb devices" from the command line. I have also already tried to kill-server, and start-server, I've rebooted both the Kindle, and the PC. Also, my PC is running Windows Vista. My computer detects both devices as a Kindle, and I am able to transfer files to and from both devices fine. The only apparent difference between the 2 is that adb will detect one fine and not the other. When I run "adb devices" with my other Kindle connected, it detects that one just fine. If anyone can help, I'd really appreciate it!
Click to expand...
Click to collapse
Are you using the same cable?
Try going to the computers device manager and disabling the kindle uninstalling the driver reinstalling it then reenable the kindle. then try adb devices and see if that works
I am using the same cable. I reinstalled the drivers by uninstalling, and reinstalling in device manager. It worked thank you! I'm surprised that it had to be reinstalled for an identical device, but I'm happy it worked. Sorry about the slow response, I've been busy the last couple of days. Again, I really appreciate the help!

can't install drivers on win7 or win10

i've tried all suggestions to install the drivers and when i connect my fire to my computer, it shows up as portable device > fire. if i try to update drivers, it says that i am already using the best one, the MTP usb device.
i've followed this:
http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
and also tried the drivers from amazon and neither allow me to select the adb driver.
You have turned adb on on the Fire?
Pond-life said:
You have turned adb on on the Fire?
Click to expand...
Click to collapse
thanks for the reply.
yes, i put it in dev mode by tapping the serial numbers and it is adb enabled.
ultraman69 said:
and also tried the drivers from amazon and neither allow me to select the adb driver.
Click to expand...
Click to collapse
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
thekrakah said:
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
Click to expand...
Click to collapse
ultraman69 said:
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
Click to expand...
Click to collapse
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
thekrakah said:
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
Click to expand...
Click to collapse
for some reason, on only one out 4 of my win 10 rigs, i had to turn off driver signature enforcement. to do this go to settings, update and security, recovery, advanced startup, restart now. then in the restart menu push, troubleshoot, advanced options, startup settings, then restart. when booted choose "Disable driver signature enforcement" (which is option 7 on current build). now try to install the drivers. after successful just do a normal restart to enable the signature enforcement again
ultraman69 said:
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
Click to expand...
Click to collapse
Can you verify that, "android debug" mode is turned on in the Fire devices developer settings? At least that was the only way I could reproduce the same message output from "adb devices".
I faut with my win 7 laptop for about an hour with one of my fires. Has the yellow icon on unknown device. Ended up "update driver" "browse for file" "let me choose from a list" picked Android/adb composite device. Adb and fast boot now work. I originally had to install Android studio and some extras to get my first fire to link up. Pm if you need help.
Sent from my Nexus 6P using Tapatalk
I recommend RootJunky tool, does everything and gives you instructions what to dohttp://www.rootjunky.com/amazon-fire-5th-gen-supertool/ Also recommend watching all his videos https://www.youtube.com/watch?v=sVv1D_LNLTg&feature=youtu.be

[SOLVED] Please Help! Can't get fastboot to recognize device, but adb does

Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?
Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse
mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!

Request Driver for ADB Detection CMD for NOKIA 8

I have a problem after updating to latest June Security patch for Nokia 8 TA-1004. I had installed driver long time ago when I wanted to obtain root and there I did it. However, after updating to latest patch which also causes to lose root, I couldn't get my phone to detect adb in cmd. I tried reinstalling driver but still not working. USB Debugging is also on. What could this be the problem? I need help. I want to obtain root back. Thank you very much in advance.
Is your adb up to date? I'm using the latest version of Minimal ADB and Fastboot with bundled driver from my TA-1052, works like a charm.
Get that fork of ADB and Fastboot and use it straight out of cmd :
https://developer.android.com/studio/releases/platform-tools
Rakaloah said:
Is your adb up to date? I'm using the latest version of Minimal ADB and Fastboot with bundled driver from my TA-1052, works like a charm.
Click to expand...
Click to collapse
I've got ADB drivers installed and the N8 is correctly detected as a fastboot device when in "Download mode", however I cannot flash anything, most likely because "adb devices" does not show any device (it is correctly shown when fully booted up). So I'm guessing it's a driver problem...and the problem is that I cannot install the bundled drivers, either on my Win10 (the setup.exe doesn't do anything) laptop or my old W7 laptop (error). Can anyone help ? Thanks !
webvan said:
I've got ADB drivers installed and the N8 is correctly detected as a fastboot device when in "Download mode", however I cannot flash anything, most likely because "adb devices" does not show any device (it is correctly shown when fully booted up). So I'm guessing it's a driver problem...and the problem is that I cannot install the bundled drivers, either on my Win10 (the setup.exe doesn't do anything) laptop or my old W7 laptop (error). Can anyone help ? Thanks !
Click to expand...
Click to collapse
Have a look at my post: https://forum.xda-developers.com/showpost.php?p=78074773&postcount=67
Thanks.

Categories

Resources