[Huawei Watch] str8spir:
Hello everybody! :)

I just wanted to post on my experience with Going Back to Stock.

I apologize in advance for information that you already know. I just wanted to relay what I have experienced in the past 7 hours in total of this eventually successful process.

Reason:

My Stock never fiddled with Huawei Watch W1 that just last month went past its two-year warranty started becoming increasingly slow.

So I did what I normally do ever so often: I went into Fastboot via Hardware Button Mode->Stock Recovery->Wipe Cache and for the first time ever, it took well over twenty minutes and it was still going for it.

As a fool, I thought it was just frozen so I forced restarted it.

Surpriseee! Failed to Mount Cache error in a loop and with the watch at 30% battery. I had to shut it down from fastboot menu.

Troubleshooting:

I tried to search for every square inch of information about people in the same situation. I came across very few XDA Threads.

Some explained that they had to OEM Unlock and install TWRP. Here in TWRP they went to the data partition->Repair partition or something similar and then it magically worked.

Yupee

So I tried the same. Unlocked, installed TWRP and tried to repair partition

--->>>Error: Unable to mount \data

--->>>Unable to mount \system etc

Found some other guy on youtube that explained: In this situation, you have to change the storage Format type. Mine was Ext4 and the only one that worked was FAT.

Now it was detecting storage, data, everything....but no more operating system, or data, boot, recovery(TWRP was just booted from fastboot not flashed)

Followed this thread's steps

Tried the first variant: fastboot boot, recovery and then system.

At the system.img it would start with: Invalid sparse file format at header magi

I rebooted and it was going through bootloop. Of course I went into stock recovery and tried wiping cache and factory settings etc. Still bootloop.

Tried 2nd variant.

But since no-one mentioned the exact order for the 2nd variant, or at least I was not able to see someone mention it probably due to the level of desperation I had, I was doing the following:

Boot the 3 images in order and THEEEN push via ADB and use the ADB shell command.

Of course, most of the times it would boot directly to TWRP.

I attempted this process over and over. Formatting the data, erasing the cache, wiping all data, even storage.

At one point, It booted and I was seeing for the first time in 5 hours the

Welcome Message

BUT immediately after:

Error: Google Play Services Framework has stopped Working-OK

Over and over and over. In half a second intervals.

So I tried hitting it from scratch but with a different approach.

-Tried with compiled zip found on this thread.->Bootloop

-Tried with other people's kernels and ROM from other post-neither combination worked

-Tried to find stock image from Google Website-Found ABSOLUTELY NOTHING(it's as if they deleted everything or they just would not allow access anymore to stock images)

Resolution:

Eventually I tried this Thread's procedure the following way:

1.fastboot flash system boot.img

2.fastboot flash system recovery.img

3.fastboot boot TWRP2.8.7.0-Sturgeon.img ->it will boot into TWRP->remove watch from the cradle and put it back.

4.adb push system.img /sdcard/

5.adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system and at this step you need to wait a LOT. It took about 20min.

6. Wipe cache/factory reset

7. reboot

8. Wait to see if it actually works. If it does without errors then do not forget about the last step.

9.Fastboot OEM lock

I apologize for the long post and I hope that, in my disorganized way of writing, I will be able to help others not to go through the same lengthy process that I had to follow.

Thank you all for all the information I was able to gather from you.

Without you guys, I wouldn't have been able to enjoy my smartwatch again.