Can only get to OS via "fastboot continue"

ThongSong7 commented 3 years ago

Not sure if this is normal behaviour, but I flashed my Sturgeon with the nightly images from the webpage via instructions on how to install.

After booting into AsteroidOS and setting it up - all is (seems) well
Reboot via pull down menu and go to strait to bootloop with an error flashing too fast to see, something about cache mount problem?
In order to even have a functional watch, I must reboot to fastboot and issue via computer "fastboot continue"
If my watch is ever out of battery or something else and I do not have a PC with fastboot/ADB with me (and cradle), I will never be able to use this watch.

Kindly advise, as I would like to keep AsteroidOS and because seemingly there is no longer Android Wear available since it boots to a bootloop with error (too fast to read, but something to do with cache).

Surely a guru has seen this type of behaviour and could assist here?

Thanks in advance for all/any help!

ThongSong7 commented 3 years ago

Faute de Frappe...

MagneFire commented 3 years ago

Can you clarify how you solved it?

ThongSong7 commented 3 years ago

I flashed the original image of Android Wear because I could not find a correct way to have this bootable from a shutdown state... also if the instructions are correct then there is not even a way since this is overwriting only the userdata partition and not the boot partition of the watch. So really not solved, but by design?

OliverGeneser commented 3 years ago

@ThongSong7 Do you have a link to the image of Android wear ?

MagneFire commented 3 years ago

I flashed the original image of Android Wear because I could not find a correct way to have this bootable from a shutdown state... also if the instructions are correct then there is not even a way since this is overwriting only the userdata partition and not the boot partition of the watch. So really not solved, but by design?

The watch should definitely be able to boot into AsteroidOS from a shutdown state as demonstrated here:

https://user-images.githubusercontent.com/7857908/127991375-47eab2e6-5f31-4f44-a4f1-f73c67fd317e.mp4

AsteroidOS only uses the boot and userdata partition for this. So that it is only needed to flash the Android Wear boot.img if you want to return to Android Wear.

@ThongSong7 Do you have a link to the image of Android wear ?

Generally, you can use the files from https://forum.xda-developers.com/t/guide-howto-return-to-stock-for-huawei-watch.3219596/ to return to Android Wear. If that still doesn't work, there are also full firmware images available here: https://rootjunkysdl.com/?dir=Huawei%20Watch of which I would recommend the sturgeon-mec23l-wear-stock.zip file.

ThongSong7 commented 3 years ago

@MagneFire : Super and thanks for the information. I will flash again.... not sure what went wrong before.

MagneFire commented 3 years ago

Did some experimenting. I don't know why the recovery is triggered on your watch. But I can recreate the bootloop by simply booting into fastboot menu and then boot into recovery from there. While bootlooping it shows the identical error where it mentions that the cache partition failed to mount. At this point the bootloader will always try to boot to recovery. Even from a shutdown state. So it looks like the recovery is broken for some reason on my watch too.

However, I did find a workaround to this issue: Flash the fastboot image (https://release.asteroidos.org/nightlies/sturgeon/zImage-dtb-sturgeon.fastboot) also on the recovery partition.

Boot into fastboot mode.
Flash recovery using: fastboot flash recovery ~/Downloads/zImage-dtb-sturgeon.fastboot

AsteroidOS / meta-smartwatch

Can only get to OS via "fastboot continue" #28