[Q] Kindle Fire HD - No ADB? - 7" Kindle Fire HD Q&A, Help & Troubleshooting

i just got a Kindle 7 HD (7.3.0)...tried installing the ADB drivers several times, seemed to work OK, but i still have an error with the MTP driver....trying to use KFFirstAide64, but every time i try to run an option i get "The System Cannot find the Path Specified" ...the Kindle is also not visible at all using Windows Explorer
i eventually used "Root_with_Restore_by_Bin4ry_v17", and think i have Root (according to SuChecker: "Congratulations!! This Device has Root Access!), but still can't use ADB and KFFirstAide64 to do anything else...keep getting "The System Cannot find the Path Specified"
following the instructions here: http://forum.xda-developers.com/showthread.php?t=2069117
what am i missing?
using Win7 x64

phunzoid said:
i just got a Kindle 7 HD (7.3.0)...tried installing the ADB drivers several times, seemed to work OK, but i still have an error with the MTP driver....trying to use KFFirstAide64, but every time i try to run an option i get "The System Cannot find the Path Specified" ...the Kindle is also not visible at all using Windows Explorer
i eventually used "Root_with_Restore_by_Bin4ry_v17", and think i have Root (according to SuChecker: "Congratulations!! This Device has Root Access!), but still can't use ADB and KFFirstAide64 to do anything else...keep getting "The System Cannot find the Path Specified"
following the instructions here: http://forum.xda-developers.com/showthread.php?t=2069117
what am i missing?
using Win7 x64
Click to expand...
Click to collapse
You should have read more.
Go here and follow the instructions. http://forum.xda-developers.com/showpost.php?p=38409721&postcount=1018

Guardian10 said:
You should have read more.
Go here and follow the instructions. http://forum.xda-developers.com/showpost.php?p=38409721&postcount=1018
Click to expand...
Click to collapse
Took me forever to get the ADB working. Course, I refused to read instructions, and was working under the premise that ADB stood for A Drink Before.

A Drink Before.......

Guardian10 said:
You should have read more.
Go here and follow the instructions. http://forum.xda-developers.com/showpost.php?p=38409721&postcount=1018
Click to expand...
Click to collapse
thanks for pointing that out :silly:...i actually had gone through those steps, BUT, i just realized i had used the wrong folder name...i had "KFFirstAide64" instead of "KFFirstAide" ...KFFirstAide seems to be OK now :good:
anyone know why i have the yellow triangle next to MTP under "Other Devices" in Device Manager, and why the Kindle is not showing up in WIndows Explorer?...anyway to manually get the MTP driver installed properly?...at least the ADP drivers seem to be working

phunzoid said:
thanks for pointing that out :silly:...i actually had gone through those steps, BUT, i just realized i had used the wrong folder name...i had "KFFirstAide64" instead of "KFFirstAide" ...KFFirstAide seems to be OK now :good:
anyone know why i have the yellow triangle next to MTP under "Other Devices" in Device Manager, and why the Kindle is not showing up in WIndows Explorer?...anyway to manually get the MTP driver installed properly?...at least the ADP drivers seem to be working
Click to expand...
Click to collapse
Do you use a Windows 7 N Version? Try this : link

Related

[Q] Stuck in *Daemon Started Successfully* during ROOT

Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
I'm having the exact same problem here.
RooQemu hangs at *Daemon started successully* and nothing happens
when I try to enter "adb shell" in a cmd i get the error "device not found"
Kindle is shown correct in device manager as "Android Composite ADB Interface" and I can transfer files via explorer without problems.
Windos 7 64 bit and Kindle from amazon Germany Version 7.2.1_user_2040020
Tried on my Laptop and my PC, both with the same result.
At least someone seems to have the same problem as I do. Hope someone comes up with a solution. I tried the steps mentioned above, same result...
spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
Thanks man..
unfortunately, it didn't work for me..
i think it might be something with the drivers since it keeps telling me that the install didn't work correctly..and i need to "manually install it".
Any more ideas?
Thanks everyone! :good:
retroflashbacks said:
Thanks man..
unfortunately, it didn't work for me..
i think it might be something with the drivers since it keeps telling me that the install didn't work correctly..and i need to "manually install it".
Any more ideas?
Thanks everyone! :good:
Click to expand...
Click to collapse
Try this. Install the Android SDK in your computer reboot your kindle and the computer and try again. It worked for me
Darn..still not working...
This problem is due to the drivers!
You need to uninstall the drivers in the device manager, and manually install the drivers from the location you install the ADB drivers.
In my computer, the location is "C:\program files\amazon.com\kindle fire\drivers".
The wrong driver is like this: ”Android ADB Interface“
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And the correct driver is like this:
retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
retroflashbacks said:
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
Click to expand...
Click to collapse
Try to do what PMcHargue explained, it didn't work for me but who knows? Locate the adb_usb.ini file and insert the last line.
PMcHargue said:
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
retroflashbacks said:
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
Click to expand...
Click to collapse
Hey! I'm the one that had the same problem as you.
I tried everything... Then I installed Android SDK and followed this guide:
groovypost . com / howto / kindle-fire-hd-connect-adb-debug
Then it worked.
Hope that helps!
spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
I had the same problem but I did this bur turned my wifi off before step 2. The device appeared with a caution sign next to it in the device manager (no driver installed) but the adb commands started to work and I could root my kindle. Hope this works for you.
Sent from my KFTT using xda app-developers app
It didn't work for me with the drivers in this post, it worked using the Amazon drivers from Android SDK.
retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
What worked for me was to download the android SDK into the root folder of the PC...OR C: If you like....I still found that after every step I had to unplug the device and re-plug it (Is that a word) to continue as the device wasnt found. Im now told ADB tools works better? Gotta have another go since Super user didnt get root access....Guess were on the same journey!
I have the "Android ADB Interface" and not the Composite one and its worked fine for me
thanks alot mate ...
i have windows 8 and faced same problem ...
i did what u said n the root method worked like charm..
thanks again
spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
x64 problem?
I'm having the exact same issue, 'daemon started successfully' I think it has something to do with my OS being x64. I kpet the Task Manager open, and it seems like it opens up 2 adb.exe *32 at once. I tried closing one, and the program would continue. I'm using an Intel x64, and I noticed that the only drivers in the Amazon.com folder were *386, and AMD64. I'm not sure if AMD64. Not sure if this added info is relevant, since the original driver is prior to these directories. I hope an easier method evolves.
Update ... I tried downloading the android sdk, then copied the adb.exe over to the Root\stuff folder and it worked! once you copy the adb.exe, just follow the original OP's instructions.
Eu quero meu root

Help- Accidental No OS on Kindle Fire HD7

Hello all.
Was tinkering around with my KF- And accidentally wiped everything from my internal storage and system. When it boots up I get the blue KF logo and it stays stuck there- Can't boot into recovery.
ADB doesnt recognize it.
Have a fastboot cable.
How do I atleast push files to it /boot into recovery??
Many thanks.
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
SilverRoxas said:
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
Click to expand...
Click to collapse
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
LinearEquation said:
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
Click to expand...
Click to collapse
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
SilverRoxas said:
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
Click to expand...
Click to collapse
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
LinearEquation said:
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
Click to expand...
Click to collapse
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
SilverRoxas said:
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
Click to expand...
Click to collapse
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
LinearEquation said:
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
Click to expand...
Click to collapse
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
SilverRoxas said:
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
Click to expand...
Click to collapse
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
SilverRoxas said:
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
Click to expand...
Click to collapse
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, my Kindle is still recognized.
i dont os on my kindle fire hd 7
I am having a mare with my kindle fire hd 7
It all starrted when anything google related kept crashing.
I tried to find solutions to the problem but no joy.
I then tried to install a different update to cyanogenmod nightly software but i then had a major problem with not being able to turn on my wifi.
I went into Twrp and tried to restore to my previous software but when my kindle re-booted i got stuck with a flashing teamwin logo
After trawling for days i managed to get out of that but im now in a situation where i dont have any OS on my kindle.
I have followed instructions on how to push files onto my kindle but despiote finding some files on my sdcard i am unable to reboot past the blue and white Kindlefire logo.
I have tried using the kindle un-brick java option but no joy either
I would really appreciate some help solving this proble as it is really driving me crazy.
I can still access twrp and i can access bootloader to get the orange and white fastboot logo.
If someone can help guide me through how i can get my kindle working again id really appreciate it
cheers
JJ
Might be able to help.
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Hey Danny101
Danny101 said:
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Click to expand...
Click to collapse
Thanx for your response.
Sorry its taken me a while to reply but have had loads going one recently.
Shortly after making my post i did find that exact same youtube vid tutorial and was able to solve my problem.
I just wanted to say thanx for taking time to respond even so.
All the best.
JJ

[Q] Kindle Fire HD Stuck Booting on TWRP Instead of Android

I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
GogoplataMMA said:
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
Click to expand...
Click to collapse
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
stunts513 said:
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
Click to expand...
Click to collapse
Now I'm all screwed up. Before I saw this message, I restored my Kindle back to when it was still running the factory default OS with root, then I shut it down to enter TWRP, and it appeared on its own, but it was installing some sort of update... and when the Kindle's factory default OS appeared, my root was gone. Now I am stuck on the factory default Kindle HD 8.9" on System Version 8.4.8. Man, I should have never accepted that update and just left it as it was. Ugh. Well, for right now, there's an entry in my Device Manager that says "Kindle Fire" and when you click the arrow to bring down the submenu, it says "Android ADB Interface." The Kindle is now working when connected through USB. Now... how do I go about rooting this thing and getting TWRP on it again, because it seems the entire thing got erased. Not having my ROM installed on this thing makes it mostly useless to me.
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I can't find anything. Download links are dead for KFFA. You have a link to get it through another source?
They are up and running when I click em. You were on this thread right?: http://forum.xda-developers.com/showthread.php?t=2096888
If that doesn't work you can always use binary's root.
http://forum.xda-developers.com/showthread.php?t=1886460
Use the old normal method if I remember correctly.
Sent from my Amazon Kindle Fire HD using Tapatalk
Nah, the link is dead here. Says the file was removed. There are other members in the forum asking as well for a new link.
I managed to get ADB working, and in Device Manager, I have "Android Device -> Android Composite ADB Interface."
I open CMD and type "ADB" and it scrolls a bunch of stuff, but when I type "ADB Devices" I get a list with nothing there. It's just blank.
I tried using BIN4RY Revision 33, using Option #1, but it just keeps bringing me to a "Path not Found" error of some sort.
It looks like all I need to manage to do now is get ADB to list my Kindle device before attempting the ROOT, but how can I do that?
I still wanna give KFFA a try, but no downloads anywhere, and I don't trust random 4Share and the likes, not that it's gonna fix my problem.
I'm close... I just need this damn ADB to list my Kindle device and I think I'll be okay.
Also, I want to say thanks for the help you've given me so far. It's greatly appreciated. :highfive:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb kill-server
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
i.imgur.com/gZrrqXm.jpg
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
GogoplataMMA said:
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
Click to expand...
Click to collapse
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, that didn't work. I'm pretty sure one or more of my drivers are interfering with the connection to the Kindle, but this is such an old OS with so many drivers, it's hard to tell.
Right now, I have a Virtual Machine of Windows 7 up. I plugged my Kindle in and I can instantly see it. I can even enter the internal storage! I'm currently installing the Android SDK for the ADB after installing the Java SE x86 version. Once I get ADB on it, I'll see if it lists my device now. Seems promising since the VM sees and allows me to already enter the internal storage, unlike my original Win7 OS.
EDIT #1: Great news! ADB now lists my device! Thing is... Root with Bin4ry Revision 33 does not seem to want to work. This is what I get...
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (14.12.2013) v33 =
======================================================================
Device type:
0) Xperia Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
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!
Press any key to continue . . .
Click to expand...
Click to collapse
It doesn't give me a chance to do anything. All of that pops up as soon as I press enter. ADB and third party software is enabled on my Kindle. ADB even reads my device as:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9110232560198 device
Click to expand...
Click to collapse
I'm at a loss now. Any ideas?
EDIT #2: Success! The issue was I was using Root with Bin4ry Revision 33. I should have been using Root with Bin4ry Revision 30. That worked, and I am now ROOT. Mission accomplished. Now the next part of my mission... figuring out how to get TWRP on this thing.
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
Everything seemed to work until I get to Step 3. I'll enter the commands but it tells me that there is no such directory or something. Something about there not being any "stack." Can't recall. I wanted to ask on the thread there but the site isn't allowing me to post there.
adb push stack /sdcard/ is where the issue occurs. Everything else worked.
I'm at a loss, and the comments don't seem to help on that thread. Please tell me there is an easier method of getting TWRP on this thing.
ERROR:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push stack /sdcard
/
cannot stat 'stack': No such file or directory
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
GogoplataMMA said:
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
ERROR:
Click to expand...
Click to collapse
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He's on a 8.9", he just posted in the wrong section. Use the fireflash method from seokhuns tutorial, just don't forget to check the box with red text near it or you will get a nice redscreen brick. Lemme grab a link
Edit: link grabbed! http://forum.xda-developers.com/showthread.php?t=2277105
I used FireFlash, followed the instruction... now I cannot get passed the first "Kindle Fire" logo when I turn the Kindle on. It just freezes at "Kindle Fire" as soon as I turn it on. I can't seem to do anything at all, and it won't connect via USB. Any ideas?
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It's not working... it won't read at all. Device Manager doesn't see the Kindle at all. And yes it is 8.9". I think it may be bricked now. ;'(
And all because of that stupid update... ughhhh. Sucks!
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I switched over to my main Windows 7 OS and did what you said. I connected it and it showed for a brief moment in Device Manager, so I quickly loaded the driver and updated. But wen I type the command you gave me, it says <waiting for device>, so I plug it back in and... nothing. At all. Just sits there at <waiting for device>
I'd try Linux, I have several copies of different OS's, but I'm not very good at working with it or using Terminal... I can try that though, but no clue how I'd get ADB or the Kindle to read on it. :\
And yes, 100% it's the 8.9". The resolution is 1200p.
OK the command has to be run while the device is off and disconnected, once it says waiting for device, plug the kindle in and it should work if the drivers are working. Linux is really easy to use with a kindle, it has the fastboot and adb drivers built in natively, only thing you need is the fastboot command from the Ubuntu repos if you are using Ubuntu, believe they were added to the repo in 13.10.
Sent from my Amazon Kindle Fire HD using Tapatalk

[S] How can I repair /system/build.prop ?

Hello to everyone,
I was looking how to install Amazon Store on my Kindle Fire HD 2012 running CM11, when I noticed that I have to change something in /system/build.prop
I had troubles to edit this file because root privileges, so I copied it to emulated SD, then I edited it and copy again to its original path.
It seems than anything went wrong. The tablet gets stucked with "Kindle Fire" blue logo on the screen.
Notes:
My laptop (W7) doesn't recognize the tablet. ADB drivers are correctly installed (or, at least, it seems it). It tries to install "MTP USB device" but it fails before complete setup.
How can I repair /system/build.prop?
EDIT: Nevermind, I ****ed it up.
I have made a wipe of cache, davik and system with "team Win Recovery Project" and it screwed everything. It looks like it is erased, so I'll try to install a new CM version.
--
I know that I make mistakes writing in English, I'm Spaniard.
elRufo said:
Hello to everyone,
I was looking how to install Amazon Store on my Kindle Fire HD 2012 running CM11, when I noticed that I have to change something in /system/build.prop
I had troubles to edit this file because root privileges, so I copied it to emulated SD, then I edited it and copy again to its original path.
It seems than anything went wrong. The tablet gets stucked with "Kindle Fire" blue logo on the screen.
Notes:
My laptop (W7) doesn't recognize the tablet. ADB drivers are correctly installed (or, at least, it seems it). It tries to install "MTP USB device" but it fails before complete setup.
How can I repair /system/build.prop?
EDIT: Nevermind, I ****ed it up.
I have made a wipe of cache, davik and system with "team Win Recovery Project" and it screwed everything. It looks like it is erased, so I'll try to install a new CM version.
--
I know that I make mistakes writing in English, I'm Spaniard.
Click to expand...
Click to collapse
You can ADB sideboard onto TWRP. Easier than starting over.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
You can ADB sideboard onto TWRP. Easier than starting over.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe it's a noob question, but... how I could do that? I had tried several times to install ADB drivers (W7) and it doesn't install correctly. Installer says that it can't write 0x1949 in users/MYUSER/.android/adb_usb.ini file
elRufo said:
Maybe it's a noob question, but... how I could do that? I had tried several times to install ADB drivers (W7) and it doesn't install correctly. Installer says that it can't write 0x1949 in users/MYUSER/.android/adb_usb.ini file
Click to expand...
Click to collapse
To install the adb driver you need the drivers in my signature. I haven't seen people even messing with the adb_usb.ini file in a while. If you are trying to install it while in twrp and you still happen to see a MTP device then you will need to find a USB composite device in the device manager and if you have more than one, it's simple enough to find the right one, just right click one and goto details and then choose hardware id's, if one has a vid of 1949 then uninstall it and scan for new devices and it should pick it up correctly.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
To install the adb driver you need the drivers in my signature. I haven't seen people even messing with the adb_usb.ini file in a while. If you are trying to install it while in twrp and you still happen to see a MTP device then you will need to find a USB composite device in the device manager and if you have more than one, it's simple enough to find the right one, just right click one and goto details and then choose hardware id's, if one has a vid of 1949 then uninstall it and scan for new devices and it should pick it up correctly.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Right Click>Install (w/ Administrator rights)
My Windows 7 (x64) says "This install metod is not valid for this .inf file"
I tried to install original ADB under Administrator account and it looks like are correctly installed, but after that, my pc detects the Kindle Fire HD on "printers/other (and a picture of a mainframe as icon)", so I don´t have access to internal storage to copy CM11 rom and gapps zip.
Note: I own a fastboot cable, I don't know if it could be usefull in this case.
You don't install my drivers like that... open the device manager and if you see a device with a triangle next to it, right click it and hit update drivers, then point it to where you extracted them and it should install.
Sent from my LG-P769 using Tapatalk
stunts513 said:
You don't install my drivers like that... open the device manager and if you see a device with a triangle next to it, right click it and hit update drivers, then point it to where you extracted them and it should install.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Done! Thank you for your patience explaining something thousand times

Cannot Get Drivers Installed for Windows 8.1 - Manual Installation or SDK

I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.

Categories

Resources