Hi everybody,
I was using the latest version of CWM (i think 6.0.4.7 Touch) and everything was OK. ADB in my PC recognized my Nexus and sideload worked too.
I've just tried the latest TWRP (2.8.4.0). Problem is, when I boot to recovery and connect phone with my PC, it won't recognize it.
A cannot see my phone in list of connected devices, when I type adb devices and adb sideload isn't working as well.
I upgraded to latest Samsung USB drivers (Android Composite ADB Interface version 11.0.0.0) and also the ADB in my PC (version 1.0.32).
Fastboot is working without any problems.
Does anybody know, how to make it work with TWRP?
Related
Hi! I want to update my girlfriend's GNex by pushing update via recovery. I have adb working and recognizing device when it's turned on (with debugging mode). But when I go to recovery (adb reboot recovery), I can't get my device recognized again - "adb devices" shows nothing. I figured it can't be problem with drivers (since the device is recognized when turned on?), I must be doing something else wrong? But I have no idea where to look.
Sorry for the (probably) common question, but all I've found (using search) is adb not recognizing devices at all. I've been only using "fastboot" commands so far, and I never had problems with recognizing.
Joplisan said:
Hi! I want to update my girlfriend's GNex by pushing update via recovery. I have adb working and recognizing device when it's turned on (with debugging mode). But when I go to recovery (adb reboot recovery), I can't get my device recognized again - "adb devices" shows nothing. I figured it can't be problem with drivers (since the device is recognized when turned on?), I must be doing something else wrong? But I have no idea where to look.
Sorry for the (probably) common question, but all I've found (using search) is adb not recognizing devices at all. I've been only using "fastboot" commands so far, and I never had problems with recognizing.
Click to expand...
Click to collapse
what recovery are you using? in twrp, in advanced menu, theres a adb sideload option.
The problem is that her phone is locked, everything is stock. The only option is adb sideload (as far as I know). Any suggestions? I really don't have a clue.
Sent from my Galaxy Nexus using my thumbs.
Stock recovery does not offer the ADB interface, so adb commands will not work. You need to flash a custom recovery such as CWM or TWRP.
Ahhh, I didn't know that. I guess I have to wait for the ota, then, since I can't flash or use custom recovery. Thank you for your help!
Sent from my Galaxy Nexus using my thumbs.
Actually you can use adb commands in stock recovery - this works on build number JRN84D and newer only (JRN84D corresponds to 4.1, the first Jelly Bean build).
1) Reboot your device into the stock recovery (i.e., the screen with the Android on its back with the "!");
2) Access the stock recovery menu by pressing power and volume up;
3) Select "Apply update from ADB";
4) Download the correct update for your build and place it in the same directory as your ADB binary;
5) Open a command prompt in the same directory as your ADB binary;
6) Type adb devices to make sure that your device is recognized;
7) Type adb sideload name-of-file.zip
8) Reboot. Done.
Click to expand...
Click to collapse
This is from Method 4 in http://forum.xda-developers.com/showthread.php?t=1419170
Hope this helped
It's been a while since I have updated my recovery and rom so I downloaded latest CWM and CM. I formatted all the options inlusing sdcard and system. That turned out to be a big mistake because now I can not push any files to the phone to flash a rom. I can get to CWM inlcuding the option to adb sideload but my computer does not have the fastboot or adb drivers installed. Is there a way for me to push a rom to the device to get back up and running? I have tried to install the fastboot drivers but the mahine is not recognizing the device.
***Update**
I ended up using the universal toolkit in linux so I wouldn;t have to set up the drivers and was able to get back to a stock image and work from there.
Guys, i have a bit of a problem, when trying to flash Omni ROM 4.4, i installed TWPR Recovery but wiped everything, included sdcard, mistake, now, i wanted to use KDZ to flash stock firmware or through CMD push ROM file to sdcard but can't get to connect the device, if i'm in download mode or recovery, adb is not working, in Devices it lists as "Android" but with trouble to obtain drivers, and if i boot normally, can't enter the OS because i wiped, i get MTP installation and another ones, but device in ADB (adb devices) is Offline.
What can i do?
Does download mode install drivers or find your phone?
Sent from my LG-E975 using Tapatalk
atifsh said:
Does download mode install drivers or find your phone?
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
The problem was about drivers, that i knew, so i found some universal adb drivers, and they got installed, device was recognized but not as online, just as host, so i couldn't use adb sideload or just use adb to push the file. Found out that adb was outdated so i downloaded another one and, everything working, sideloaded the files, and now everything is runinng up again.
hello, i have wiped everything in my phone except twrp. i want to go back to stock, but adb only finds my device when in twrp, but NOT in bootloader
rsd lite 2.6.4 does not find my device in either bootloader or twrp
Just install drivers for your phone to PC.
Here you can download windows drivers (for x64 and x86)
P.S. This drivers will help you to have MTP device in TWRP mode. But - if you have USB 3.0 and Win x64 - you`ll not aloowed to flash your phone with RSD.
Just use fastboot commands. You can find it on forum.
Hey,
I need some help.
I tried to install LineageOS 14.1 on my Oneplus 3 following this guide, but I think by wiping /data or /system the ROM, which I copied to the phone beforehand, got deleted. Now I don't have any ROM in the storage and also no system installed.
I think fastboot only works in the bootloader mode (I get my phone serial number if I enter the command fastboot devices), but it doesn't work in the recovery mode (because I don't get my serial number then).
If I use the command: C:\adb\SDK\platform-tools>adb push lineage-14.1-20180328-UNOFFICIAL-Sultan-oneplus3.zip /sdcard/ I get the error: adb: error: failed to get feature set: no devices/emulators found while in bootloader mode and also the same error if I am in recovery mode. And if I try ADB Sideload (without wiping Dalvik Cache or Cache) my phone just says Starting ADB sideload features but does nothing else.
Does anyone know what I can do to fix my phone? If it helps I backed up my phone beforehand, but the backup files also got deleted on the phone, but I still have them on my pc.
Not sure if it will help, but make sure you are using the latest ADB downloaded from:
https://developer.android.com/studio/releases/platform-tools
I have had some strange problems with old ADB versions in the past,
good luck hope it helps you.
jeffrey268 said:
Not sure if it will help, but make sure you are using the latest ADB downloaded from: ...
I have had some strange problems with old ADB versions in the past,
good luck hope it helps you.
Click to expand...
Click to collapse
Is this the most recent version?
Code:
C:\adb\SDK\platform-tools>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\SDK\platform-tools\adb.exe
C:\adb\SDK\platform-tools>adb devices
List of devices attached
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
C:\adb\SDK\platform-tools>adb devices
List of devices attached
C:\adb\SDK\platform-tools>fastboot devices
3d0553dc fastboot
It should be, because I installed the SDK Platform today.
Also most guides which help to get adb working say, that if the phone doesn't get recognized you should get the install the drivers via the device manager, but my phones doesn't show up there, probably because it is in bootloader/recorvery mode.
EDIT: I now discovered that my phone gets recognized as Marshall London Device in the windows device manager and if I click on it it says Google Nexus ADB Interface. Are there any Oneplus 3 drivers which I should install instead?
Flix117 said:
Is this the most recent version?
Code:
C:\adb\SDK\platform-tools>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\SDK\platform-tools\adb.exe
C:\adb\SDK\platform-tools>adb devices
List of devices attached
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
C:\adb\SDK\platform-tools>adb devices
List of devices attached
C:\adb\SDK\platform-tools>fastboot devices
3d0553dc fastboot
It should be, because I installed the SDK Platform today.
Also most guides which help to get adb working say, that if the phone doesn't get recognized you should get the install the drivers via the device manager, but my phones doesn't show up there, probably because it is in bootloader/recorvery mode.
EDIT: I now discovered that my phone gets recognized as Marshall London Device in the windows device manager and if I click on it it says Google Nexus ADB Interface. Are there any Oneplus 3 drivers which I should install instead?
Click to expand...
Click to collapse
I use this drivers https://androidfilehost.com/?fid=24591020540821930
xGOGI said:
I use this drivers https://androidfilehost.com/?fid=24591020540821930
Click to expand...
Click to collapse
Try this:
Download the stock recovery for your device:
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Place it in c:\OP3\
Go into cmd and go to c:\OP3\
then type: fastboot flash recovery recovery_op3.img
If you get reboots after this, do the following:
Boot back into fastboot and type:
fastboot format userdata
after that type:
fastboot flash recovery recovery_op3.img
Flix117 said:
Hey,
I need some help.
I tried to install LineageOS 14.1 on my Oneplus 3 following this guide, but I think by wiping /data or /system the ROM, which I copied to the phone beforehand, got deleted. Now I don't have any ROM in the storage and also no system installed.
I think fastboot only works in the bootloader mode (I get my phone serial number if I enter the command fastboot devices), but it doesn't work in the recovery mode (because I don't get my serial number then).
If I use the command: C:\adb\SDK\platform-tools>adb push lineage-14.1-20180328-UNOFFICIAL-Sultan-oneplus3.zip /sdcard/ I get the error: adb: error: failed to get feature set: no devices/emulators found while in bootloader mode and also the same error if I am in recovery mode. And if I try ADB Sideload (without wiping Dalvik Cache or Cache) my phone just says Starting ADB sideload features but does nothing else.
Does anyone know what I can do to fix my phone? If it helps I backed up my phone beforehand, but the backup files also got deleted on the phone, but I still have them on my pc.
Click to expand...
Click to collapse
To clear some things up for you. Fastboot is only used in bootloader mode since that is what it is.
And for the adb sideload, are you initializing the sideload on your phone as well? To use sideload the phone has to be ready on the receiving end, in recovery you have to start adb sideload then launch the process on pc for it to work properly. And if you dont want the whole android SDK to just use ADB and Fastboot i recommend you install the minimal tool https://forum.xda-developers.com/showthread.php?t=2588979 :good: