So I am having trouble with adb it seems like. When in fastboot and using adb I type in "fastboot devices" and my phone shows up and when typing "adb version" the version number shows up too. But when I go into recovery and try to sideload the 4.4.1 update to my phone I get a message that my device couldn't be found.
Any suggestions on what this could be? I tried using a toolkit too and I get the same message showing up too.
Did you press vol up + power button in stock recovery and select sideload from adb? That right there should enable adb mode in recovery.
peachpuff said:
Did you press vol up + power button in stock recovery and select sideload from adb? That right there should enable adb mode in recovery.
Click to expand...
Click to collapse
Yes I did. After I do that I type "adb sideload <file name>" and then that is when i get the message that the device cant be found.
peachpuff said:
Did you press vol up + power button in stock recovery and select sideload from adb? That right there should enable adb mode in recovery.
Click to expand...
Click to collapse
Install Koush's Universal ADB Drivers.
Had the same problem. Google drivers not working in recovery sideload mode.
Aerowinder said:
Install Koush's Universal ADB Drivers.
Had the same problem. Google drivers not working in recovery sideload mode.
Click to expand...
Click to collapse
Will do. I shall report back if it works or not.
Aerowinder said:
Install Koush's Universal ADB Drivers.
Had the same problem. Google drivers not working in recovery sideload mode.
Click to expand...
Click to collapse
Worked like a charm thanks!
Related
Hey,
i just wanted to flash the newest clockworkmod but my fastboot.exe does nothing.
Phone is in fastbootmode, please help
Windows 7 x64...but it worked the other day
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Fmbl said:
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Click to expand...
Click to collapse
i can flash the recovery fia ROMManager, and also can boot into it, but when i boot the phone into bootloader/fastboot mode i can't flash a new recovery, because when i hit enter after "fastboot" i get no output in cmd
If you don't get anything back on fastboot devices, then you either don't have the proper drivers installed, don't have the phone in fastboot mode, or don't have the phone connected via USB. Probably the first one.
Easiest way to get the fastboot drivers is to simply install PDA Net on your computer and follow the on screen prompts. It will automatically install the appropriate drivers for your device.
Sent from my Nexus S using XDA App
thanks, i will try when i am at home again
Sent from my Nexus S using XDA App
Check in device manager that the ADB Bootloader driver is installed.
zero383 said:
Check in device manager that the ADB Bootloader driver is installed.
Click to expand...
Click to collapse
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
eiabea said:
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
Click to expand...
Click to collapse
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
matt2053 said:
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did it very carefully, but no success
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
ericshmerick said:
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
Click to expand...
Click to collapse
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
zero383 said:
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
Click to expand...
Click to collapse
Yes and yes.
May want to continue here:
http://forum.xda-developers.com/showthread.php?t=1303522
Had the same issues, although drivers were installed. After including "C:\android-sdk-windows\tools"
and "C:\android-sdk-windows\platform-tools"
in the path of win7 (systemvariables)
and a restart adb and fastboot worked.
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
spooky71 said:
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
Click to expand...
Click to collapse
What happened?
This is a common result if you flash a non-4.2 twrp on a 4.2 bootloader, which will cause a fastboot flash brick.
You will need adb drivers installed on pc, then while in recovery connect your tab to pc, open a command prompt and cd to you android-sdk/platform-tools folder and type
Code:
adb devices
if adb is setup correctly you will get a response with your devices s/n. If this is ok then type
Code:
adb reboot-bootloader
which will reboot your tab to the bootloader screen.
The problem is that whenever I boot up, all i get is the TWRP menu, not letting the pc see the pad. On device manager I get Transformer under other devices. Ive downloaded the drivers, but its not installing them. When I run adb reboot-bootloader, I get device not found.
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
pjc21 said:
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
Click to expand...
Click to collapse
Still nothing. Whats killing me is that it cant detect different sd cards.
My Nexus 5 (bone stock) shows up properly as a device in ADB when in regular ON mode. As soon as I reboot in recovery mode (abd reboot recovery) it shows "error device not found" even after I choose the option to update via sideload in recovery mode.
ADB can see it when ON, but can't see it in recovery.
I'm obviously trying to sideload 4.4.1
Thanks!
When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
Then you can sideload your zip file.
Or
Reinstall naked USB adb driver...
Sent from my Nexus 5 using Tapatalk
Bombn said:
My Nexus 5 (bone stock) shows up properly as a device in ADB when in regular ON mode. As soon as I reboot in recovery mode (abd reboot recovery) it shows "error device not found" even after I choose the option to update via sideload in recovery mode.
ADB can see it when ON, but can't see it in recovery.
I'm obviously trying to sideload 4.4.1
Thanks!
Click to expand...
Click to collapse
I had this issue. Resolution was to manually install the ADB driver.
lpganesh said:
When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
Then you can sideload your zip file.
Or
Reinstall naked USB adb driver...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The menu will appear. Select “apply update from adb”
Click to expand...
Click to collapse
That's exactly when ADB no longer see my Nexus.
Resolved.
Reinstalled the Google USB Driver via Device Manager and all everything works.
Thanks for the help!
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.
Hi guys,
I have a rooted Device with CM and TWRP installed, but someting happenend using the device and my Moto G got stuck on startup logo and Recovery TWRP logo, with adb I have acess to adb shell but everything else like adb reboot bootloader etc doesn't seems to work, with adb shell I have realized that the TWRP wasn't running 'cause when I use the interface on shell I get this message
$twrp wipe cache
"TWRP does not appear to be running. Waiting for TWRP to start"
Is there any way to install a new recovery via adb shell or reinstall a new rom, factory reset or something like that to make my cellphone work again?
Thanks,
If you are okay to wipe internal storage, the following fastboot command will probably make TWRP load again:
fastboot erase userdata
fastboot flash recovery newrecovery.img - is a way to reflash recovery, however the above command may still be required.
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
gconsentini said:
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
Click to expand...
Click to collapse
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
lost101 said:
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
Click to expand...
Click to collapse
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
gconsentini said:
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
Click to expand...
Click to collapse
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
lost101 said:
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
Click to expand...
Click to collapse
Sorry, I'm using Windows 10, if I use only wipe data, the command wipe is not reconigzed.
Can you enter fastboot mode by holding vol down and powering phone on?
lost101 said:
Can you enter fastboot mode by holding vol down and powering phone on?
Click to expand...
Click to collapse
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
gconsentini said:
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
Click to expand...
Click to collapse
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
lost101 said:
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
Click to expand...
Click to collapse
Yes, I thought about that too =x
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
gconsentini said:
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
Click to expand...
Click to collapse
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
thomasswan5547 said:
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
Click to expand...
Click to collapse
Install the Minimal Fastboot & ADB package and the Motorola USB drivers, use the mfastboot package and install the stock ROM as per the instructions provided, but ignore the disassembly part, unless you have your phone does not respond to keypresses.
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915