Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
ssj3hulk said:
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
Click to expand...
Click to collapse
same problem.
fix for it -> use linux
setup vmware, install ubuntu
when everything is set up connect device in fastboot mode
open command line:
sudo apt-get update
sudo apt-get install adb
sudo apt-get install fastboot
now you can make adb and fastboot commands, don't forget the sudo before the command e.g.: sudo fastboot reboot
I made the mistake of wiping my entire device when going to do a clean flash so the only thing I could access was recovery. I had no issues with using adb to sort out my mess in Win 10. The last phone I had was an old HTC that I was using between getting my OP3 stolen and the OP5 release and for that I had HTC drivers installed.
Not sure if that is a solution that will help you, but just putting it out there.
ssj3hulk said:
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
Click to expand...
Click to collapse
Did you enable usb debugging in developer options?
Related
So, after flashing CM10.2's latest nightly, I can't boot, and the only ROM .zip I have currently on my phone is the one that isn't booting.. I have TWRP installed as my recovery. When I plug my phone into my computer (running Ubuntu Linux), my computer doesn't recognise my phone as a device at all, so I can't push a different nightly to it.. Any ideas?
If you haven't installed adb and fastboot already, follow the instruction #1 and #2 from here: http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Then download a working 4.3 rom, SlimRoms4.3beta5 works for me.
Connect the phone to the computer while in TWRP, go to Advance and enable ADB Sideload, then type: abd sideload '/path/to/rom.zip'
You can also use "adb push" anytime while in the recovery: adb push '/path/to/rom.zip' /sdcard
Thank you so much eksasol, figured I would need to install adb.
Dear people of xda,
Recenlty ive receive a FOTA update to my device which runs 4.2.2. Being stupid, i did the update although i had cwm recovery installed on my devices. Now my device keeps bootlooping into cwm without being able to do anything.
Ive read tons of threads talking about this issue but i still cant get my to boot normally.
Yingy in this thread http://forum.xda-developers.com/showthread.php?t=2563527 had the same problem but the only diffrence is my pc cant recognize my device in order to do the adb fix by thecubed.
Im plugging my G2 for the first time in this computer and that is why i think my pc is failing to install drivers. I downloaded and instellad latest driver although windows device manger shows error devices not detected and the end of the process.
In order to fix my phone i just need to make me pc recognize my phone in adb although phone was never plugged before to this pc so i think my G2 wont let it access. I tried installing universal driver such as Pdanet as offered in threat but still when i write adb devices in cmd i get device offline!
Download latest adb drviers, lates lg g2 driver, lg user support tool does not recognize plugged device as well. All me sdk manger tools are patched to latest version.
PLEASE ive tried anything possible. spend like 9 hours and still nothing. i would really appriciate your help.
Thanks.
Edit: here my problem with pdanet drivers, it asks me to allow pc usb debbuging as shown in screenshot below but icant do it since im stuck at cwm recovery!
Solved!
BOOM!! after 12 hours i FINALLY manged to solved this problem. Really simple actually lol.
If anyone come across the issue please do the following:
1. Go to clockwork recovery as always, go to install zip from sdcard, choose install zip from sideload.
2. Plug your phone to pc.
3. Run adb with lastest drivers and sdk tools.
4. At the adb folder press shift+right click and start cmd.
5. write adb devices it should show your device id like this (xxxxxxxxx sideload).
6.Download latest twrp recovery from here http://teamw.in/project/twrp2/197 and if you have open europe version G2 like me download latest version from here: http://techerrata.com/browse/twrp2/g2d802
7.put the zip file in the adb folder, do not unzip it.
8. write in cmd console adb sideload xxxx.zip (xxxx is the name of twrp file).
9. cwm will flash twrp recovery over cwm.
10. reboot in recovery in advanced options.
11. now you have twrp recovery.
12. follow this guide : http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
13. THATS IT!!!
finally after going through this mess, im never using cwm recovery again. twrp is the best
good luck everyone!
Hi everybody, 2 months ago I tried to encrypt my nexus using the security settings. When my n4 rebooted the touch stopped working. I couldn't use the recovery becouse the data partition was encrypted, so I used this tutorial (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060) to reset my phone. Now windows (neither ubuntu) do not recognize the n4. I tried to follow any kind of guide or tutorial i found but uselessly. I'm desperate, the recovery doesn't work, if i try ,it stop on android logo saying "no command". Entering in windows device manager (after i formatted my pc) the nexus is seen as "full jellybean on mako", i tested this driver (http://forum.xda-developers.com/nexus-4/help/phone-detected-jellybean-mako-install-t2411201) but the situation has not changed. I hope someone can help me.
Does your phone boot?
BTW, if you need only driver download from this thread: http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
PsyGik said:
Does your phone boot?
BTW, if you need only driver download from this thread: http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
Click to expand...
Click to collapse
It works perfectly, but I can't copy files on or change rom (now is running stock android 4.2)
werba59 said:
It works perfectly, but I can't copy files on or change rom (now is running stock android 4.2)
Click to expand...
Click to collapse
Boot into bootloader and flash stock rom from here :https://developers.google.com/android/nexus/images
BTW, did you enable developer options?
Sorry, I misread your answer. "It works perfectly" means that i can use it to call or whatever. Using the key combo (vol up+vol dw+power) it doesn't boot in download mode. I think it isn't a driver problem, something in my n4 went wrong. It boot only in fastboot mode and the recovery doesn't work.
werba59 said:
Sorry, I misread your answer. "It works perfectly" means that i can use it to call or whatever. Using the key combo (vol up+vol dw+power) it doesn't boot in download mode. I think it isn't a driver problem, something in my n4 went wrong. It boot only in fastboot mode and the recovery doesn't work.
Click to expand...
Click to collapse
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
Then open the downloaded image from here https://developers.google.com/android/nexus/images and Execute the flash-all script. This script installs the necessary bootloader, firmware,and system. Wait for a couple of minutes and then phone will reboot itself. After phone boots enable developer options in the phone and enable USB debugging.
If you are still not able to mount the storage in Ubuntu, you can install the mtpfs tool for Ubuntu.
Code:
sudo apt-get install mtp-tools mtpfs
sudo gedit /etc/udev/rules.d/51-android.rules
and in the 51-android.rules write the following:
Code:
#LG – Nexus 4
SUBSYSTEM==”usb”, ATTR{idVendor}==”1004?, MODE=”0666?
Then do:
Code:
sudo chmod +x /etc/udev/rules.d/51-android.rules
sudo service udev restart
sudo mkdir /media/nexus4
chmod 755 /media/nexus4
sudo mtpfs -o allow_other /media/nexus4
This should get it working. This thread tells everything in much more detail if you still didn't get it to work.
http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
PsyGik said:
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
My PC do not recognise my phone when it boots into fastboot mode, that's the problem, any pc and any kind of so i tested do not recognise my n4.
Click to expand...
Click to collapse
werba59 said:
PsyGik said:
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
My PC do not recognise my phone when it boots into fastboot mode, that's the problem, any pc and any kind of so i tested do not recognise my n4.
Click to expand...
Click to collapse
If no pc will recognize it it's probably your pc port on the device. Have you tried different cables too? It's pretty easy to replace or have replaced.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Seems like something going wrong with drivers, open the device manager on windows, plug in your phone (in fastboot) and uninstall the driver. Then use this http://www.koushikdutta.com/post/universal-adb-driver
Dunno what that full JB driver is about but it doesn't seem right.
You might have to repeat this process when phone is booted normally too if it won't connect via MTP
Hi, just get here after look in several forums.
my laptop can't recognize my n4, also tried in other two computers. i already updated the drivers, used a toolkit. what should i do next? the phone works good, just can't connect it to any pc. "USB device is not recognized"
as i said, already updated the drivers.
Anything else i can do?
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
You try install mi pc suite
cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
had experienced this before. Do you use Windows 10 ?
Install MiPc suit
N u r done!
kpratama24 said:
had experienced this before. Do you use Windows 10 ?
Click to expand...
Click to collapse
Yes..i do use windows 10....the solution that worked for me this time is to delete every driver of my phone present in my pc and connecting it....by every driver i mean each and every one(inclusive of adb and fastboot and also usb drivers)...so pc installs a driver by itself and surprisingly it works
cypherx1998 said:
Yes..i do use windows 10....the solution that worked for me this time is to delete every driver of my phone present in my pc and connecting it....by every driver i mean each and every one(inclusive of adb and fastboot and also usb drivers)...so pc installs a driver by itself and surprisingly it works
Click to expand...
Click to collapse
Good to hear that.
cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
Download Adb and fastboot.rar from google.
Extract it to desktop.
Then install Miflash , downloaded from google.
And for fastboot watch video from youtube.
If you are again unable to found or for any type of help.
I'll provide you the files with the video.
cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
download MI Pc suit http://pcsuite.mi.com/
and you won't be needing drivers. and your device would be listed.
Hello everyone,
I recently decided too install the LineageOS.
Everything went fine, but I forgot Gapps and didnt want too use my phone without them so I decided too install the ROM again but this time with the apps.
I followed the linageos guide but accidently wiped everything before I could
Code:
adb push filename.zip /sdcard/
(dunno if thats the problem)
Im using TWRP 3.1.1-1. I can get into Recovery Mode. While in fastboot modus my pc detects my phone as an OnePlus, in Recovery modus its just android.
Code:
fastboot devices
shows my serial number. OEM is unlocked.
while in recovery mode
Code:
adb push filename.zip /sdcard/
gets me
Code:
No such file or directory
Code:
adb push C:\User\...filename.zip /sdcard/
gets me
Code:
failed to copy.. remote couldnt create file
while in fastboot mode I get
Code:
no devices/emulator found
Copying by dragging the file into internal storage doesnt work neighter.
I dont know what I did different besides the wipe before the copying. Maybe the wipe deactivates USB Debugging?
Maybe someone sees where my problem is.
Thanks
r717
I guess you don't have an OTG Drive.
you could always go 100% stock again and then flash LineageOS
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.13/
well first thanks for your reply. I flashed the original recovery and tried 2 sideload now. Seems to be driver problems. So I have to try every solution with Win10 and OP5 drivers I guess?
Make sure the Android drivers on your computer are up to date and also that you don't have any old drivers from a previous phone. I accidentally wiped everything on my OP5 once but when I connected it to my Windows 10 computer the OP5 was still recognized as a storage device--but I used TWRP not the stock recovery and also used the file explorer in TWRP. With the stock recovery you should still be able to side load flash the stock ROM from your computer. If you can't it's likely a driver issue.
I had once a similar issue, although not exactly this, just something with drivers.
A long process to fix was to install Linux as a virtual machine in Windows and that worked well. I could do all I needed, the phone was quickly recognized.
Virtualbox or VMware both are free/have a free version and I used Ubuntu.
Give it a try if all else fails.