I can't update my OP3. The device is on Open beta 16. When updating through settings, the update downloads and then it shows a restarting dialog box that does nothing. The only way to get rid of it is to restart the phone(which leads to an update failed notification). I tried updating via adb sideload but it isn't detected on my PC even though I have the drivers(neither is fastboot detected). I also tried to update via adb with the file on the system but it just says update failed. The phone is completely functional in all other ways and I haven't faced the issue while updating previously.
TL;DR : OTA update gets stuck on restarting and can't detect the phone in ADB/Fastboot but rest of the phone is completely functional
Related
Hello there fellows,
I have an Oppo R1K R8001. It is a Qulacomm Device and does not have and SDCard. I have just updated the phone VIA OTA and the process was completed without any problem.
After my phone is turned one it keeps showing Force Close errors on everyting. com.somethign.phone [close].
I have downloaded the OTA update for this phone but it does not have a SDcard.
Can somebody please help me out on how I can flash this phone?
Thank you
-------------------------------------
I fixed it. Turned off phone. Then plug the USB Cable and phone appeared in ADB mode.
Then I used ADB push method to put the OTA file into the phone and it worked.
Flashed VIA Recovery and it worked.
bump
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
Is my watch bricked? PC & Device Manager not recognizing watch, drivers are installed
I was running on the latest (v2.7) Negalite Rom NX 1 when I got the notification to update the watch. Upon rebooting (and presumably installing), the watch got stuck in loading screen (4 dot animation) so I force rebooted the watch into recovery and wiped everything (Advanced Wipe, everything).
Upon connecting my watch to my computer (watch in recovery (TWRP)), I was not able to connect the watch to ADB nor Fastboot; adb/fastboot devices returns nothing.
I tried reinstalling, uninstalling, deleting and reinstalling the drivers but I haven't gotten any success
I've tried several ports (and another computer) without any success
The watch does not show up at all in Device Manager (definitely not in "Other Devices")
I'm unable to manually install the device drivers because the watch does not show up in Device Manager
The device is connected because it's charging, but there's no notification sound when plugging the watch/USB cable into the computer
I have previously been able to connect the watch through ADB, to be able to transfer Negalite rom, likely half a year ago
I've tried installing Pdanet ADB Drivers, but it requires the watch to be detected otherwise it closes the installer
I am using Windows 10
Has anyone else had this problem? Is there a way to check if the drivers are installed or not?
Every thread I've read instructs to install the drivers manually for the device, but I don't have the device in Device Manager.
I'd love to be able to use the watch again (currently sitting @ 100% battery, in TWRP).
Thank you
Edit: When I boot system from recovery (I know I don't have an OS installed), I get a message that I haven't seen before: "Device software can't be checked for corruption"
I read that it was caused by unlocked bootloader, but I've never encountered that before, if I had accidentally booted system without OS.
After rooting the device (n 5110) and installing a custom recovery I had to flash it back to stock (which I had to download because I somehow didn't have it backup from before) in order to get an OTA update. I used Odin to flash back to stock and AFAICT everything seems fine. After the update I don't see what was different, the android system was 4.4.2 before the update, but I was prompted to update so I did. Now am looking to reflash the custom recovery and install a custom rom. I didn't have a custom ROM on it before, just custom recovery and root.
So I'm trying to flash TWRP back on it so I can flash a custom ROM. I recall flashing TWRP and rooting was pretty problematic the first time and I don't recall what I did to get it to work.
This time I've tried following the instructions for flashing lineage os. Running a windows machine. If the tablet is hooked up booted into system windows sees it and I can transfer files to and from the tablet via explorer, both the internal memory and sdcard, if that matters, so I know the cable and usb port are functional. I just flashed stock yesterday, so I guess they would be.
I've enabled USB debugging and checked the box to remember the computer. When it's in system, if I type "adb devices" it reports a device, it did say "unauthorized" before I got the prompt and checked the box to remember my computer, after I got the prompt it just listed the device and it seemed fine. If I kill the adb server and disconnect the tablet and reboot tablet into system it's remembering my computer and granting access. Adb reports the device.
I've gone to the samsung site and downloaded the drivers for the tablet and installed them. I've tried updating them both through device manager and zadig that comes with heimdall.. I've tried all three usb ports and three different usb cables.
However whenever I boot into download mode, and type "adb devices" I get blank. I've tried leaving the device plugged in, unplugging and rebooting, then plugging in, I've tried disconnecting and connecting the device at various times, stopping and starting adb, waiting 30 seconds or so before hitting volume up to confirm going into download mode. Adb devices just pulls up blank.
Odin doesn't light up or say anything when I boot it up into download mode, heimdall throws errors when I try to do anything. I have odin 3.09 so I don't see this "AP" button people mention, I think tha'ts supposed to be "PDA" on my current version? I dunno, if I got it to work I'm not sure how I would flash TWRP with it.
If I type "heimdall print-pit", which is part of the instructions for lineage os, I get the following error.
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The parameter is incorrect.
ERROR: Failed to send data!Releasing device interface...
I dunno, I have to be missing something, but I don't know what.
My problem started when I attempted to bypass the FRP by flashing a custom TOT file. I neglected to notice the file was specified for a 32GB version. I flashed it on a 16GB version using LGUpgrade Tool. The phone then froze at the splash page that just says "Google" . I thought I was fortunate enough to be able boot to recovery mode and so I flashed the stock firmware through ADB - the same ROM version that was previously on my phone and from a copy which I had used in the past with no problems. Everything seemed to be working again except my PC doesn't detect the USB connection anymore. I've tried the same procedure but now the command 'adb devices' doesn't list the phone. However, there is a point when I boot to recovery mode the PC makes a sound as if it detects the phone but then moments later it makes the other sound as if it gets disconnected. As I stated earlier, my phone seems to be where I was stuck at FRP with Android version 7.1.2 but my problem now is I can't get the PC to detect the phone when it's plugged into its USB connection. Nothing shows in Windows Explorer as well as Device Manager? I tried re-installing the drivers. Stopping and restarting the ADB server... still no detection. Is there a way to set USB mode to MTC while in FRP mode? Should it matter in Recovery Mode?
I'm going to wait for a response before I attempt to flash again but this time through the SD card because this will be a first time for me using that method and I hope there's a less risky solution.