Related
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App
EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...
perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes
Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.
Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.
Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...
What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.
try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.
Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever
It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.
buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip
No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.
**BUMP**
Anyone care to take a shot??
A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.
soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.
soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.
Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?
Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.
soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....
I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.
That will work. Download Ubuntu 10.4
Basically, when trying to use the KFU from my pc, my kindle got stuck in the dreaded amazon logo because of wrong bootloader setting, and at this point it was still a factory rom with nothing else loaded. Probably what i get for trying @ 3am.
Read the guides here about 200 times, tried all troubleshooting I could find. Still, Windows saw it as an unknown device (DEV_ID 0000) and no reinstall of Google USB Drivers would work. Spent hours trying different suggestions in trying to launch adb commands that wait, then connect the kindle, all to keep falling back to the previous problem ---- Unknown Device. Windows couldn't see it to load the google drivers, and therefore adb could never connect or see it (adb devices)
After reading further, it seemed that my two options were to boot to linux via USB, or get the factory cable. I then decided to try from the mac I have, and when I connected via USB, I saw that it did recognize the device id and didn't detect it as a device id 0000. So I downloaded the Android SDK, and about 20 minutes later, I used the mac apple script to do what I failed to do on windows....and it worked. (load a bootloader, and set the boot mode back to the proper setting)
I don't know what I screwed up in using KFU, but I knew I was hosed when I couldn't get passed the unknown device. Tried second pc, and same problem. Mac fixed it though, but only b/c it could see the device id of the kindle even when it was stuck at the amazon logo while the pc could not.
I'm sure someone understands why ---- I'm curious why the mac could see it and windows didn't. I did have the google usb drivers working before & did verify the detected hardware was seen as dev id 0000. (Windows 7 Pro, x64, all updates vs OSX Mountain Lion all updates), so I am sure it wasn't a driver inf related issue.....
Android is a Unix derivative, as is Linux and Mac. That is why these "see" each other better than Windows.
Sent from my Amazon Kindle Fire using xda app-developers app
Ixthusdan said:
Android is a Unix derivative, as is Linux and Mac. That is why these "see" each other better than Windows.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Well OS wise I knew the origins of each but I guess it's just driver related. Was just very suprised to see OSX be able to see the device ID when in that hung state. Thanks for the reply.
calpha said:
Well OS wise I knew the origins of each but I guess it's just driver related. Was just very suprised to see OSX be able to see the device ID when in that hung state. Thanks for the reply.
Click to expand...
Click to collapse
It isn't driver related. It's, Windows is a POS-OS related.
So, I tried searching for days on how to fix my problem.
A little while ago I rooted my Kindle Fire, and it was great. Then I did something. Not sure exactly what. But It ended up just doing nothing. When I boot up the Kindle it shows the blue and white Kindle Fire logo. Nothing else past that (unless I go to recovery.) Now, my computer doesnt recognize it anymore, even after doing most of the driver updates that people on here have said to do.
I need help, basically, getting it back to normal, so I can give rooting a try again. Now that I know what exactly I am dealing with, I can do this and not screw everything up.
First, the computer says the driver is installed, yet it doesnt recognize it.
Second, (before the driver mishap) KFU said it was connected but the adb was unknown.
Third, I have CWM and I tried to flash the normal Amazon update to bring it back, and it says"it cant open it (bad)".
Now, I would really like some help with this. I'm just at a complete lost.
Now should I put that into command prompt in the adb part? because it just says fastboot is not recognized.
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Now its just not connecting to the computer. I installed Android sdk and everything and its just not working. It says the driver is installed but there was an error because a problem had occurred. Any help? :crying:
As soon as you get tired messing with drivers you can move on to something that works http://forum.xda-developers.com/showthread.php?t=1850038
ManofFishFry said:
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Click to expand...
Click to collapse
I hope u r on windows PC..
first after u set up adb, make sure u install adb drivers that came with kindle fire utility with ur kindle fire unplugged..if u had plugged in kindle fire while doing that, go to device manager and uninstall that device and its driver software and start up from beginning..
keep kf unplugged and install driver..u dont get usb debugging option in stock kf rom..its enabled if u have installed the drivers properly..ur kindle fire appears as android phone in device manager if everything u hav done is correct..
then boot up ur kf..that blue and white kf logo is of firefirefire bootloader..i hope its v1.4a and u see it on right top of the screen..if its stuck there then open command prompt as administrator on ur pc..connect ur kf to pc..type in to cmd
Code:
fastboot devices
if u see something under list of devices attached that will be ur kindle fire(unless some other android device is connected in fastboot mode lol)
Because kindle fire, as far as i know, can only boot into 3 bootmodes(normal, recovery, fastboot) unless u have altered the partition table to install different roms and multiboot ur kindle fire..
if fastboot command is not recognized, try setting the path to where fastboot.exe is present in KFU folder
alternatively u can go to folder where fastboot.exe is located and right click while holding shift and selecting 'open command window here' and fastboot needs to firefirefire bootloader to be installed on ur kindle fire..
also u can try this..
JUST GO TO RECOVERY..twrp has always been a better recovery software than cwm based thing available for kindle fire at least for me..if u go to recovery, ur kf will definitely show up as an adb device..u can change the bootmode using this..just type in:
Code:
adb devices
if ur kf is seen as in recovery then type this in cmd
Code:
idme bootmode 4000
reboot
just report if this worked..
okay well, I deleted all the drivers and started from the beginning. Yet, after running the install_driver.bat I plugged my Kindle in and it still says device not recognized. Now, you how can get adb working? It is coming up as unknown device. Its just seeming like theres something wrong on the kindle part. But hey, what do I know. haha
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
But doesn't that require linux? I have windows 7. Is there something like that for windows?
Thepooch said:
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
This is what I get when I try to install the driver....
To run soupkit all you need is at least a 2 gig usb flash drive ubuntu 12.04 32 bit and universal usb creator. By the way your problem with the driver is you (or how you`re going about it), You would trip if I got on your computer and got it to work or could at least tell you why its not working. that`s why I suggested soupkit if you would of actually read the information I gave you, I wouldn`t have had to tell you twice and you would know that to use it it`s not required to be installed on your computer. But hey catch me online I can either help you fight through windows crappy drivers or help you set up soupkit I`m always game for a challenge When updating the driver you need to point it to the 32 bit version of the driver for instance on my computer it`s located here C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers. After it`s ran unplug and replug device if that doesn`t work power off and power on while connected this generally does the trick when windows finally catches on it will install android adb interface, this is the fastboot driver (if you`re stuck in fastboot). Then select option 1 in KFU for changing bootmodes, then option 1 for normal if it does nothing power off and power on while connected it should then detect the kindle and reset the bootmode to normal. Pm me later I will be online all evening and most every evening I will help you sort it out.
Josepho1997 said:
Whoops! Somehow my post was posted twice. I didn't even get to see your reply. Sorry!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
this is what I get when I try this... (btw im working with firefirefire. its got the blue and white kindle fire.)
Why don't you let me take a look?
Dark__king said:
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
Click to expand...
Click to collapse
Yes soupkit can fix mounting problems.
This is a very interesting issue with this Kindle windows detects it as unknown usb device, drivers are installed properly from what I can see. Ubuntu with soupkit ran on it fails to detect it in recovery or fastboot. multiple cables tried, lsusb doesn`t show the device connected. I really think this one the computer is the problem, because it`s the only unchanged variable.
Firekit may be the only option if Linux won't detect the device. Before doing that, make sure a USB 3.0 port isn't being used and try a fresh install of Linux to be safe. Otherwise, it seems putting it in USBboot is the only option for getting Linux to detect.
I'm not exactly sure what causes the unknown device error, but it almost always means there is something wrong with the bootloader, and it seems as though Windows might be the main culprit. Not sure why exactly, but it may be similar to the problem soulweeper51 had. Possibly a hardware issue involving the computer's USB port or the motherboard itself.
@ManoFishFry has doomlords cwm recovery and he flashed JB at first I thought it was an issue with cwm not being detected but the fact that it`s not detected in fastboot raised my eyebrows. The bootloader appears to be functional but I cannot rule out any minor state of being broken in another fashion when lsusb returns null. The computer doing the work had never been used prior to the incident so driver install didn`t take place till after the fact. The usb ports are all either 1.0 or 2.0 no 3.0 ports are being used. An alternate computer would be nice to rule out the computer itself @ManoFishFry only has a dinosour of an xp machine as alternate use of is not possible yet, not that it would even be possible to install drivers because of the typical unsigned driver failure of xp and booting ubuntu isn`t happening at the moment on this machine.
I'm willing to bet it is the bootloader.
Just USBboot and get it over with.
We did try usb boot once but it didn`t work will keep trying.
Hi guys,
First of all I am new to this forum but i have read almost every thread about this subject but i can't seem to find my exact situation.
So yesterday I decided I wanted to root my kindle fire HD 7 and put Cynangonmod on it. So i found this video of a guy explaining it and I downloaded the files he provided and I followed his steps.
That is when the first problem came up. He wanted me to install the ADB drivers which I couldn't get done. It told me something like '' could not install the drivers, please install them manually ''.
Thats is when I came to you guys and I noticed there were a lot of people having the same problem. I had to download some other replacement drivers and install those but even that didn't work so I was basically out of luck.
After a couple hours I managed to get the drivers functioning after deleting them and installing them again. I was surprised this actually worked because I did try that before.
But anyway the drivers were working and my kindle responded just like in the video. I followed the steps in the video and I was happy to see some progression. So my device basically was rooted at this point. So just like in the video I transferred the recovery files, CM-11 and the GAPPS I downloaded to my Kindle while strictly following the steps in the video. Next up I used ES file manager to open up the APK file and install it. At this point I exactly followed the tutorial by selecting the right files and checking the right boxes in the Fire Flash menu. Everything looked OK.
I flashed and installed the script like in the tutorial and pressed rebooted into recovery. Unfortunately this is when the party was over.
Instead of the device booting up and saying Kindle Fire with Fire being orange and turning Blue after a couple seconds, my device just booted without turning blue and was basically looping the hole time.
This was a real bummer since I was so happy that I luckily passed the hole ADB driver issue.
Now when I connect my Kindle to my computer nothing happens....just nothing...my computer doesn't even recognize my Kindle at all. So I decided to search the web for this bootloop problem and I downloaded several utility's which should unbrick my Kindle. But since my computer doesn't even recognize my Kindle actually being plugged in these tools will never work anyway.
I have no idea what is going on but it seems like it's the ADB drivers not functioning again? and what I should do now? Or can I just throw my Kindle in the trash?
This is the video I used on YouTube. You might want to watch this to understand my situation.
/watch?v=PVuvR-hHOLE
The files I downloaded are in the description of the video. I do not have the unbrick utilities and the replacement drivers anymore. But that doesn't matter now anyway since my computer doesn't recognize my device.
Please help me guys!!
Thanks!
Maric98 said:
Hi guys,
First of all I am new to this forum but i have read almost every thread about this subject but i can't seem to find my exact situation.
So yesterday I decided I wanted to root my kindle fire HD 7 and put Cynangonmod on it. So i found this video of a guy explaining it and I downloaded the files he provided and I followed his steps.
That is when the first problem came up. He wanted me to install the ADB drivers which I couldn't get done. It told me something like '' could not install the drivers, please install them manually ''.
Thats is when I came to you guys and I noticed there were a lot of people having the same problem. I had to download some other replacement drivers and install those but even that didn't work so I was basically out of luck.
After a couple hours I managed to get the drivers functioning after deleting them and installing them again. I was surprised this actually worked because I did try that before.
But anyway the drivers were working and my kindle responded just like in the video. I followed the steps in the video and I was happy to see some progression. So my device basically was rooted at this point. So just like in the video I transferred the recovery files, CM-11 and the GAPPS I downloaded to my Kindle while strictly following the steps in the video. Next up I used ES file manager to open up the APK file and install it. At this point I exactly followed the tutorial by selecting the right files and checking the right boxes in the Fire Flash menu. Everything looked OK.
I flashed and installed the script like in the tutorial and pressed rebooted into recovery. Unfortunately this is when the party was over.
Instead of the device booting up and saying Kindle Fire with Fire being orange and turning Blue after a couple seconds, my device just booted without turning blue and was basically looping the hole time.
This was a real bummer since I was so happy that I luckily passed the hole ADB driver issue.
Now when I connect my Kindle to my computer nothing happens....just nothing...my computer doesn't even recognize my Kindle at all. So I decided to search the web for this bootloop problem and I downloaded several utility's which should unbrick my Kindle. But since my computer doesn't even recognize my Kindle actually being plugged in these tools will never work anyway.
I have no idea what is going on but it seems like it's the ADB drivers not functioning again? and what I should do now? Or can I just throw my Kindle in the trash?
This is the video I used on YouTube. You might want to watch this to understand my situation.
/watch?v=PVuvR-hHOLE
The files I downloaded are in the description of the video. I do not have the unbrick utilities and the replacement drivers anymore. But that doesn't matter now anyway since my computer doesn't recognize my device.
Please help me guys!!
Thanks!
Click to expand...
Click to collapse
Have you tried getting into recovery manually? Turn the device on, immediately hold down volume up while the logo is still yellow, keep holding until a few seconds after it turns blue, it should go into twrp if you flashed twrp correctly. If worse comes to worst you can always use a fastboot cable to recover from this. Also adb is not supposed to work when you are at a bootloader screen, at most you probably could access fastboot if the logo turns blue, because the device may breifly show up as a tate device with second bootloader installed, normally it wouldnt. You would have to isntall the drivers in that brief moment or run a ubuntu live cd to do it. Anyways tell me if you can get into recovery.
stunts513 said:
Have you tried getting into recovery manually? Turn the device on, immediately hold down volume up while the logo is still yellow, keep holding until a few seconds after it turns blue, it should go into twrp if you flashed twrp correctly. If worse comes to worst you can always use a fastboot cable to recover from this. Also adb is not supposed to work when you are at a bootloader screen, at most you probably could access fastboot if the logo turns blue, because the device may breifly show up as a tate device with second bootloader installed, normally it wouldnt. You would have to isntall the drivers in that brief moment or run a ubuntu live cd to do it. Anyways tell me if you can get into recovery.
Click to expand...
Click to collapse
Thanks for your reply!
I have actually tried to holding down the volume button when it turns on but it doesn't do anything. It's like the device is ignoring me and just keeps looping.
Could be the recovery partition is screwed up but that would only happen if you had a bad recovery image. This is going to get a bit complicated. I recommend using a Ubuntu live CD for this because you won't run into a very annoying driver issue if you use Ubuntu, though they just released a update and I don't know for sure if the package names are the same. Use the latest Ubuntu if you choose to do this or you could simply get a fastboot cable or the blackhat fastboot adapter that goes in between the kindle and the cable. You simply need to try to flash a recovery IMG through fastboot. It should be pretty straight forward, no need to return to stock kindle os to fix this assuming my theory as to why its doing this is correct.
If you wanna use Ubuntu then grab the latest version from their site(think its 14.something) and either burn it to a CD or make a bootable USB using either their instructions, or my preferred utility unetbootin, then boot up into Ubuntu live os and open the settings and look for something about software update. I haven't upgraded to the latest distro so this bit of info is a bit guess and check. If you find software update then make sure all the download from internet boxes are checked then hit close, if it asks to reload choose yes and ignore the first command i'm about to mention. Open a terminal, run these commands in order:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot android-tools-adb
sudo fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in with the power off, it should then go into fastboot since you have 2nd bootloader installed. Normally this method wouldn't work without a second bootloader unless you are on the 8.9". From there you can open the 2.7 zip of twrp and extract the img file from it to your home folder and run:
Code:
sudo fastboot -i 0x1949 flash recovery recovery-image-name-here
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Could be the recovery partition is screwed up but that would only happen if you had a bad recovery image. This is going to get a bit complicated. I recommend using a Ubuntu live CD for this because you won't run into a very annoying driver issue if you use Ubuntu, though they just released a update and I don't know for sure if the package names are the same. Use the latest Ubuntu if you choose to do this or you could simply get a fastboot cable or the blackhat fastboot adapter that goes in between the kindle and the cable. You simply need to try to flash a recovery IMG through fastboot. It should be pretty straight forward, no need to return to stock kindle os to fix this assuming my theory as to why its doing this is correct.
If you wanna use Ubuntu then grab the latest version from their site(think its 14.something) and either burn it to a CD or make a bootable USB using either their instructions, or my preferred utility unetbootin, then boot up into Ubuntu live os and open the settings and look for something about software update. I haven't upgraded to the latest distro so this bit of info is a bit guess and check. If you find software update then make sure all the download from internet boxes are checked then hit close, if it asks to reload choose yes and ignore the first command i'm about to mention. Open a terminal, run these commands in order:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot android-tools-adb
sudo fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in with the power off, it should then go into fastboot since you have 2nd bootloader installed. Normally this method wouldn't work without a second bootloader unless you are on the 8.9". From there you can open the 2.7 zip of twrp and extract the img file from it to your home folder and run:
Code:
sudo fastboot -i 0x1949 flash recovery recovery-image-name-here
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
That actually sounds really difficult.
Just to be clear there is no way to do this on just Windows 7 or OSX? Instead of installing Ubuntu ( which I am not familiar with ). Also could you explain a bit more about the functions of those fastboot cables / adapters because I don't really understand what they do and are you sure those will work with the status of my device? I assume as soon as I get that cable / adapter I Need to plug my device in to the computer and have to get it working via some commands? But anyway is there a way I can stick to windows or mac OSX ( Which I did not use before in the rooting process )
, mac os, normally I would hate mac os just because its a bit nooby and i don't agree with apples policy towards open source(or the lack of) and finding loopholes in whatever the license the unix kernel was under, but this time it may actually be useful, mac is is based on a Unix kernel, which is in a manner similar to the Linux kernel that Ubuntu uses. If you have used a mac then using Ubuntu would be easy, but in this case you shouldn't need to because it should load the drivers up immediately like in Ubuntu. Just grab the android SDK for mac os since i don't think the Linux binaries are compatible. Try placing the extracted android SDK on your desktop, and put previously mentioned recovery img file in the same folder as the fastboot command, open a terminal from applications>utilities and CD into the directory on the desktop that fastboot is in, and try running the fastboot commands I mentioned. Not sure if sudo is needed or not on a mac.
OK as to fastboot cables/adapters, basically you plug your kindle into it and the PC, and your kindle immediately kicks into fastboot mode. You could easily repair it fro windows in this manner since the Tate device would hang around so you could update it's driver without much difficulty. Tech locally you could try the same on windows without a fastboot cable but the device would only appear for a few seconds before it disappears making it hard to install the drivers in that time frame.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
, mac os, normally I would hate mac os just because its a bit nooby and i don't agree with apples policy towards open source(or the lack of) and finding loopholes in whatever the license the unix kernel was under, but this time it may actually be useful, mac is is based on a Unix kernel, which is in a manner similar to the Linux kernel that Ubuntu uses. If you have used a mac then using Ubuntu would be easy, but in this case you shouldn't need to because it should load the drivers up immediately like in Ubuntu. Just grab the android SDK for mac os since i don't think the Linux binaries are compatible. Try placing the extracted android SDK on your desktop, and put previously mentioned recovery img file in the same folder as the fastboot command, open a terminal from applications>utilities and CD into the directory on the desktop that fastboot is in, and try running the fastboot commands I mentioned. Not sure if sudo is needed or not on a mac.
OK as to fastboot cables/adapters, basically you plug your kindle into it and the PC, and your kindle immediately kicks into fastboot mode. You could easily repair it fro windows in this manner since the Tate device would hang around so you could update it's driver without much difficulty. Tech locally you could try the same on windows without a fastboot cable but the device would only appear for a few seconds before it disappears making it hard to install the drivers in that time frame.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks I hope my mac will get the job done. It would make it a lot more easier than going linux I think.
Ok. Ill try it on my mac. I will now download Android SDK and place the extracted file on my desktop. I guess I install all tools and all that. And keep you up-to-date.
I downloaded the SDK and placed the folder to my desktop and opened the SDK manager by going to sdk / tools / android and installed SKD tools and SDK platform Tools. Although when i downloaded it it gave me a log that told me something like '' Stopping ADB server failed (code -1). '' And now I get a red checkmark. I don't know if getting a red checkmark is actually good. And i don't know if it's installed now and if the error message matters.