So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Syflox said:
So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Click to expand...
Click to collapse
The GS3 does not have fastboot. All flashing is done through odin.
ddggttff3 said:
The GS3 does not have fastboot. All flashing is done through odin.
Click to expand...
Click to collapse
Thanks! Also, how do I update ClockworkMod recovery to the newest one? I've used ODIN before but am not sure if it is capable of flashing .img files.
EDIT: Nevermind, I just downloaded ROM Manager and used that to flash 6.0.2.3
Related
I was trying to flash a custom ROM on my moto g xt1033. I used choosing the zip from USB otg after wiping and formatting everyrhing but. It flashed but a black screen came instead of cm logo and I was stuck at welcome to cm screen without touchscreen working. http://forum.xda-developers.com/mot...4-4-4-help-t3019082/post58587594#post58587594
Then I tried side loading or pushing method. But problem is adb commands are not working in fastboot mode. They are working when phone is switched on. (Adb devices show serial number and device in normal mode) Fastboot commands are working fine in fastboot mode but not adb. When I type adb devices in fastboot mode there is nothing after list of device attached. So adb push or adb side load give me waiting for device or device not found result. Is it normal. Earlier I have latest Motorola device manager and latest android SDK. Tried uninstalling and installing them, tried changing USB ports, tried rebooting the phone and restarting windows pc several times but still no luck.!!
Yes, it's normal that ADB commands do not work in Fastboot mode. But you can access custom recovery from the fastboot screen.
@lost101 if adb commands do not work in fastboot mode then how "adb sideload" works when we clean install a ROM? Many threads at XDA say it should work
Guru.Eclairs said:
@lost101 if adb commands do not work in fastboot mode then how "adb sideload" works when we clean install a ROM? Many threads at XDA say it should work
Click to expand...
Click to collapse
You have to be in a custom recovery (TWRP, CWM, Philz Touch) and enable the 'adb sideload' option.
lost101 said:
You have to be in a custom recovery (TWRP, CWM, Philz Touch) and enable the 'adb sideload' option.
Click to expand...
Click to collapse
I have latest philz touch. Also tried twrp..but adb still not working in fastboot mode or recovery mode. The device disappears from My Computer area when in fastboot
Guru.Eclairs said:
I have latest philz touch. Also tried twrp..but adb still not working in fastboot mode or recovery mode. The device disappears from My Computer area when in fastboot
Click to expand...
Click to collapse
It doesn't work on all versions of Windows; I think I've had it working in Windows 7. But I mainly use it in Linux - where no driver is required.
I also have windows 7.. Thanks Anyway
Guru.Eclairs said:
I also have windows 7.. Thanks Anyway
Click to expand...
Click to collapse
It's a driver issue. Your phone is not being recognised. If you boot a Linux LiveCD from DVD / USB, you can access recovery mode ADB that way.
sudo apt-get install android-tools-fastboot
Not sure if this will help but, after completely wiping my phone, I installed TWRP using fastboot commands, booted to TWRP, mount, copy ROM to moto g, and install using TWRP.
If you are in fastboot mode, type fastboot devices and see what happens.
audit13 said:
Not sure if this will help but, after completely wiping my phone, I installed TWRP using fastboot commands, booted to TWRP, mount, copy ROM to moto g, and install using TWRP.
If you are in fastboot mode, type fastboot devices and see what happens.
Click to expand...
Click to collapse
Fastboot Devices command works flawlessly in fastboot mode. I can flash .IMG files. But none of adb commands working. When I type adb devices there is no result after List of Devices attached. So I can't sideload anything
I'm not 100% sure how adb works on the moto g but I don't think adb commands work in fastboot mode. When I connect my moto G to my computer after the ROM has booted and I am at the phone's desktop, I type "adb devices" and I see my device listed. Then I type "adb reboot-bootloader" to get into fastboot mode and adb commands no longer work.
I have Philz Touch on my Moto G and sideloading is an option. I don't think you can side load from fastboot.
audit13 said:
I'm not 100% sure how adb works on the moto g but I don't think adb commands work in fastboot mode. When I connect my moto G to my computer after the ROM has booted and I am at the phone's desktop, I type "adb devices" and I see my device listed. Then I type "adb reboot-bootloader" to get into fastboot mode and adb commands no longer work.
I have Philz Touch on my Moto G and sideloading is an option. I don't think you can side load from fastboot.
Click to expand...
Click to collapse
If adb doesn't work in fastboot mode then whats the propose of word "sideload"
Guru.Eclairs said:
If adb doesn't work in fastboot mode then whats the propose of word "sideload"
Click to expand...
Click to collapse
I have no idea as I have never used adb to install anything except apk files when the phone has been booted to the desktop.
I always use fastboot commands to install recovery and install stock ROMs.
Using adb to side load may refer to the aibility to install files while the phone is running.
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/
audit13 said:
I have no idea as I have never used adb to install anything except apk files when the phone has been booted to the desktop.
I always use fastboot commands to install recovery and install stock ROMs.
Using adb to side load may refer to the aibility to install files while the phone is running.
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/
Click to expand...
Click to collapse
OK leave it. Do you have any idea how to increase 2g/3g speed. Any trick/mod/script?? I flashed cm11 quarx build and internet is painfully slow
Edit- no sideload means pushing a flashable zip to the root of internal storage when phone is in recovery mode. We do it for clean installing ROMs.(Format and wipe everything). After format there is no operating system left in phone so we do sideload rom
Guru.Eclairs said:
OK leave it. Do you have any idea how to increase 2g/3g speed. Any trick/mod/script?? I flashed cm11 quarx build and internet is painfully slow
Edit- no sideload means pushing a flashable zip to the root of internal storage when phone is in recovery mode. We do it for clean installing ROMs.(Format and wipe everything). After format there is no operating system left in phone so we do sideload rom
Click to expand...
Click to collapse
Sorry, I don't know how to increase speed except try a different radio/modem on your phone. I rarely use data on my phone because I have an iPad with LTE.
Guru.Eclairs said:
Fastboot Devices command works flawlessly in fastboot mode. I can flash .IMG files. But none of adb commands working. When I type adb devices there is no result after List of Devices attached. So I can't sideload anything
Click to expand...
Click to collapse
Sounds like your fastboot driver is working fine but your adb driver is not...go into your custom recovery and then check Device Manager in Windows to see if you have all your drivers working properly.
If you are having adb driver issues you could try the Universal adb driver setup file attached.
adb commands don't work in fastboot mode. Install a recovery (Preferably TWRP because I forget how CWM's adb sideload works). For TWRP, go to advanced, then adb sideload. Make sure to install the adb drivers tho, or else the sideload won't work. If you're sticking with stock, press the Vol+ button for about 15 secs, then tap the power button. Use the Vol- and + keys too scroll. There should be an option like "Install firmware through adb" or something. Scroll to that, then hit the power button to go to that option. Then, just sideload the firmware.
Check device manager 1st phone is conected properly
adb has no relation to fastboot.adb will not work while in fastboot, it never worked that way either.
There is no sideload while in fastboot, you're confusing it with the adb sideload, that has nothing to do with fastboot.
Reading and comprehension are desirable here.
I need to restore to stock firmware to get Lollipop, but adb won't recognise my phone in cmd, thus I can't follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 . I installed the Motorola Drivers from here: http://forum.xda-developers.com/showthread.php?t=2550635 , and I have the Motorola Device Manager installed. MotoTool picks up my device and is able to boot it into fastboot and install CWM or TWRP, but when I try to flash stock recovery using MotoTool it either gives me a 'no command' screen or doesn't work at all. Anyone having the same problem/know how to fix this? I'm on the Moto G 2013 XT1032 British retail.
EDIT: I fixed it! I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/show...3#post54872143 then used Moto Tool to flash it, as that recognised my phone. I could then download the OTA as normal and installed it like a regular update. Enjoying Lollipop!
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
audit13 said:
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Click to expand...
Click to collapse
SammyP6 said:
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes to both of these, I was in fastboot and 'adb devices' came back with nothing even though I was in the directory where adb and fastboot were installed and the phone had USB debugging enabled. I fixed it a different way though, I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143 then used Moto Tool to flash it as that recognised my phone. I could then download the OTA as normal and installed it like a regular update.
Adb commands won't work when the phone is in fastboot mode from what I have seen.
audit13 said:
Adb commands won't work when the phone is in fastboot mode from what I have seen.
Click to expand...
Click to collapse
They didn't work at all, no matter what mode I was in. All sorted now though.
Fithboy said:
They didn't work at all, no matter what mode I was in. All sorted now though.
Click to expand...
Click to collapse
It's great you that got the issue sorted out.
Post your solution in case it may help other users down the road. Thanks.
Hello guys. I have HTC Sensation, Bootloader unlocked, S-ON, HBOOT-1.27.0000
Yesterday I tried to flash TWRP using fastboot. I have downloaded ADB drivers and also HTC drivers. Connected device and everything was working good. ADB showed my device serial number (or what it is, I don't remember) when I type "adb devices" in command. Then I typed "cd Downloads" to point to download directory (this is where I have twrp.img) and at least "adb reboot bootloader" . Device rebooted into bootloader, but, suddenly, popup appeared on my laptop, it was saying "USB device not recognized". I have closed it and go into command, I typed "adb devices" again, but it didn't show anything at this time. Then I run command "fastboot flash recovery twrp.img" and it returned "Waiting for device...".
After no luck., I have tried to install twrp.img though Flashify. It successfully flashed. I go into recovery, make a backup, perform clean wipe and tried to flash CM12. But it didn't flash. Then I go to restore tab but I can't see my backup. So, TWRP is not flashing anything, I have even tried stock ROM, also it's not backing up things. So now, I'm in bootloop, no OS is installed on my sensation and every time I boot up device, it automatically going into recovery.
I have laptop running Windows 10. I want to make ADB working in bootloader mode or make TWRP working to flash something.
Thanks in advance.
DroidTwe4kz said:
Hello guys. I have HTC Sensation, Bootloader unlocked, S-ON, HBOOT-1.27.0000
Yesterday I tried to flash TWRP using fastboot. I have downloaded ADB drivers and also HTC drivers. Connected device and everything was working good. ADB showed my device serial number (or what it is, I don't remember) when I type "adb devices" in command. Then I typed "cd Downloads" to point to download directory (this is where I have twrp.img) and at least "adb reboot bootloader" . Device rebooted into bootloader, but, suddenly, popup appeared on my laptop, it was saying "USB device not recognized". I have closed it and go into command, I typed "adb devices" again, but it didn't show anything at this time. Then I run command "fastboot flash recovery twrp.img" and it returned "Waiting for device...".
After no luck., I have tried to install twrp.img though Flashify. It successfully flashed. I go into recovery, make a backup, perform clean wipe and tried to flash CM12. But it didn't flash. Then I go to restore tab but I can't see my backup. So, TWRP is not flashing anything, I have even tried stock ROM, also it's not backing up things. So now, I'm in bootloop, no OS is installed on my sensation and every time I boot up device, it automatically going into recovery.
I have laptop running Windows 10. I want to make ADB working in bootloader mode or make TWRP working to flash something.
Thanks in advance.
Click to expand...
Click to collapse
adb doesn't work in bootloader, only fastboot
when you enter in bootlaoder choose fastboot
in the hboot screen you will see fastboot usb
then you can use any fastboot command
i suggest to change the recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
then before flashing the new rom from 4ext enable smartflash from it(because you are on S-ON)
rzr86 said:
adb doesn't work in bootloader, only fastboot
when you enter in bootlaoder choose fastboot
in the hboot screen you will see fastboot usb
then you can use any fastboot command
i suggest to change the recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
then before flashing the new rom from 4ext enable smartflash from it(because you are on S-ON)
Click to expand...
Click to collapse
It doesn't even works in fastboot too :/ So I can't use any fastboot command
DroidTwe4kz said:
It doesn't even works in fastboot too :/ So I can't use any fastboot command
Click to expand...
Click to collapse
Probably win 10 is the issue
rzr86 said:
Probably win 10 is the issue
Click to expand...
Click to collapse
Drivers and SDK is compatible with Windwos 10. I don't think it's the problem, but thanks anyways.
DroidTwe4kz said:
Drivers and SDK is compatible with Windwos 10. I don't think it's the problem, but thanks anyways.
Click to expand...
Click to collapse
use usb 2.0 ports not 3.0
if nothing works then a ruu.exe to return back to stock
http://forum.xda-developers.com/showthread.php?t=1672425
by the way did you enable usb debugging mode from settings?
rzr86 said:
use usb 2.0 ports not 3.0
if nothing works then a ruu.exe to return back to stock
http://forum.xda-developers.com/showthread.php?t=1672425
by the way did you enable usb debugging mode from settings?
Click to expand...
Click to collapse
OK thanks, I'll try them.
Well, I'm not that much noob USB Debugging is enabled.
Hi, I've deleted all storage from my device and all I've got now is TWRP recovery.
I', trying to push a rom through fastboot but my PC won't recognize my device, I have Universal ADB Drivers intalled, also I've got Samsung ADB drivers istalled, and Android SDK installed; yet my device won't show up when I'm in fastboot and typing 'adb devices'.
Obviously I cannot turn Debugging on since I don't have a system.
so...
what CAN I do?
thanks
Lidor167 said:
Hi, I've deleted all storage from my device and all I've got now is TWRP recovery.
I', trying to push a rom through fastboot but my PC won't recognize my device, I have Universal ADB Drivers intalled, also I've got Samsung ADB drivers istalled, and Android SDK installed; yet my device won't show up when I'm in fastboot and typing 'adb devices'.
Obviously I cannot turn Debugging on since I don't have a system.
so...
what CAN I do?
thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2788632
Use drivers and setup from this guide.
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
J0hncramer said:
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
Click to expand...
Click to collapse
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
LokifiedMee said:
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
Click to expand...
Click to collapse
I just tried fastboot devices in powershell while the phone is connected via USB in fastboot mode and nothing was listed
Edit: i was able to get fastboot to work, I had to do the following steps i found on stack exchange to get my device to show up properly in device manager:
https://stackoverflow.com/questions/8588595/android-fastboot-devices-not-returning-device
Open device manager
Find Unknown "Android" device (likely listed under Other devices with an exclamation mark)
Update driver
Browse my computer for driver software
Let me pick from a list of devices, select List All Devices
Under "Android device" or "Google Inc", you will find "Android Bootloader Interface"
Choose "Android Bootloader Interface"
Click "yes" when it says that driver might not be compatible
Click to expand...
Click to collapse
With fastboot working and issues in device manager solved I was able to get TWRP loaded to my phone via fastboot and change my boot slot to get back into the phone