-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can only get to OS via "fastboot continue" #28
Comments
Faute de Frappe... |
Can you clarify how you solved it? |
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? |
@ThongSong7 Do you have a link to the image of Android wear ? |
The watch should definitely be able to boot into AsteroidOS from a shutdown state as demonstrated here: asteroidos-sturgeon-boot.mp4AsteroidOS 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.
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 |
@MagneFire : Super and thanks for the information. I will flash again.... not sure what went wrong before. |
Did some experimenting. I don't know why the recovery is triggered on your watch. However, I did find a workaround to this issue: Flash the
|
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.
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!
The text was updated successfully, but these errors were encountered: