I recently received an OTA for my Ticwatch E which fails every time it tries to install. So, I captured the OTA url from logcat and downloaded the file to my PC so I could sideload it. However, I quickly discovered that my PC doesn't recognize the device when it's in recovery mode. ADB works fine when the device is on, and will reboot it to recovery, and it recognizes it in fastboot mode as well. Usually, I would find the unrecognized device in Device Manager and configure it to use the Android ADB drivers, however the watch is not found in device manager AT ALL when it's in recovery mode. I've tried the usual steps of switching USB ports and unplugging the watch until it's booted into recovery, those don't work. Furthermore, the watch doesn't have an SD card, so sideloading from the device is not possible. Any suggestions to get the device to be recognized by Windows in recovery mode?
Did you ever find a fix?, I'm in the exact same boat right now.
ClemmerC said:
Did you ever find a fix?, I'm in the exact same boat right now.
Click to expand...
Click to collapse
Yes, it was defective and I RMA'd it. The new one was good to go.
Related
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
brandonyoung said:
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
Click to expand...
Click to collapse
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
sparkplugDev said:
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
Click to expand...
Click to collapse
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
brandonyoung said:
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
Click to expand...
Click to collapse
I've heard that unplugging the device from the PC until you're in recovery mode might help. I would also suggest, if that doesn't work, to install the ADB drivers again once you're in recovery mode.
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
When it is running, and usb debugging is enabled, it shows up under Android Phone as Android Composite ADB Interface.
I turn USB debugging off, and it shows up under Portable Devices as Nexus 10
I boot into the bootloader and it shows under Android Phone as Android Bootloader Interface.
but It doesn't show at all when I am in recovery
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
mevensen said:
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
Click to expand...
Click to collapse
I am connecting with a USB cable. I don't know if it is "good' or not, but it works with the tablet in all other modes. I was able to use adb to transfer files, reboot, etc. I was able to use fastboot to flash Chainfire's autoroot, and to flash the factory images.
I was using a USB2 port directly on my laptop, but I just tried the USB3 port and it didn't change anything.
Plugging it into my USB hub, and my hub did not detect that it was plugged in either while it was in recovery mode. It was detected when I rebooted back into the system.
USB debugging is on when I enter recovery. I used "adb reboot recovery" to reboot my tablet into the recovery mode
garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
Thank you !!!!!!!!!
my lenovo a6000 shot no display but detecting n device manager.
it occured due to flash flash.rec.
please help me.
Hi
As many people here i've encountred a problem with fota while being using a rooted ROM (g.lewarne ROM)
Now my phone is bricked. I can't go into recovery nor Download mode. I only have the LG logo for moments with error: secure booting error!
cause: boot certification verify
When i plug my phone it is not recognized in the hardware manager. I've already installed Drivers.
All i have in the hardware manager is a new hard under name QHSUSB_BULK that needs driver.
I have just one hope to get my phone alive, by reconizing it again by my computer, then maybe i can go under download mode.
I've tried everything but nothing could work without download mode.
PS: I've made a hard reset, which was maybe a silly decision.
By the way, after installing the OTA my phone went into CWM Recovery, it was detectable by adb, i used adb to reinstall TWRP, then i used command
"adb reboot download" instead of "adb reboot recovery", then i had never seen the CWM recovery again, only the mentioned above error.
After few seconds my phone screen goes black but the phone is still on since i can see light at the corners of the phone.
and it is not reachable by adb.
It makes me crazy now.
once i plug it to the computer it gives me plenty drives to format and one drive with only one folder inside called image, only readable, with many files inside.
Could you please help me to get my phone alive?:crying:
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand
Hello there!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
Code:
fastboot devices
in both Windows and Linux, I get the response as
Code:
???????? devices
.
When I try with
Code:
adb devices
I get back nothing.
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
Code:
lsusb
I get back that it is being recognized as
Code:
Google Inc. 18d1 d00d
, which I believe is the phone.
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
Code:
Error too many links
.
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated!
PS. Forgot to mention that I have tried with other computers and have the same result and the model of my phone is the D800.
Just to add a bit more into the case.
I had installed prior to all this mess, TWRP which had a Nandroid backup in the internal storage and file backup.
When using the LG Flash tool (KDZ one) I am able to see the available storage, which is about 2.5gb. This leads me to believe that both the Nandroid backup and Backup files are still in the internal storage.
Also, I did some more digging and got information that it might be the USB cable, however, this cable worked fine the first time and with other devices. and while connecting the phone with it to the PC it will still register the device as connected, but apparently no USB port is assigned or fastboot flash tool does not find the phone.
I tried rooting my G2 using this guide, and seem to have f'ed up somehow.
The phone now won't boot (stuck at the "LG" screen, with rainbow LED), and I can't get into download mode.
The strange thing is that I do get into recovery mode, but it seems to exit abruptly. When I try to recover (by selecting yes twice), the Android recovery icon shows up for a couple of seconds, but then it goes back to the "LG" boot screen again.
I would be grateful for any help.
I've tried connecting to a computer with Ubuntu, as per this guide: http://forum.xda-developers.com/showthread.php?t=2582142, but I was unable to mount the phone.
It does show up in the device manager in Windows, under "Portable Devices".
I've disovered that the guide I followed for rooting was for G3 phones (and the G2 D805). I'm guessing this could be part of my problem.
But the guide said that I should be safe, since I had Lollipop. The Download mode should be able to save me if anything went wrong. But alas.
Before starting the rooting process I had the latest Lollipop update from LG (it was performing poorly, that's why I wanted to install a custom ROM).
Is it possible to save this phone? I'll probably look for a good deal on the 5X at Black Friday if I can't fix the G2, but I'd rather keep this phone working for a while anyway.
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
no connecting to pc
FonderPrism said:
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
Click to expand...
Click to collapse
bro install adb driver or qualcomm driver.
link:https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0
kalpesh patil said:
bro install adb driver or qualcomm driver.
link:
Click to expand...
Click to collapse
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
FonderPrism said:
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
Click to expand...
Click to collapse
bro i think ur phone is hard bricked.