for some reason my crespo4g is having issues being detected through fastboot (on Ubuntu 11.10). This happened over a month ago when I flashed the unrooted leaked 4.0.4 and I did it to both mine and my girlfriend's devices. I had no problem flashing CWM through fastboot onto her device but it won't detect mine for some reason. This is getting aggravating because I don't know any other way to replace stock recovery with CWM. Does anyone have a fix for this?
Same here, drivers are working, device shows up in the device manager (Win7x64), ADB is working properly, but fastboot refuses to detect the device. Any ideas on this?
EDIT: Would you look at that? New fastboot version required to talk to the 4.0.4...
Update your Android SDK, and you should be all set!
Related
Hi guys, I have a strange issue and hope that someone could help me...
I'm on 4.2 CleanRom with 3.14 bootloader (the old one, I flashed it for the root) and I can't activate debug, so I can't get adb working, if I activate it on dev options just doesn't change anything...
so I tried to do a "flash factory img" from wug's toolkit, but...when I get in fastboot and plug the cable the fastboot menu freezes, and I have to force turn off...if I don't plug the cable it works!
at this point I tried to flash the new 4.13 bootloader (I think that the 4.2 rom doesn't like the old one), I flash it from recovery but when I reboot I find the old one...
SO, no adb. no fastboot, no factory image....what should I do? luckily I have a good working rom and I can get to recovery, but if something goes wrong? I can't restore the stock image...and I will have to throw away my nexus...
anyone has a suggestion? thanks
EDIT: solved, it was a driver problem, I tried to root an xperia few weeks ago and something with drivers messed up...everything is ok now!
close please
hi everybody, i hope, that someone can help me,
i thought i should root my Z1 and it was not a problem via windows (via LINUX i couldnt even find the device via "adb devices")
it was not a problem. first i installed twrp, but everytime when i restarted the recoverymenu, twrp went away and the default recovery menu started. so i installed CMR and it was not a problem. so far everything okay. but than i thought i should install the current nighlies of cynagonMOD and the problems started
when i try CMR to installed the current nightlies, i get the error
""this package is for device:Z1 ; this device is jfltexx" nomatter if its the nightly from 13.11.2015 or 14.11.2015
under windows, when i start adb devices, the device will be found
adb devices
List of devices attached
529e86fb device
and when i try to start into fastboot, it is possible. but when i'm in fastboot-modus
i can do anything. nothing happens. whatever i try, i get the feedback "waiting for devices"
any idea? can someone tell me, whats the problem is?
@update: when im in CMR, windows shows my ZUK z1 as GT-I9505 (i guess its samsung right?) how can i deinstall CMR and install TWRP (cause via fastboot its not possible)
Do you use fastboot with the -i switch followed by the device ID?
at the first time yes. but now its not possible. im now really frustrated, cause now im in the boot animation loop and can do nothing. even not able to upload any zip files to restore the zuk cyagon OS . any idea how i can install now the normal version of the phone again? i can only enter CMR
After taking nougut update my moto x style was having some bettery drain issue so i flashed MPHS24.107-58-5 using fastboot. Then updated to MPHS24.107-58-13 via ota.
Everything works fine and the rom status is official.
But sometime when using mx player it freeze and if i try to use home button to recover from freeze it goes to home but the luncher also freezes.
After some browsing i came to know that flashing Motorola phones using fastboot instead of mfastboot can cause problems.
So is it mx players bug or because of flashing via fastboot?
And when i had nougut i installed it using ota so i had to flash stock firmware via fastboot before taking update.
Can the battery drain can come from this issue?
yk1999 said:
After taking nougut update my moto x style was having some bettery drain issue so i flashed MPHS24.107-58-5 using fastboot. Then updated to MPHS24.107-58-13 via ota.
Everything works fine and the rom status is official.
But sometime when using mx player it freeze and if i try to use home button to recover from freeze it goes to home but the luncher also freezes.
After some browsing i came to know that flashing Motorola phones using fastboot instead of mfastboot can cause problems.
So is it mx players bug or because of flashing via fastboot?
And when i had nougut i installed it using ota so i had to flash stock firmware via fastboot before taking update.
Can the battery drain can come from this issue?
Click to expand...
Click to collapse
It's probably an MX Player bug, try a different player.
Fastboot or mFastboot is not relevant... the protocols are used are open and I believe both are built on the same source code, Moto just built their own for some reason. mFastboot hasn't been updated for years, I wouldn't use it anymore. there is no reason not to use normal fastboot or to suspect it could cause any issue. It will either work, or not work.
acejavelin said:
It's probably an MX Player bug, try a different player.
Fastboot or mFastboot is not relevant... the protocols are used are open and I believe both are built on the same source code, Moto just built their own for some reason. mFastboot hasn't been updated for years, I wouldn't use it anymore. there is no reason not to use normal fastboot or to suspect it could cause any issue. It will either work, or not work.
Click to expand...
Click to collapse
Which is the newest fastboot version ?
I use 1.4.3 portable.
But when i try to sideload official ota via adb it says no device found.
When i try adb devices it doesn't show my device serial number but when the phone is on it recognises my phone.
yk1999 said:
Which is the newest fastboot version ?
I use 1.4.3 portable.
But when i try to sideload official ota via adb it says no device found.
When i try adb devices it doesn't show my device serial number but when the phone is on it recognises my phone.
Click to expand...
Click to collapse
fastboot ≠ adb
Your device must be in sideload mode (start recovery, select "Apply update from SDB") in order for it to be seen in adb as a sideload device, if it is then your ADB version is too old (like more than 3 or 4 years old) or your drivers are not installed correctly (I use Linux, drivers are not relevant). If it isn't in sideload mode, then it won't be seen in the bootloader at all (although sometimes it will say "fastboot" with some devices, but not Motos).
I have no idea what the most current version is, if you use Windows then just grab the latest Mini ADB & Fastboot package from here. EDIT: 1.4.3 is the latest, your good.
Am using pretty old adb and fastboot... ADB is 1.0.32 and both are from March 2016 and I have no issues with any device from Froyo (yes, I still have a 2.2 device that is functional) to Nougat.
If your system is corrupt, which you seem to be questioning, it isn't because of your fastboot or adb applications.
acejavelin said:
fastboot ≠ adb
Your device must be in sideload mode (start recovery, select "Apply update from SDB") in order for it to be seen in adb as a sideload device, if it is then your ADB version is too old (like more than 3 or 4 years old) or your drivers are not installed correctly (I use Linux, drivers are not relevant). If it isn't in sideload mode, then it won't be seen in the bootloader at all (although sometimes it will say "fastboot" with some devices, but not Motos).
I have no idea what the most current version is, if you use Windows then just grab the latest Mini ADB & Fastboot package from here. EDIT: 1.4.3 is the latest, your good.
Am using pretty old adb and fastboot... ADB is 1.0.32 and both are from March 2016 and I have no issues with any device from Froyo (yes, I still have a 2.2 device that is functional) to Nougat.
If your system is corrupt, which you seem to be questioning, it isn't because of your fastboot or adb applications.
Click to expand...
Click to collapse
I have motorola device manager installed and my os is windows 7 32 bit.
Device is in sideload mode but adb doesn't recognize.
So I can only flash ota via "flash update from sd card " option.
Is there any problem using this option?
yk1999 said:
I have motorola device manager installed and my os is windows 7 32 bit.
Device is in sideload mode but adb doesn't recognize.
So I can only flash ota via "flash update from sd card " option.
Is there any problem using this option?
Click to expand...
Click to collapse
No... Just rename OTA file to "update.zip" place on root of SD card.
Still a driver issue... I don't know Windows anymore, haven't used it on a personal computer for over 3 years.
acejavelin said:
No... Just rename OTA file to "update.zip" place on root of SD card.
Still a driver issue... I don't know Windows anymore, haven't used it on a personal computer for over 3 years.
Click to expand...
Click to collapse
Is there any problem if i don't rename it as "update.zip"
I flashed ota many time without renameing it.
yk1999 said:
Is there any problem if i don't rename it as "update.zip"
I flashed ota many time without renameing it.
Click to expand...
Click to collapse
No, it's fine... Just old habits. On some devices it's required or recovery can't find the update file.
Don't worry so much... Things like this either work or don't, there is no "kinda".
Please help!!!
I tried to update my rooted Nexus 6P to 8.0.0 (OPR5.170623.011, Nov 2017) using the Flashfire app and something went wrong!!! The phone is now stuck in bootloop and will not get past the 4 google coloured dots. I can boot the phone into the bootloader and then get into TWRP recovery from there but thats pretty much it.
I hoped I would be able to fix it by flashing the system image, bootloader etc using adb and fastboot but have had no luck. I have tried on both a PC and a Mac and neither seem to recognize the device. When using the commands "adb devices" or "fastboot devices" nothing shows up and when I try to flash anything it says "waiting for any device" yet when the phone is off it signals that it is charging from the laptop.
I have updated my rooted 6P multiple times before using both Flashfire and adb/fastboot from both a PC and a Mac and have never had problems before this. I have run out of ideas to try so any help would be greatly appreciated but I fear I might have bricked my beloved Nexus 6P.
MilkyOolong said:
Please help!!!
Click to expand...
Click to collapse
Weird. You should at least have fastboot when in bootloader mode, and MTP with TWRP. In bootloader mode, plug the device into your PC. The device is not detected at all? Have you tried wiping cache/dalvik? MTP not working in TWRP?
If you can boot into recovery then your device is not bricked. Make sure the adb and fastboot binaries on your computer are completely up to date. I'm pretty sure Google updated them for Oreo. You will need to flash the full stock image with flash-all.bat command when you get your computer to recognize your phone. Updating from Nougat to Oreo using Flashfire or Flashify is a bad idea because you are dealing with something way more extensive than an OTA update.
I had previously unlocked my bootloader, installed the latest Magisk, and created and booted a patched recovery.img to gain root access. I recently updated to SHIELD Software Experience Upgrade 8.2, but for some reason, fastboot no longer detects my 2019 SHIELD TV Pro when I am trying to send commands on the bootloader menu. It detects my device just fine when I boot up Android and successfully executes any ADB commands that I send, so it is only a fastboot problem. I made sure to install the latest drivers for fastboot, but while my Surface detects my SHIELD without errors, fastboot still cannot find it. After hours of trial and error, I decided to finally sign up here to see if anyone could help me.
Here is a similar issue with a different device a few months ago:
https://forum.xda-developers.com/galaxy-a20/help/fastboot-sm-a205u-t4135987