Well I am familiar with ADB and fastboot although when I boot my S7 into fastboot protocol my MAC does not see it.
When my S7 is booted up in Android my MAC does see it in ADB devices.
I really do want to root my S7 but I do not own a pc and I'm not very proficient with windows.
So if anyone has any advice then I am all ears.
Found this on an android wiki:
If you are developing on a linux host, you may need to tweak UDEV to recognize the phone in fastboot mode. You may already have done this to get the phone recognized in Eclipse, but you need to do it again for fastboot, since fastboot uses a different device ID: 0bb4:0c01. The warning sign is that fastboot says "< waiting for device >" forever, even when you have the "FASTBOOT" message on the phone; if this happens, try adding the device ID 0bb4:0c01 to your UDEV configuration for Android."
That <waiting for device> is exactly what is happening to me. Is there anyone who can explain the UDEV configuration for android thing?
Related
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
Any help with my problem would be greatly appreciated!
Recently I managed to soft brick my Kindle Fire HD 7", and hoped to use the "KFHD System.img Restore Tool" to fix. I bought a factory cable and was able to put my Kindle into fastboot mode. Prior to this I had ADB installed so I could root my KFHD (which I did).
Now obviously when I rooted my KFHD, ADB recognized my device then. Unfortunately, now I have no such luck. While in fastboot I tried to use the command ---> adb shell su -c "reboot bootloader" <--- but I kept getting error messages that stated there was no recognized device.
I re-installed the AndroidSDK file to ensure there were no errors there and tested ADB with successful results. I also re-installed the Device Drivers and made sure that in my device manager under Kindle Fire it said "Android ADB composite interface" (or similar, I don't remember off of the top of my head). I went back and tested again, and ADB still does not recognize my device while in fastboot. I then left my Kindle on until it ran out of battery to test to see if ADB would recognize when out of fastboot.
After turning on my Kindle when not in fastboot, I typed in the command prompt "adb devices" and no device showed up. Also, now under my device manager "Android ADB composite interface" or whatever doesn't even show up. I have searched over and over again on many forums with no luck. Does anyone know what I am doing wrong? Or what I should try doing?
Sorry for that ^huge story^ but thanks in advance for any feedback!
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
"That's a special kind of stupid. The kind that makes me laugh."
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
bryanchapman9999 said:
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
Click to expand...
Click to collapse
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ive been using the android drivers on windows 8 without an issue. They have to be manually installed and driver signing needs to be turned off.
Sent from my KFOT using Tapatalk 2
soupmagnet said:
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
Click to expand...
Click to collapse
I see, well the program seemed to work fine without it apparently (the line of code). My Kindle is working perfectly again! Thank you for the reply.
I originally posted this question in XDA Assist yesterday. I was directed to this forum, and after reading more here, have added a few more questions/concerns with ***___**** that came after digging through the forum stickies. I know this has become a huge post, so apologies in advance.
I'm having some trouble mounting a Kindle Fire HD 7 Gen2 (Tate) in Fastboot mode on my system which is running Ubuntu 14.04.
I am new to any kind of Android development and have been following the excellent guides here by @kinfauns. Specifically I have the 5-scecond boot loop problem related to the power draw issue. The solution I'm pursuing is to swap the stock bootloader for FireFireFire. The guide says to do it with fastboot, since the conventional flash recovery method could be interrupted by the shutdown cycle.
******* After reading the Faq here, I am concerned that even if Fastboot were to detect the device, that simply using it to load the FireFireFire bootloader directly onto the device would cause the problem of the wall of fire because of the M-Shield issue. Seems I would have to follow these steps here or here to load FireFireFire as a 2nd bootloader (including downgrading the OS to v7.2.3), is that correct? Also one of those pages says not to use automated tools like FireFireFire... which I thought was a bootloader, so what bootloader should I use to get around the low battery cycle startup problem that FireFireFire specifically addresses with it's startup battery check *******
So now, just when I think I have a solution to my real problem, I get out the fastboot cable, connect the kindle to my PC, and I get an error in Nautilus.
******In one of the pages linked above, it makes a passing reference to some fastboot cables not putting the device in Fastboot. Since I cannot connect to the device in the first place when it is in "fastboot", I cannot use their method to confirm fastboot is working. When bootup with my fastboot cable, the "image" on the device does change from orange & flashing "Kinde Fire" to the orange "Kindle Fastboot" pic, so I'd to know if I can rule out the cable as part of my problem... *****
Here is the error from Nautilus: Unable to open MTP device '[usb:001,006]'. Attempting mtpfs at the terminal returns:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=1949 and PID=0007) is a Amazon Kindle Fire (ID1).
Found 1 device(s):
Amazon: Kindle Fire (ID1) (1949:0007) @ bus 1, dev 6
Attempting to connect device
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
I found a tutorial on Ubuntu forums for getting MTP to work that involved using lsusb command to get the device id, making entries in /etc/udeb/rules.d and /lib/udev/rules.d, supposedly to allow MTP to access the device with proper credentials. However that didn't work. It seems that in Fastboot I actually might not MTP to handle the device...
OTOH, when the device is NOT in Fastboot mode, it mounts just fine, both in Nautilus and for purposes of checking with the adb devices command....
***** Since yesterday, I back and compared the vendor and product codes reported in lsusb and noticed that they are the same regardless of whether I connect the device using a regular cable (when it mounts correctly) and the fastboot cable (when the screen says fastboot, and I get the "raw device" failure to mount. My understanding is that the hardware ID should be different if the device is in fastboot mode vs "normal" mode. Is that correct? How do I deal with this behavior if the device is supposed to load different drivers when in different modes?*****
However, it seems to me that what I want is for it to mount in file transfer mode instead of MTP mode when in fastboot. The fix for this exact issue in Windows (as reported on other sites) is to change the driver in Windows Device Manager.
***** The other thing I tried was using the modprobe command to manually start the usb-storage driver as explained here. However the step to confirm the driver was unsuccessful because the /var/log/messages file was not found by the tail command. Even though that is really an ubuntu / linux question, perhaps someone here can help with some guidance on confirming the mass storage driver as well?*****
Can anybody help with this problem please?
Thank you
Additional detail
In case it's helpful to diagnose the issue, I am now experiencing an odd behavior where the device starts out in Fastboot (using the fastboot cable), and then after about 30+ seconds, it automatically switches to the "swipe" screen as though it was in normal mode.
This happened after I went and rem'd out all references to this device in the MTP rules files. The first time I plugged it in, Ubuntu popup asked how it should handle the device. I didn't see "mass storage" so I hit cancel. At that point, it started to flop over from fastboot into normal automatically even though it is plugged into a fastboot cable.
My understanding was that a fastboot cable forced it into fastboot mode (or else was somehow device in-compatible with certain Kindles). I don't understand how the host OS could do this without issuing an ADB / shell command?
man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason
You can't use adb commands when in fastboot mode and vice versa.
knives of ice said:
man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason
Click to expand...
Click to collapse
I have same problems. Please explain how you have solved. Which drivers the Mi Mix needs in fast boot mode?
basically, you have to watch your device manager for the ANDROID to pop up and it should have a yellow exclamation. you have to fix the drivers, but the problem is at least in my case you have to complete and fix the drivers before the mix puts itselt out of fastboot and into charging (which it does quite quickly when not connected)
install this:
http://forum.xda-developers.com/showthread.php?t=2588979
and follow the guide that he posts in the pictures on what you need to change
here
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
as soon as you have the drivers fixed windows will tell you and the mix will stay connected
I'm using Ubuntu Yakkety Yak, 16.10.
According to Android SDK manager: Android SDK Tools v 25.0.3 Android Build Tools v 25.0.2 Android SDK Tools v 25.2.5
My phone is a OnePlus 3t and I'm developing for it for a while, adb works normally, udev rules are configured. I enabled OEM boot, and manage to reboot in a way which looks like to me fastboot. After rebooting to "fastboot" the device's USB id is exactly the same as in normal boot, that's a red flag.
Regular USB ID is Bus 001 Device 024: ID 05c6:676c Qualcomm, Inc.
I get the desired fastboot one when I switch the USB mode to MTP (Bus 001 Device 013: ID 2a70:9011).
My final goal is to unlock my phone ans install TWRP (for DayDream mod). Since fastboot devices doesn't show any device I cannot issue fastboot oem unlock.
Do I need some USB driver for Linux for the MTP mode? The Bus 001 Device 013: ID 2a70:9011 doesn't show any OEM manufacturer string.
This should just work. I don't get it. I'm tearing my hair out.
android.stackexchange.com/questions/169509/why-fastboot-devices-is-empty-on-ubuntu-16-10
android.stackexchange.com/questions/166033/how-to-flash-and-root-oneplus-3t-on-linux?noredirect=1&lq=1
MrCsabaToth said:
I'm using Ubuntu Yakkety Yak, 16.10.
According to Android SDK manager: Android SDK Tools v 25.0.3 Android Build Tools v 25.0.2 Android SDK Tools v 25.2.5
My phone is a OnePlus 3t and I'm developing for it for a while, adb works normally, udev rules are configured. I enabled OEM boot, and manage to reboot in a way which looks like to me fastboot. After rebooting to "fastboot" the device's USB id is exactly the same as in normal boot, that's a red flag.
Regular USB ID is Bus 001 Device 024: ID 05c6:676c Qualcomm, Inc.
I get the desired fastboot one when I switch the USB mode to MTP (Bus 001 Device 013: ID 2a70:9011).
My final goal is to unlock my phone ans install TWRP (for DayDream mod). Since fastboot devices doesn't show any device I cannot issue fastboot oem unlock.
Do I need some USB driver for Linux for the MTP mode? The Bus 001 Device 013: ID 2a70:9011 doesn't show any OEM manufacturer string.
This should just work. I don't get it. I'm tearing my hair out.
android.stackexchange.com/questions/169509/why-fastboot-devices-is-empty-on-ubuntu-16-10
android.stackexchange.com/questions/166033/how-to-flash-and-root-oneplus-3t-on-linux?noredirect=1&lq=1
Click to expand...
Click to collapse
Just OEM unlock from the settings...
domsch1988 said:
Just OEM unlock from the settings...
Click to expand...
Click to collapse
I wish it was that easy. The Settings option is more precisely called "OEM unlocking" with the explanation "allow the bootloader to be unlocked". So it just allows it, but does not do the unlocking itself. I turned this option on. For the unlocking I should issue the fastboot oem unlock command. I did try to install TWRP BTW without it, but obviously it didn't succeed. I need to unlock first, just as other tutorials say. For that I first have to see my phone in the fastboot devices list, which is empty. I'm still tearing my hair out.
MrCsabaToth said:
I wish it was that easy. The Settings option is more precisely called "OEM unlocking" with the explanation "allow the bootloader to be unlocked". So it just allows it, but does not do the unlocking itself. I turned this option on. For the unlocking I should issue the fastboot oem unlock command. I did try to install TWRP BTW without it, but obviously it didn't succeed. I need to unlock first, just as other tutorials say. For that I first have to see my phone in the fastboot devices list, which is empty. I'm still tearing my hair out.
Click to expand...
Click to collapse
Try running
Code:
sudo fastboot devices
casual_kikoo said:
Try running
Code:
sudo fastboot devices
Click to expand...
Click to collapse
Yes, sudo didn't make any difference from the beginning.
Hello,
I too am going crazy trying to get fast boot to work on this OnePlus 3T. My research prior to purchasing indicated that this phone was friendly to rooting. I'm no on hour 6, and still can't get fast boot to work. Using Ubuntu 16.04, and the adb and fastboot packages installed from the standard repositories (apt-get install adb..)
sudo, sudo -s, udev rules, etc. nothing has worked.
If anyone has used this phone and os combination to get the unlocking working, please advise.
I've found out the root cause of my problem. I thought that fastboot is one step further from the "actual" fastboot screen. You have to issue the fastboot commands when you see the screen what is in my android stackexhange link.
So I could unlock the bootloader now, now when I try to flash TWRP I get:
Code:
[email protected]:~/Android/Sdk/platform-tools$ sudo ./fastboot flash recover twrp-3.0.3-1-oneplus3t.img
target reported max download size of 440401920 bytes
sending 'recover' (17588 KB)...
OKAY [ 0.560s]
writing 'recover'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.580s
The USB device I see is
Code:
Bus 001 Device 018: ID 18d1:d00d Google Inc.
and I set up udev rules for it.
Ok, it was just a typo: recover -> recovery
Finally!
Thank you MrCsabaToth!
After 2 more hours trying this following instructions for Windows 7, and OS X (after Ubuntu 16), MrCsabaToth's reply looks to be the way to get past the fastboot oem unlock step.
You have to run it while actually on the phone's boot screen where it gives you options of what type of boot to do, where the top line option is "fast boot". Only then, will the fastboot command from the terminal work.
Not even the oneplus web site tutorial, which is for this exact phone, mentions this. WTF......