Related
So i installed C7 with clockworkmod then when i rebooted i was stuck at the firefirefire loader. I dont have a computer availible AT THE
MOMENT, i hope to be getting my laptop soon. But how can i fix this error??
can you boot into recovery? Sounds to me like you need to reinstall ROM.
No, nomatter how many times i press the button, nothing happens, but how can i mount the usb/install fresh update.zip?
To fix this you will need a computer... I don't know any other way atm... use KFU to install update.zip (aka stock) and try again.
Well by no computer i meant no windows, i have a mac with virtualbox, can that work
Ethanzh said:
Well by no computer i meant no windows, i have a mac with virtualbox, can that work
Click to expand...
Click to collapse
i think you are stuck in fastboot mode
if you have a mac try the mac version of kfu to set the bootmode to normal or any other task you want to do:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
How do i setup KFU on vista?
- download http://random.kennocha.com/kindle/utility/Kindle_Fire_Utility_v0.9.3.zip
- extract to c:\
- rename to "kfu" (it don't like spaces in pathname)
- if you want to use the drivers from kfu read http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
btw do you have vista in a virtual box ?
hope you don't try to flash the original rom from amazon - you will loose fff, twrp and root
would recommend a prerooted stock rom instead:
http://forum.xda-developers.com/showthread.php?t=1569298
Yes i am using vista in virtul box and i extracted the fku to C:\fku , but how do i install the drivers, Windows isnt recognizing the fire because its stuck on fireifrefire, or does that not matter?
Ethanzh said:
Yes i am using vista in virtul box and i extracted the fku to C:\fku , but how do i install the drivers, Windows isnt recognizing the fire because its stuck on fireifrefire, or does that not matter?
Click to expand...
Click to collapse
you have to install the drivers because windows is'nt recognizing
please read the linked in post about the drivers from my last post - there is everything in there
also read this one - that should clear things up:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
for some it worked in a virtual box and for some not - good luck !
Thanks but im just curious, how can windows detect thr kindle even with thr drivers, if itsnt fully turned on yet, just stuck at boot? And also does adb have anything to do with this??
Windows will probably not recognize your kindle fire... KFU should though.
Ethanzh said:
Thanks but im just curious, how can windows detect thr kindle even with thr drivers, if itsnt fully turned on yet, just stuck at boot? And also does adb have anything to do with this??
Click to expand...
Click to collapse
I think your confusion stems from your belief that if it's "stuck" at the FFF logo, the device is malfunctioning. In most cases when the KF appears to stop working at this point, it's just in fastboot mode. In this state, you are able to issue fastboot commands to the KF and do many useful things. I believe fastboot utilizes the drivers that are packaged with ADB, so you'll see "Android Phone -> Android ADB Interface" in the device manager when Windows sees it in this mode. However, the command "adb" is entirely separate from fastboot. The device must be booted to recovery or the main OS to issue adb commands. To use fastboot, the device must be booted into fastboot mode for fastboot commands to be issued.
fiddlefaddle said:
Windows will probably not recognize your kindle fire... KFU should though.
Click to expand...
Click to collapse
This isn't meant to be a flame, although it might come off like one, but that doesn't make much sense. KFU is just a Windows batch file. All it does is shield the user from having to type a series of complex fastboot and adb commands (and performing some other menial tasks) in the proper sequence to get the desired effect. Without the hidden fastboot and adb commands, KFU is powerless to do anything meaningful on the Kindle Fire. Since fastboot and adb need the proper drivers in place to interface with the KF, Windows must first recognize the KF through those drivers.
Whenever i do Normal boot on kfu, it stays on waiting for device, as it obviously isnt recognizing the device.
And also would o have to install the drivers manually? I ran the install_drivers.bat...
Ethanzh said:
And also would o have to install the drivers manually? I ran the install_drivers.bat...
Click to expand...
Click to collapse
If you're still using Windows in a virtual machine, you're also going to have to make sure that the virtual machine has control of the device and not the Mac OS. Then see what the Windows device manager shows for the device. I posted up above what it should show when the KF is in fastboot mode. If it doesn't show that specific device when in fastboot mode, you need to remove whatever driver it's currently using, remove the device from the device manager, disconnect the KF and then try installing the drivers again. The KFU driver installer "should" work and it works for me, but YMMV. b63 also gave you directions on alternate ways of installing the drivers in a previous post if the KFU's installer doesn't work.
When i setup the vista machine. I told it to run windows by itself, and not share files with OsX, so i assume ill have to check the devic manager, i am at school for 4 more hours so ill try then, im 12 but im not stupid
Ethanzh said:
When i setup the vista machine. I told it to run windows by itself, and not share files with OsX, so i assume ill have to check the devic manager, i am at school for 4 more hours so ill try then, im 12 but im not stupid
Click to expand...
Click to collapse
nobody says you'r stupid - there are a lot much older people having problems with the drivers !
and allthrough i'm a win admin with 30 years of experience sometimes i don't understand what windows is doing ...
so back to your problem - found this post:
http://forum.xda-developers.com/showpost.php?p=24161305&postcount=11
maybe it's helpful for you ...
and you'r right - would check the device manager for the right driver for fastboot mode - it should be "android adb interface" - not the one with "composite" - if everything is right the command "fastboot -i 0x1949 getvar product" should return "kindle"
b63 said:
nobody says you'r stupid - there are a lot much older people having problems with the drivers !
and allthrough i'm a win admin with 30 years of experience sometimes i don't understand what windows is doing ...
so back to your problem - found this post:
http://forum.xda-developers.com/showpost.php?p=24161305&postcount=11
maybe it's helpful for you ...
and you'r right - would check the device manager for the right driver for fastboot mode - it should be "android adb interface" - not the one with "composite" - if everything is right the command "fastboot -i 0x1949 getvar product" should return "kindle"
Click to expand...
Click to collapse
OK, but when I check the device manager, there is no ADB references or such, this may mean I have to uninstall whatever the install_drivers.bat did, and manually install the drivers, and that may have also caused KFU to return '<waiting for device>' when i entered fastboot -i 0x1949 getvar product. So I'm guessing this MUST be done on windows? I sortof need to fix this by Saturday morning, because I am going on a trip without any computer!
I assume i must also download the androidsdk and extract that to C:\? I just dont realize how a computer let alone virtual machine can detect a fastbooted device.
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Same thing happening with me, i want to re-lock my bootloader but when i am in bootloader mode windows does not want to recognize the device, i have tried everything too.
Did you install the correct drivers?
When connected and in the bootloader open the device manager in windows. You should see "android 1.0" near the top.
Update that driver. It should work.
Sent from my Nexus 7 using xda premium
Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Hey, As i said earlier i was having the same problem...try switching your usb cable then try. That is what fixed my problems.
ive done all mentioned above, even tried 3 different cables, no luck, anyone have suggestions
I dont know about what you want to do, but if you want to root and unlock use the wugfresh took kit. Its the bomb and as soon as I figure out where I can thank him and give a big kudos I will give thanks.
Sent from my Nexus 7 using xda app-developers app
I could be wrong, but I don't think adb works from bootloader, but the fastboot command should. I think you can also use Google's Composite ADB Interface driver too for it (I can't reboot my N7 atm or else I'd find out).
I don't have any other android-related drivers on my system either, only Google's USB driver from the SDK. I'm also on Windows 8, but I would assume Google's USB driver would work fine on Windows 7 too.
Also certain USB filter drivers may cause issues too, such as libusb, or even AMD's USB filter driver (however, I had no problems). Or if you want to wipe out any/specific USB drivers, I recommend getting: http://www.nirsoft.net/utils/usb_devices_view.html
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand
- How My Phone Got Bricked?: (Chinese Version Oneplus 2) I Was On Oxygen OS 3.0 And TWRP 3.0 And I Decided To Flash The Resurrection Remix ROM, I Did A Full Wipe And I Installed The Rom And It Failed To Installed The ROM. Now My Phone Is In A Bootloop With No OS Installed. I Have The Chinese Version OP2
- Current State Of My Device: My Device Is In A Bootloop With No OS Installed, I Did Notice That My Phone Was Not Being Recognized VIA Fastboot & ADB On My PC. I Went Fastboot Mode And My Phone Is Not Being Recognized By PC, And I Went To TWRP, ADB Was Not Working And ADB Sideload Is Not Working. I Also Tried A USB OTG With A USB Drive And Still TWRP Recovery Is Not Recognizing It. How Ever When I Connect My Device To PC And Check Device Manager And Press Scan For Hard Ware Changes My Device Shows Up As "COM 1". I Also Did Try To Put My Phone Into Qualcomm Mode Trying Alot Of Key Combinations But My Phone Is Not Getting Into Qualcomm Mode Or It Just Might Be Me Since I Heard Its Tricky For The Phone To Get Into Qualcomm Mode. I Did Try One Click ADB And Fastboot Installed And Qualcomm USB Driver, Still No Luck. And I Did Try The MEGA Unbrick Guide. I Have Tried This With 3 Other Computers Which Are All Running Windows 10 And Turned Driver Signature Enforcement Off And Still No Luck, And Also A PC Running Linux Mint And Still No Luck. Please Help Me And I Will Put All Thanks On All Of Your Replies And I Really Appreciate Your Help!
- Whats Working:
- My Device Charges From The PC And Wall
- I Am Using The Official OP2 Cable
- Can Access Recovery + Fastboot
- Turns On But In A Bootloop
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
foomanjackel said:
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
Click to expand...
Click to collapse
Yeah I did try typing ADB devices and Fastboot devices in both twrp and fastboot. I think the issue might be the cable
evertking said:
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Click to expand...
Click to collapse
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
fahad999 said:
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
Click to expand...
Click to collapse
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
evertking said:
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
Click to expand...
Click to collapse
My cable did used to work with adb and fastboot before, and I did unlock the bootloader with it before. I think now the cable got broken
Same issue working cable
Same issue... but my cable is working fine. I have a 2nd OP2 and tried the qualcomm connect with my cable and volume up, and worked perfect. More over, I swapped motherboards and still didnt work. I have access to twrp on the phone and I can get into fastboot. But no way to connect to my pc
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
extremeinside said:
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
Click to expand...
Click to collapse
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Pieter20 said:
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Click to expand...
Click to collapse
I am also facing same problem...please help me
Does the stock recovery even have adb capabilities?