Related
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
THANHVO31 said:
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
Click to expand...
Click to collapse
That link you posted doesn't use my same ids
Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
EDIT: and I made a huge mistake and i had not put in the bootloader (FIREFIREFIRE) on my bricked kindle, however, I took extra precaution and put it on my working kindle and to prevent it even further I am not using any roms and only using GoLauncher EX, googleframework, Superuser(root), and Market
as some roms are unstable and ALWAYS have a problem that something is not working correctly!
umarsl said:
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
Click to expand...
Click to collapse
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Th3-Chronikk said:
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Click to expand...
Click to collapse
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\Vid_1949&Pid_0006&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006
Click to expand...
Click to collapse
And try again.
Goodluck
THANHVO31 said:
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
And try again.
Goodluck
Click to expand...
Click to collapse
Didn't work
Th3-Chronikk said:
That link you posted doesn't use my same ids
Click to expand...
Click to collapse
The hardware IDs in that link look identical to yours, and I think every other Kindle Fire I've seen. Yours don't look unusual.
I'm having the same damn issue, my 6.2.2 kindle is not recognized by adb. The weird thing is that sometimes it does see the device and then it disappears? The driver ID's that are posted are identical to the ones that are included with KFU.
If anyone figures this out please let me know!
Troy.
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
p-niiice said:
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
Click to expand...
Click to collapse
android update adb
add 0x1949 on its own line to adb_usb.ini in C:\users\<username>\.android\adb_usb.ini
save the file
adb kill-server
adb start-server
adb devices
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
jcc2z said:
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
Click to expand...
Click to collapse
Thanks - doing this plus the hardware ID lines earlier in the thread got me further, but adb still isn't picking up the composite device.
androidcues said:
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Click to expand...
Click to collapse
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
K3nDroid said:
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
Click to expand...
Click to collapse
Interesting that you had such an issue with getting windows to work. I have rooted 2 Kindles(took an hour total to get them set up, rooted, recovery and Gapps installed), Samsung Epic 4g, Multiple Evo 4gs, Optimus M, Hauwei Ascend, and HTC Hero and never had an issue with drivers or having to uninstall them. I am running Windows 7 and each one I plug in it recognizes.
Ok guys I need your help with this question, is there a way to root the Kindle Fire without a computer?
I've tried Z4 root and it crashes after a certain point and never roots and I'm without a computer for a few weeks and badly need to root my Kindle Fire and was hoping to find a solution that could possibly work.Hoping there was a app like z4 root that could be an alternative solution ....Please post your feedback
Thanks in advance!!!
No
Thanks for the info
I haven't tried it and I don't even know if it's possible, but theoretically you could run adb commands from another Android device.
You start an adbd server from within Android but whether it succeeds or not depends on whether or not it can recognize a Kindle Fire on the other end of the tether.
It's worth a shot.
All you need to do is get "su" to /system/xbin and the rest can be done on your own device.
soupmagnet said:
I haven't tried it and I don't even know if it's possible, but theoretically you could run adb commands from another Android device.
You start an adbd server from within Android but whether it succeeds or not depends on whether or not it can recognize a Kindle Fire on the other end of the tether.
It's worth a shot.
All you need to do is get "su" to /system/xbin and the rest can be done on your own device.
Click to expand...
Click to collapse
Interesting thought... I'm not sure it will work though.
You'd have to remount the /system partition as rw to get su on there and that requires root privileges. That's the chicken/egg problem you'd have to overcome.
Whatever the case, the whole experiment would require considerable blurring of the definition of "a computer."
kinfauns said:
Interesting thought... I'm not sure it will work though.
You'd have to remount the /system partition as rw to get su on there and that requires root privileges. That's the chicken/egg problem you'd have to overcome.
Whatever the case, the whole experiment would require considerable blurring of the definition of "a computer."
Click to expand...
Click to collapse
Well, if you have adb on your device and you enter "adb root" from a Terminal, it will start the adbd server as it would on a computer but returns "error: device not found", obviously because it doesn't detect a device connected to the USB.
Presumably, if you had another device tethered to the one you want rooted, you could, with USB debugging enabled, start an adbd server from the first device and "adb root", "adb remount", etc.
The problem with that is the "adbd cannot run from stock devices" garbage. I'm sure there's a way around it though.
[Edit:] Oh and...it was the egg.
Duplicate post. Deleted. Damn XDA app!
soupmagnet said:
[Edit:] Oh and...it was the egg.
Click to expand...
Click to collapse
The point of that is to point out the fact the chicken/egg paradox was only such because at the time of its inception, the answer was unforeseeable.
Code:
</geek>
[Edit:] Besides, who's to say it can't be done with fastboot?
soupmagnet said:
The point of that is to point out the fact the chicken/egg paradox was only such because at the time of its inception, the answer was unforeseeable.
Code:
</geek>
Click to expand...
Click to collapse
That's what the liberal media bias would have you believe!
Interesting how fast this discussion has degenerated from technical to scientific to political.... surely Hitler will come into play within the next couple of posts.
kinfauns said:
That's what the liberal media bias would have you believe!
Interesting how fast this discussion has degenerated from technical to scientific to political.... surely Hitler will come into play within the next couple of posts.
Click to expand...
Click to collapse
Hitler.
Hey, you were right!
Back on topic...If only I had a USB micro to USB micro cable to test it out with...
I think fastboot is the way to go.
soupmagnet said:
[Edit:] Besides, who's to say it can't be done with fastboot?
Click to expand...
Click to collapse
Because fastboot is the egg and by that point the host is in every way a computer but in name. I think we are way off the intent of the original OP which I'm sure was meant to ask if rooting could be accomplished on a standalone device without the aid of another attached to it... and the answer to that is still "NO."
EDIT: soup nazi!
kinfauns said:
Because fastboot is the egg and by that point the host is in every way a computer but in name. I think we are way off the intent of the original OP which I'm sure was meant to ask if rooting could be accomplished on a standalone device without the aid of another attached to it... and the answer to that is still "NO."
EDIT: soup nazi!
Click to expand...
Click to collapse
I must respectfully disagree with you. The intent of the OP is to be able to root without access to a computer that won't be available for a few weeks. The availability of another Android device is exponentially greater.
[Edit:] [email protected] nazi
soupmagnet said:
I must respectfully disagree with you. The intent of the OP is to be able to root without access to a computer that won't be available for a few weeks. The availability of another Android device is exponentially greater.
[Edit:] [email protected] nazi
Click to expand...
Click to collapse
"Exponentially" is reaching a bit, but point taken. He doesn't explicitly exclude the possibility of attaching another android device. I'll concede that point.
However, he does say he tried using some app and asks if there's another app that would do something similar for the Kindle Fire... and that at least implicitly supports my view of the OP.
Whatever the case may be... I don't think this debate needs to go much further. We've already invoked Godwin, so it should have ended already.
kinfauns said:
We've already invoked Godwin, so it should have ended already.
Click to expand...
Click to collapse
I secede to your geekiness
there is a way
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process.
of course it can!
Yes.. just download rootmaster
Of course it can!!!!
thacoolestnerd said:
Ok guys I need your help with this question, is there a way to root the Kindle Fire without a computer?
I've tried Z4 root and it crashes after a certain point and never roots and I'm without a computer for a few weeks and badly need to root my Kindle Fire and was hoping to find a solution that could possibly work.Hoping there was a app like z4 root that could be an alternative solution ....Please post your feedback
Thanks in advance!!!
Click to expand...
Click to collapse
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process.:laugh:
---------- Post added at 02:06 AM ---------- Previous post was at 01:58 AM ----------
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process. Use rootmaster first(the one that is not ceskas,) it will start rooting the device until it gets to 50 percent and says you need to finish the root with te computer.. but when you use the other app.. it finishes the rooting process. But every time you open an app that requires root permission.. it asked for root permission to run the app. Just press the right button when the ceskas menu pops up..( it will be in a different language)[email protected]
This will also work on the s4 and any kindle base platform including hd, hdx, and it should work on the paper white.
I have a Kindle Fire that is stock and was NEVER rooted. It was being used and the user said it told them that the space was getting full. He began to remove apps in order to free up space (he's a novice user) and as he was doing this it rebooted and is now stuck in a boot loop. It will flash the kindle fire logo for a few seconds, screen goes black, etc.
I was able to get it connected and accept adb commands. I first was able to reboot it (./adb reboot) and then see it listed as a device (./adb devices). However, it still wouldn't boot up all the way. I've rooted a number of devices before and work with computers for a living so I'm pretty familiar with what's going on, however I know that every device is different. I looked into the different things to do with a Kindle Fire and decided I should try to push the fbmode app to the kindle. When I tried that I got an error saying:
failed to copy 'fbmode' to '/data/local/temp': No space left on device
Any idea what I should do? I don't really want to root the device if I can just get it to run first. What is the best way to free up some storage so that it might boot again?
UPDATE: I've sent the wipe_data and wipe_cache commands to the KF. The screen kinda turns yellow for a second and then reboots and goes back into a boot loop. I can't seem to find another way to clean up space. Help?
Same here
I'm having the same problem. Did you ever find a solutions?
dawn12123 said:
I'm having the same problem. Did you ever find a solutions?
Click to expand...
Click to collapse
No. I'm still searching or hoping someone else might have an answer.
carlowahlstedt said:
No. I'm still searching or hoping someone else might have an answer.
Click to expand...
Click to collapse
I started a new thread about it. Here is the link:http://forum.xda-developers.com/showthread.php?p=40509965#post40509965
arestspubs
Thanks! Looks like you might be getting somewhere. I'll be anxious to see what you figure out.
Connect it to computer and navigate to Android/data/com.amazon.venezia/cache and delete the entire folder.
This took about 3.51 GB of the Kindle's 4.99 GB of Space!When clearing up after receiving a low storage notification, i saw that the Android folder had over 3 GB so i decided to see if i could clean anything over there.Once I saw that this had 3.51 GB in a cache folder,I googled com.amazon.venezia to see if i could delete it and this post was the first link.:good:Thanks this really helped me a lot and i have no idea why amazon follows this method
Please help me.
I'm trying desperately to root my nans brand new kindle fire hd - software version 7.4.9 so that she can access the google play store for the apps she uses as some aren't available on the amazon store.
I have followed your tutorials to the nth degree, downloaded lots of software on to my computer including kff, and binary versions, but each time I try to root her kindle I get the following errors:
fastboot.exe is not responding
adb.exe is not responding.
I then get the error
The application was unable to start correctly (0xc00005) Click ok to close the application.
I've tried removing all software and rebooting again. I'm trying to use your software package as shown in your tutorial.
The device is showing in device manager as Android Composite ABD Interface
I'm at my wits end I'm just trying to do something to keep her from being bored and lonely and I feel terrible because I said she should get a fire hd as it would be better for her than her previous table that kept freezing. I don't know why its so difficult as I rooted my other two fire hd's last year no problem!
Please please help me, I'd really appreciate it
ladyhthe8th said:
Please help me.
I'm trying desperately to root my nans brand new kindle fire hd - software version 7.4.9 so that she can access the google play store for the apps she uses as some aren't available on the amazon store.
I have followed your tutorials to the nth degree, downloaded lots of software on to my computer including kff, and binary versions, but each time I try to root her kindle I get the following errors:
fastboot.exe is not responding
adb.exe is not responding.
I then get the error
The application was unable to start correctly (0xc00005) Click ok to close the application.
I've tried removing all software and rebooting again. I'm trying to use your software package as shown in your tutorial.
The device is showing in device manager as Android Composite ABD Interface
I'm at my wits end I'm just trying to do something to keep her from being bored and lonely and I feel terrible because I said she should get a fire hd as it would be better for her than her previous table that kept freezing. I don't know why its so difficult as I rooted my other two fire hd's last year no problem!
Please please help me, I'd really appreciate it
Click to expand...
Click to collapse
Did you enable ADB in Security>ADB? Do you have the right drivers? (There's some in the KFFA folder which I'll mention later) You could also try different USB ports, cables, and Kindle Fire First Aide (http://forum.xda-developers.com/showthread.php?t=2096888). Also, I don't know if you're talking about Binary or Bin4ry, but try this Bin4ry Root with Restore. It should work too. (http://uploaded.net/file/a1ycrsqj) You're welcome if I helped.
For some reason it makes me think one of the needed dll's adb comes with is missing, or adb just hates your PC.
OK so: I updated my N7(2013) to lollipop 5.0.1 using the Skipsoft toolkit and now I cannot restore my data from a backup on my windows 7 x64 PC.
The N7 is unlocked, rooted, and running lollipop 5.0.1. A few weeks ago the USB port stopped working due to the well-known physical weakness of the N7's USB socket. Fortunately I had made backups and copied them to my PC (windows 7 x 64 up-to-date) via USB just prior to the failure. The backups were a TWRP nandroid made from recovery, a TiBackup of all the apps and app data, and I copied the entire contents of sdcard (/storage/emulated/legacy) to a folder on my pc via drag-and-drop using explorer. (MTP mode on the N7 seen as "Nexus 7\Internal storage" by windows.)
Prior to sending it in for repairs I deleted all my personal data from sdcard, did a factory reset using TWRP recovery, and verified that the phone would boot into android lollipop 5.0.1. I paid iResQ to fix the port, which they did.
When I got it back, I hooked up the N7 to the PC via USB and attempted to copy the files back to sdcard, by dragging them in the opposite direction using explorer. I did not work. "Nexus 7\Internal storage" is read only! I was unable to change the permission on the N7 using explorer. (Apparently since the hated MTP mode makes the PC think that the N7 is not a storage device with permissions). I tried using adb push (did not work). I tried to change the permissions of sdcard on the N7 itself using root explorer (and ES file explorer and xplorer -- did not work). I tried adb shell followed by su then chmod (did not work). I tried "mkdir test" at the su prompt to see if that would work and was told "mkdir failed for test, Read-only file system".
So how do I restore my apps and data? How do I make "/" read-write? Does lollipop make an N7 into a ROM?
I think I'll go back to kitkat.
--------------------------------------
Some hours later~
I tried removing 5.0.1 and went back to kitkat, Android 4.4.4 (KTU84P). I am able to copy files from pc to sdcard via wireless using an explorer on the N7. Nevertheless, using an explorer on the pc I cannot copy a file from it to the n7 via usb . I don't get it. What is going on here?
----------------------------------------
The next day~
It appears to me that the problem with the MTP transfer from the PC to the N7 is on the PC side. Apparently when I plug the N7 into the PC via USB, a file transfer window is supposed to appear on the PC. It does not.
That does not explain why, however I was completely unable to write (via usb, wireless, adb, or on the N7 itself) to the virtual sdcard when the N7 was on lollipop 5.01 but works with KitKat 4.4.4. Any clues? Anyone?
Amazing. All the people who read this forum and not a one has a clue as to why I cannot write to my N7.
lamoid said:
Amazing. All the people who read this forum and not a one has a clue as to why I cannot write to my N7.
Click to expand...
Click to collapse
Yeah that's gonna make people want to help you.
Since you seem wholely incapable of searching for yourself, here you go- http://forum.xda-developers.com/showthread.php?p=56720490
Maybe you did not want to, but you did help me _MetalHead_. Thank you.
lamoid said:
Maybe you did not want to, but you did help me _MetalHead_. Thank you.
Click to expand...
Click to collapse
You're welcome. And I did want to help, but that comment that you posted was rather rude. Next time, instead of acting entitled, a simple "can anyone please help?" would have sufficed.
Anyways... I take it you got it fixed?
I agree that was rude. And I apologize for it. However, on 18 January, I asked after not getting any responses, "Any clues? Anyone?" I checked for a response every day after that and by the 30th was rather frustrated at not having received one. Also I had searched the board extensively and could not find anything like my problem. Clearly I did not use the correct keywords or I would have found the page you pointed me to.
I don't know if that will solve the problem because I need to try to install the upgrade again then try it. Which I will soon.
Nevertheless I do greatly appreciate you for having helped me _MetalHead_ despite the rudeness of my request.
lamoid said:
I agree that was rude. And I apologize for it. However, on 18 January, I asked after not getting any responses, "Any clues? Anyone?" I checked for a response every day after that and by the 30th was rather frustrated at not having received one. Also I had searched the board extensively and could not find anything like my problem. Clearly I did not use the correct keywords or I would have found the page you pointed me to.
I don't know if that will solve the problem because I need to try to install the upgrade again then try it. Which I will soon.
Nevertheless I do greatly appreciate you for having helped me _MetalHead_ despite the rudeness of my request.
Click to expand...
Click to collapse
No worries man, I understand how frustrating it can be, especially when the life of your cherished Nexus 7 hangs in the balance. Keep me posted if you get it worked out or not.