Hi, my device wasn't recognized by the computer so i tried to block abd sideload and after one hour it's still trying to cancel it. Is it normal?
Related
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?
So I have had my Droid DNA for a few months and I've been messing around with it and doing fine. Since I installed TWRP it allows me to delete internal storage...
Oops, there goes my ROM I had saved. Now I'm stuck in either bootloader or recovery. I can't get ADB to recognize my DNA to save my life. It's really really irritating.
I've tried flashing a zip with fastboot since fastboot can recognize my device but ADB can't and it didn't work.
I have Minimal ADB installed and HTC sync manager, but i installed sync after i messed it up so idk if it installed the drivers.
I need a step by step instruction guide to get this to work. I can't find it anywhere. I keep getting no ADB devices and it saying server out of date and what not. I've been searching for hours and hours.
I can't get this to work. I even bought a new phone in the meantime to get me by and that's not exactly what I wanted to do... Any help would be appreciated. Thank you very much!!
No one?
Pretty quite.. I recently had this happen as well.. No fear tho.. If you have twrp already installed your golden.. Download a rom 2 your computer and on twrp goto advanced and sideload.. Command prompt on your computer.. Easiest if found is running xp. Get to your folder of adb hit control and right click poem command prompt here.. adb devices, then adb sideload rom(name). zip.. Your computer will find your device then , and if it didn't send it will allow you to file Explorer.. Throw a rom on your internal reboot into twrp and flash
Æaa..\../
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
dyllysoilly said:
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
Click to expand...
Click to collapse
You can restrt the phone. Hold down power and volume down together. Then you can reaccess the bootloader from there. If you have twrp you can just go through the file manager instead of messing with sideload.
Hey guys, My brother gave me a tablet to use for my etextbooks at college and I haven't used the tablet too often tbh. I saw that there was an update and the entire tablet froze during the process and now is stuck in a bootloop. I'm completely new to abd and every time I run it, it doesn't recognize the commands. I tried side loading and got this error through adb "adb server version (31) doesn't match this client (39) killing."
This is the only way I can see it on my computer. I was able to get around the adb server error by using my new laptop but now I'm stuck because it's stock so the bootloader is locked.
https://imgur.com/JKZ79sy
Sideload an OTA image with stock recovery: -
https://developers.google.com/android/ota
You can't use ADB commands while in fastboot mode ("fastboot devices" is the correct command in that mode).
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 am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Have you tried with another cable or diffrent USB port?
I did but same result. Any other advice I can follow?
TSKXDA said:
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Click to expand...
Click to collapse
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
MobyDuhFreak said:
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
Click to expand...
Click to collapse
If I try to fastboot into recovery I still get the same error.
TSKXDA said:
If I try to fastboot into recovery I still get the same error.
Click to expand...
Click to collapse
Is your phone a redmi 5(codename Rosy) or a redmi 5 plus or a redmi note 5 in India (codename Vince)?