Related
I seriously need some help. My normally fierce Google-fu has failed me. I have searched countless threads on here (and elsewhere) and tried just as many solutions, but I haven't had any luck. My Kindle Fire is stuck at the "Kindle Fire" boot logo. I was using the KF utility, and ADB status was online, everything looked good. I chose the option to root and install TWRP. However, it couldn't grab TWRP through my corporate firewall/proxy, so it skipped it, placed my KF in fastboot (I think), rebooted, now I'm bricked.
Depending on which PC I use, and in what order it's plugged in, I get different results in the Device Manager (both Windows 7):
Home PC -
Hardware Ids = USB\UNKNOWN
Yes, I've tried loading drivers six ways from Sunday, and none worked.
Absolutely no solution involving ADB in any way will work until I can at least get Windows to recognize it correctly and load the proper drivers.
Work PC -
If I have the KF turned on when I plug it into my PC, I get the same result as on my home PC (though I don't think I tried plugging it in on my home PC while my KF was powered off).
If I have it turned off when I plug it in, my PC sees it as an "Android ADB Interface", with the correct hardware ids.
Even when it sees my KF correctly in Device Manager, I still can't get ADB to communicate with it.
I've tried FireKit on my Ubunutu 12.04 laptop, but it never sees my device, and gets stuck at the <waiting for device> message. I've tried countless driver iterations and many utilities, and none seem able to communicate with it while it's stuck at the logo.
Any help would be immeasurably appreciated!!
[UPDATE]
While my device was detected correctly in Device Manager (but still not able to communicate via ADB), I reloaded the drivers using the KF Utility. It is still detected as "Android ADB Interface" but with an error in Device Manager. The error is "This device cannot start. (Code10)". I uninstalled it, including drivers, and let Windows autodetect. It was identified as "kindle", so I ran the same driver package and it still sees it as "Android ADB Interface", but still with the error.
[UPDATE 2] - Steps I took to (finally) get mine working
Note: If your device is recognized in Device Manager as something *other* than "Unknown Device* (such as "kindle" or "Android ADB Interface"), skip to step 3.
1. Turn off the device.
2. Plug the device into USB to your computer. This should turn the device on.
3. Delete the ".android" folder from your Windows profile. This is very important. If you just uninstall the device and driver, Windows will still use this to reinstall the device. You want to start as fresh as possible to eliminate complications from previous attempts.
4. Uninstall it from Device Manager. Make certain to check the box to uninstall the driver as well.
5. Start a new scan for hardware changes in the Device Manager.
6. As mine was stuck in fastboot mode, it recognized the device as "kindle" (lower-case "k")
7. Run the "install_driver.bat" from the Kindle Fire Utility.
8. After driver install, run the Kindle Fire Utility.
9. ADB status will say "offline", that's fine.
10. Choose option 1 to go into the Bootmode Menu.
11. Choose option 1 to boot into Normal Mode.
12. It will be stuck at <waiting for device>.
13. Turn off the device, keeping it plugged into the PC. *very important* This step was one among others that made THE difference for me.
14. Turn on the device. *Hopefully*, you should immediately see the utility spit out some text and your device should reboot.
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
IT LIVES!!! While I was still getting the error code 10, I launched the KF utility one more time. ADB status was still offline. I went into the menu to modify boot mode, told it to boot in normal mode and it was stuck <waiting for device>. On a whim, I left it there and cycled power on my KF. It found the device, finished, rebooted, and it's good!!! The Device Manager is happy now too!!
The behavior was so odd between my work and home PC. I was seriously scared when it gave a bad device ids on my home PC. I think it was more a combination of several different things that helped, and I'll update my main post with all that I did to get it back (that I can remember). Hopefully it will help someone else.
This is an *amazing* community, and I can't thank everyone enough for the incredible work you all do and the true sense of selflessness exhibited here on the forums!
btw, How do I edit the subject to indicate it's solved?
^_^
OH ,MY GOSH I DO NOT NO HOW MUCH TO THANK U THNX FOR THE POST
jaetrix said:
OH ,MY GOSH I DO NOT NO HOW MUCH TO THANK U THNX FOR THE POST
Click to expand...
Click to collapse
Glad it could help someone! I was frustrated enough about it and couldn't find a single solution that fit my issue. I just had to combine some to get it to work for me.
Bump
Yes this saved two bricked kindles. Trial and error is sometimes the best means to solving a problem.
Sent from my GT-I900 using xda premium
This is happening alot here of recent thats why I bumped it to the top of the list
Thank you for this. Maybe a moderator will be kind enough to sticky this.
Sent from my Galaxy Nexus using Tapatalk 2
pugsley42 said:
I seriously need some help. My normally fierce Google-fu has failed me. I have searched countless threads on here (and elsewhere) and tried just as many solutions, but I haven't had any luck. My Kindle Fire is stuck at the "Kindle Fire" boot logo. I was using the KF utility, and ADB status was online, everything looked good. I chose the option to root and install TWRP. However, it couldn't grab TWRP through my corporate firewall/proxy, so it skipped it, placed my KF in fastboot (I think), rebooted, now I'm bricked.
[...]
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Click to expand...
Click to collapse
Pugsley42...you 'da man! I had the same story as you told above, including searching and following countless threads of instructions. Nothing worked until I found your instructions! Thank you, thank you, thank you!
Stuck at the KF logo
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Neely said:
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Click to expand...
Click to collapse
My first suggestion would be to read this:
http://forum.xda-developers.com/showpost.php?p=25884555
Neely said:
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Click to expand...
Click to collapse
Agreed, you really need to be more specific. "Waiting for device" .... which part of the KF utility?. What *exactly* are you seeing, where? What does Device Manager show your KF identified as (keep in mind, there is a big difference between seeing it as "Kindle" and "kindle"). What *exactly* did you do that brought you to this point?
Symptoms. Symptoms. Symptoms. The more detail you provide, the more likelihood we can help.
Take heart. If there's anything I learned in my stubborn refusal to admit my KF was fully bricked, is that it can be brought back from a lot worse than we give it credit for. I also learned quite a bit that I never would have if I never failed. That's what I love about breaking things!
pugsley42 said:
Agreed, you really need to be more specific. "Waiting for device" .... which part of the KF utility?. What *exactly* are you seeing, where? What does Device Manager show your KF identified as (keep in mind, there is a big difference between seeing it as "Kindle" and "kindle"). What *exactly* did you do that brought you to this point?
Symptoms. Symptoms. Symptoms. The more detail you provide, the more likelihood we can help.
Take heart. If there's anything I learned in my stubborn refusal to admit my KF was fully bricked, is that it can be brought back from a lot worse than we give it credit for. I also learned quite a bit that I never would have if I never failed. That's what I love about breaking things!
Click to expand...
Click to collapse
Okay, I was attempting to load a ROM on it. It had been rooted already with no issues and then something happened during the installation of TWRP and spit out an error message of unable to load and then rebooted. That's where I am with the kindle fire boot screen.
As for the "Device Manager" It shows up as "Android Composite ADB Device" and with KFU it shows the following status:
ADB Status: Online
Boot Status: Unknown
At this point is when if I try to run Install Latest TWRP Recovery or FFFF or anything it just sits there and says "Waiting For Device"...
I've read though most of these posts and have tried several different suggestions with no luck so far. So I have actually read through here. :-/
Hope this helps at all.
I would try by trying to change the bootmode using the KF utility. If you're stuck at the KF logo on boot, then the other functions of the utility won't do anything. Your KF needs to be in a "usable" state before that can happen. Have you tried changing it to "Fastboot" or "Normal"?
Stuck at the KF logo
pugsley42 said:
I would try by trying to change the bootmode using the KF utility. If you're stuck at the KF logo on boot, then the other functions of the utility won't do anything. Your KF needs to be in a "usable" state before that can happen. Have you tried changing it to "Fastboot" or "Normal"?
Click to expand...
Click to collapse
Yeah, I've tried it using the KF Utility as well as using fastboot at the command line :-/
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
Click to expand...
Click to collapse
Your explanation and guidance cut right to the solution for me. Thank you so much!
Thank you!!
I've been searching forever for this same issue. This has not fixed it completely but has helped me! Thank you for taking the time to post this!!
cmgroden said:
I've been searching forever for this same issue. This has not fixed it completely but has helped me! Thank you for taking the time to post this!!
Click to expand...
Click to collapse
I presume if any of this helped, you were able to get further than you have been. What state is it in now? What error(s) if any?
I seem to be having this same issue but I cannot get my pc to recoginze the kindle fire as anything. perhaps i did something wrong but i was following a video on youtube and though i was doing it exactly as it showed. First thing i did after I finally got the drivers loaded was start KFU and then chose to load TWRP. It started the process but when it hit the part about rebooting my device that's where it stopped. Since then i've been stuck at the white and yellow kindle fire logo. No matter what i do to try to reinstall the ADB drivers I cannot get my computer (win xp) to recognize the kindle. It shows as "unknown device" in device manager and when it's plugged in the little pop up says that the usb device has malfunctioned and windows doesn't recognize it. So am I totally dead? I'm assuming before i can do anything to recover it I need to get windows to recognize it with the ADB drivers.
hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.
Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/
Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse
Hey guys... Only second kindle I've ever attempted (have a butyload of other android devices I've rooted... But this bigger with no other buttons has me stumped )
Anyway... Went to root today, plugged in kindle, battery was dead... No problem... Let it charge.
When it booted, ran KFU to tell it to install TWRP. Here's where it gets....odd.
I had twrp in the KFU folder but it decided it wasn't there and wanted to download it... Mind you, this is... I believe... After it sent a command to fastboot ... Well, I didn't have internet, so KFU just sort of stopped when it couldn't download twrp...
Since then, the kindle is just stuck on KindleFire screen... Doesn't go any further... If I let the battery run out for about an hour, it will start rebooting every 5 seconds even if I plug it in. In the "bootloop" I can't turn it off, it just keeps rebooting...
If I let it die, I can plug it in, let it charge and turn it on... Sticks at KindleFire screen... I have tried holding in power for 30 seconds... It just turns the kindle off, doesn't help.
Windows sees it as an unrecognized device (tried rebooting, unplugging, uninstalling the drivers, looking at the KFU folder to manually select drivers (windows says they're not the correct drivers for the device) adv can't see it (cms... Adb devices shows no devices connected)
Any help is appreciated... If I missed needed info, please ask and ill supply...
I'm happy to try anything and report the findings...
RBThompsonV said:
Hey guys... Only second kindle I've ever attempted (have a butyload of other android devices I've rooted... But this bigger with no other buttons has me stumped )
Anyway... Went to root today, plugged in kindle, battery was dead... No problem... Let it charge.
When it booted, ran KFU to tell it to install TWRP. Here's where it gets....odd.
I had twrp in the KFU folder but it decided it wasn't there and wanted to download it... Mind you, this is... I believe... After it sent a command to fastboot ... Well, I didn't have internet, so KFU just sort of stopped when it couldn't download twrp...
Since then, the kindle is just stuck on KindleFire screen... Doesn't go any further... If I let the battery run out for about an hour, it will start rebooting every 5 seconds even if I plug it in. In the "bootloop" I can't turn it off, it just keeps rebooting...
If I let it die, I can plug it in, let it charge and turn it on... Sticks at KindleFire screen... I have tried holding in power for 30 seconds... It just turns the kindle off, doesn't help.
Windows sees it as an unrecognized device (tried rebooting, unplugging, uninstalling the drivers, looking at the KFU folder to manually select drivers (windows says they're not the correct drivers for the device) adv can't see it (cms... Adb devices shows no devices connected)
Any help is appreciated... If I missed needed info, please ask and ill supply...
I'm happy to try anything and report the findings...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
#30 & #31
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
#30 & #31
Click to expand...
Click to collapse
OK... but why does it stick on the KindleFire logo? (It does that without rebooting, it just hangs there).. And the battery drain was not intentional... It's ff now... charging (I assume... no logo, no led )
RBThompsonV said:
OK... but why does it stick on the KindleFire logo?
Click to expand...
Click to collapse
#16
It's ff now... charging (I assume... no logo, no led )
Click to expand...
Click to collapse
I would have to agree...it does appear to be charging.
soupmagnet said:
#16
I would have to agree...it does appear to be charging.
Click to expand...
Click to collapse
Sorry if im being super-noobish... I prefer my nook over this kindle
The logo is bright and unchanging (Seems to be stuck in fastboot?) But adb doesnt recognize it... windows sees it as an unknown device... and KFU shows... well, nothong Even when I try to normal boot in KFU (or adb..) it hangs on waiting for device.
Also, thanks a billion for even responding Soup... Its nice to know there's someone out there
RBThompsonV said:
Sorry if im being super-noobish... I prefer my nook over this kindle
The logo is bright and unchanging (Seems to be stuck in fastboot?) But adb doesnt recognize it... windows sees it as an unknown device... and KFU shows... well, nothong Even when I try to normal boot in KFU (or adb..) it hangs on waiting for device.
Also, thanks a billion for even responding Soup... Its nice to know there's someone out there
Click to expand...
Click to collapse
Okay,
Yes, it is in fastboot. ADB won't recognize the device in fastboot because ADB commands don't work in fastboot, only fastboot commands will. The KFU won't detect the device in fastboot because of the bootloader itself. It used to, but not anymore...likely due to an update on Amazon's part. There can be a couple of reasons why it just hangs at "waiting for device". When you see "waiting for device", you can reboot the KF and see if it detects upon rebooting. If not, you'll have to completely uninstall your drivers and try again. Even then, there's still a good chance it won't work. If not, you can reference the following thread for clues to get it working properly:
http://forum.xda-developers.com/showthread.php?t=2179748
soupmagnet said:
Okay,
Yes, it is in fastboot. ADB won't recognize the device in fastboot because ADB commands don't work in fastboot, only fastboot commands will. The KFU won't detect the device in fastboot because of the bootloader itself. It used to, but not anymore...likely due to an update on Amazon's part. There can be a couple of reasons why it just hangs at "waiting for device". When you see "waiting for device", you can reboot the KF and see if it detects upon rebooting. If not, you'll have to completely uninstall your drivers and try again. Even then, there's still a good chance it won't work. If not, you can reference the following thread for clues to get it working properly:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
OK.. Ive tried everything in the thread... Only thing I cant find is the android_winusb folder (Im running Win7 x64).
Also, when I look up the UNKNOWN DEVICE Hardware ID, I get USB\UNKNOWN) in device manager
RBThompsonV said:
OK.. Ive tried everything in the thread... Only thing I cant find is the android_winusb folder (Im running Win7 x64).
Also, when I look up the UNKNOWN DEVICE Hardware ID, I get USB\UNKNOWN) in device manager
Click to expand...
Click to collapse
Make sure you have the hardware IDs that I posted in that thread, in your KFU's 'android_winusb.inf' file.
You also have to find and delete the folder that gets created by KFU's install_drivers.bat. It will be in the WINDOWS directory somewhere, most likely in a hidden folder. Make sure "Show hidden folders" is enabled.
You may have to search your hard drive for any directory containing the string "android" OR for the filename 'android_winusb.inf',making sure to search hidden files and folders.
Once you have found and deleted it, reboot your computer and run KFU's newly edited 'install_drivers.bat'
Still Stuck...
OK, so, I did a CLEAN install of windows XP, installed the complete Android SDK package, then installed the modified KFU package (Added the lines of Device IDs supplied in your post on how to get it to work) and edited the install bat to install in legacy mode.
I still get an error in windows about the Kindle Fire.
I installed everything, then plugged in the kindle after turning it on. Kindle is still stuck on Kindle Fire logo (doesnt flicker or sparkle or dim or anything)... and windows says:
(In FOUND NEW HARDWARE WIZARD):
Cannot start this hardware
There was a problem installing this hardware:
Android Composite ADB Interface
This device cannot start (Code 10)
...
Thats a USB error code , maybe trying to use a different cable or use the usb ports on the back of the pc instead of the front
OMFG!!!!
I want to thank all of you for your help...
But, get this...
Apparently the kindle was waiting for me to send the TWRP package... THATS ALL!!!
I built the factory cable... proved useless for me
I went through all of my USB cables... NONE worked...
So, as a last ditch effort I thought... screw it, lets see what happens if I... (Fill in the blank)...
Tried sending the TWRP package and BAM!!!! Blue kindle...
Go figure
Do not see a section for the A200..... A100 is the closest, I think.....
OK, so I soft bricked my A200 and need to USB connect to it, so I can use fastboot or some other recovery tool.
Problem is that when I plug the A200 into my computer, it grinds away for a bit then gives a driver failed to install red "X" message.
I've reloaded the Acer USB drivers a couple of time, but no joy there. I've tried two different computers, I've tried XP and W7, nothing seems to help. Looking in the device manager shows an error 10 (device can't start).
Since the PC at least recognizes the A200 when plugging in, I think if I can get the USB talking I can easily unbrick the A200.
I posted this same message over on Acertabletforums, but so far no response's
Help??
Boowho??
boowho said:
Do not see a section for the A200..... A100 is the closest, I think.....
OK, so I soft bricked my A200 and need to USB connect to it, so I can use fastboot or some other recovery tool.
Problem is that when I plug the A200 into my computer, it grinds away for a bit then gives a driver failed to install red "X" message.
I've reloaded the Acer USB drivers a couple of time, but no joy there. I've tried two different computers, I've tried XP and W7, nothing seems to help. Looking in the device manager shows an error 10 (device can't start).
Since the PC at least recognizes the A200 when plugging in, I think if I can get the USB talking I can easily unbrick the A200.
I posted this same message over on Acertabletforums, but so far no response's
Help??
Boowho??
Click to expand...
Click to collapse
The A200 guys are over in the A500 section, we're all by our lonesome over here.
Is the screen just blank, or what does it do when you power it on? We get stuck in apx mode when we brick so we have no way back out for us, not sure of the A200s.
I would plug it in, uninstall all android drivers, even for other devices, uninstall all software for android, reboot, then plug it in and install fresh and see how it goes. If its in apx mode then the normal drivers won't work.
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
The A200 guys are over in the A500 section, we're all by our lonesome over here.
Is the screen just blank, or what does it do when you power it on? We get stuck in apx mode when we brick so we have no way back out for us, not sure of the A200s.
I would plug it in, uninstall all android drivers, even for other devices, uninstall all software for android, reboot, then plug it in and install fresh and see how it goes. If its in apx mode then the normal drivers won't work.
Tapatalked from my HTC DNA - Akakaze
Click to expand...
Click to collapse
Hey, thanks..... Maybe a moderator will move this thread over there??
When I power it on, it boots to the IconiaTab screen, but no further. I don't know what apx mode is. It's been rooted and bootloader unlocked using HBWelch's Simple Tool. I can get into fastboot mode by using a convoluted (to me, at least) procedure, that takes 6 fingers to accomplish.
Boowho??
fixed
Problem solved..... Thanks. Was able to flash via update.zip on SD card.
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Mambobuzzz said:
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Click to expand...
Click to collapse
This is a problem related to Windows 10 that uses the wrong driver.
Somewhere I have found a guide to manually choose the correct one, but at the moment I don't remember where... googling you will find instructions
Mambobuzzz said:
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Click to expand...
Click to collapse
This is not the Q&A section. Please post your questions there, according to the forum rules. Can a moderator please move this? Thanks.
Monfro said:
This is a problem related to Windows 10 that uses the wrong driver.
Somewhere I have found a guide to manually choose the correct one, but at the moment I don't remember where... googling you will find instructions
Click to expand...
Click to collapse
I've googled it. Tried many. Event tried to boot Windows without driver signature. Didn't work. :/
michie said:
This is not the Q&A section. Please post your questions there, according to the forum rules. Can a moderator please move this? Thanks.
Click to expand...
Click to collapse
Oh sorry.
Does someone have an idea?
This might come a year too late, but in case someone else runs into the same problem (like myself), you can solve it by installing the latest (signed) ADB drivers with this Tool, then rebooting the tablet to fastboot mode and run the tool again. This still doesn't install the correct fastboot drivers, but it should now be listed as "ADB Interface" -> "Unknown Device" in the device manager, and if you right click and choose "Update driver" -> "Browse my computer for driver software", you should see a driver called "Fastboot interface (Google USB ID)", that installs and works correctly for the Pixel C.
@Mambobuzzz
One option you have and it's been updated this month too, is you could try installing and using tiny adb & fastboot from here: https://forum.xda-developers.com/t/tool-windows-tiny-adb-fastboot-august-2021.3944288/
I can't stand Windows for a few reasons! Make a live USB and try a Linux distro! You will never have this problem again and I guarantee you won't miss Windows.
Edit added:
Reasons why this is happening:
Bad connection somewhere.. The USB connection you are plugging in to on your PC could be messed up, the USB cord could be messed up, or where your type c plugs in to your device is messed up.... Oooorrrrr it's driver issue. And knowing Windows I betcha it's a driver issue. When you plug your tablet in are you enabling USB debugging and developer options and changing the "default USB configuration" from "Charging" to "File tansfer ?" And when you do those things are you watching the table REALLY CLOSELY for the little box that pops up for 5 seconds that you MUST put a checkmark in otherwise adb and fastboot will not work? Reboot a few times on your PC and update the drivers in Windows Device manager.. I remember once I had to reboot 3-4 times to finally get mine working. When you type adb --version then push enter in terminal and fastboot --version push enter what does it say?