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.
Related
Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.
Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!
Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on
http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode
mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?
deleted!!!!!!!!!!
I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.
Okay, so put it in fastboot mode and try to run a fastboot devices real quick.
First off, I am very much an iOS person, so Android is very new to me. Bear with me.
My brother got a Kindle Fire today, and naturally I told him he should root it, etc. I rooted it and was installing TWRP 2.0 with Kindle Fire Utility. Unfortunately, silly me accidentally closed the CMD window, resulting in...bad things. It won't boot, the computer will not recognize a USB storage device, and it is stuck on the Kindle Fire logo. KFU does not see it either.
Please someone help. Bro will be pissed if I broke his Fire day one...
Uninstall/reinstall device drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Uninstall/reinstall device drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
How?
kona314 said:
How?
Click to expand...
Click to collapse
oh my
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
oh my
snip
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Yeah, I figured it out, I just came back to edit the post haha.
That did nothing.
OK so you've uninstalled and manually reinstalled your drivers, right?
Are you using KFU or just command prompt to change your bootmode?
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
OK so you've uninstalled and manually reinstalled your drivers, right?
Are you using KFU or just command prompt to change your bootmode?
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Neither one even recognize a Kindle.
OK, so command prompt it is.
Turn your Kindle off.
In your command prompt type (don't enter)...
fastboot devices
Plug your Kindle into the computer. It should turn itself on.
Wait about 3 seconds and hit enter. It should return a string of numbers.
Then type...
fastboot -i 0x1949 oem idme bootmode 4000
Then restart (hold power button for 30 sec.)
If you don't get a string of numbers it is usually indicative of a driver issue. In which case....Uninstall and manually reinstall your drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
OK, so command prompt it is.
Turn your Kindle off.
In your command prompt type (don't enter)...
fastboot devices
Plug your Kindle into the computer. It should turn itself on.
Wait about 3 seconds and hit enter. It should return a string of numbers.
Then type...
fastboot -i 0x1949 oem idme bootmode 4000
Then restart (hold power button for 30 sec.)
If you don't get a string of numbers it is usually indicative of a driver issue. In which case....Uninstall and manually reinstall your drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I did not get a string of numbers. I tried reinstalling the drivers earlier... Would it make a difference now? And does the fact that I'm using drivers from the KFU have anything to do with that?
Windows is a real pain sometimes when it comes to adb drivers. Try rebooting your computer and check to make sure your device manager says [Edit:] "Android ADB Interface"
Sent from my Amazon Kindle Fire using xda premium
Quick heads up, when you killed the command prompt in the middle of installing twrp 2.0 you probably just ended up leaving the kindle in fastboot mode (which is usually shown by getting stuck at the firefirefire bootloader) basically you need to plug your kindle into the computer and cd to where the adb is in your android folder like you did when you were installing twrp and punch in the command to change the boot mode back to 4000 (normal boot). In fastboot you won't get recognized by adb but when you punch in the command it will go to the kindle because fastboot is actually sort of like adb where there is a file called fastboot in the same directory on your computer that adb is in that lets you interface with your kf.
So basically plug the kindle it, cd to android/android-sdk/platform-tools/ and enter in:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot reboot
One of those should work. Don't worry about adb not recognizing the device, in fastboot mode you won't see it under adb. But the computer sees it regardless.
---------- Post added at 10:19 PM ---------- Previous post was at 10:09 PM ----------
It just occured to me that maybe you were only using the kfu and not the android sdk if not you should look into installing the android sdk and not rellying on the kfu, while it is useful these situations are easier to deal with when you have complete adb access through android sdk, google the android sdk and install it.
If "fastboot devices" doesn't recognize that a device is connected, no amount of other fastboot commands will work; in which case it's usually a driver issue.
Sent from my Amazon Kindle Fire using xda premium
In you command prompt when you type
dir
...do you see fastboot?
Sent from my Amazon Kindle Fire using xda premium
I tried a different computer...same issue.
The fastboot commands did nothing, stalled on "waiting for device."
soupmagnet said:
In you command prompt when you type
dir
...do you see fastboot?
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I did, see above post.
Well the next thing for you to do is get a factory cable as that's the best way to unbrick a brick. And sorry I guess I missed the fastboot post in the thread, I had an issue where I got stuck in fastboot and the method I posted worked but I guess your issue is different than the one I had.
isaiahhhhh said:
Well the next thing for you to do is get a factory cable as that's the best way to unbrick a brick. And sorry I guess I missed the fastboot post in the thread, I had an issue where I got stuck in fastboot and the method I posted worked but I guess your issue is different than the one I had.
Click to expand...
Click to collapse
You're fine.
By factory cable do you mean a USB cable from Amazon? If so, that's what I'm using... How do I unbrick?
If I'm horribly wrong, please explain.
isaiahhhhh said:
Well the next thing for you to do is get a factory cable as that's the best way to unbrick a brick. And sorry I guess I missed the fastboot post in the thread, I had an issue where I got stuck in fastboot and the method I posted worked but I guess your issue is different than the one I had.
Click to expand...
Click to collapse
Even with a factory programming cable which will put you in fastboot mode anyway, if there is a problem that is keeping the device from being recognized in the first place, it wouldn't do you any good.
So let's stop and start all over with the basics and try to eliminate any possibility of mistakes.
First, get rid of KFU. Uninstall and delete BOTH the adb_usb.ini and android_winusb.inf drivers. Download and install Android SDK. Configure and and install the android and adb drivers that come with the SDK using the tutorial posted here. http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Sent from my Amazon Kindle Fire using xda premium
It's funny.. this is such a simple process, yet it stumps almost everyone on these boards.
It is simply a driver issue. But it is not something you can just explain to people bow to do. It has been my experiance that even when you give a step by step people will not follow it correctly.
However.. I will attempt to at least get your driver issue solved.
First.. open device manager, device manager can be accessed from windows 7 by clicking the start menu and typing device manager.
Once device manager is up, plug in the kindle, wait for device manager to show something. You will see , unknown device, android phone, kindle fire or something similar.
Next, find the folder you downloaded with the kindle fire drivers. They are just adb drivers, but you will need to know their location. If device manager does not show "adb composite device" then you need to do the next steps.
With the driver folder located, right click on the device in device manager associated with your kindle. Click properties, click update driver, click choose driver location manually, browse to that driver folder, here you will have to uncheck the box that says display compatible devices. You should see "android composite device" as an option. Select.it and continue the install.
If you did that correctly, you should now see the fire as an adb composite device in device manager. It will now take fastboot commands.
If when you plug.in your kindle, your hear the USB connect sound, your kindle.is.not.bricked , you just need to get the right driver on it, and that is all user error when it is not done right.
I will update this thread with some screenshots for you , and verifiy my steps. I'm writing this on my phone while in bed and I stilll need coffe
Sent from my ADR6425LVW using XDA
Serinety said:
It's funny.. this is such a simple process, yet it stumps almost everyone on these boards.
It is simply a driver issue. But it is not something you can just explain to people bow to do. It has been my experiance that even when you give a step by step people will not follow it correctly.
However.. I will attempt to at least get your driver issue solved.
First.. open device manager, device manager can be accessed from windows 7 by clicking the start menu and typing device manager.
Once device manager is up, plug in the kindle, wait for device manager to show something. You will see , unknown device, android phone, kindle fire or something similar.
Next, find the folder you downloaded with the kindle fire drivers. They are just adb drivers, but you will need to know their location. If device manager does not show "adb composite device" then you need to do the next steps.
With the driver folder located, right click on the device in device manager associated with your kindle. Click properties, click update driver, click choose driver location manually, browse to that driver folder, here you will have to uncheck the box that says display compatible devices. You should see "android composite device" as an option. Select.it and continue the install.
If you did that correctly, you should now see the fire as an adb composite device in device manager. It will now take fastboot commands.
If when you plug.in your kindle, your hear the USB connect sound, your kindle.is.not.bricked , you just need to get the right driver on it, and that is all user error when it is not done right.
I will update this thread with some screenshots for you , and verifiy my steps. I'm writing this on my phone while in bed and I stilll need coffe
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Hmm... Windows tells me that it won't update the drivers because the ones I have are the same or better...
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.
i know that it's a bit silly to create an entire thread for one guy's problem, but i am stuck and probably going to give up hope when it comes to rooting my s5 neo (again, g903f), which is running android 5.1.1.
several days worth of research have yielded nothing. i can connect to my device using mtp, and i have usb 2 and 3 ports. lsusb and adb are working for me; i have set udev rules and "adb devices" returns my phone's serial number and its status. usb debugging is enabled as is the oem unlock (though whenever i try to disable developer tools and put them on again, the gui messes itself up and it won't let me turn them off, even if i refuse to put in my device's password). that's the only success i've had.
fastboot isn't working; "fastboot devices" shows nothing and it hangs at "< waiting for device>" with other commands, such as "fastboot oem unlock". adb won't work in download mode, either - though this is expected. rebooting into download mode via adb doesn't fix my problem, nor does using "sudo" or the root account.
odin3 won't work either despite the window opening with wine; the device never shows up in download mode. heimdall also doesn't seem to detect my device - although it might just be down to my ignorance.
the usual root tools, such as srsroot and kingo don't seem to do any good, though neither worked under wine, which helps to diagnose the problem. i have no access to windows, even through vmware.
i feel like everything i do only brings me one step closer to a brick wall, which i'm hitting all the time. it's like i've been chosen to experience this. if any of you guys can help me to get this phone rooted, i'd probably scream out of sheer ecstasy. and no, "try getting a girlfriend" who has windows isn't an answer.
[insert wojak here]
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Reyse said:
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Click to expand...
Click to collapse
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
thefailure said:
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
Click to expand...
Click to collapse
Did you debug (adb, fastboot) another phone already or is this your first one?
I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked
Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help