##PLEASE NOTE##
These files are from Motorola's Development site and I take no liability with anything that happens with your device if something goes wrong.
DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
Click to expand...
Click to collapse
You're going to need to have the Android SDK installed. You can download it here:
ANDROID SDK - DOWNLOAD
XOOM Firmware Downloads:
[3G|MZ600-HRI66]
[4G|MZ602-HLK75D]
Unzip the files in MZ600_HRI66.zip and move or copy them to the /platform-tools folder in your SDK folder.
Connect your Xoom to your computer. Type:
Code:
adb reboot bootloader
Wait for it to reboot into the bootloader.
Type the following commands, waiting for each to finish before continuing:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device. Type
Code:
fastboot oem lock
wait for the menu
then press the volume-down button.
Then press the volume up button.
It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.
So if you are on Three . One you can use this to revert back to out of the box freshness?
Brenardo said:
So if you are on Three . One you can use this to revert back to out of the box freshness?
Click to expand...
Click to collapse
Yes. That is correct. This will return your XOOM to 100% stock.
word!
I have already been thru the LNX 0x0004 debacle and it was absolutely no fun whatsoever.
well I got a stuck at moto logo for 10 minutes
I am going to try to fastboot oem unlock, reflash images again and fastboot lock to see if I get out of moto logo
second install fix it
jlouang said:
second install fix it
Click to expand...
Click to collapse
So that means that you got it working, correct?
>.>
So the HRI66 is the latest version on the Motorola site? I really need to get a grasp of their version numbers.
EDIT:
Never mind looks like HRI66 is the latest version Thanks anyway.
i was thinking that with the change to the bootloader in the 3.1 update we couldn't use previous versions img's. But I am glad we can return to stock and get this 4G update!
I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?
Dead link...
dchurch85 said:
I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?
Click to expand...
Click to collapse
Did you extract all of the files in the ZIP into the 'tools' folder? The same one that adb is in.
Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version
CakraMas said:
Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version
Click to expand...
Click to collapse
This is what I was afraid of..... try searching the error you are getting. Not many options on how to fix.
i am curious about the LNX 0x0004 error. I know it comes from trying to relock with non-factory img's but what exactly does that mean? I am curious what actually causes the device to soft brick.
Finally I made it, .
I can enter to bootloader by fastboot method, flash the stock image, then relock my device.
Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?
gatorhater73 said:
Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?
Click to expand...
Click to collapse
You can try manually going into fastboot as well... there are two ways to do this:
No matter what, power off the Xoom. Then, 1) Power on the Xoom and as soon as you see it turn on (within a second or two of the power on), press the Volume Down button, which kicks it into Fastboot. 2) If you miss the 1st couple of seconds and press Volume Down after 3-5 seconds, it will say "Android Recovery." You can then press Volume Down until you get to Fastboot, then press Volume Up.
My guess is that you have a different issue, something to do with your Fastboot image. Not sure if booting the Xoom into the OS and connecting with USB Debugging on will work or not to flash the files, perhaps maybe just the boot.img?
I also believe that when the Xoom says "Starting Fastboot protocol support", it is in fastboot mode and you can send the fastboot commands to the Xoom. If your PC does not show the Xoom as a device in your PC's Device manager, then you will probably need to load new/correct drivers onto your PC.
Did you make sure that adb recognized your device? Adb devices in the camaned prompt
Sent from my Xoom using Tapatalk
Oh dear, am a noob, please forgive me!!
I have a Kindle Fire HD 8.9, rooted it OK, then followed "Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial" to install TWRP.
Everything seemed ok, then got stuck on blue/white logo, so got into TWRP hoping somehow I could move a rom on there to flash it. Now I'm in TWRP , the Kindle won't show up on My Computer, so how do I do this? I did try pressing "mount" but nothing happened.
I've searched forums but am just getting more confused!!
Maybe the drivers are wrong, but I don't know how to fix that.
Tried looking at "[HOW-TO] ADB Push a ROM to your phone"http://forum.xda-developers.com/showthread.php?t=1667929, it tells me to find where my ADB is on my PC's hard drive, but I can't find anything that says AndroidSDK on my c:drive.
Oh God!! Am I doomed???
Please can someone kind help me??
Thanks guys
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
http://forum.xda-developers.com/showthread.php?t=2277105
mfg
German JPL
Thank you German JPL,
I did try to follow this trobleshooting bit at the end, but I'm kinda stumped by the fact I don't know where this "ADB binary is (usually inside platform-tools folder in Android SDK directory)"
I'm on Windows 7 and there's no such thing on my c:drive. Under User, there is an ".android" folder, but I don't think that's it.
Hi pixie67,
sorry for my bad english, I'm a German speaking English writer.
in what way do you have adb drivers and fastboot drivers installed?
when did you proceed to the manual, you would still have a folder with android sdk?
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
Click to expand...
Click to collapse
I have windows 7 and when I enter in the search window windows sdk, I find the folder.
mfg
GermanJPL
Hello,
I installed KindleADB.exe for the drivers. That seemed successful. I managed to root it ok,
My Kindle, in TWRP shows up in device manager as Android Phone/Android ADB interface.
I can boot into fastboot from the options in TWRP.
I've updated the android SDK package and rebooted my computer.
I can't use ADB sideload, it just sticks on "starting ADB sideload feature...."
If I reboot to system, I just end up on the white/blue logo.
I don't know what to do next
I do not understand ... have you thought you were the instructions?
you've got installed 2nd Boot Loader & TRWP after manual with ADB and fastboot .... ? why are you not looking adb.exe, then you have your folder
or you install you Andrid sdk subsequently follow the instructions, then you've got everything you need.
German JPL
I don't really understand your answer German, I've followed the instructions, but I'm still stuck on the boot screen, or in TWRP with no way to flash a ROM as there is no ROM on the device and I can't transfer a rom onto the device because mounting doesn't work and Adb sideload doesn't work.
So I'm stuck.
Help!
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
GermanJPL said:
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
Click to expand...
Click to collapse
I can't find a SDK folder anywhere, I've searched, I've enabled hidden folders. I don't know if this is why the ADB sideload option doesn't work, but it doesn't, it just hangs there.
I can start the Kindle in fastboot, there is a message saying "installing device driver software", then another, confirming the ADB driver software has been successfully installed. In device manager I now see
Kindle Fire listed with android adb interface.
I don't know what "play the 3 img a backup folder." means. I'm sorry. While I'm in fastboot mode, I'm not sure what to do. Can you tell me?
And I don't know how to start from scratch as I can't copy anything anywhere. Although I can see the Kindle in device manager, I can't get to it in windows explorer.
The problem is, I didn't copy the ROM and GAPPS onto the Kindle before installing TWRP and now I can't.
Oh dear, I'm sorry to be so frustrating!! Thank you for trying to help though xx
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Click to expand...
Click to collapse
German JPL
Thank you for helping me.
I can't transfer the 2 files as I can't access the sdcard, but I did do this initially.
Also, do I use the command prompt just from the desktop and will it work while I'm in fastboot mode as I can only get into fastboot or recovery. I can't boot normally.
I will give it a go anyway, I really am very grateful for your help
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
HELP
pixie67 said:
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
Click to expand...
Click to collapse
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
OhhRey said:
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
Click to expand...
Click to collapse
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
HELP
stunts513 said:
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
Click to expand...
Click to collapse
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
OhhRey said:
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
Click to expand...
Click to collapse
Do a factory reset from twrp and see if it fixes the problem.
Disregard, issue resolved.
I followed the procedure listed below from the 'Help how root new update 8.5.1' thread page 10 from andraw40 (which worked fine btw) but when I got to step 7, Fastboot doesn't seem to be doing what it is supposed to do which is reboot my device into Fastboot. I shut my tablet down, issue the command and then plugin my device but all it does is just boot up into the OS. What am I doing wrong? The SDK is installed and ADB appears to be working. With the device plugged into my PC, I can issue the command 'adb devices' and it shows a device plugged in. Any help would be greatly appreciated!
andraw40 said:
Guys, first of all THANK YOU for posting and helping other people.
For the last several days I have tried as hell to make my Kindle Fire HD to work like an usual android tablet. It was hell! with blocking the tablet, bricking it, reinstall it, coming back to Amazon version, and all of that for many times. Why? Because of too many version of procedures, because of missing important info from different procedures, because of me doing things wrong, and of course, because of me not reading carefully the procedures. Whatever... Finally I get it. And because it is normal to give back, here I am trying to make easy the path for a next "me".
(This procedure is for Windows Vista or above. On Windows XP there will be a lot of problems with ADB.)
So, what I had: Kindle fire HD, 8.9", version 8.5.1
What I have now: Kindle Fire HD, 8.9" (same ), runing CyanogenMod 11 and all the Google Services
How did I get there:
1. install from Amazon the ES File Explorer
2. make sure you enable ADB in Security, on Kindle
3. connect Kindle on computer and make sure you have installed ADB drivers. Check this in Device Manager. If you have the yellow warning, with the tablet connected, install "Kindle_Fire_HD_ADB_Drivers"
4. download, copy on Kindle (in Downloads) and then install "www apks.org-com zhiqupk root apk" to root the tablet. You need to root it in order to give permission to write in System folder. The aplication is the one mentioned by esema1o in the begining (keymasteroot) - Thank you esema1o! It is in Malaysian and you can use Google translate on computer if you are curious about the labels. It will not help you further but it will satisfy your need to know. So: press Mulai Root - it will do something, then will get a message. Press Root, not Batal. Another "doing something" then a new message. Choose Batal. (search on youtoube for "How to Root an Android Device with Key Root Master"). Done! You have rooted the Kindle. Reboot.
5. Open ES File Explorer and in Tools put all the switches on. Actually you will need only the Root Explorer. If you have problems keeping on the Root explorer reboot, open again ES File Explorer, try again. On the same tablet I had experienced different result after restoring the tablet to original Amazon version. Some time, I let the tablet open, come back after 15-30 minutes and try again to activate Root explorer. Surprise! it worked! Other times worked from first try or at seccond try. It is about your luck! Now, after is staying on, press on Root Explorer. A window will pop-up. Choose there to allow w/r on System folder.
6. Download "KindleFireHD89Root.zip" (you can fiind it by search on this forum by name. I'm not yet allawed to post links so remove the space before here: downloadandroidrom com/file/KindleFire/8.9root/KindleFireHD89Root.zip). Extract. Navigate into "stuff" folder. Shift +right click in window, then choose "Open command window here". (Or you just run cmd and navigate to "stuff" folder.)
7. Check fastboot avability:
Type the following command into the cmd window you had opened before at 6.
fastboot -i 0x1949 getvar product
it should return:
< waiting for device>
Then connect Kindle to computer with a regular usb cable. Power down Kindle. Press power buton to start Kindle. . It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04
Type this to reboot out of fastboot mode:
fastboot -i 0x1949 reboot
8. follow this procedure: wiki cyanogenmod org/w/Install_CM_for_jem (again, remove spaces and add points to have working link)
Note: when you get to the point "Installing CyanogenMod from recovery" you may be confuse about the fact that adb commands are not working. If so, you check not to be in the recovery boot mode. Just shut down Kindle by long pressing power button, or reboot from meniu and if not passing the booting yellow logo, shut it down again by long pressing power button, then go in the fastboot mode again (see the first part of point 7; do not execute reboot! if you did reboot try again to enter in fastboot mode). Now, in fastboot mode, you can follow the instructions to copy zip files on tablet (I used the cyanogenmode 11 and Google apps zip files). After copy them on tablet, go back to the procedure at the point 4 where you start the kindle in recovery mode again by pressing volume up etc. If you do not succeed by pressing volume up during boot, simple enter again in fastboot (you should know how to do it by now ) and from terminal window on computer (cmd window where you are in "stuff" folder) type:
fastboot -i 0x1949 oem recovery
At this point you are back in the procedure at point 6. Do or not the backup and go next. I did not encountered any problems from this point on.
That is all. Sorry for my English, and I hope that my "procedure" will help someone. Again, thank to all the good people that bother to help us!
Click to expand...
Click to collapse
Stock watch, never turned on debugging. Have tried to do the steps in Skin1980 post (return to stock... load boot, recovery and system (got the error on System). Tried the ADB steps (but noob on ADB with no luck). Am I toast? Attached are screen shot showing fastboot recognizes devices. Also here is device screenshot. Any help would be appreciated... Love this watch but for now it's a paperweight.
Also when I try and write .img files (boot, recovery, system) I get the FAILED (remote: device locked).. I am in fast boot screen on watch.
Can u see the device if it is connected n u enter 'adb devices' in the command prompt?
If not then have to confirm does your driver install correctly.
The device must be connected to PC before you can do anything to it. My understanding.
In fastboot screen on your watch doesnt mean it is connected to PC.
You have to unlock bootloader to be able to use fastboot flash.
While in bootloader, use "fastboot oem unlock" command.
Note, that this automatically wipes all user data on the watch.
What is the error you are getting on System?
A lot of people are reporting errors but in reality they are not.
Can you screenshot the error like you did the fastboot command?
Any progress so far???
It has been a while; have you succeeded to recover the Huawei watch pass the Google animation?
I have read no thread who has solved the problem. Any feedback is appriciated.
Update: After so many days I managed to flash... My watch is working again; still no news from Huawei!!!
For newbies like I am, you have to know is you don't need to enable anything before you are stuck to google logos.
I just downloaded "adb-setup-1.4.3" and "Minimal ADB and Fastboot". Whenever the windows didn't recognize the watch I ran adb-setup which at the end asks for installing drivers and when I disconnect and connect the device, it worked.
After getting connected check if the watch is getting fastboot command by c:\fastboot devices. If you can see any letters and fastboot at the right you're ok to go.
You need to c:\Fastboot Oem Unlock which unlocks the watch and you're out of warranty. Just accept it.
Then follow the steps of skin1980 (thanks it was really great)) http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596
If you need "twrp" not written; just "swipe right" and follow the instructions of skin1980.
Boot Stuck Problem is over.
The watch is getting the updates right now but I guess I'll learn more and get to stock by the experts' help...
Thanks to you all...
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
This worked great for me thanks. BUUTTTT, I now have this issue:
error: cannot load 'bootloader-sturgeon-mec23l.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
W/ (58966): Unable to open 'image-sturgeon-mec23l.zip': No such file or directory
error: failed to open zip file 'image-sturgeon-mec23l.zip': I/O Error
STEPHENs-Mac-Pro:~ HomePC$ fastboot devices
FFS7N15B06002296 fastboot
All 3 files are in the PATH sdk/platform-tools folder: bootloader img, flash shell, and image zip.
Can anyone please help me..
I got my Huawei watch today.. And u was doing the flash system and it didn't work so I did a reboot recovery from the watch.. Then it's not working.. After boot loading the Android logo appears for 2 sec then it's blank then the logo.. Etc.
It isn't recognized by my PS so I can't use any command prompt.. What can I do?
Please help