Hi,
after receiving the OPX, adb and fastboot where working as normal.
Then I installed TWRP and rooted the phone, after that adb is not working as before:
adb is only working when booted into recovery mode,
fastboot only when booted into fastboot mode.
Because of not working OTA updates and the problem with adb/fastboot installed the stock recovery,
OnePlusOxygen_14_OTA_003_all_201510241934.zip and OnePlusOxygen_14_OTA_003-004_patch_201511031712.zip
then booted TWRP with
fastboot boot twrp.img and installed SuperSU.
The behaviour now is the same as before.
USB debugging is enabled.
One thing I noticed when connecting to the phone, there is no request to "allow USB debugging".
Anybody with the same problem?
Any advice?
Related
Hello,
Recently I flashed a CWM file on my android 'Lava Iris X1 Grand'. Now my phone is stuck in a bootloop. For some reason i cant enter recovery mode even before my phone was stuck in a bootloop. I am not sure whether my phone has USB debugging enabled or not. I have even rooted my android with KingRoot. I have downloaded your Minimal Adb and Fastboot but it cant find my device.
Overall problem:
1) Phone Stuck in Bootloop
2)USB debugging enabled ? Not sure
3) Can't enter recovery mode
4) ADB wont find my device
Note : When I used Minimal Adb and Fastboot, when i type Fastboot devices some numbers appear but when I used the command 'adb devices' my device is not shown. I have a backup at my phone through the Flashify app but since recovery mode cant show I cant recover it.
Please help me out here. I don't know what else to do.
Thank You in advance
Fixed
Sorry posted in wrong section
My phone is fixed now using SP Flash Tool
Hi all, trying to install CM on Nextbit Robin and I'm having trouble getting the TWRP recovery img flashed. I have working Fastboot & ADB tools installed. Robin driver is installed on PC. Device IS responding to Fastboot and ADB commands. Have unlocked Bootloader and in Fastboot mode now trying to flash recovery (TWRP) img. Have latest TWRP file etc but CMD screen on PC returns a "cannot load file" message. TWRP file located in same directory as Fastboot etc. (I'm working from Windows 10 environment.) Debugging enabled etc. on device. I've flashed CM many times on other Android devices - haven't encountered this issue before. Only issue I've noticed is that the command ADB Devices returns "List of devices" but nothing is listed - HOWEVER device IS responding to ADB commands and Fastboot commands. Thanks in advance for any help you can provide!
I have the exact same problem,
Hello,
Since a few years, I have root, TWRP recovery and XPOSED framework on my device.
I thought It's time to go further and try out new ROM, but to do it I need to unlock a bootloader.
Unfortunately, when I'm entering a fastboot mode (notification LED is blue) the adb "fastboot devices" command does not show anything.
I'm working on Windows 10.
What am I doing wrong?
Is a twrp somehow blocking the access? Or maybe I can do it directly from TWRP recovery.
PS. Drivers are OK, because I'm entering the fast boot mode by "adb reboot bootloader" command.
Im fairly certain its driver on the pc side.
Try it on a different pc.
Adb needs different drivers from fastboot. You havent installes fastboot drivers from the driver package.
I'm running into issues with my Compact X. Current situation:
- Omni 8.1 rom installed, but doesn't boot. Stuck on Sony logo.
- TRWP 3.3
- Rooted
- When in fastboot mode (vol up + connect usb cable) the device manager shows: Android Device > Sony Fastboot Interface.
- Windows 10 running in "Test mode"
- adb & fastboot v1.4.3
ADB does not recognize my device when the device is in fastboot mode. When it's in recovery mode the command 'adb devices' shows me the device listed. I can then reboot in fastboot mode, but then the device isn't listed anymore. I'm not sure what happened because a couple of hours ago I installed TWRP using fastboot.
I'm trying to get this thing up and running again, but not being able to flash anything via fastboot complicates things. Any idea's what could be the culprit?
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Some random said:
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Click to expand...
Click to collapse
Thank you for your reply. As far as I know the official drivers were already installed. Because at first my device did show up listed when using the command 'adb devices' and I successfully flashed TWRP recovery. But to be sure I repeated the process:
- Connected my phone in fastboot mode (vol up + connect usb cable). The blue led lights up.
- Go to the device manager, right click on 'Android ADB interface' device and manually install the driver via 'Have disk'.
- The driver installs with no errors.
But still my phone is not listed and I cannot flash anything.
When the phone is in recovery mode it is listed using the 'adb devices' command. But when I'm trying to flash something I get the message <waiting for device> .
Ok, I restored my computer to a point before I started messing with my phone. After installing the official drivers my phone is still not listed (adb devices), but this time flashing did work. I managed to flash the AOSP 8.1 image. My phone is up and running again!
Hello all,
I am stuck in this problem. Would appreciate any help.
Working in LINUX ubuntu 18.
Got a MI pad 1 with locked bootloader.
flashed TWRP recovery using fastboot. Booted into TWRP successfully.
Flashed the files from this
https://www.techeia.com/2018/10/best-custom-rom-for-mi-pad-1-2018.html
Everything flashed successfully.
Rebooted only to be stuck into MI logo screen. Bootloop probably because of locked bootloader.
Hence, I decided to wipe the bootloader itself
got the hint from here https://forum.xda-developers.com/mi-pad/how-to/fix-fastboot-bootloop-fix-xiaomi-mi-pad-t4008653
but I didn,t wiped recovery. but erased everything else. Then powered off to boot into previously installed TWRP recovery.
From there, I am trying to boot into fastboot or TWRP but the screen is showing blank. I am using the key pattern for fastboot or recovery and trying to detect the device into any mode through ubuntu terminal using
sudo fastboot devices and
adb devices
but its not detecting the device there also. USB debugging was enabled already.
Any clues for how can I boot into fastboot or TWRP from this.
Regards
Hiteshkartik
@hiteshkartik
A device with erased boot-loader never can work: you simly get a black screen. You no longer can communicate with it - neither via ADB nor via Fastboot.
Can I have a way around ?? I mean installing bootloader or somehow booting into fastboot or TWRP directly with any toolkit or terminal.