Related
So guys I feel so very stupid right now because I completely did this to myself and I realized what I did after the fact and now I am stuck with a KF that is booting up and then crashing and rebooting after about 20-30 seconds.... I decided that I wanted to have a stock ROM on the fire backup up if for some reason I wanted to go back to that UI. I made a nandroid and then flashed the 6.3.1.zip file that i downloaded from amazon's website. Have you spotted the mistake already? that's right, i forgot to wipe the cache and system and now I have a broken KF.... does anyone know what I can do to recover from this horrific boot loop? perhaps a hard reset of some sort that will erase everything so I can start from scratch? or at least have a stock fire?? thanks in advance for any help, such a n00b mistake....
If you think it helps, I CAN access the "SD" memory but I haven't had success with ADB
If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..
fiddlefaddle said:
If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..
Click to expand...
Click to collapse
Disconnect KF, shut it off, reinstall driver and finally connect the KF to the computer.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
fiddlefaddle said:
If you can reach the sdcard then you should have adb..... AFTER reinstalling the drivers.. try that..
Click to expand...
Click to collapse
Two odd things: I rooted the kindle using this computer, so you would think that the drivers would be fine but for some reason it is not working. I ran the install_drivers.bat from KFU and it installs fine but then if i go back to device manager it says that these drivers "WPD FileSystem Volume Driver" is installed and when I try to install the adb drivers it says that the best driver for the device is already installed which is the WPD FileSystem Volume Driver and if I try to uninstall the drivers, it seems like it doesn't do anything at all. I will uninstall the drivers, disconnect and then reconnect the kindle and then it shows up with the same drivers again! any suggestions? I would really like to be able to use my kindle again...
nschiwy said:
Two odd things: I rooted the kindle using this computer, so you would think that the drivers would be fine but for some reason it is not working. I ran the install_drivers.bat from KFU and it installs fine but then if i go back to device manager it says that these drivers "WPD FileSystem Volume Driver" is installed and when I try to install the adb drivers it says that the best driver for the device is already installed which is the WPD FileSystem Volume Driver and if I try to uninstall the drivers, it seems like it doesn't do anything at all. I will uninstall the drivers, disconnect and then reconnect the kindle and then it shows up with the same drivers again! any suggestions? I would really like to be able to use my kindle again...
Click to expand...
Click to collapse
Uninstall the drivers from device manager first, then run install_drivers.bat
sent from my Nokia 5110
Thought I saw someone else with this problem a bit ago. Found this link. Maybe it will help a bit.
http://forum.soft32.com/windows/Microsoft-WPD-FileSystem-Volume-Driver-bootup-ftopict347023.html
pbailey212 said:
Uninstall the drivers from device manager first, then run install_drivers.bat
Click to expand...
Click to collapse
It's very strange, the install_drivers.bat seems to be installing drivers for a device that it is not associating with my kindle so every time I try to uninstall, it just comes back. It's really strange too because ALL of my computers are doing this... would I be better off if i tried from a linux machine rather than windows? from what I've gathered this default driver is a windows/microsoft substitute for mass storage that it doesn't know what else to do with. Is it possible that even though android is clearly running (even though it is only for a little while) that it is unable to communicate with the computer at all?
this is mostly a bump, not sure if it will work but I still haven't had any luck. I was grounded on my XP machine when it wouldn't install the drivers because they were unsigned... saw a tutorial on how to fix that but it was very confusing and unclear. But if anyone has had this problem or has ANY suggestions I am all ears. The kindle was a christmas gift from my parents and I really wish I had just left it alone now. ("if it ain't broke, don't fix it")
It is really much harder on xp to sort out the driver issue acesss to a machine running at least windows 7 would help you out alot. Otherwise go through the process of downloading the Java development kit and using sdk manager to acquire the platform tools for android 2.3 make sure you grab the Google driver this one is signed .
I have no problem putting the jdk and sdk on my personal computers but the xp machine is my mom's so I'm not going to put those on. I thought there would be no problem if i could have used the install_drivers.bat but that turned out to be a bust. Besides that, I wasn't able to find the kindle in the device manager...
nschiwy said:
I have no problem putting the jdk and sdk on my personal computers but the xp machine is my mom's so I'm not going to put those on. I thought there would be no problem if i could have used the install_drivers.bat but that turned out to be a bust. Besides that, I wasn't able to find the kindle in the device manager...
Click to expand...
Click to collapse
Your last sentence tells me that you might not be sure what you are looking for in the device manager.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
kinfauns said:
Your last sentence tells me that you might not be sure what you are looking for in the device manager.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
I really appreciate your help. I've actually been trying to use your guide to see if there was anything I missed. Unfortunately I've not had very much luck. Honestly I've gotten to the point that I would be willing to pay someone if they were confident that they could fix it and I would even pay the shipping both ways. I just want to try to use a linux box to fix it and if I am still unable to communicate with the device through ADB I would be willing to employ anyone from these forums with enough knowledge that they are confident that they could fix it to do it for me. As long as the price was reasonable, of course, keeping in mind that I could buy a refurbished one from amazon for $160 so paying 70-100 would be outlandish... I bought a new HDD for my pc so I could boot linux (I hate dual boots) and after that comes and I still have no luck I will be seeing if anyone would be interested. It's probably a great learning opportunity as well and would be a great addition to the forums if we know what to do when something like this happens.
What OS were you basing this guide from out of curiosity?
http://forum.xda-developers.com/showthread.php?p=26491884
soupmagnet said:
http://forum.xda-developers.com/showthread.php?p=26491884
Click to expand...
Click to collapse
Thank you so much, this will certainly come in handy! I've actually used Ubuntu 11.04 before and I really liked it aside from a few bugs that I didn't feel like dealing with that eventually led me to switch back to windows. So, hopefully this will be the end all in terms of android/kindle fire issues.
okay so, I finally got a hard drive today for my laptop. Booted up Ubuntu 12.04 and used andadb.sh to install all of the necessary software. However, I am not able to connect to my kindle through adb, even on linux. Is there something I may have done wrong somehow? I used the adb_usb.ini from KFU, I don't know for sure that was correct but soup didn't put a link up on his guide so I made an educated guess. I am amazed that nobody has had this problem before, it seems like a very easy mistake to make, at least it was for me! as always, any suggestions will be greatly appreciated!
Try sudo fastboot devices
I'm sorry is this a command? I'm not very familiar with linux you might need to hold my hand on this one. and I tried to adb devices and nothing was listed, will using sudo fastboot devices make a difference? again, sorry for the ignorance, I will try it, I am just addressing concerns.
What bootloader are you using just give me a refresh of your situation so I don't have to read I'm at work but I can still help ya.
okay so basically I don't have a bootloader or recovery because I was planning on rerooting after reinstalling the stock amazon android, only problem is that I forgot to wipe before installing the OS and now I have a Frankenstein amazon gingerbread which is competing with the ICS i had previously installed on the device and continues to crash after about 20 seconds being on and reboots. I am able to access the sd memory, even when it is rebooting but I haven't had any successful connection using adb. If I had, I would imagine I could just reflash twrp and fff and I would then wipe and install a ROM and be good to go but as of now I just have a constantly bootcycling KF that for some reason has no precedent for repairing.
Shutdown and reboot the phone
ok so my buddy just bought a kindle fire and asked me to go to town on it and make it "look good". i'm new to the whole kindle fire method of doing things. my wife has a nook tablet running cm7, and i have my SGSII skyrocket running cm9. i'm familiar with most things in the rooting process, but not too familiar with twrp ( but understand what it is).
the problem i am having is getting KFU to recognize the KF. i have read the KFFB and all associated threads, i have used the forum search, google, and even youtube but no luck. i have tried 3 different computers and only one of them actually showed the proper device info in device manager. the first laptop is running 64 bit windows 7, ran the install_drivers.bat and everything said it was good but no matter how many times i uninstalled and reinstalled the drivers the KF will not show up. the results did not change whether it was manually installed or not (possibly due to my samsung drivers causing a problem), laptop 2 is running the same configuration, and still the same problems. the 3rd laptop is running 32bit xp and with a manual install the drivers installed and the abd composite driver showed up on device manager under android phone.
so when i plug the KF in the computer recognizes it but when i try to run KFU nothing happens. i tried to run the install_drivers.bat but it comes back as installed fail - unsigned drivers.
so after hours of searching and reading i'm at a loss. is there anything else that i can do?
ok well i got KFU to work on laptop #1. i uninstalled my samsung drivers and all other android drivers i could find, ran the install driver.bat and it worked. seems my drivers from my phone were causing the device manager to not install the KF drivers properly. now to flash away!!!!
I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
self bump, since it's been three or four days with no reply. I could really use advice on this.
In your laptop, when you go to Devices manager, do you see an unknown device? If you try searching online for the appropriate driver through Windows Update, does it find any helpful driver?
CTurmoil said:
I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
Click to expand...
Click to collapse
I was dealing with this on my Win7 rig, and came across some advice that helped. If you have an SD card installed, turn the phone off, remove it and then reboot and connect the phone to the computer. I don't know why it worked for me, but it did.
Good luck to you.
CTurmoil said:
I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
Click to expand...
Click to collapse
Possibly two things download revouninstall to uninstall your drivers it searchs bolth registry and system for left over files (delete them)
I had same problem all I did was use revouninstaller to uninstall old drivers (it scans entire system and registry for left overs. a must.
Then I used these drivers, also when letting your installing drivers (turn internet off) don'lt update them there older, but they work for everyone who does this. If you need a better guide search there is one somewhere but point is use these drivers and don't update them (smile) works with adb everything you won't see a difference these drivers work better. peace.
Drivers------>Samsung Drivers 1.4.6.0 search for 1.4.6.0 drivers samsung fix for more info later
search for revo uninstaller
Whenever I have this problem, I must manually install the driver.
Open device manager.
Go to the unrecognized device that you know is your phone.
Properties and "update driver".
Tell it you have your own driver.
Don't let it "search" for a driver.
Manually point it to the exact driver file you need.
Works every time for me.
I took out the SD card to try all possible solutions posted.
Uninstalled drivers and installed the older versions that one of you linked me to, didn't help.
Tried directing Device Manager to install the driver manually, but I have no idea where to find it. If you have the driver file or at least the name and version, I can get it and use that.
I can't believe how much trouble it is just to hook an android phone to a computer, this happened with my Atrix as well.
Have you tried and different cable ?
So I was having a problem with my laptop recognizing my S3 when connected via USB. The notification would not appear in the status bar that a connection was made, and neither Fedora Linux or Windows 7 would recognize that the device was connected. I tried reinstalling Kies/drivers under Windows, and checking the output of dmesg/lsub on Linux. Nothing.
Did some googling and found this thread that help solve the problem!
http://blog.vacs.fr/index.php?post/...ot-detected-problem-on-Android-Samsung-phones
I found the problem. It was the cable. Somehow, it was severed where the cable connects to the mini-USB connector. I discovered this when the entire mini-USB piece fractured and fell off, revealing the tangled and snapped wires. I went today to AT&T to buy a replacement, and it worked on the first try. I don't know how the cable got damaged like that without being detected, but there we go. Now how do I set a question as resolved?
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Silent Assasin said:
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Click to expand...
Click to collapse
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
wizardknight said:
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
Click to expand...
Click to collapse
Thanks for replying. That's the guide I was using. I can't get into fastboot. ADB commands work. I tried to manually install the drivers (On the computer). Windows 7 says my drivers are up to date. I can't move forward out of mini pooploader (funny name by the way). Any ideas would be appreciated...
I meant to say that I found that thread after being stuck in mini poop mode.
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
Click to expand...
Click to collapse
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
plrusek said:
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
Click to expand...
Click to collapse
I followed your advice. I let mini pooploader run the blue screen with white letters. Once finished, I removed the battery, placed the battery back in and then plugged usb into computer. I then powered the phone up with the same results. I performed this task 11 times with the same results. No black screen and no win 7 driver install. The computer says unknown device. I have tried to install drivers and computers states the drivers are up to date. I have tried different USB ports. I have attempted to install HTC drivers someone posed in this forum as well as the drivers that come with SDK with negative results. I have tried to uninstall the drivers in hopes that windows would install upon recognizing device with no luck.
Any ideas? I really need to get this working. i have not had a phone for a week now
Hi,
I'm having some issues where the MTP driver fails to load. Tried all the obvious stuff and did a lot of reading of forums and stuff but can't find a fix. Could anyone help me to fix it please?
Here's what hardware I have and what I've tried so far:
Tab Pro 8.4 16gb wifi UK model, rooted.
Connected via cable to Dell XPS 17, latest USB drivers installed, win 7 x64.
First of all, I enabled USB debugging and windows installed drivers for all except MTP.
Tried installing the Samsung driver package, same problem. Uninstalled at present.
Installed kies, didn't work, wouldn't even connect to the device. Uninstalled.
Followed the instructions on the wiki but the suite software installs the driver succesfully but then windows won't accept the driver. Tried the workarounds in the wiki but still no luck.
Tried rebooting the tablet and leaving the cable connected.
Tried wiping the cache.
Tried restarting both the tablet and laptop after reinstalling software and drivers, still no luck.
Found several workarounds on my travels, one was a command line for windows to add to usergroup ( it's on the laptop downstairs, will add it to the post tomorrow).
One post said to change a registry entry...really? Tried that, and another registry trick, but still no.
Using the same laptop, I had similar problems trying to flash a custom rom onto an s4, but the CM installer worked first time. I've done a fresh install of win 7 since then.
Can anyone shed any light on this for me please? Is there any kind of workaround? Running out of ideas!
Thanks
Fixed this, well, kind of. Here's a quick rundown of what I did, for people like me who are struggling with connection problems.
I thought I had tried everything, was going to dump the whole thing and then remembered that I'd fixed some previous USB problems (sound card) by doing a clean boot.
First, remove Kies.
The only other thing that is required are the samsung mobile drivers from their website. I tried with and without and this would only work with them installed.
Restart your tablet, make sure MTP is selected.
You can find out how to do a clean boot for you version of windows here.
Leave your device connected via USB cable. Once you have clean booted into windows, windows will attempt to install the drivers from windows update, let it do this. It can take a minute or two to complete. You should then see a green tick in the notification area rather than the dreaded red cross.
If, for some reason, the driver doesn't install first time, you can unplug and then plug back in the USB cable and this should do the trick.
What I did find, is that the connection wasn't consistent, I could restart either my laptop or tablet and then it wouldn't connect, so I'd have to go through the above process again to get it to connect.
Doing this allowed me to flash the Clockworkmod recovery with odin 3.09, but for whatever reason, I was still unable to use the recommended Eimdall suite to flash cyanogenmod.
In the end, I downloaded the CM11 zip file to my tablet (via http) and then used ES file manager to move it to the SDCard root and then clockworkmod picked it up from there.
Also, once CM was installed, there were no connection problems at all, as far as I can see.
Hopefully this will help others in the same predicament.