Database Users

Stuck in CWM - device not recognised

Hi
I flashed CloudG3 rom under CWM, and after install it won't boot the system - it sends me to CWM recovery instead.
Figured I would install another ROM but my device is not recognised by windows (won't show up under my computer). Can you please guide me on what I could do to sort this?
Thanks

Install the lg g2 drivers to get recognised by the os, after you download driver for adb sideload and restart, run sideload in the recovery with the usb pulgged in ur pc.
Open Android folder, and then do to platform-tools, drag a ROM there to be installed. Open a command in this folder. Write what is in the cellphone, adb sideload romfilename.zip if i'm right, then it will start installing and then you get out of the recovery stuck.
Using TWRP.

Hi
I installed lg drivers but it didn't help - looked like it was CWM that was causing an issue to get the device detected by computer.
Before you posted, I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2739739 - this helped to get TWRP on top of CWM. Under TWRP, the device is detected by windows
Now should I install a rom using your guidance above or can I do it under TWRP? Or is it the same?

New ROM

Hello there
I had a custom rom on my op2 then i deletet everything over the recorvery. Now i have no OS installed so it only shows the boot screen. I can get into the twrp recorvery and fastboot mode but if i try to fastboot or adb sideload a new rom im unable to connect my op2 to my PC. I doesnt show up.
I tried this guide : https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
I cant make my device show up in my device manager. (I did the windows driver thing).

Can you connect through fastboot? In fastboot mode type in: fastboot devices
If so: flash this https://www.androidfilehost.com/?fid=529152257862717275

Working ADB Driver?

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?

Oneplus 2 drivers issue in adb - fastboot mode

hello, i have problem fastboot mode, it detect my phone but in device manager not Identify the device. only show (!Android)
but in adb it detect when turn on devices. i want unlockbootloader to install custom rom

MOD can close this thread. done by install driver Android device to Android bootloader interface (windows 10 pro)

ADB Doesn't Recognize Fire in Recovery Mode

I boot looped my 2017 Fire 8 trying to install the Xposed framework. I have booted to recovery in an attempt to flash the Stock Firmware to my device, and selected the "apply update from ADB" option. When I attempt to do so, ADB does not recognize the device as connected.
I assume I have the correct ADB drivers installed, as I am capable of opening up a root shell on my 2017 Fire 10 when it is connected with the same USB cable and port. Maybe there is something wrong with the Fire 8 drivers?
Is there anything additional that must be done to enable ADB in recovery mode?
Edit: fixed it by manually updating the fire drivers through the device manager. This could only be done when in ADB sideload from recovery boot.