HI,
This is my first post so I must apologise if it's in the wrong place. I have tried searching the relevant forums for help but cannot find anything specific enough.
I have been trying to install the ADB drivers for my Kindle Fire 2nd Gen for the past half of a day now with the intention of rooting the device using THIS method. The drivers seem to be readily installed, however when I am prompted to restart my computer for the installation to complete I am greeted upon restart by the drivers seemingly installing again. I have tried multiple restarts on both my kindle and the PC but I've had no luck.
If anyone has had a similar problem and has any form of solution or advice it would be greatly appreciated, OR if i have simply missed a thread relevant to my issue please post a link.
Thanks.
Related
hello, let me first say i have posted appropriate questions on the NVflash webpage for this issue, and so far have been unanswered.
i am hoping that by posting this in the Q&A section of XDA someone might see this.
I feel as though my issue is very simple, but i cant seem to find any answers and as i have said, my posts on the NVflash webpage have so far been unanswered (over a month)
i am on 4.0.3 zeus rom, have rooted and added TWRP recovery. yet, now that im trying to use NVFlash so i can update to JB finally. it wont let me start fastboot. just sits there at boot saying starting USB Fastboot protocol…
and thats it…. i plug it in, adb devices. nothing. fastboot reboot. “waiting for device”
i have the proper drivers, as i had to have them to root/rom/recover the tablet in the first place. i have NOT done NVFlash yet (i exchanged my TF201 for a TF700 at bestbuy to avoid needing to nvflash the first time)
can anyone please help me? im not sure what to do, if i cant get fastboot to work.
the ROM i am on works, no issue, no brick. i just wanted to update to JB finally.
any help is greatly appreciated. Thank you!
Ignore the drivers you used before. Use the ones stated on the nvflash page. That should fix your problem.
i appreciate you trying to help but the drivers on the nvflash page... are the ones i am using... it seems fastboot will not run ON my device. says "starting usb fastboot protocol"
ill redownload them and try it again though. thanks
That is the message it says when running fastboot on the tablet. It will never say anything else.
Redo the drivers on your pc. Uninstalling asus sync if you have it as that could have broken it.
sbdags said:
That is the message it says when running fastboot on the tablet. It will never say anything else.
Redo the drivers on your pc. Uninstalling asus sync if you have it as that could have broken it.
Click to expand...
Click to collapse
i will wipe all drivers i have for all my android devices in case something is messing with it.
thank you very much for your help. its been frustrating not being able to use my tablet at all, hopefully this will work.
malaeus said:
i will wipe all drivers i have for all my android devices in case something is messing with it.
thank you very much for your help. its been frustrating not being able to use my tablet at all, hopefully this will work.
Click to expand...
Click to collapse
Your phone drivers could have overwritten something.
I have read all types of forums to Reboot Bootloader. Yeah, I know stuck at the beginning, not a good sign.Any way I went to Developer.android and got SDK. Followed various suggestions and have it on machine. However the windows 7 won't recognize device. I downloaded Motorola Device Manager for the drivers (I beleive this may be the issue) and it found no updates. I have debugged checked on Xoom, but jellybean icon shows up intermittently. When I type in CMD prompt to adb reboot bootloader, it doesn't recognize the device.
Other CMD commands suggested during instruction video worked verifying I had ADB installed coirrectly. I checked the device in control panel and it is unidentfied.Device properties has this error" Windows has stopped this device because it has reported problems. (Code 43)"
Please, can someone assist. I think that I need the drivers, but the motorola Device manager is the only tool I can find and I dont think it has the drivers, I could be wrong, but this is what I'm guessing.
Ok. I found online that the new USB 3.0 has issues with this process. I plugged into a 2.0 USB and I'm in business. I've gone through unlocking. Now I can't locate the Universal Xoom Root Zip. All tutorial links that I could find go to a link that no longer has the file. can someone point me in the right direction or send me a link to the file- Thanks for the help
Ok status update. I was able to find the file and have successfully Rooted. The question, now is I restarted and I have an Green Android robot on my screen with Tiamat engraved on front stomach area. I believe I was in recovery last. IS the Xoom doing anything in the background. I don't want to interrupt something if it is running. I have downloaded BiGPART and Omni 4.4 components but I seem to be stuck
Wow... Not one response. I was able to figure it out and now am the owner of 4.4
Hello all.
This is my first post and my first experience with android devices so please go gentle.
I recently purchased for £20 a kindle fire 2nd gen otter.
The reason it was so cheap was that it is stuck in a bootloop.
The friend I bought it from intended to bring it back to life and install CM to the device but never got round to it. So I took it on as my little project.
I have been scrolling through pages and pages of google and this site for research but have hit a brick wall.
I purchased a factory or fastboot cable knowing I may well need it. I also have the original cable.
When trying to boot the device I get the usual kindle and fire logo orange as of it's booting then every 10 seconds or so the screen will go black and back to the kindle fire bootloop.
I have tried to use the normal cable to link to my desktop on windows 7. When doing this the device will not show up in device manager at all.
When I plug it via a fastboot cable it boots into fastboot with a green flashing light on screen and is recognised as an otter prod 04 on device manager.
I have installed the latest sdk. Also fastboot.
I have changed the windows environment variables under path on the PC and can successfully run fastboot in a command window. I can also issue adb commands through also a dos command window so I know both are working correctly on my PC.
I have typed in fastboot devices
I have also typed in adb devices.
When I issue either or these commands my device will not be found through the command window. It just returns a blank.
I know this is due to drivers not working correctly so have opened device manager. Update driver , have tried the android sdk path for drivers have also tried my adb drivers. I have also downloaded the latest Google USB driver and none will install. I have a programme running that allows any unsigned driver to be installed on win 7 so I know it's not that.
All I have returned is cannot install drivers for otter prod. 04
The only thing it will accept is choosing from a list of devices, Then android. And installs as adb device or adb composite device, this is obviously useless as I can't boot device into normal mode to be able to use it as adb or issue commands to it.
I have tried everything. I know this kindle is save able I just don't know how. My end result is make it bootable, root device and install CM
I have trawled through loads of pages of info and tried tried and tried for answers but nothing works. Can anybody shed some light on the issue for me.
Many thanks in advance
Hi,
You've already posted in an appropriate section.
Please be patient and if someone can help, they will.
XDA Assist is here to help members navigate the site, not for support. And you've already found your way to a section to post in.
Thank you for understanding. ?
---------- Post added at 04:32 PM ---------- Previous post was at 04:28 PM ----------
Though, there is a dedicated section for your device.
> Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2 > Kindle Fire 2 Q&A, Help and Troubleshooting
I will report your thread in General to be moved to the above section.
Good luck!
Sorry I do apologise.
Wasn't sure if it was In the right place my mistake. I have gone through the forum searching keywords for the issue. Wondering if anyone has had this issue or could help
Sorry again
vincent198526 said:
Sorry I do apologise.
Wasn't sure if it was In the right place my mistake. I have gone through the forum searching keywords for the issue. Wondering if anyone has had this issue or could help
Sorry again
Click to expand...
Click to collapse
Don't worry. Your General thread should get moved to the section I linked above soon. ?
Thread closed. Thank you.
I am visiting a member of my family and their Kindle Fire "Broke". It seems as if its bricked to fastboot mode only, as when you power it on, the kindle fire logo shows up and then very quickly swaps to the Fastboot logo. Im not too big on kindle stuff so so far I havent gotten anywhere and am having trouble. They wouldnt have rooted, enabled ADB, or done anything beyond vanilla kindle stuff. ADB wont recognize the device on my computer and nothing works on the device to get it into recovery or anything besides fastboot. I am using the stock cable but I have also tried multiple cables and USB ports and restarting computer and kindle. Not sure how to proceed as it seems like theres no way I can communicate with the device.
XDA Visitor said:
I am visiting a member of my family and their Kindle Fire "Broke". It seems as if its bricked to fastboot mode only, as when you power it on, the kindle fire logo shows up and then very quickly swaps to the Fastboot logo. Im not too big on kindle stuff so so far I havent gotten anywhere and am having trouble. They wouldnt have rooted, enabled ADB, or done anything beyond vanilla kindle stuff. ADB wont recognize the device on my computer and nothing works on the device to get it into recovery or anything besides fastboot. I am using the stock cable but I have also tried multiple cables and USB ports and restarting computer and kindle. Not sure how to proceed as it seems like theres no way I can communicate with the device.
Click to expand...
Click to collapse
Welcome to XDA Developers.
First, please register as a user, here > http://forum.xda-developers.com/register.php
After you have registered, go to the following thread. Read the OP (Original Post) carefully, then scan the rest of the pages, looking for information that can help you. After you have done that, you can post your help request here > http://forum.xda-developers.com/showthread.php?t=2128848
One of our experts will help you.
Good luck.
Hi guys!
Long story short I have a TF101G stuck in bootloop after a failed attempt to install a new recovery, I searched here for a possible solution and i found "OneClickRecovery" that seems to suit my situation perfectly.
My problem is that my device in not recognized by my computer (windows 10, but i tried also Ubuntu and Windows 7): when i plug it, device manager doesn't read any new device.
I manage to get it recognized in APX mode, but from what i have read around this forum solution as "wheelie" and "Easyflasher" works only for TF101.
Thanking you in advance for your help in this matter, I look forward to your reply