Related
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.
anyone?
i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.
TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???
Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.
ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.
HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible
blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
clsA said:
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
Click to expand...
Click to collapse
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
alray said:
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
Click to expand...
Click to collapse
Get no luck on that... The y510p cannot even boot from a USB /___\
But anyway, I have borrowed my fds computer with Win 7 installed. And all works fine now. Thank you very much~~
ac3kill said:
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
Click to expand...
Click to collapse
Your Phone is broken send it to HTC or take it to a repair shop
I’m a noob when it comes to android adb but I'm an IT guy so what the hell I want 5.1.
I am following some directions on line on how to side load the OTA update seems easy, just a few commands and it should work. Here is what I'm doing and where I'm getting stuck any help?
Loaded Android SDK
Enabled Dev options, USB Debugging and OEM Unlock.
adb Devices - shows my device
adb reboot bootloader – restarts into the bootloader.
Select Recover Mode
Hold Power button, then press once the Volume Up button. To get Recovery Mode
This is where I get stuck, I'm reading I need to send the command “adb sideload <filename of update.zip>” but at this point ADB no longer sees my nexus 6? Nothing happens when I run this command and nothing is reported when I run ADB Devices?
Now I'm thinking drivers but I loaded the drivers? Can someone point me in the right direction?
I'm trying on a Windows 8 PC
Also when I'm looking at the device manager everything shows up fine until i enter the recover. At this point nothing shows up in device manager and when i resead the USB cable nothing happens no sound like im disconnecting something and reconnecting it, not device manager refresh, weird.
update! got it working.
So it turns out the device manager dose not show anything until you get into adb sideload options then the wrong driver is loaded and i had to manual pick Android adb driver. once i did this i was able to side load the ota update and now on 5.1.
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
tom1226 said:
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
Click to expand...
Click to collapse
Thanks you are right you have to be in the adb sideload options for the phone to show up in device manager and at this point it was not seeing the right driver, once i picked android adb driver i was able to update Thanks!
Awesome, glad it worked out for you!
Hi,
Am a novice when it comes to rooting, unlocking android devices. So please excuse my ignorance and my long-winded style of writing. I want the expert users to educate me on this issue and so I don't want to miss any trivial (or not so trivial) information.
1) So, I got Samsung gear live from ebay. It came with a sprat-userdebug 5.0.1. After googling I found out that it's a user/refurb build and can't be updated to 5.1.1
2) Thanks to rootjunky! I used Gear live restore tool V3 and unlocked the bootloader (option 2). Faced few issues in getting the driver. However, fixed everything and unlocked it. Flast TWRPd it (option 8). Flashed recovery (option 4) and bootimage (option 5). Then I sideloaded stock image from 4.4W.2 (using boot.img and system.img). That was the version I found after googling.
3) Then I tried to update it via OTA download. Download completed and it went back to recovery mode and did't apply the download. There was an error message that said something like "Unable to verify the download"
4) Tried multiple times and no luck with that
5) Then tried to sideload new version 5.1.1 LCA43 from xda wiki page. However, when my device went to recovery mode, my pc lost the connection and i wasn't able to sideload (received - device "null" not found" - error from adb command)
6) Until this point I was able to pair my device with my samsung S5 phone and only problem was not able to install the update
7) Then I reset my watch to factory setting, restarted multiple times, went to recovery mode to boot as a new device etc. No luck
8) Then I did something I shouldn't have done (or I think I shouldn't have done). Used option 7 root gear live. When the system went to SH mode, I panicked and closed the cmd prompt and hard reset the device by holding power button
9) After this step, I was not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N
10) Tried resetting my device, restarted it, used recovery mode to restart it, revoked all debug access, deleted adbkey from my PC, uninstalled android SDK, all drivers, etc. Reinstalled it again with no help.
11)Suddenly android wear in my phone sees my wifirouter as a device (strange)
11) When I plug in the device to my Pc, I could see it in my device manager. When I use recovery tool it says unregistered device and asking me to register it via my phone. Where as am not able to pair it with my phone. Tried to pair it with a new phone (moto e) and no help either
12)Somewhere read that disabling wifi in the phone before pairing works. Tried that and no luck
So here am with a bricked device that stays in the screen where it says "install android wear in your phone" and detects nothing else. Am able to go to bootloader mode, recovery mode from the device. However when it's in recovery mode, my PC doesn't detect it. Even the recovery tool says unregistered device.
Please help in unbricking this device and thank you for reading thru the whole problem. Any help would be much appreciated!
Use Gear live restore tool v2. Lots of known issues with v3
Thanks for the reply. I will try this. However, how will I make my device discoverable? Now, none of my phones detect my device.
So I guess I will get "Unauthorized Device" error when I use recovery tool. Could you please let me know if there's other way around? Or am i missing something?
I've never used it
Pretty sure all the info you need is in the thread
http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
unbricked using v2 of the tool. Now trying to update the os version. Will see if I can get lucky this time. Thanks for the help!
All is good now. Now my gear live is running on 5.1.1 with latest updates.
Good work
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
darwchprish said:
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
Click to expand...
Click to collapse
Simple procedure.
Just download v2 of this tool
Make sure to install USB drivers
Unlock bootloader - option 2
Then use option 6 to flash it. Then you'll get new OTA updates.
Refer rootjunky video - https://www.youtube.com/watch?v=x7oRjESQh_o
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
darwchprish said:
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
Follow this procedure.
1)Make sure all drivers are installed properly in your PC
2) Make sure when you connect your device to your PC, it's discovered as unauthorized device. It's ok
3) Long press power button in the device and swipe from top left to botom right corner when you see samsung gear live logo
4)This will get the device to bootloader mode
5)Now connect the device to your PC and run V2 of the tool. Your device will be discovered in fastboot mode
6)Now select option 6 to flash the device to stock. It'll flash it
7) Now swipe down to highlight start and swipe from right to left to start. If it goes to Raw dump code = 6. do a hard restart by long pressing power button. You'll get back your device in original setting.
Check rootjunky youtube video to get the live demo of this procedure.
noviceinandroid said:
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
mike061215 said:
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
Click to expand...
Click to collapse
Good luck.
It worked -- and I finally got the OS to update an all that and now I finally have a functional Gear Live. Phew!
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
lamik91 said:
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
Click to expand...
Click to collapse
sounds like USB driver issue. Please install correct drivers and follow the steps mentioned above. It should be unbricked.
Where can i find correct drivers? Additionally my Gear Live doesn't turn on and has only black screen.
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
pedalquickly said:
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
Click to expand...
Click to collapse
You need to factory reset first of all. After that let connect to your wifi, the updates will download on their own. They put a new one out today. I can't go into how but if you look at the forum and search the answers are there. There's even a tool to use.
Sent from my SM-N910T3 using XDA-Developers mobile app
So I am currently rooted on a Motorla Nexus 6 in Android 5.1.1, I started up the Nexus Root Toolkit and when it finishes downloading stock Android 60.1 to restore my device ready for Android N it sends the adb reboot bootloader command but my device then says in the bootloader menu "Connect USB Data Cable"
Since I cannot post the image link of what the toolkit says then I will just write it below...
"FASTBOOT device was not found
STEP #1: Connect your device via USB:
- Utilize the OEM USB cable if available
- Try an alternative USB port.
STEP #2: Manually Boot your device into bootloader mode:
- Power your device down completely:
- Press and hold the volume down button, them press and hold the power button t the same time until the phone turns on. You'll see the word 'start' with an arrow around it/
STEP #3: Install drivers:
- Utilize the 'initial setup' if you not done so already.
- USB debugging is NOT required for connectivity in bootloader mode.
- Just follow the the instructions in the guide for configuring your device in bootloader mode.
- For example: if you are using driver solution #3, start on step 7.
Alternatively you may just need to recheck connection.
Press 'OK' to recheck device connectivity.
Press 'Cancel' to exit this script"
If anyone has any info on how to get around or resolve this issue as I cannot proceed with the stock flash unless the Fastboot connectivity is working, then that would be great
(if it helps I already have Android Studio installed with all its components)
Lucas_Stone said:
So I am currently rooted on a Motorla Nexus 6 in Android 5.1.1, I started up the Nexus Root Toolkit and when it finishes downloading stock Android 60.1 to restore my device ready for Android N it sends the adb reboot bootloader command but my device then says in the bootloader menu "Connect USB Data Cable"
Since I cannot post the image link of what the toolkit says then I will just write it below...
"FASTBOOT device was not found
STEP #1: Connect your device via USB:
- Utilize the OEM USB cable if available
- Try an alternative USB port.
STEP #2: Manually Boot your device into bootloader mode:
- Power your device down completely:
- Press and hold the volume down button, them press and hold the power button t the same time until the phone turns on. You'll see the word 'start' with an arrow around it/
STEP #3: Install drivers:
- Utilize the 'initial setup' if you not done so already.
- USB debugging is NOT required for connectivity in bootloader mode.
- Just follow the the instructions in the guide for configuring your device in bootloader mode.
- For example: if you are using driver solution #3, start on step 7.
Alternatively you may just need to recheck connection.
Press 'OK' to recheck device connectivity.
Press 'Cancel' to exit this script"
If anyone has any info on how to get around or resolve this issue as I cannot proceed with the stock flash unless the Fastboot connectivity is working, then that would be great
(if it helps I already have Android Studio installed with all its components)
Click to expand...
Click to collapse
Make sure you have develops options unlocked and usb debugging enabled.. Then unplug cord and plug it back in.
kwdan said:
Make sure you have develops options unlocked and usb debugging enabled.. Then unplug cord and plug it back in.
Click to expand...
Click to collapse
Got the same error again (I always have USB Debugging on)
Lucas_Stone said:
Got the same error again (I always have USB Debugging on)
Click to expand...
Click to collapse
Try a different port on the computer
kwdan said:
Try a different port on the computer
Click to expand...
Click to collapse
Still the same man, my Laptop has the Google Nexus ADB drivers installed but for some reason the Root Toolkit does not detect Fastboot in my phone
Lucas_Stone said:
Still the same man, my Laptop has the Google Nexus ADB drivers installed but for some reason the Root Toolkit does not detect Fastboot in my phone
Click to expand...
Click to collapse
did you install adb and fastboot onto your computer? it doesnt matter if you have the driver installed if you dont have the actual program installed onto your computer. and anyways, learn to do it right instead of using a toolkit, its very easy.
simms22 said:
did you install adb and fastboot onto your computer? it doesnt matter if you have the driver installed if you dont have the actual program installed onto your computer. and anyways, learn to do it right instead of using a toolkit, its very easy.
Click to expand...
Click to collapse
All sorted now I think lol, I will close this thread when I finish. if it fails horribly then I will let you know (p.s I use the cmd most the time it's just I use the Toolkit to download and install stock)
Lucas_Stone said:
All sorted now I think lol, I will close this thread when I finish. if it fails horribly then I will let you know (p.s I use the cmd most the time it's just I use the Toolkit to download and install stock)
Click to expand...
Click to collapse
please dont close the thread, people always have issues, maybe someone will read this thread and it will help them.
and about toolkits, i dont recommend using them, but feel free to. its just many dont take the time to learn to do it the "right" way. but if you do know it, a toolkit is alright usually.
simms22 said:
please dont close the thread, people always have issues, maybe someone will read this thread and it will help them.
and about toolkits, i dont recommend using them, but feel free to. its just many dont take the time to learn to do it the "right" way. but if you do know it, a toolkit is alright usually.
Click to expand...
Click to collapse
Okay, I will keep it open and also everything is fine now, I am now on Android N preview (had it for 5 mins and I love it)