Develop Bugs

fastboot mode not working

hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers

WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.

Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie

WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/

Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse

[Q] Screen not working - how to relock bootloader and unroot

Hi guys, is there a way to unroot my phone and relock the bootloader without needing to do anything on the phone itself? The screen is broken completely and, though the phone turns on, the screen remains turned off. I do not know if my network provider will fix my phone but I thought it would be worth a shot and I want to cover all the bases before I ask.

Illiok said:
Hi guys, is there a way to unroot my phone and relock the bootloader without needing to do anything on the phone itself? The screen is broken completely and, though the phone turns on, the screen remains turned off. I do not know if my network provider will fix my phone but I thought it would be worth a shot and I want to cover all the bases before I ask.
Click to expand...
Click to collapse
Make sure you have installed Fastboot and ADB drivers..
You only need Fastboot drivers!
Boot Nexus into Fastboot mode!
Open terminal / command prompt =CMD and navigate to folder where is your fastboot files which you need...
Download Stock Google's factory image and extract the files into the fastboot folder and then open flash-all.bat (windows) or flash-all.sh (linux)
Let it finish flashing and let your nexus rest 5 minutes after installation, then pull battery off and put it back and boot into fastboot mode again
Now:
type into CMD or into terminal:
fastboot oem lock
That's it! Easy... and you don't have to see nothin' from Nexus...

Thanks for taking the time to help me out, really appreciate it. If I download mskip's Galaxy Nexus toolkit then will that give me the drivers I need?

Illiok said:
Thanks for taking the time to help me out, really appreciate it. If I download mskip's Galaxy Nexus toolkit then will that give me the drivers I need?
Click to expand...
Click to collapse
You should really drop the toolkit, if you're asking how to relock bootloader and unroot...
Concerning the drivers, there's this really nice package here, there's also instructions for windows 8.
Basically, the steps are those manumanfred told you, although if you're feeling lost, http://forum.xda-developers.com/showthread.php?t=1626895 is the thread you should look up and read several times at least the first post.

Is there a way to get pictures etc off my phone without being able to activate the screen? When I connect my phone to my computer using the USB cable, it shows as a "portable device" as per usual but when I open it up there is no storage icon and no files.
My phone doesn't have a sim in it but it does have a pattern unlock because it has a VPN saved on it. I know the phone works despite the screen being broken because when I boot it up I get a flashing LED and notification sounds for my e-mail.

Did you had USB debugging on and the PC's RSA key added to the device? Then yes, you can 'adb pull /sdcard/', it will give you a full backup of /sdcard/.
a manta wrote this.

The easiest way is to use one of the fine toolkits which will guid you through the whole process:
For Mac: http://forum.xda-developers.com/showthread.php?t=1790399
For Windows: http://forum.xda-developers.com/showthread.php?t=1392310

USB debugging might have been turned off - I can't remember fully. I recently tried to install fresh drivers as per the other poster's suggestions - will that reset the RSA key permission for my PC?
As for the toolkits, I have one but if I remember correctly the toolkit says that some traces of root will be left on the phone which is why I was inquiring about a way to unroot and relock without any traces of root having taken place.

Illiok said:
USB debugging might have been turned off - I can't remember fully. I recently tried to install fresh drivers as per the other poster's suggestions - will that reset the RSA key permission for my PC?
As for the toolkits, I have one but if I remember correctly the toolkit says that some traces of root will be left on the phone which is why I was inquiring about a way to unroot and relock without any traces of root having taken place.
Click to expand...
Click to collapse
As for the RSA key, I don't think changing drivers will matter. Try it. 'adb devices' should return your SN.
As for safely unrooting or whatever, just go back to stock through factory images: they will return your device to full stock, pronto. Use fastboot commands instead of a toolkit.
a maguro wrote this.

I have never done this manually before but in your first post I believe you linked to a guide for me to read so I'm sure I'll find the information I need from that. By the way, is there a way for me to wipe all data stored on my Galaxy Nexus after I have pulled everything from it?

[Q] Can Not get ADB and Fastboot drivers to install

Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm

USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.

beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.

_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959

Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.

Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.

beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.

Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus

W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.

Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.

beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.

_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus

Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.

I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks

[Q] cant enable usb debugging, fastboot doesnt work

I have a Nexus 7 2013 that wont boot. USB Debugging was not enabled. At this point, I am just trying to wipe the machine with a stock image, but I am having trouble.
I have installed the sdk and drivers (so many drivers!)
Recovery mode fastboot does not recognize the device.
ADB recognizes the Nexus, but I cant seem to get it to do anything with it.
e: failed to mount anything.
I have read through so many forum threads that I'm just overwhelmed, and they all seem to require the machine being in USB debugging mode before any changes can be made.
Please help or tell me what pertinent information I have omitted.
Thank you

I think USB debugging only matters in ADB, which is when the device is actually booted into Android OS. You probably want fastboot, which is a different "application" and set of commands in a command prompt.
Code:
fastboot devices
Does that give you anything when the tablet is in fastboot mode? It should list the serial number of the device, similar to "adb devices" does. If not, it could be drivers, or another issue with the device.
Have you tried unlocking the bootloader? This will induce a factory reset of the current firmware version, which may allow you at least boot normally and take any available OTA updates.

Hello,
fastboot devices lists nothing, while adb does show the serial number.
I have used so many tutorials and a couple of toolkits that now I have no idea what is happening with my drivers.
Unlocking the bootloader to force a factory reset sounds amazing, but all the information I can find says I need to have USB debugging enabled to do so. I can not boot into the system to enable it.
Is there a way to force a reset without USB debugging?
Thank you

Usb debugging is irrelevant. Forget about it, it's only used when the system is booted.
You need to get fastboot devices to recognize the tablet.
Uninstall any and all toolkits and drivers. Redownload the sdk. Boot to the bootloader and plug it in, the drivers should install automatically. If not install the google usb drivers from the sdk manager in the sdk.
Try fastboot devices again. If it doesn't work try a different usb cord/port/computer.
You are in the bootloader when running this command right? Not the recovery? I think with the tablet off it's volume down and power. The screen that says start in big green letters at the top and has device info in the bottom left is what you want.
Edit: Did you boot to recovery and select the options to wipe data and cache? Sometimes thats all thats needed.

Also booting to recovery and performing a factory reset may be sufficient.
ADB will indeed function in recovery. I don't think you have to enable USB debugging to get this to work though.

Are you typing fastboot devices while booted in recovery? Typing fastboot devices while in recovery or booted into Android will do nothing.

hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?

helpmynexus said:
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
Click to expand...
Click to collapse
I have the same problem .. Have You reslove it?

bikicviki said:
I have the same problem .. Have You reslove it?
Click to expand...
Click to collapse
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
---------- Post added at 07:12 PM ---------- Previous post was at 06:57 PM ----------
Troops42 said:
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
Click to expand...
Click to collapse
Tried to edit but anyway:
After re..re, rereading your post, and responces. Have you tried the old fashioned way
Hold down the (down volume) button at the same time the (power) key.."Together" If you get anything that pops on your screen let go of the keys, one tap at a time tap the volume up or down key ONLY, until it says (START), its in green type. if you get there you should be ok, to move along

Unlocking Is easy

I have had this watch for about an hour now... ANNNND the bootloader is unlocked...
easy steps below
Note For Clarification: you CANNOT do this over Bluetooth.
Enable ADB and connect to computer.
reboot into fastboot using: adb reboot-bootloader
then issue command: Fastboot Oem Unlock
accept the prompt on the watch.
then reboot the watch...
Piece of cake.
Now... about that boot logo...

Yeah its like a nexus in that regard. And no I don't have the watch yet but have ordered it today.

I would unlock mine but there's no reason to yet. I always unlock my Nexus devices first thing yet with the watch I would like to keep it stock for now.

No reason to unlock, until someone creates twrp, and root.

suzook said:
No reason to unlock, until someone creates twrp, and root.
Click to expand...
Click to collapse
I agree, a factory reset on it only takes 2-3 minutes so its not like a phone where it takes forever to set up again.

ApoKyla said:
I have had this watch for about an hour now... ANNNND the bootloader is unlocked...
easy steps below
Enable ADB and connect to computer.
reboot into fastboot using: adb reboot-bootloader
then issue command: Fastboot Oem Unlock
accept the prompt on the watch.
then reboot the watch...
Piece of cake.
Now... about that boot logo...
Click to expand...
Click to collapse
Hello, may iam to stupid, but i cant force a reboot.
i connect phone via USB to PC, then Bluetooth to the watch, enabled ADB,...and i can see the watch but when i want reboot, only the phone reboots not the watch.
i see this...
C:\ADB>adb devices
List of devices attached
FA2CJW201138 device (PHONE)
localhost:4444 device (WATCH)
regards
UPDATE:
Whit this i can reboot the Watch into FASTBOOT MENU.
C:\ADB>adb -s localhost:4444 reboot-bootloader
but how can i unlock it now?? (after rebooting, there is no connection to the Phone)

Carlossianz0815 said:
Hello, may iam to stupid, but i cant force a reboot.
i connect phone via USB to PC, then Bluetooth to the watch, enabled ADB,...and i can see the watch but when i want reboot, only the phone reboots not the watch.
i see this...
C:\ADB>adb devices
List of devices attached
FA2CJW201138 device (PHONE)
localhost:4444 device (WATCH)
regards
UPDATE:
Whit this i can reboot the Watch into FASTBOOT MENU.
C:\ADB>adb -s localhost:4444 reboot-bootloader
but how can i unlock it now?? (after rebooting, there is no connection to the Phone)
Click to expand...
Click to collapse
Have not done it, but fastboot takes the -s parameter as well. So I would try:
fastboot -s localhost:4444 oem unlock

brizey said:
Have not done it, but fastboot takes the -s parameter as well. So I would try:
fastboot -s localhost:4444 oem unlock
Click to expand...
Click to collapse
Hi,
no, the fastboot command does not work,it stops with the message < waiting for device >

Cannont get USB drivers to work
I tried bith google USB drivers and ClockWorkMod universal ADB drivers and cannot get my Huawei to properly connect. I tried two separate computers with the same result. Each time the USB drivers seem to install but the watch shows up under other with exclamation point. My objective is to side load watch face apks to see what I can accomplish with running this watch under iOS.
ADB debugging is on and I also tried also turning on Bluetooth debugging. Intersetingly Bluetooth debugging does kick in.
I'm a novice at BT debugging and any attempt to communicate with the watch following on-line guidance did not work.
Any suggestions/help would be appreciated.
---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------
I tried both google USB drivers and ClockWorkMod universal ADB drivers and cannot get my Huawei to properly connect. I tried two separate computers with the same result. Each time the USB drivers seem to install but the watch shows up under other with exclamation point. My objective is to side load watch face apks to see what I can accomplish with running this watch under iOS.
ADB debugging is on and I also tried also turning on Bluetooth debugging. Intersetingly Bluetooth debugging does kick in.
I'm a novice at BT debugging and any attempt to communicate with the watch following on-line guidance did not work.
Any suggestions/help would be appreciated.

I still use the old pdanet drivers...they seem to work with everything.

Hi Guys,
still can not work whit the watch after rebooting, may i missunderstand somthing.
Thats the way i do:
From PC to Phone via USB DEBUGING, from PHONE to WATCH via BLUETOOTH DEBUING!
but after reboot into bootloader, i can not talk to the watch anymore, so how can i put the files on the watch???
thanks for help!!!

Carlossianz0815 said:
Hi Guys,
still can not work whit the watch after rebooting, may i missunderstand somthing.
Thats the way i do:
From PC to Phone via USB DEBUGING, from PHONE to WATCH via BLUETOOTH DEBUING!
but after reboot into bootloader, i can not talk to the watch anymore, so how can i put the files on the watch???
thanks for help!!!
Click to expand...
Click to collapse
Enable ADB on the watch (settings/about/tap build# 10 times then developer options, ADB enable)
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
reboot into fastboot using: adb reboot-bootloader
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Sent from my SM-N920T using XDA mobile app

Thanks for replay,
last night i got it, via Bluetooth.
Thanks all, now i have the new kernel and recovery.
I think the new kernel works faster and need less power then the orig one.
best Regards

Thank you !

az93civic said:
Enable ADB on the watch (settings/about/tap build# 10 times then developer options, ADB enable)
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
reboot into fastboot using: adb reboot-bootloader
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Sent from my SM-N920T using XDA mobile app
Click to expand...
Click to collapse
I have the same problem. Once it boots into bootloader on the watch, cmd prompt on the pc becomes unresponsive and i cannot type anything else in. Were you able to fix yours
---------- Post added at 03:27 AM ---------- Previous post was at 03:04 AM ----------
wookie_666 said:
I have the same problem. Once it boots into bootloader on the watch, cmd prompt on the pc becomes unresponsive and i cannot type anything else in. Were you able to fix yours
Click to expand...
Click to collapse
just realised i should probably be using the magnetic charger, because when i reboots it looses bluetooth connection
ill try when i get home

az93civic said:
...
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Click to expand...
Click to collapse
What does "issue command: fastboot oem unlock" mean exactly? There is a little red action name which I can cycle between "Reboot", "Shutdown", "Reboot-bootloader" and "Reboot-recovery", none of which seem remotely correct. I went into "Reboot-recovery" to see whether there was further stuff in there, but nothing seems relevant.

Trejkaz said:
What does "issue command: fastboot oem unlock" mean exactly? There is a little red action name which I can cycle between "Reboot", "Shutdown", "Reboot-bootloader" and "Reboot-recovery", none of which seem remotely correct. I went into "Reboot-recovery" to see whether there was further stuff in there, but nothing seems relevant.
Click to expand...
Click to collapse
So what this means is you need to have ADB and fastboot setup on your computer. From there, you will need to go into developer settings on the watch and enable ADB debugging. Then once you have that enabled, go to where you set up ADB on your computer and type in those commands provided.
P.S. If you're sitting there not sure what ADB means and how to set it up, you NEED to do more research before trying anything like this.

dbroer91884 said:
So what this means is you need to have ADB and fastboot setup on your computer. From there, you will need to go into developer settings on the watch and enable ADB debugging. Then once you have that enabled, go to where you set up ADB on your computer and type in those commands provided.
P.S. If you're sitting there not sure what ADB means and how to set it up, you NEED to do more research before trying anything like this.
Click to expand...
Click to collapse
Actually, it has been a bit of a ride.
I knew of adb already from my watch face development so I had initially wondered whether fastboot was a subcommand of that. I didn't expect it to be another command in the SDK at all for some reason. But yep, it's in the same place as adb, and it works, and now everything flashed fine. I don't know why I didn't search my computer for a file with that name, since that would have located it.
Un-hiding the development options is mentioned on the wear developer site so that was fairly easy to set up. The only hard part was that they gave a text-only explanation, but this watch came set to Chinese, so it was a bit fun to figure out which button to press to "confirm" a dialog. I recognised the first option as the "no" and the second option turns out to have been the "yes", but there are more options below that I still don't know what they are, lol.

suzook said:
No reason to unlock, until someone creates twrp, and root.
Click to expand...
Click to collapse
Custom recovery already available by skin 1980. Take a look here. Custom kernel with custom twrp.
http://forum.xda-developers.com/showthread.php?t=3219596
I was thinking to upload a custom rom for Huawei watch “slim system.img, deodexed, root and more " But I need someone to try it first. I am still waiting for my watch. I will upload if anyone is interested.
Sent from my Nexus 6P using Tapatalk 2

janjan said:
Custom recovery already available by skin 1980. Take a look here. Custom kernel with custom twrp.
http://forum.xda-developers.com/showthread.php?t=3219596
I was thinking to upload a custom rom for Huawei watch “slim system.img, deodexed, root and more " But I need someone to try it first. I am still waiting for my watch. I will upload if anyone is interested.
Sent from my Nexus 6P using Tapatalk 2
Click to expand...
Click to collapse
You are quoting me from 4 mos ago? LMFAO!